Save changes to dynamic subsystem catalog
Component: | DSSM |
Functional area: | Subsystem management |
Domain: | SYSTEM-MANAGEMENT |
Privileges: | SUBSYSTEM-MANAGEMENT |
Function
This command allows users with the SUBSYSTEM-MANAGEMENT privilege to save changes to the dynamic subsystem catalog in a static subsystem catalog.
Changes made with the ADD-SUBSYSTEM, REMOVE-SUBSYSTEM and MODIFY-SUBSYSTEM-PARAMETER commands as a rule affect only the dynamic subsystem catalog, not the static catalog.
Consequently, any such changes are lost the next time the system is started up unless they are saved in a static catalog with the aid of the SAVE-SUBSYSTEM-CATALOG command. Note, however, that changes which are useful for the current session may be pointless or even counter-productive after the next startup. (For example: a message file is assigned to a subsystem which has BEFORE-DSSM-LOAD as its activation point. If the subsystem is restarted during the current session, this may well be a useful change to make; but it cannot be implemented the next time the system is started up.)
Format
SAVE-SUBSYSTEM-CATALOG |
CATALOG-NAME = *STD / *STARTUP-CATALOG / <filename 1..54 without-gen-vers> ,FORCED = *NO / *YES |
Operands
CATALOG-NAME = *STD / *STARTUP-CATALOG / <filename 1..54 without-gen-vers>
Designates the file in which the dynamic catalog is to be saved.
CATALOG-NAME = *STD
The dynamic catalog is saved under the default file name '$.SYS.SSD.CAT.X'.
CATALOG-NAME = *STARTUP-CATALOG
The dynamic catalog is stored under the name of the catalog used at startup time.
CATALOG-NAME = <filename 1..54 without-gen-vers>
The file named here is used as the static catalog.
FORCED = *NO / *YES
Defines whether, despite errors, the dynamic catalog is saved to the static catalog.
FORCED = *NO
A dynamic catalog which contains errors will not be saved in the static catalog.
FORCED = *YES
The dynamic catalog will be saved in the static catalog even if it contains errors.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | Command successfully executed | |
32 | ESM0288 | DSSM bourse not available | |
32 | ESM0296 | Request for memory space (REQM) not executed | |
32 | ESM0350 | Internal DSSM error; DSSM task restarted | |
32 | ESM0360 | Error due to insufficient memory | |
32 | ESM0409 | DSSM not initialized | |
32 | ESM0643 | Internal error during save operation | |
64 | ESM0648 | Command not executed |
Notes
The dynamic catalog to be saved may be inconsistent for a number of reasons. For example, the catalog required by DSSM may have been saved using the operand FORCED=*YES, in which case there will be inconsistencies between the subsystems. Another possibility is that changes made by means of /MODIFY-SUBSYSTEM-PARAMETER will be unacceptable at the next BS2000 startup, although they will be accepted in the current BS2000 session. Because of the danger of such inconsistencies, the catalog must first be subjected to a variety of checks before it can be saved. Any errors detected in the course of these checks are reported, and a corresponding message is output via SYSOUT.
Even if the dynamic catalog was saved without inconsistencies being detected, it cannot be taken for granted that the next startup carried out with this catalog will be successful. For example, if the start time (CREATION-TIME) of a subsystem has been changed by means of an earlier /MODIFY-SUBSYSTEM-PARAMETER so that it is no longer started automatically during BS2000 system startup, this may lead to serious problems for other subsystems.
If a DMS error relating to the catalog file occurs during saving of the catalog, message ESM1806 is output. The result of the save operation must be checked accordingly. If the same message is output in relation to one of the subsystems involved, it should merely be interpreted as a warning; it has no influence on the result of /SAVE-SUBSYSTEM-CATALOG.
If the specified catalog name is the same as the name of an existing file, a message is displayed inquiring whether the user wishes to overwrite this file.
If certain functions cannot be correctly processed, appropriate messages are output via SYSOUT.
Example
Provided that it contains no errors, the dynamic catalog is to be saved as a static catalog under the file name COPY.DSSMCAT:
/save-subsystem-catalog catalog-name=copy.dssmcat,forced=*no
CHECK REPORT: **** NO ERROR **** CHECK OF LINK REFERENCES: VERSION RANGE CHECK: **** NO ERROR **** LINK RELATION CHECK: **** NO ERROR **** CHECK OF FUNCTIONAL DEPENDENCE: VERSION RANGE CHECK: **** NO ERROR **** DEPENDENCE RELATION CHECK: **** NO ERROR **** CYCLE CHECK: **** NO ERROR **** CHECK OF RELATED FILES: ******************************************************************** * 2 * SUBSYSTEM NAME: ACS VERSION: 20.0 * ******************************************************************** **** NO ERROR **** ******************************************************************** * 3 * SUBSYSTEM NAME: AID VERSION: 03.4 * ******************************************************************** **** NO ERROR **** . . . ******************************************************************** * 40 * SUBSYSTEM NAME: SDF VERSION: 04.8 * ******************************************************************** **** NO ERROR **** . . . % ESM1200 CATALOG ':MAG2:$TSOS.COPY.DSSMCAT' GENERATED % ESM0254 COMMAND 'SAVE-SUBSYSTEM-CATALOG' COMPLETELY PROCESSED