A parameter file consists of parameter records, comment records and control records.
Parameter records are data records that are interpreted by the relevant software component only. The readin routine accepts parameter records without checking them. Comment records always start with an asterisk (*), are ignored by the parameter service and are therefore not logged.
Control records are records that contain statements for the parameter service. They always start with a slash.
BS2000 PARAMS statement
This statement is always the first statement in the parameter file. It is omitted when input is from the console.
BEGIN <keyword> statement
The specified keyword determines to which software component the subsequent parameter records belong. Possible keywords are:
ACCOUNT
DSSM
GTIME
IOCONF
ISAM
JMS
MEMORY
OPR
PAGING
SNAP
SYSOPT-CLASS2
SYSOPT-IPL
The keyword SRPM is processed by the software product SECOS to determine the user ID of the security officer. The corresponding parameter record is described in the “SECOS” manual “Access Control” [46]. The keywords BCAM and VM2000 are explained in the appropriate product manuals.
EOF statement
This statement completes the parameter section for the software component addressed by <keyword>.
ADD statement
A parameter file may also contain the names of additional parameter files to be used. The files specified in the ADD statements are read in as soon as readin of the parameter file containing the ADD statements has been completed.
A maximum of 16 ADD statements may be specified.
An ADD statement must not be followed by any statement apart from another ADD statement or the END-PARAMS statement. No further ADD statements can be specified in a parameter file defined using ADD.
END-PARAMS statement
This statement is the last statement in the parameter file.
The parameter records belonging to a software component need not necessarily be specified in succession. It is quite possible for several BEGIN statements with the same keyword and subsequent parameter records and EOF statements to be contained in the parameter file.
The file SYSPAR.BS2.<ver>.TEMPLATE is supplied as a specimen of the system parameter file. It contains
the statements BEGIN <keyword> and EOF
Specimen defaults for parameters, if no default values are valid without defaults (only affects the parameter record for GTIME)
Explicit statements are only needed for GTIME. The specimen file records the legal time specifications for three time zones known at the time the version is released (Time Zone 0, 1 and 2, including details of the changeover between summer time and winter time). When operating BS2000 in one of these time zones, the specifications for the other time zones can be deleted in each case (when operating in Time Zone 3 the comment characters must be removed).
When operating in a time zone other than the one specified, the specifications must be generated in the same form in accordance with the applicable changeover times by the customer himself.
The default values for the OPR parameter record mean that all console messages that require an explicit routing default are not output at the main console.
The specimen file must be renamed SYSPAR.BS2.<ver> for operation as a system parameter file. It can be expanded with customized defaults.
Example of a parameter file
/BS2000 PARAMS *Accouning system /BEGIN ACCOUNT /START-ACC NAME=$RZ. /EOF *Paging /BEGIN PAGING PAGING VOLUME=(PUBA04,PUBA05) /EOF *Memory management /BEGIN MEMORY SHRSIZE 6,UNIT=1MB ASAMCTRL 4 /EOF *System time and season /BEGIN GTIME ZONE=+01:00 DIFF=1:00 SEASON=S CHDATE=1900-01-01/00:00 CHDATE=2011-03-27/02:00 CHDATE=2011-10-30/03:00 CHDATE=2012-03-25/02:00 CHDATE=2012-10-28/03:00 /EOF *TSN mode /BEGIN JMS TSN-MODE=A /EOF *DSSM /ADD PAR.FILE.DSSM /END-PARAMS
Every parameter file on disk must be a SAM file with variable records and standard blocking. The record length must be 1-72 bytes exclusive of the record length field or 5-76 bytes inclusive of the record length field.
For BLKCTRL=PAMKEY the hexadecimal block length is expected in the first two bytes of a block and the hexadecimal record length (i.e. record format V) in the first two bytes of a record.
In NONKEY mode the block length is taken from the simulated key within the data field (length 4 bytes).
It is possible, for instance, to use EDT to create, update and merge parameter input files.