Selecting the parameter file

Automatic selection of the parameter file

If a system is to be operated on changing Server Units, a different parameter file can be used according to the Server Unit.

This parameter file is selected automatically by BS2000 in FAST and AUTOMATIC startup and in DIALOG startup when selecting the standard parameter file (entry of P.) in the following order:

• In native mode and in the VM2000 monitor system:

  1. The $TSOS.SYSPAR.BS2.<ver>.<name> file (for SUs /390).
     <name> here is the value of the NAME operand from the GEN statement of IOGEN which is entered in the first eight characters of the IOCF comment field of the active IOCF.

  2. The $TSOS.SYSPAR.BS2.<ver>.<system-name> file (for SUs x86).
     <system-name> is the system name that was assigned in the BS2000 configuration (option auto IPL) and can still be changed in the IPL menu (dialog screen of the SE manager or SVP menu of the allocated KVP console).

• In a VM2000 guest system:

  1. The file $TSOS.SYSPAR.BS2.<ver>.<vm-name> (for SU /390 and for SU x86, if the guest system is started with /START-VM).
     <vm-name> here is the VM name of the guest system.

  2. The file $TSOS.SYSPAR.BS2.<ver>.<system-name> (for SU x86, if the guest system is not started with /START-VM).
     <system-name> is the system name that was either assigned 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 started on SU x86 with /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, any FAST or AUTOMATIC startup is interrupted and DIALOG startup is switched to for the time it takes to read in the parameter.

Dialog-controlled selection of the parameter file

In the case of a DIALOG startup, the operator may allocate either a disk or the console as the input source. Allocation takes places when a response is made to message NSI0050 (see section "Input of REP records at the console" in chapter "REP records").

• Parameter records can be read in from more than one file or entered directly at the console.

• If systems support has stored the parameter file on disk, allocation is effected via the relevant file name.

• A response of P.CONS to message NSI0050 switches input to the console. The following message invites the operator to enter the keyword for the subsequent parameter records.

  NSI4120 ENTER PARAM KEYWORD: (<KEYWORD>; ? (DISPLAY LIST OF POSSIBLE
        KEYWORDS); EOT (END))

  The operator has the option of entering “?” in order to view all the possible keywords. The keyword must be entered directly. (BEGIN is generated internally for logging in the CONSLOG file).

  The following message asks for the individual parameter records to be entered:

  NSI4125 ENTER PARAM RECORD FOR KEYWORD (&00); (<PARAM>; /- (IGNORE LAST
        RECORD); EOT (END))

  This message is repeated until EOT is entered. In this case, the EOF statement is generated internally. Message NSI4120 then follows, inviting the operator to enter the next keyword.

  Entering EOT terminates input at the console; an “/END-PARAMS” record is also generated internally

The data records are read in immediately before loading the class 1 exec and prior to reading the class 1 REP records. The parameter and control records are stored in compressed form in a buffer of the startup load module.

All the records processed via the parameter service are written as messages in the CONSLOG logging file.

If readin of the parameter file is abnormally terminated, an error message followed by message NSI008F is output to the console. The operator can then specify whether the records read are to be retained or ignored. Message NSI0050 then appears. In each instance an input device may be specified. This process is repeated until the operator terminates the parameter service with END. If the parameter file contains invalid parameter service statements, these statements are output on the console so that they can be corrected or skipped by the operator immediately.