The generated BS2000 operating system on its own is not a loadable unit. It must be loaded by bootstrapping via other files. The same applies for the dump generator SLED.
The following startup files which are created by SIR are available, anchored in the SVL of the IPL disk:
SYSPRG.BOOT.DSKnnn.SAVE | Save area for IPL |
SYSPRG.IPL.DSKnnn | IPL routine, initialization routine for EXEC, SLED dump routine |
SYSREP.IPL.DSKnnn | Object corrections for IPL(orig. |
SYSPRG.SLED.DSKnnn.SAVE | Save area for SLED |
SYSREP.SLED.DSKnnn | Object corrections (REPs) for SLED (orig. |
SYSDAT.IPL-CONF.DSKnnn | Save area for the startup configurations (created by SIR).Several startup configurations, even from different servers,can be stored in this file. |
At startup, these files are searched for on the disk via address chaining only. Address chaining is performed in the standard volume label (SVL) of the IPL disk by the appropriate SIR run (see the “Utility Routines” manual [1]).
The “nnn” in DSKnnn stands for the nnn-th disk of the pubset. During the SIR run, the SYSPRG/SKMPRG.IPL.<ver>, SYSREP.IPL.<ver> and SYSREP.SLED.<ver> delivery files are copied to the appropriate DSKnnn files.
DSKnnn is replaced by vsn in private disks.
The DSKnnn files must not be copied or relocated (e.g. in the course of reorganization measures), since the only way they can be referenced during startup is via pointers in the SVL. SIR catalogs them at backup level ‘E’ before address chaining is carried out. This excludes them from implicit save operations (e.g. ARCHIVE), but the delivery files are backed up and restored by ARCHIVE. To protect these files against migration by HSMS, they have the file attribute MIGRATE=*FORBIDDEN.
Address chaining (see above) must be carried out to update these files (see above).
If several IPL disks are installed within one pubset in order to increase availability, the file names must be different, regardless of the content of the data objects. SIR guarantees this via the disk-specific file name suffix DSKnnn.
If CREATE-IPL-VOLUME or MODIFY-IPL-VOLUME is specified for a pubset, SIR creates the SYS.NSI.SAVEREP file in order to save system corrections during system initialization.
The table lists the files which should be present on the home pubset under the TSOS ID in addition to the startup files anchored in the SVL.
File name | Utilization |
|---|---|
| Load object SYSSTART |
| Object corrections for SYSSTART |
| Object corrections (REPs) for BS2000 1 |
| Parameter settings 1 |
| Load object “BS2000 CLASS1/2 EXEC” 1 |
1 These file names can be modified via the startup parameter service
Automatic selection of the parameter file by startup
If a system is to be operated on alternating Server Units, a different parameter file can be used depending on the Server Unit involved.
Automatic selection of this parameter file is implemented by BS2000 in FAST and AUTOMATIC startup and in DIALOG startup when the standard parameter file is selected (entry of P.) in the following sequence:
In Native mode and in the VM2000 monitor system:
the
$TSOS.SYSPAR.BS2.<ver>.<name>file (for SU /390).
<name>is the value of theNAMEoperand from the GEN statement of IOGEN which is entered in the first eight characters of the IOCF comment field of the active IOCF (see "GEN - Define program name").the
$TSOS.SYSPAR.BS2.<ver>.<system-name>file (for SU x86).
<system-name>is the system name that was assigned in the BS2000 configuration (option auto IPL). It can still be changed in the IPL menu (dialog screen of the SE manager or SVP menu of the allocated KVP console).
<name>and<system-name>must be different when different parameter values are to be defined for the Server Units.in a VM2000 guest system:
The file
$TSOS.SYSPAR.BS2.<ver>.<vm-name>(for SU /390 and for SU x86, if the guest system is booted via/START-VM).
<vm-name>is the VM name of the guest system.The file
$TSOS.SYSPAR.BS2.<ver>.<system-name>(for SU x86, if the guest system is not booted via/START-VM).
<system-name>is the system name that was assigned either for the persistent VM (option auto IPL) or entered/changed in the IPL menu (dialog screen of the SE manager or SVP menu of the allocated KVP console).
If the guest system is booted on SU x86 using/START-VM, the system name will be matched to the VM name.If no specific parameter file is found, the file with the default name
$TSOS.SYSPAR.BS2.<ver>is searched for.If none of the above-mentioned parameter files is found, a FAST or AUTOMATIC startup is interrupted and DIALOG startup is switched to while the parameter is read in.