Control Data Corporation CYBER 170 Series Operator's Manual page 43

Entry
INITIALIZE,xx,op.
INSTALL=xx.
60435600 L
TABLE 2-3. CMRDECK ENTRIES (Contd)
Function
Blank labels a mass storage device during a level 0 deadstart. This entry is valid only
when entered from the console keyboard. That is, the INITIALIZE entry cannot be
included as part of the CMRDECK on the deadstart file. Before any mass storage
device defined in the CMRDECK (by an EQ entry) can be used, it must have a label
that can be recognized by the system. Existing labels are normally recovered
automatically during all levels of system deadstart. However, should the existing label
be destroyed (for example, during maintenance operations on the device) or a new mass
storage device be added to the system, you enter the INITIALIZE command to create a
new label.
xx One- to two-digit number specified in EQ entry for device (for example,
EQ05 •.• ). This is also the EST ordinal for the device.
op Level of initialization
AL
. PF
QF
DF
AF
EF
FP
MF
Total ini tialize
Permanent files
Queue files
System dayfile
Account dayfile
Error log dayfile
Format pack (844)
Binary maintenance log
Depending upon the levels of initialization selected, all or part of the previously
existing information on the device is lost when the new label is created. Total
initialization or 844 format pack (AL or FP options) destroys all information on a
device. The other options selectively purge information. A separate INITIALIZE entry
is required for each option selected. Selecting FP results in an automatic system
selection of AL. The system deletes all existing information (including the system
deadstart file) from a device initialized with the AL option (you cannot initialize the
device from which you are deadstarting). You should initialize the device if you have
loaded CTI, DDS, or MSL on it.
No options (except AL and FP) are processed until deadstart is completed. At that
time, the K display is requested and you must enter the family name (FM) and device
number (DN) of the device to be initialized. This is a final check to ensure that the
correct device is being ini tialized; the selected options are then processed.
If permanent files are to reside on the device being initialized, the CMRDECK should
contain a PF entry for that device. The PF entry corresponds to the EST ordinal
specified in the EQ entry and indicates that permanent files can reside on the device.
If the CMRDECK displayed contains a PF entry for the device being initialized, a new
PF entry is not required unless the existing entry is to be altered, or the associated EQ
entry is altered. Modification of an existing EQ entry clears all other associated
entries except SYSTEM, LINK, and FAMILY entries (PF, INITIALIZE, and so forth, are
cleared). In addition, if PF entries do not exist in the CMRDECK, initializing the
device causes a default family name and device number to be assigned. Thus, it is
necessary to reestablish the PF entry via the console keyboard if the device is to
remain a permanent file device. For this reason, it is recommended that the PF entry
for all mass storage devices used for permanent files reside in the CMRDECK.
Although this is recommended, it is not required. Refer to the Installation Handbook
for complete information concerning the PF entry to CMRDECK.
If the EQ entry in the CMRDECK displayed indicates that the status of a particular
mass storage device is OFF when the INITIALIZE entry is made, initialize status is
maintained and occurs automatically when the DSD command ON is entered for that
device during normal system operation.
It
should be noted that initialization of mass storage devices can also be accomplished
during normal system operation via the DSD command INITIALIZE (refer to description
of command in section 3).
Specifies the mass storage device on which the system deadstart file is to be installed.
The INSTALL entry must follow the EQ entry for the specified device and the status
must be set to ON. A full INITIALIZE must have been specified for a shared (MMF)
device. The device must be a single-unit device, such as an 844 or 885, and must have
CTI installed. This entry is illegal in the CMRDECK and can be entered only from the
console on a level 0 deadstart. It is recommended that neither the mass storage device
nor any controllers accessing the device be accessible from another mainframe.
2-25
I
I
I