Already at system initialization, it is possible to make various specifications for the message handling system via the parameter service:
In addition to the number of message files that can be processed via the DLAM access method (MSGDLAM) and the language in which messages are to be output by default (MSGLPRI), systems support also determines in the SYSOPT-CLASS2 parameter record the number of system message files and the file names to be defined by the parameter service. The following default settings apply to the system parameters MSGFIL01 and MSGFIL02: MSGFIL01=SYSMES.BS2CP.version or MSGFIL02=SYSMES.EKP.01. These files are created automatically during installation with IMON.
Systems support can specify a further 13 fully qualified message files (MSGFIL03-MSGFIL15).
The rest of the message files can be kept dynamically in an MIP parameter file. In contrast to the specifications in the SYSOPT-CLASS2 parameter record, this parameter file can have message files added or removed. The MIP file is created/managed by systems support with the MODIFY-MIP-PARAMETERS command and is given the name SYSPAR.MIP.<version> by default. It is stored under the TSOS ID and is structured as follows:
MIPPAR=SYSTEM * this must be the first line * * comment lines begin with an "*" * MSGFILE=$.SYSMES.product_1.version MSGFILE=$.SYSMES.product_2.version :
The MIP parameter file can contain any number of declarations. However, since BS2000 can only manage a total of 255 message files, specifications in excess of this are ignored. A corresponding warning is output on the console.
The MIP parameter file can be empty but must always be cataloged at the time of system initialization. (If it is empty, the system asks for a new name. In this case it is advantageous to have an MIP parameter file with “MIPPAR=SYSTEM” in the first line.) A message file inserted with the MODIFY-MIP-PARAMETERS command is written at the beginning of the MIP parameter file, immediately after the opening line and any subsequent comment lines. The MIP parameter file can be read by means of the SHOW-MIP-PARAMETERS command.
The command MODIFY-MSG-FILE-ASSIGNMENT or MODIFY-MIP-PARAMETERS ..., SCOPE=*TEMPORARY can be used to temporarily influence the scope of the message files during the BS2000 session.
Systems support thus has three choices for defining the message files for the BS2000 session:
at startup in the parameter service with the system parameters
during startup but after MIP is loaded, with the MIP parameter file
during the BS2000 session using the MODIFY-MIP-PARAMETERS and MODIFY-MSG-FILE-ASSIGNMENT commands
When the system run ends, all message files are closed.