Dynamic subsystem management is started during BS2000 system initialization.
All the information necessary for DSSM initialization is entered via the parameter service. This information includes the name of the static subsystem catalog and the DSSM version number. If absolutely necessary, logging of DSSM-specific data for error diagnosis may be activated at this point.
All the records processed by means of the parameter service are listed in the form of messages in the CONSLOG logging file.
The keyword for starting up subsystem management is DSSM.
The procedure for starting up DSSM via the parameter service is described in detail in themanual “Introductory Guide to Systems Support” [14] .
In order for DSSM V21.0 to operate, the following files must be stored on the home pubset under the TSOS user ID:
SYSLNK.DSSM.210 SYSNRF.DSSM.210 SYSREP.DSSM.210 SYSSDF.DSSM.210 SYSMES.DSSM.210 | Library with load modules for DSSM Reference file for DSSM REP file processing (NOREF file) REP correction file for DSSM SDF syntax file Message file |
The subsystem catalog which is to be created must likewise be placed on the home pubset and stored under the TSOS user ID. The catalog may be named as desired, and the name can be made known to the system via the parameter service.
The SSCM program is available for generating a subsystem catalog. This program is described in detail in section "SSCM".
Problem handling during a system run
If DSSM cannot be initialized, the reason is displayed in a message (e.g. missing static subsystem catalog) and message ESM0401 is output. The operator can specify a new subsystem catalog during the system run on the operator terminal if it was not defined in the parameter file or the standard catalog (SYS.SSD.CAT.X) is not present.
The system run is generally not continued if mandatory subsystems cannot be started up. The reason for the error during DSSM initialization must first be eliminated and the system run must then be repeated.
If subsystems with the *BEFORE-SYSTEM-READY attribute cannot be started up, DSSM continues the system run.
If one of the following files of a subsystem with the *AT-DSSM-LOAD or *MANDATORY-AT-STARTUP attribute is missing, the operator can specify a new, valid name during the system run:
information file
REP correction file
module library
The system run is stopped if the operator does not input a new file name for the missing REP correction file or the module library.
If the information file is missing, the operator can
input a new, valid file name
ignore the message and continue the system run
ignore the message and stop the system run.
Format of the parameter record for starting up DSSM
Format | Meaning |
SSMCAT=name | Name of the static subsystem catalog |
VERSION=versno | Version number of DSSM |
LOGGING=ON / OFF | Controls DSSM-specific logging for error diagnostics |
REPFILE=<repfile name> | Name of the REP correction file for loading DSSM |
START-SUBSYSTEM commands must be issued in the BS2000 session for any subsystems that are not set up automatically during system initialization.
Excerpt from the parameter file
/BS2000 PARAMS : /BEGIN DSSM SSMCAT=name —————————————————————————————————————————————————————————— (1) VERSION=versno ——————————————————————————————————————————————————————— (2) LOGGING=ON / OFF ————————————————————————————————————————————————————— (3) REPFILE=repfile name—————————————————————————————————————————————————— (4) /EOF : /END-PARAMS
(1) | Control and parameter records must exist in the parameter file only if the system support wishes to set values different from the following default values: for BS2000/OSD-BC V5.0: SSMCAT=$TSOS.SYS.SSD.CAT.X and VERSION=040 for BS2000/OSD-BC V4.0: SSMCAT=$TSOS.SYS.SSD.CAT.X and VERSION=040orSSMCAT=$TSOS.SYS.SSD.CAT.X and VERSION=039orSSMCAT=$TSOS.SYS.SSD.CAT.X and VERSION=038 for BS2000/OSD-BC V3.0: SSMCAT=$TSOS.SYS.SSD.CAT.X and VERSION=040orSSMCAT=$TSOS.SYS.SSD.CAT.X and VERSION=036 |
(2) | The version number refers to all DSSM-specific file names(e.g. SYSLNK.DSSM.040, SYSREP.DSSM.040 in the case of BS2000/OSD-BC V5.0). |
(3) | The statement LOGGING=OFF deactivates logging. With LOGGING=ON a log containing diagnostics data is created during DSSM startup. Logging is not possible if only default values are specified. |
(4) | Name of the desired REP correction file for loading DSSM.If the parameter is not specified, DSSM is loaded with the default name of the REP correction file (SYSREP.DSSM.version). |