Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!floyd!vax135!cornell!uw-beaver!tektronix!hplabs!sri-unix!ALMQUIST@SU-SCORE.ARPA
From: ALMQUIST@SU-SCORE.ARPA
Newsgroups: net.unix
Subject: DECUS session wanted
Message-ID: <302@sri-arpa.UUCP>
Date: Mon, 26-Mar-84 17:07:07 EST
Article-I.D.: sri-arpa.302
Posted: Mon Mar 26 17:07:07 1984
Date-Received: Fri, 30-Mar-84 00:45:32 EST
Lines: 24

From:  Philip Almquist <ALMQUIST@SU-SCORE.ARPA>

	Is there anyone out there who is going to the Cincinnatti
DECUS who would be both willing and able to give a session on VAX
hardware oriented towards systems programmers and system managers?
The purpose of such a session would be to enable people responsible
for the day-to-day operation of VAXen to deal intelligently with
hardware problems.

Examples of things the session might cover are:

 - What do the various kinds of machine checks mean?
 - How does one run basic processor/memory/channel/disk diagnostics?
 - On a not terribly technical level, what are the various major
   components of a VAX and how do they interact with each other?
 - My VAX seems ill.  How do I know if it is the hardware or the
   software which is acting up?
 - What are all the things one sees when one opens up the back of VAX
   cabinet?
 - How does one disable a bad but non-critical piece of the hardware
   (memory boards come to mind, but there may be other possibilities)?

						Philip
-------