 [VAXF84.FERMILAB.STARTUP]   I  This submission includes a few of the procedures used in the VMS startup L  on the on the Fermilab Accelerator Controls VAXen.  Each procedure includes,  comments documenting its usage and actions.  L  The files PUBDSK*.COM and MOUNTDSKS.COM were developed to solve the problemH  of locating and mounting public disks (mounted /SYSTEM) amoung a set ofH  removeable media disk drives (RM03's and RA60's).  The problem was thatM  disk packs could be moved around between shutdown and startup of the system. K  Our configuration includes a spare disk drive to which a pack may be moved L  from a failed drive, we wanted a automatic means of configuring the volumesH  so that no pack was explicitly tied to a drive nor were the acceleratorN  operator's required to perform any special actions to reconfigure (other thanJ  to move the disk pack).  These same procedures can also assist V3 systemsI  with dual HSC's to make the mounting of public user packs independent of M  which HSC is to used (assuming the drives are dual-ported to the two HSC's). J  At Fermilab, if an HSC fails all that is required is to reboot the systemM  and the other HSC will automatically be used.  Of the files mentioned above, N  MOUNTDSKS.COM is specific to Fermilab and only included here is to illustrate   the procedures described above.  N  In a similar vein, the procedures DSKCONFIG.COM and SPAREDISK.COM are used toK  coordinate the usage of a pool of disk drives between multiple processors. K  The configuration in the Fermilab Accelerator Control System includes RM03 I  and RM80 disk drives dual-ported between two 780's.  This past year, two L  HSC50's with several RA81 and RA60 disk drives were added.  The two systemsH  used are the Operational system used to control the accelerator and, onI  the backup VAX, the Development system used to develope the software for G  the control system.  The Operational system uses only removeable-media M  disks for reliability - a pack can be moved from a failed drive to a standby G  and have the control system in operation after 10 minutes or less.  In L  addition, backups of the Operational disks are done pack-to-pack to provideL  an extra level of redundancy.  The Development system uses only fixed-mediaL  drives with backups maintained on tape.  The management problems associated  with configuration were:   A 	1. Coordinating the identity of the standby RM03 and RA60 drives G 	   from the Operational system (given the startup procedures described > 	   in the second paragraph, above) to the Development system.  D 	2. Preventing access by users to the RA60 disk drives in actual use 	   by the Operational system.  M  The DSKCONFIG and SPAREDISK procedures were created to automatically enforce L  this management scheme.  The Operational system sets all fixed-media drivesJ  to /NOAVAILABLE, the Development system does the same for all removeable-N  media drives.  DECnet is then used to communicate the identity of the standbyK  RM03 and RA60 drives from the Operational system to the Development system H  so the Development system may use these drives to access offline media.  H  The procedures described above will be upgraded with VMS V4 and used toN  manage a system consisting of 3 785's configured as a single processor systemN  and a two-processor VAXCluster with both systems accessing logically distinct%  sets of disks connected via HSC50's.   