Instructions for Booting the L1 Trigger Control Computer  D0HTCC
  -------------------------------------------------------------------

                                                           Rev. 11-JAN-1994 


0. These are instructions for booting the L1 Trigger Control Computer (the
   L1  ELN node D0HTCC).
   These are NOT instructions for the L1 VME Transfer Computer (the L1 68k).

1. You should suspect that the TCC has crashed if neither COOR or TrgMon can
   connect to it.

2. If possible (e.g. if a store is not in progress) please try to contact
   Philippe Laurens before booting the TCC.  If it has crashed we would like
   to understand why it crashed before booting it.

3. Except for very unusual circumstances you should be able to boot TCC by
   triggering it over the network.  You can do this with the following command:

     $  MCR NCP Tell D0HSC Trigger Node D0HTCC   <carriage return>

   Note that the account used for typing this command must have OPER in its
        list of default privileges. Or you can specify another account with 
        ... Tell D0HSC"account pwd" Trigger ...

4. You should give TCC about 2 minutes to finish booting and then try
   restarting the TrgMon display.  After TrgMon has successfully connected
   to TCC you should try to reconnect COOR to TCC.

   A convenient way to get COOR to reconnect to TCC is by starting the Test
   Trigger.  However, you will need to define the Test Trigger twice (during 
   the first download COOR will reestablish its link to TCC while loosing the
   first message sent to define the Test Trigger, the second and all subsequent
   downloads will be ok).  You can start the Test Trigger running to verify 
   that events can flow up to L2 OK. 

   If TrgMon is running and COOR has reconnected to TCC then you have
   successfully booted TCC and you should NOT proceed with steps #5 through #9.

5. If in step #4 TrgMon could not reconnect to TCC then TCC is probably so
   hung that the NCP Trigger command in step #3 did not cause TCC to boot
   and it will be necessary to boot TCC manually.

6. TCC and its associated BA23 box are both ON TOP OF rack M114.  Neither of
   these units is inside this rack.  You will need to have a ladder at the
   BACK of M114 to climb up to get at TCC and its BA23 box.  From the back
   of M114 climb up and turn off both TCC and its BA23 box.  Both of these
   units have labels on them near their power switches.  Wait at least 30
   seconds and turn both of them back on.

7. TCC will spend about one minute going through self testing.  You should
   watch the D0HTCC Console (the VT320 terminal hanging from the ceiling in
   front of rack M114) to see that TCC finishes its self testing OK and
   that it eventually makes a  >>>  prompt.   There will typically be a lot
   of other old information displayed on TCC's console so you will need to
   look very carefully to find the  >>>  prompt.

8. Once you have the  >>>  prompt then you need to tell TCC to boot by typing

        B   <carriage return>    on the keyboard of TCC's VT320 console.

   The keyboard for TCC's console is on top of TCC's  BA23 box on top of
   rack M114.   Please be careful to leave this keyboard on top of the BA23
   box where it is out of the way and nothing can accidently touch any of
   the keys.  During normal TCC operation it is important that none of the
   keys are pressed on this keyboard.

9. TCC will finish booting in about 2 minutes and you should then be able
   to reconnect TrgMon and COOR as described in step #4.