FAST startup permits system initialization to be performed without dialog. To this end, the object code corrections (REPs), parameter and programs to be loaded must be stored in files with version-specific standard names. Alternatively, the file names can be stored in the parameter file. The parameter file itself must have the version-specific standard name, with or without a suffix.
The most important events during system initialization are logged on the IPL console. The detailed log - as in DIALOG mode - is written to the CONSLOG logging file.
If the files SYSREP.BS2.<ver>, SYSREP.STRT.<ver>, SYSPAR.BS2.<ver>[.<name>], SYSPRG.STRT.<ver> or SYSPRG.BS2.<ver> are missing and if the parameter file does not specify a REP file or BS2000, the correction data and parameters may optionally be submitted from disk files with any name or via the console in an operator dialog (see chapter "Parameter service" and section "System corrections").
The choice of startup type and the decision as to whether the user catalog is to be reconstructed depends on the values that have already been set for the system parameters STUPTYPE and RECONUC.
For information on selecting the startup type, see also section "Selecting the startup type and catalog reconfiguration".
The following standard file names are valid for dialog-free system initialization and must be cataloged under user ID TSOS on the home pubset:
Filename | Use |
SYSPRG.BOOT.DSKnnn.SAVE | Save area 1 |
SYSPRG.IPL.DSKnnn | Load objects SYSBOOT, SYSIPL and SLED, use at startup 2 |
SYSREP.IPL.DSKnnn | Reps for SYSIPL, use at startup 2 |
SYSDAT.IPL-CONF.DSKnnn | Save area for the function IPL-CONF 1 |
SYSPRG.STRT.<ver> | Load object SYSSTART |
SYSREP.STRT.<ver> | REPs for SYSSTART |
SYSREP.BS2.<ver> | Object code patches (REPs) 3 |
SYS.NSI.SAVEREP | Buffer for REP logging 4 |
SYSPAR.BS2.<ver>[.<name>] | Parameter |
SYSPRG.BS2.<ver> | Load object BS2000-CL1/2 exec 3 |
1 | The file is created by SIR as an empty backup file and is anchored in the SVL. “nnn” in the name part “DSKnnn” is the number of the disk on which the file was created by SIR. These file names are not checked during startup. The files with a disk-specific name are not taken into account in a logical save. |
2 | The file was copied by SIR from a version-dependent original file into this version-independent file (suffix“DSKnnn”), which was then incorporated in the SVL. “nnn” in the name part “DSKnnn” is the number of the disk on which the file was created by SIR. These file names are not checked during startup. |
3 | The file name can be specified via the startup parameter service. |
4 | The file is created by SIR as an empty backup file. If this file is missing or if it is too small, this has repercussions on the “secure system startup”. |
If one of the files is missing or cannot be used, the file name is requested via the console (not in the case of anchored files).
The disk-specific naming of the anchored files, i.e. those stored in the SVL, means that several IPL disks of a BS2000 version can be created in parallel in a pubset.