Save subsystem catalog as PAM file
Function
With the aid of this statement, a subsystem catalog created in memory by means of statements entered earlier can be saved as a PAM file.
The file name is either derived from the last START-CATALOG-CREATION statement or from the START-CATALOG-MODIFICATION statement , or a new file name can be specified in fully qualified form.
SAVE-CATALOG will be rejected with an error message:
if neither of the statements START-CATALOG-CREATION or START-CATALOG-MODIFICATION has been executed beforehand
if the catalog created in memory contains no definitions, i.e. is empty
if the catalog already contains a file with the name (other than *CURRENT) specified in CATALOG-NAME and REPLACE-OLD-FILE=*NO was specified.
Note that this statement must be preceded by a check run for the catalog. This check run can be initiated by a CHECK-CATALOG statement .
Format
SAVE-CATALOG | |||||||||
| |||||||||
Operands
CATALOG-NAME =
File name under which the catalog is to be saved.
CATALOG-NAME = *CURRENT
The catalog will be saved under the file name specified in the last START-CATALOG-CREATION or START-CATALOG-MODIFICATION statement.
CATALOG-NAME = <filename 1..51 without-gen-vers>
Fully qualified file name under which the catalog is to be saved.
REPLACE-OLD-FILE= *NO / *YES
Specifies whether an existing, cataloged file with the name specified in CATALOG-NAME may be overwritten (*YES) or not (*NO).
FORCED =
Determines how SSCM is to behave if there are errors in the subsystem definition.
FORCED = *NO
Default value: in the case of errors which SSCM recognizes during the analysis of the subsystem definition, the catalog is not to be saved in a PAM file.
Errors may arise in the definitions of subsystems due to a set of relations (address, dependency or external reference relations) which contains loops. Such a loop results if a relation (“ --> ”) is defined which, after a number of steps, refers back to itself:
Subsystem A --> Subsystem B
Subsystem B --> Subsystem C
Subsystem C --> Subsystem A
FORCED = *YES
In spite of any errors which SSCM may identify during the analysis of the subsystem definitions, the catalog is to be saved in a PAM file.
Responsibility for a catalog saved in this way lies with the user; the behavior of DSSM cannot be guaranteed.
FORCED = *FOR-ADD-SUBSYSTEM
The specified catalog will be saved even if the following errors arise:
a subsystem includes dependency relations to undefined subsystems or
a subsystem is to share a holder task with an undefined subsystem.
Use of this operand is a good idea when a catalog is to be created that contains nothing but new subsystems, which may, however, have relations to other subsystems defined in the old catalog. This new catalog is added to the existing old catalog by means of the command ADD-SUBSYSTEM ...,TYPE=*NEW-SUBSYSTEMS.