Add subsystem definition(s) to subsystem catalog
Function
This statement copies the definition of new subsystems, which are held in an SSD object, into the subsystem catalog which is currently open.
This statement will be rejected if the catalog into which the definitions are to be integrated is not currently open as a result of a START-CATALOG-CREATION or START-CATALOG-MODIFICATION statement. Any definition for a subsystem which is already contained in the open catalog will be ignored; processing will continue, however, after output of a corresponding message.
Format
ADD-CATALOG-ENTRY |
FROM-FILE = <filename 1..54> ,INSTALLATION-USERID = *UNCHANGED / *DEFAULT-USERID / <name 1..8> ,CORRECTION-STATE = *UNCHANGED / <c-string 3..3> / <text 3..3> |
Operands
FROM-FILE = <filename 1..54>
Name of the file in which to search for the subsystem definition(s). This file must be an SSD object generated by SSCM of type ISAM, in which the attributes of one or more subsystems are stored.
INSTALLATION-USERID =
Specifies a user ID under which the subsystem satellites (REP file, object module library, message file, syntax file and subsystem information file) are expected, in cases where these files have not already been assigned to a user ID.
INSTALLATION-USERID = *UNCHANGED
Default value: the files are expected under the user ID specified in the subsystem definition (SET-SUBSYSTEM-ATTRIBUTES statement).
INSTALLATION-USERID = *DEFAULT-USERID
The files are expected under the system’s default user ID (prefix “$.”).
INSTALLATION-USERID = <name 1..8>
User ID under which the files are expected. If a different ID was specified in the SET-SUBSYSTEM-ATTRIBUTES statement for an SSD object, it will be overwritten.
CORRECTION-STATE =
Replaces in the catalog the last three characters of the subsystem version from the SSD file; these characters indicate the release and correction states of the subsystem version. If the subsystem version in the SSD file consists of four characters, the three characters specified for CORRECTION-STATE are chained with them.
CORRECTION-STATE = *UNCHANGED
Default value: the release and correction states remain unchanged.
CORRECTION-STATE = <text 3..3>
Specifies the release and correction states in the format: ann, in which the text elements have the following meanings:
a: Release state; alphabetic character
nn: Correction state; numeric characters
CORRECTION-STATE = <c-string 3..3>
Specifies the release and correction states as a character string in the format: ann;for the meanings of the text elements, see CORRECTION-STATE=<text 3..3>.
Notes
If a subsystem definition contains file names without a user ID and if no installation ID is specified, the relevant DSSM task searches for the files under the user ID TSOS or, in the case of a local subsystem, under the user ID of the calling task.
If the files are stored under a different user ID, this ID must be specified in the INSTALLATION-USERID operand of one of the commands ADD-CATALOG-ENTRY, SET-SUBSYSTEM-ATTRIBUTES or MODIFY-SUBSYSTEM-ATTRIBUTES.If an SSD object containing multiple subsystem definitions is specified in the FROM-FILE operand, the release and correction states of all the subsystems defined in this SSD object will be affected by the value of the CORRECTION-STATE and INSTALLATION-USERID operands.
The file names of a subsystem are not changed if the release and correction states are specified. Users wishing to change these names must use the MODIFY-SUBSYSTEM-ATTRIBUTES statement to do so.
If the CORRECTION-STATE operand is specified, a version check for mutually dependent subsystems or for subsystems which have address relations with one another may result in a CHECK-CATALOG error. This can be avoided by specifying suitable entries in MODIFY-SUBSYSTEM-ATTRIBUTES MODIFY-REFER-SUBS=..., MODIFY-RELATED-SUBS=....