Procedure to Follow When Frankenheim Has a Problem

When there are problems with Frankenheim, do the following to help Bill
diagnose the problem so he can determine if the problem is hardware or 
software.

Make a note of the contents of the Frankenheim monitor.  What windows 
are there?  Is part of the screen black?  If the computer is logged in
as OBS and the screen has no black, will it open a window (such as the Greg or
Chef window) where there's a command prompt?  If so, type SHOW ERROR and
record the results.  Also type SHOW SYSTEM and either record the results or
call Bill and read them to him. 

If the login screen is there, can you log in as OBS?  (If so, skip the 
following and call Bill.)

If the screen is partially black, there's probably a >>> prompt in there
somewhere.  Press <Return> a few times to find it and scroll off enough
of the screen to get the prompt on a blank line.  Then type SHOW DEVICE
and record the results.  Next, type B to boot the machine.  (This should 
clear the screen and print DKA0 in the upper left corner.  After a minute
or less you should see some output from the Boot Script.)

If the screen was NOT partially black, but the computer is unresponsive,
force a crash dump, using the following procedure from Compaq/Digital:


 1.  (Not Applicapable)

 2.  Stop the system by pressing the HALT button (recessed in the center hole 
     of those on the right side of the Pizza Box near the back).  This should
     produce a >>> prompt.  Strike <Return> if necessary to scroll the screen
     to where the prompt is on a blank line.

 3.  Examine and record the processor registers by entering the following
     commands: 

          >>> E/I 0               ! Examine Stack Pointers - Kernel
          >>> E +                 !                        - Exec
          >>> E +                 !                        - Super
          >>> E +                 !                        - User
          >>> E +                 !                        - Interrupt
          >>> E/G/N:F R0          ! Get contents of R0-R15

 4.  Examine and record the PC (Program Counter) and PSL (Processor
     status Longword) and place the system back in its original hang
     condition:

          >>> E/G F               ! Get the PC
          >>> E PSL               ! Examine PSL to determine IPL level
          >>> C                   ! Continues the hang condition

 5.  Repeat steps 1, 2, and 4 for at least 5 iterations, omitting
     the ">>> C" (Continue) command in the 5th iteration.  (N.B., you
     can skip step 3 in these iterations.)

     Note:
       Since Frankenheim is a member of a VMScluster, a CLUEXIT bugcheck
       may occur during this step.  Do not become concerned, this
       is expected.  Simply let the system continue to write to the
       dumpfile.  If not, proceed with step 6.

 6.  Deposit an invalid value in the PC and direct the system to
     begin execution on the interrupt stack at the highest IPL
     (Interrupt Priority Level), 31:

          >>> D PC FFFFFFFF       ! Invalid value in the PC
          >>> D PSL 041F0000      ! Interrupt stack, IPL 31
          >>> C                   ! Force an INVEXCEPTN Bugcheck

     This step will cause the contents of memory to be written to
     the dumpfile followed by an automatic system reboot.  If the
     system does not automatically reboot, you must boot it manually.
     See the "Installation and Operations Guide" for instructions.