Modify subsystem parameters
Component: | DSSM |
Functional area: | Subsystem management |
Domain: | SYSTEM-MANAGEMENT |
Privileges: | SUBSYSTEM-MANAGEMENT |
Function
A user with the SUBSYSTEM-MANAGEMENT privilege can run this command to modify the parameters governing a subsystem; only the parameters explicitly specified are changed.
The command modifies only the dynamic subsystem catalog, not the static catalog. Consequently, any changes that are made do not remain in effect at the next startup. To prevent the changes being lost, the SAVE-SUBSYSTEM-CATALOG command can be used to store them in a static catalog. 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.)
The command has three different types of operand:
operands which have their value stored in the dynamic subsystem catalog and take immediate effect (such as VERSION-COEXISTENCE).
operands which have their value stored in the dynamic subsystem catalog but do not take effect until the next START-SUBSYSTEM command (such as LIBRARY).
operands which are accepted only if the subsystem is not currently running (such as MESSAGE-FILE).
For further information see the “Subsystem Management” manual [49].
Format
MODIFY-SUBSYSTEM-PARAMETER | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
SUBSYSTEM-NAME = <structured-name 1..8>
Specifies the name of the subsystem for which the parameters are to be changed.
VERSION = <product-version mandatory-man-corr> / <product-version without-man-corr>
Identifies the version number.
If a version number is specified, the format specified here must be identical to the format used when the subsystem was defined (release and correction status mandatory or not allowed; cf. SDF metasyntax).
INSTALLATION-UNIT =
Defines a name for the installed release unit. A value other than *NONE must be specified for all subsystems installed using IMON if *INSTALLED(LOGICAL-ID=...) is the value specified for any of the following operands: SUBSYSTEM-LIBRARY, REP-FILE, SUBSYSTEM-INFO-FILE, MESSAGE-FILE or SYNTAX-FILE.
INSTALLATION-UNIT = *UNCHANGED
The name of the installed release unit remains unchanged.
INSTALLATION-UNIT = *NONE
No name is allocated. This value is not allowed for any subsystem installed using IMON.
INSTALLATION-UNIT = *STD
The name specified in the SUBSYSTEM-NAME operand is used as the name of the installed release unit.
INSTALLATION-UNIT = <text 1..30>
New name for the installed release unit.
INSTALLATION-USERID = *UNCHANGED / *NONE / <name 1..8> / *DEFAULT-USERID
Changes the default user ID of the files associated with the subsystem (REP-FILE, SUBSYSTEM-LIBRARY, SYNTAX-FILE and MESSAGE-FILE, SUBSYSTEM-INFO-FILE operands). File names specified without a user ID are assumed to belong to the new installation user ID defined here.
A change to the installation user ID is rejected if the subsystem is active and there is a message file (MESSAGE-FILE operand) or a syntax file (SYNTAX-FILE operand) assigned to it with no user ID specified.
The change takes effect immediately.
INSTALLATION-USERID = *UNCHANGED
The installation user ID is not changed.
INSTALLATION-USERID = *NONE
Removes the installation user ID.
If an installation user ID existed before the command was issued, it is stripped from all files to which it was assigned.
INSTALLATION-USERID = <name 1..8>
The user ID given here will be the new installation user ID. The name of the user ID must be given without its dollar sign prefix '$'.
INSTALLATION-USERID = *DEFAULT-USERID
Selects the system default user ID as the installation user ID (which means that file names begin with '$.').
COPYRIGHT = *UNCHANGED / *NONE / <c-string 1..54>(...)
Changes the copyright notice displayed when the subsystem is loaded.
The change takes effect as soon as the subsystem is restarted (START-SUBSYSTEM command).
COPYRIGHT = *UNCHANGED
The copyright notice is not changed.
COPYRIGHT = *NONE
No copyright notice is displayed.
COPYRIGHT = <c-string 1..54>(...)
Changes the copyright notice displayed when the subsystem is loaded.
YEAR = *YEAR-1990 / <c-string 4..4>
Defines the year displayed as the first production year in the copyright notice. The default year is 1990. Any other year must be specified explicitly. Note that the operand value is not subjected to semantic validity checking.
SUBSYSTEM-LIBRARY = *UNCHANGED / *STD / *INSTALLED(...) /<filename 1..54 without-gen-vers>
Changes the module library assignment for the specified subsystem (LIBRARY parameter). The module library supplies the code which is loaded for a subsystem which is not yet running.
The change takes effect as soon as the subsystem is restarted (START-SUBSYSTEM command).
SUBSYSTEM-LIBRARY = *UNCHANGED
The setting is left unchanged.
SUBSYSTEM-LIBRARY = *STD
Assigns the following default library name:
SYSLNK.<subsysname>.<subsysvers#>
The value of “subsysvers#” comprises three digits, which are the “mmn” elements specified in the SUBSYSTEM-NAME=...(VERSION=...) operand.
SUBSYSTEM-LIBRARY = *INSTALLED(...)
The library name is determined by the invocation of IMON-GPN (the installation path manager).
LOGICAL-ID =
Defines the logical program or object module library name by which the library is known to IMON-GPN.
LOGICAL-ID = *UNCHANGED
The logical name of the program or object module library is left unchanged.
LOGICAL-ID = *REFRESH
The path name associated with the logical name has been changed and is now to be updated in the catalog. The logical name itself is left unchanged.
LOGICAL-ID = <filename 1..30 without-catid-userid-gen-vers>
New logical name for the program or object module library.
DEFAULT-NAME =
Name of the library if IMON-GPN is not available or if the logical ID is unknown.
DEFAULT-NAME = *UNCHANGED
The library name is left unchanged.
DEFAULT-NAME = <filename 1..54>
New library name.
SUBSYSTEM-LIBRARY = <filename 1..54 without-gen-vers>
The fully qualified file name specified here is defined as the new library name (see Note 3).
SUBSYSTEM-LOAD-MODE = *UNCHANGED / *STD / *ADVANCED
Defines how the subsystem is loaded.
SUBSYSTEM-LOAD-MODE = *UNCHANGED
The subsystem loading mode is left unchanged.
SUBSYSTEM-LOAD-MODE = *STD
BLS is invoked in STD run mode (via the BLS-DSSM interface $PBBND1) to load the subsystem code as an object module.
SUBSYSTEM-LOAD-MODE = *ADVANCED
BLS is invoked in ADVANCED run mode (via the BLS-DSSM interface $PBBND1) to load the subsystem code as a link-and-load module.
REP-FILE = *UNCHANGED / *STD / *NO / *INSTALLED(...) /<filename 1..54 without-gen-vers>
Changes the REP patch file assignment for the specified subsystem version. REP patch files are designed to incorporate module updates in a subsystem which is not currently running.
The change takes effect as soon as the subsystem is restarted (START-SUBSYSTEM command).
REP-FILE = *UNCHANGED
The REP patch file parameters are not changed.
REP-FILE = *STD
Assigns the following default name for the REP patch file:
SYSREP.<subsysname>.<subsysvers#>
The value of “subsysvers#” comprises three digits, which are the “mmn” elements specified in the SUBSYSTEM-NAME=...(VERSION=...) operand.
REP-FILE = *NO
There is no REP patch file for the subsystem.
REP-FILE = *INSTALLED(...)
The name of the REP file is determined by the invocation of IMON-GPN (the installation path manager).
LOGICAL-ID =
Defines the logical REP file name by which the file is known to IMON-GPN.
LOGICAL-ID = *UNCHANGED
The logical name of the REP file is left unchanged.
LOGICAL-ID = *REFRESH
The path name associated with the logical name has been changed and is now to be updated in the catalog. The logical name itself is left unchanged.
LOGICAL-ID = <filename 1..30 without-catid-userid-gen-vers>
New logical name for the REP file.
DEFAULT-NAME =
Name of the REP file if IMON-GPN is not available or if the logical ID is unknown.
DEFAULT-NAME = *UNCHANGED
The REP file name is left unchanged.
DEFAULT-NAME = *NONE
No default name is assigned to the REP file.
DEFAULT-NAME = <filename 1..54>
New name for the REP file.
REP-FILE = <filename 1..54 without-gen-vers>
The fully qualified file name specified here is defined as the new REP patch file name (see Note 3).
REP-FILE-MANDATORY = *UNCHANGED / *NO / *YES
Defines whether the subsystem is started if errors occur while the REP patch file is being processed.
The change takes effect as soon as the subsystem is restarted (START-SUBSYSTEM command).
REP-FILE-MANDATORY = *UNCHANGED
The current setting is left unchanged.
REP-FILE-MANDATORY = *NO
Errors during processing of the REP patch file have no effect on subsystem loading.
REP-FILE-MANDATORY = *YES
Dynamic subsystem management (DSSM) inhibits subsystem loading in the following cases:
DMS errors during REP patch file processing
(e.g. REP file not cataloged)errors during REP file validation
REP file incorrectly named
DMS errors during NOREF file processing
MESSAGE-FILE = *UNCHANGED / *NO / *INSTALLED / <filename 1..54 without-gen-vers>
Changes the message file definition associated with the specified subsystem version. The subsystem version must not be running at the time.
DMS file naming requirements are not checked.
MESSAGE-FILE = *UNCHANGED
The current setting is left unchanged.
MESSAGE-FILE = *NO
No subsystem-specific message file is available.
This setting is needed for cases where BEFORE-DSSM-LOAD is defined as the activation point for the subsystem.
MESSAGE-FILE = *INSTALLED(...)
The name of the message file is determined by the invocation of IMON-GPN (the installation path manager).
LOGICAL-ID =
Defines the logical message file name by which the file is known to IMON-GPN.
LOGICAL-ID = *UNCHANGED
The logical name of the message file is left unchanged.
LOGICAL-ID = *REFRESH
The path name associated with the logical name has been changed and is now to be updated in the catalog. The logical name itself is left unchanged.
LOGICAL-ID = <filename 1..30 without-catid-userid-gen-vers>
New logical name for the message file.
DEFAULT-NAME =
Name of the message file if IMON-GPN is not available or if the logical ID is unknown.
DEFAULT-NAME = *UNCHANGED
The message file name is left unchanged.
DEFAULT-NAME = *NONE
No default name is assigned to the message file.
DEFAULT-NAME = <filename 1..54>
New name for the message file.
MESSAGE-FILE = <filename 1..54 without-gen-vers>
The fully qualified file name specified here is defined as the new message file name (see Note 3).
SUBSYSTEM-INFO-FILE = *UNCHANGED / *NO / *INSTALLED(...) / <filename 1..54 without-gen-vers>
Specifies which information file to use for the specified subsystem version.
SUBSYSTEM-INFO-FILE = *UNCHANGED
The current setting is left unchanged.
SUBSYSTEM-INFO-FILE = *NO
No information file is available.
SUBSYSTEM-INFO-FILE = *INSTALLED(...)
The information file name is determined by the invocation of IMON-GPN (the installation path manager).
LOGICAL-ID =
Defines the logical information file name by which the file is known to IMON-GPN.
LOGICAL-ID = *UNCHANGED
The logical name of the information file is left unchanged.
LOGICAL-ID = *REFRESH
The path name associated with the logical name has been changed and is now to be updated in the catalog. The logical name itself is left unchanged.
LOGICAL-ID = <filename 1..30 without-catid-userid-gen-vers>
New logical name for the information file.
DEFAULT-NAME =
Name of the information file if IMON-GPN is not available or if the logical ID is unknown.
DEFAULT-NAME = *UNCHANGED
The name of the information file is left unchanged.
DEFAULT-NAME = *NONE
No default name is assigned to the information file.
DEFAULT-NAME = <filename 1..54>
New name for the information file.
SUBSYSTEM-INFO-FILE = <filename 1..54 without-gen-vers>
The fully qualified file name specified here is defined as the new information file name (see Note 3).
SYNTAX-FILE = *UNCHANGED / *NO / *INSTALLED(...) / <filename 1..54 without-gen-vers>
Changes the syntax file definition associated with the specified subsystem version.
The syntax file contains the applicable command and operand values for the subsystem version.
The subsystem version must not be running when the command is issued.
DMS file naming requirements are not checked.
SYNTAX-FILE = *UNCHANGED
The current setting is left unchanged.
SYNTAX-FILE = *NO
No information file is available.
This setting is needed for cases where BEFORE-DSSM-LOAD or AT-DSSM-LOAD is defined as the activation point for the subsystem.
SYNTAX-FILE = *INSTALLED(...)
The name of the syntax file is determined by the invocation of IMON-GPN (the installation path manager).
LOGICAL-ID =
Defines the logical syntax file name by which the file is known to IMON-GPN.
LOGICAL-ID = *UNCHANGED
The logical name of the syntax file is left unchanged.
LOGICAL-ID = *REFRESH
The path name associated with the logical name has been changed and is now to be updated in the catalog. The logical name itself is left unchanged.
LOGICAL-ID = <filename 1..30 without-catid-userid-gen-vers>
New logical name for the syntax file.
DEFAULT-NAME =
Name of the syntax file if IMON-GPN is not available or if the logical ID is unknown.
DEFAULT-NAME = *UNCHANGED
The syntax file name is left unchanged.
DEFAULT-NAME = *NONE
No default name is assigned to the syntax file.
DEFAULT-NAME = <filename 1..54>
New name for the syntax file.
SYNTAX-FILE = <filename 1..54 without-gen-vers>
The fully qualified file name specified here is defined as the new syntax file name (see Note 3).
DYNAMIC-CHECK-ENTRY = *UNCHANGED / *STD / *NO / <text 1..8 without-sep>
Changes the reference address used to check that the loaded encoding for the subsystem is correct.
DYNAMIC-CHECK-ENTRY = *UNCHANGED
The current setting is left unchanged.
DYNAMIC-CHECK-ENTRY = *STD
The reference address specified in the LINK-ENTRY operand is used as the reference address for dynamic checking.
DYNAMIC-CHECK-ENTRY = *NO
No checking is performed. This setting is not allowed if the activation point defined for the subsystem is BEFORE-DSSM-LOAD.
DYNAMIC-CHECK-ENTRY = <text 1..8 without-sep>
The address specified here is defined as the new reference address for dynamic checking.
CREATION-TIME = *UNCHANGED / *AT-CREATION-REQUEST / *AT-SUBSYSTEM-CALL / *AT-DSSM-LOAD / *MANDATORY-AT-STARTUP / *BEFORE-SYSTEM-READY / *AFTER-SYSTEM-READY
Changes the subsystem startup time.
CREATION-TIME = *UNCHANGED
The current setting is left unchanged.
CREATION-TIME = *AT-CREATION-REQUEST
The subsystem startup time is reset to the (generation) default setting of “Startup on START-SUBSYSTEM invocation”.
CREATION-TIME = *AT-SUBSYSTEM-CALL(...)
The subsystem startup time is changed to the value AT-SUBSYSTEM-CALL. That means that the subsystem starts up automatically in response to the first SVC or ISL call.
This operand value is available only for subsystems called by the SVC or ISL mechanism.
This operand value can be assigned to the specified subsystem version after it has been withdrawn, if necessary, from another subsystem version. If no other version has this attribute, it is directly transferred to the specified subsystem version. If some other subsystem version has this attribute, it is withdrawn from that subsystem, either immediately (if the subsystem is not running) or after the subsystem has closed down (if it is currently running).
Subsystems with the attribute VERSION-COEXISTENCE=*ALLOWED are an exception to this rule. Here, different versions of the same subsystem can have the attribute CREATION-TIME=*AT-SUBSYSTEM-CALL at the same time.
As with SSCM, this attribute can only be allocated to a subsystem where the CALL entry is set to MODE=*SVC/*ISL.
ON-ACTION =
Determines what causes automatic loading of the subsystem.
ON-ACTION = *STD
Default: loading begins when any SVC entry point belonging to the subsystem is called.
ON-ACTION = *ISL-CALL
Loading begins when any ISL entry point belonging to the subsystem is called.
ON-ACTION = *ANY
Loading begins when any SVC or ISL entry point belonging to the subsystem is called.
CREATION-TIME = *AT-DSSM-LOAD
The subsystem is to be loaded under the control of the DSSM task during system initialization. It must be a privileged subsystem, and any address and dependency relations it has must be with subsystems which also have this startup attribute or the BEFORE-DSSM-STARTUP attribute.
The file name for this subsystem must be located on the home pubset under the TSOS user ID, as at startup time the user catalog is not accessible and IMPORT-PUBSET processing has not been completed.
These subsystems are not allowed to have a syntax file attached.
CREATION-TIME = *MANDATORY-AT-STARTUP
The subsystem must be loaded during system initialization (Phase 2: after DSSM has been loaded). As with BEFORE-SYSTEM-READY, subsystem activation is initiated synchronously; but in this case, as opposed to BEFORE-SYSTEM-READY, loading of the subsystem must be completed successfully. Otherwise, the startup routine is sent a message indicating that a mandatory subsystem could not be loaded. The startup routine then decides whether to continue or abort processing.
The subsystem must be a privileged subsystem, and any address and dependency relations it has must be with subsystems which have the same startup attribute or either BEFORE-DSSM-STARTUP or AT-DSSM-LOAD. The file name for this subsystem must be cataloged on the home pubset.
CREATION-TIME = *BEFORE-SYSTEM-READY
The subsystem is to be loaded during system initialization (Phase 2). Activation is initiated synchronously; control is not returned to the startup routine until after completion of loading (or a loading error). Once the startup routine has regained control, it can report SYSTEM READY.
The subsystem must be a privileged subsystem, and any address and dependency relations it has must be with subsystems which have the same startup attribute or one of BEFORE-DSSM-STARTUP, AT-DSSM-LOAD or MANDATORY-AT-STARTUP.
The file name for this subsystem must be cataloged on the home pubset.
CREATION-TIME = *AFTER-SYSTEM-READY
Loading of the subsystem is initiated during system initialization (Phase 2). Loading is not synchronized with the startup routine, which can report SYSTEM-READY before loading of this subsystem has been completed.
Any address and dependency relations the subsystem has must be with subsystems which have the same startup attribute or one of BEFORE-DSSM-STARTUP, AT-DSSM-LOAD, MANDATORY-AT-STARTUP or BEFORE-SYSTEM-READY.
The files for the subsystem must be cataloged on the home pubset.
INIT-ROUTINE = *UNCHANGED / *NO / <text 1..8 without-sep>
Changes the subsystem initialization routine, provided that this does not affect the manner in which the subsystem functions.
The change takes effect immediately to allow the subsystem to be reconstructed if necessary.
INIT-ROUTINE = *UNCHANGED
The current setting is left unchanged.
INIT-ROUTINE = *NO
No initialization routine is carried out.
INIT-ROUTINE = <text 1..8 without-sep>
The name specified here is defined as the new reference address name for the subsystem (see Note 4).
CLOSE-CTRL-ROUTINE = *UNCHANGED / *NO / *DYNAMIC / <text 1..8 without-sep>
Changes the subsystem’s CLOSE-CTRL routine, provided that this does not affect the manner in which the subsystem functions.
The change takes effect immediately.
CLOSE-CTRL-ROUTINE = *UNCHANGED
The current setting is left unchanged.
CLOSE-CTRL-ROUTINE = *NO
DSSM processes the STOP-SUBSYSTEM and HOLD-SUBSYSTEM commands without invoking a CLOSE-CTRL routine.
CLOSE-CTRL-ROUTINE = *DYNAMIC
The subsystem dynamically invokes the CLOSE-CTRL routine at the end of the initialization (INIT) routine. A reference address name must have been defined for the CLOSE-CTRL routine.
CLOSE-CTRL-ROUTINE = <text 1..8 without-sep>
The name specified here is defined as the new reference address name for the CLOSE-CTRL routine (see Note 4).
STOPCOM-ROUTINE = *UNCHANGED / *NO / *DYNAMIC / <text 1..8 without-sep>
Changes the subsystem’s STOPCOM routine, provided that this does not affect the manner in which the subsystem functions.
The change takes effect immediately.
STOPCOM-ROUTINE = *UNCHANGED
The current setting is left unchanged.
STOPCOM-ROUTINE = *NO
DSSM processes the STOP-SUBSYSTEM and HOLD-SUBSYSTEM commands without invoking a STOPCOM routine.
STOPCOM-ROUTINE = *DYNAMIC
The subsystem dynamically invokes the STOPCOM routine at the end of the CLOSE-CTRL routine or, if no CLOSE-CTRL routine is defined, at the end of the initialization (INIT) routine.
STOPCOM-ROUTINE = <text 1..8 without-sep>
The name specified here is defined as the new reference address name for the STOPCOM routine (see Note 4).
DEINIT-ROUTINE = *UNCHANGED / *NO / *DYNAMIC / <text 1..8 without-sep>
Changes the subsystem’s DEINIT routine, provided that this does not affect the manner in which the subsystem functions.
The change takes effect immediately.
DEINIT-ROUTINE = *UNCHANGED
The current setting is left unchanged.
DEINIT-ROUTINE = *NO
DSSM processes the STOP-SUBSYSTEM and HOLD-SUBSYSTEM commands without invoking a DEINIT routine.
DEINIT-ROUTINE = *DYNAMIC
The subsystem dynamically invokes the DEINIT routine at the end of the STOPCOM routine or, if no STOPCOM routine is defined, at the end of the CLOSE-CTRL routine. If no CLOSE-CTRL routine is defined either, the DEINIT routine is invoked at the end of the initialization (INIT) routine.
DEINIT-ROUTINE = <text 1..8 without-sep>
The name specified here is defined as the new reference address name for the DEINIT routine (see Note 4).
STOP-AT-SHUTDOWN = *UNCHANGED / *NO / *YES
Causes DSSM to close down the subsystem automatically as soon as the SHUTDOWN (terminate session) command is issued.
The change takes effect immediately.
STOP-AT-SHUTDOWN = *UNCHANGED
The current setting is left unchanged.
STOP-AT-SHUTDOWN = *NO
DSMM ignores the subsystem when the SHUTDOWN command is issued.
STOP-AT-SHUTDOWN = *YES
DSSM closes down the subsystem as soon as the SHUTDOWN command is issued (as with the STOP-SUBSYSTEM command).
INTERFACE-VERSION = *UNCHANGED / *NO / <text 1..8 without-sep>
Designates the entry point through which DSSM can access the interface version used for decoupled calling of the INIT, CLOSE-CTRL, STOPCOM and DEINIT routines.
The change takes effect immediately.
INTERFACE-VERSION = *UNCHANGED
The current setting is left unchanged.
INTERFACE-VERSION = *NO
None of the following entry point names is available:
INIT, DEINIT, STOPCOM, CLOSE-CTRL-ROUTINE.
INTERFACE-VERSION = <text 1..8 without-sep>
The name specified here is defined as the new entry point.
SUBSYSTEM-HOLD = *UNCHANGED / *ALLOWED / *FORBIDDEN
Defines whether a command or macro can be used to halt or unload the subsystem. The change takes effect immediately.
SUBSYSTEM-HOLD = *UNCHANGED
The current setting is left unchanged.
SUBSYSTEM-HOLD = *ALLOWED
A command or macro can be used to halt or unload the subsystem.
SUBSYSTEM-HOLD = *FORBIDDEN
As with the STOP-AT-SHUTDOWN operand value, the subsystem cannot be unloaded until the BS2000 system is closed down with the SHUTDOWN command.
STATE-CHANGE-CMDS = *UNCHANGED / *ALLOWED / *FORBIDDEN / *BY-ADMINISTRATOR-ONLY
Defines whether the DSSM commands START-SUBSYSTEM, RESUME-SUBSYSTEM, STOP-SUBSYSTEM and HOLD-SUBSYSTEM are allowed for the subsystem.
The change takes effect immediately.
In the event of a version change, this setting applies only to the new version being activated. The other, “old” version will always be deactivated.
STATE-CHANGE-CMDS = *UNCHANGED
The current setting is left unchanged.
STATE-CHANGE-CMDS = *ALLOWED
The listed commands can be issued from the console or under a user ID with the SUBSYSTEM-MANAGEMENT privilege.
STATE-CHANGE-CMDS = *FORBIDDEN
The listed commands cannot be issued either from the console or under a user ID with the SUBSYSTEM-MANAGEMENT privilege.
STATE-CHANGE-CMDS = *BY-ADMINISTRATOR-ONLY
The listed commands can be issued under a user ID with the SUBSYSTEM-MANAGEMENT privilege but not from the console.
FORCED-STATE-CHANGE = *UNCHANGED / *ALLOWED / *FORBIDDEN
Defines whether the FORCED operand of the DSSM STOP-SUBSYSTEM and HOLD-SUBSYSTEM commands is allowed for the subsystem.
The change takes effect immediately.
FORCED-STATE-CHANGE = *UNCHANGED
The current setting is left unchanged.
FORCED-STATE-CHANGE = *ALLOWED
Use of the FORCED operand in these commands is allowed.
FORCED-STATE-CHANGE = *FORBIDDEN
Use of the FORCED operand is forbidden.
RESET = *UNCHANGED / *ALLOWED / *FORBIDDEN
Defines whether the RESET=*YES operand of the DSSM START-SUBSYSTEM and RESUME-SUBSYSTEM commands is allowed for the subsystem.
The change takes effect immediately.
RESET = *UNCHANGED
The current setting is left unchanged.
RESET = *ALLOWED
The DSSM START-SUBSYSTEM and RESUME-SUBSYSTEM commands are accepted if issued with the operand RESET=*YES.
RESET = *FORBIDDEN
The DSSM START-SUBSYSTEM and RESUME-SUBSYSTEM commands are rejected if issued with the operand RESET=*YES.
RESTART-REQUIRED = *UNCHANGED / *NO / *YES
Defines whether the initialization (INIT) routine is invoked to restart the subsystem in the event of abnormal holder task termination.
The initialization routine is invoked during reconstruction of the holder task.
The change takes effect immediately.
RESTART-REQUIRED = *UNCHANGED
The current setting is left unchanged.
RESTART-REQUIRED = *NO
In the event of abnormal holder task termination, the subsystem is locked during reconstruction of the holder task.
RESTART-REQUIRED = *YES
The initialization routine is invoked to restart the system.
VERSION-COEXISTENCE = *UNCHANGED / *FORBIDDEN / *ALLOWED
Defines whether different versions of the subsystem can be active at the same time. The change takes effect immediately.
VERSION-COEXISTENCE = *UNCHANGED
The current setting is left unchanged.
VERSION-COEXISTENCE = *FORBIDDEN
Only one version of the subsystem can be active.
VERSION-COEXISTENCE = *ALLOWED
Different versions of the subsystem can be active at the same time.
VERSION-EXCHANGE = *UNCHANGED / *FORBIDDEN / *ALLOWED
Defines whether a new subsystem version can be activated without the need to delete the old version.
The change takes effect immediately.
VERSION-EXCHANGE = *UNCHANGED
The current setting is left unchanged.
VERSION-EXCHANGE = *FORBIDDEN
A new subsystem version cannot be activated unless the old version has been totally deleted.
VERSION-EXCHANGE = *ALLOWED
A subsystem version can be activated without the need to delete the other version.
MEMORY-CLASS = *UNCHANGED / *SYSTEM-GLOBAL(...) / *LOCAL-UNPRIVILEGED(...) / *BY-SLICE(...)
Changes the subsystem’s memory class or defines the subsystem’s position in main memory (above or below 16 megabytes). Note the following:
A privileged subsystem cannot be changed to a nonprivileged subsystem.
If the memory class is changed, all suboperands must be specified.
A subsystem cannot be made LOCAL-UNPRIVILEGED if there is an address overlap between two LOCAL-UNPRIVILEGED subsystems sharing the same holder task.
The change takes effect as soon as the subsystem is restarted (START-SUBSYSTEM command).
MEMORY-CLASS = *UNCHANGED
The current setting is left unchanged.
MEMORY-CLASS = *SYSTEM-GLOBAL(...)
The memory class of the subsystem is changed to class 3 or class 4 memory.
SUBSYSTEM-ACCESS = *LOW / *HIGH
Defines the rights of access to the requested space and the location of the requested space in the address space.
SUBSYSTEM-ACCESS = *LOW
Defines the rights of access to the requested space and the location of the requested space in the address space.
SUBSYSTEM-ACCESS = *HIGH
Nonprivileged address space up to 2 gigabytes is requested.
MEMORY-CLASS = *LOCAL-UNPRIVILEGED(...)
The memory pool is set up as class 5 memory (only for subsystems which are to be executed in the same way as programs).
SIZE = *UNCHANGED / <integer 1..32767 4Kbyte>
Defines the size of the address space required for the memory pool in 4K pages. The defined value must large enough to hold the subsystem and all the units and load units dynamically loaded by the subsystem.
SIZE = *UNCHANGED
The current setting is left unchanged.
SIZE = <integer 1..32767 4Kbyte>
The address space specified here defines the size of the memory pool.
SUBSYSTEM-ACCESS = *UNCHANGED / *LOW / *HIGH
Defines the rights of access to the requested space and the location of the requested space in address space.
SUBSYSTEM-ACCESS = *UNCHANGED
The current setting is left unchanged.
SUBSYSTEM-ACCESS = *SYSTEM
Privileged address space is requested. The load address is above 16 MB.
SUBSYSTEM-ACCESS = *LOW
Nonprivileged address space is requested. The load address is below 16 MB.
SUBSYSTEM-ACCESS = *HIGH
Nonprivileged address space up to 2 gigabytes is requested.
START-ADDRESS = *UNCHANGED / *ANY / <x-string 7..8>
Defines the base address of the subsystem. It must be a multiple of X'100000'. The user is responsible for specifying an address which references class 6 memory.
START-ADDRESS = *UNCHANGED
The current setting is left unchanged.
START-ADDRESS = *ANY
The location of the subsystem in class 6 memory is defined by DSSM
START-ADDRESS = <x-string 7..8>
Address in the segment raster at which the base address of the subsystem is to be located. The address must be a multiple of X'100000'.
MEMORY-CLASS = *BY-SLICE(...)
The specified subsystem is a no-privileged subsystem consisting of an LLM which is made up of shareable code (program area) and nonshareable code (data area).
The program area is loaded into shareable address space (equivalent to MEMORY-CLASS= *SYSTEM-GLOBAL). The data area is loaded into the user address space of the holder task and copied into the private user address spaces of the connected tasks at the same address.
If the subsystem is defined using *BY-SLICE, note the following:
If reserved address space designed to hold the data area already exists, the command is not executed unless there is enough space free within this reserved address area to hold the modified subsystem.
If there is no such reserved address space, it will be created by the system. The tasks which are connected to the subsystem at the time when this reserved address space is created are not able to use the data area.
When a task is first connected to a subsystem that was defined with *BY-SLICE, DSSM informs the BLSSERV subsystem that the copy of the data area in the private user address space can be accessed with the VSVI1 macro.
The VSVI1 macro informs the user about entries in the DBL tables. See the “BLSSERV” manual [3] for details on the macro.
When the last connection is shut down, DSSM informs the BLSSERV subsystem that this private area can no longer be accessed.
DSSM only accepts an address space change in the new *BY-SLICE attribute if MODE=*LINK was specified for the type of specified incoming job for the subsystem and CONNECTION-SCOPE=*TASK / *PROGRAM was specified for all subsystem entries.SIZE = <integer 1..32767 4Kbyte>
Specifies the size of the requested space for the data area in 4K pages.
LINK-ENTRY = *UNCHANGED(...) / <text 1..8 without-sep>(...)
Changes the reference address used for subsystem loading. It is also possible to specify whether automatic linking of modules in phases (AUTOLINK) is allowed.
The change takes effect as soon as the subsystem is restarted (START-SUBSYSTEM command).
LINK-ENTRY = *UNCHANGED(...)
The current setting is left unchanged.
AUTOLINK = *UNCHANGED / *ALLOWED / *FORBIDDEN
Defines whether automatic linking of modules in phases (AUTOLINK) is allowed
AUTOLINK = *UNCHANGED
The current setting is left unchanged.
AUTOLINK = *ALLOWED
AUTOLINK is allowed.
AUTOLINK = *FORBIDDEN
AUTOLINK is not allowed.
LINK-ENTRY = <text 1..8 without-sep>(...)
The address specified here is used as the new reference address for subsystem loading.
AUTOLINK = *ALLOWED / *FORBIDDEN
Defines whether automatic linking of modules in phases (AUTOLINK) is allowed
AUTOLINK = *ALLOWED
AUTOLINK is not allowed.
AUTOLINK = *FORBIDDEN
AUTOLINK is allowed.
UNRESOLVED-EXTERNALS = *UNCHANGED / *ALLOWED / *FORBIDDEN
Defines whether unresolved external references prevent subsystem startup.
UNRESOLVED-EXTERNALS = *UNCHANGED
The current setting is left unchanged.
UNRESOLVED-EXTERNALS = *ALLOWED
Unresolved external reference does not prevent subsystem startup.
This setting is intended for debugging purposes only.
UNRESOLVED-EXTERNALS = *FORBIDDEN
Unresolved external reference prevent subsystem startup.
CHECK-REFERENCES = *UNCHANGED / *YES / *NO
Defines whether DSSM is to check the status of subsystems with which there is a dependency relation. The status of these subsystems may determine whether loading or unloading of the subsystem is allowed.
The change takes effect immediately.
CHECK-REFERENCES = *UNCHANGED
The current setting is left unchanged.
CHECK-REFERENCES = *YES
DSSM checks the status of subsystems with which there is a dependency relation. Depending on the status of these subsystems, DSSM decides whether the subsystem referred to by this command can be loaded or unloaded.
CHECK-REFERENCES = *NO
If the subsystem referred to by this command has a dependency relation with another subsystem, DSSM checks that the latter subsystem is loaded. If it is, the former subsystem can be loaded, even if the other subsystem is not yet runnable (the reference is held to be resolved).
The RESUME-SUBSYSTEM, STOP-SUBSYSTEM and HOLD-SUBSYSTEM commands are executed regardless of any dependency relations which may exist.
CHANGE-STATE = *UNCHANGED / *YES / *NO
Restricts the use of subsystem control commands, or cancels a restriction currently in force. This operand is particularly significant in relation to a malfunctioning subsystem, as it can be used to prevent loading, activation, and deactivation of the subsystem for as long as it takes to eliminate the malfunction.
The change takes effect immediately. It is applicable only to the current session (it is not stored in the catalog referenced by the SAVE-SUBSYSTEM-CATALOG command). The next time the subsystem is started up, the operand value is set to *NO.
CHANGE-STATE = *UNCHANGED
The current setting is left unchanged.
CHANGE-STATE = *YES
The commands locked by an operand value of CHANGE-STATE=*NO in an earlier MODIFY-SUBSYSTEM-PARAMETER command are released for use, thus restoring full control of the subsystem.
CHANGE-STATE = *NO
Prevents subsystem loading, activation, deactivation, suspending, resuming and unlocking. The following commands are locked until the next time the MODIFY-SUBSYSTEM-PARAMETER command is entered with CHANGE-STATE set to *YES:
START-SUBSYSTEM
RESUME-SUBSYSTEM
STOP-SUBSYSTEM
HOLD-SUBSYSTEM
REMOVE-SUBSYSTEM
UNLOCK-SUBSYSTEM
Return codes
(SC2) | SC1 | Maincode | Meaning/Guaranteed messages |
|---|---|---|---|
0 | CMD0001 | Command executed without error | |
0 | CMD0001 | Command executed with warnings | |
1 | 0 | CMD0001 | Command executed with warnings (no LOGICAL-ID found or message file (de)activated) |
1 | ESM0414 | Syntax error: invalid version specified | |
1 | ESM0415 | Syntax error: invalid INSTALLATION-UNIT name specified | |
1 | ESM0653 | Syntax error: invalid job entry name specified | |
32 | ESM0646 | Internal DSSM problem during processing | |
32 | ESM0646 | Internal error | |
64 | ESM0201 | Subsystem not found | |
64 | ESM0269 | Subsystem without SVC or ISL entry point | |
64 | ESM0280 | Command not executed to avoid inconsistencies in the subsystem catalog | |
64 | ESM0340 | Reserved address-space exhausted for subsystems with MEMORY-CLASS=*BY-SLICE | |
64 | ESM0613 | Changes to the message or syntax file or the installation user ID not allowed. Subsystem must first be removed with STOP-SUBSYSTEM. | |
64 | ESM0617 | Memory class changed; all parameters must be specified |
Notes
If the command changes subsystem attributes in such a way that they are given values that they already had before the command was issued, no change is made, but message ESM0647 is nonetheless issued to indicate that changes have been made. This can be avoided by using the default values (generally *UNCHANGED).
The CREATION-TIME operand is designed to modify the parameters of subsystems added by means of ADD-SUBSYSTEM commands.
If file names are specified without a user ID in the SUBSYSTEM-LIBRARY, MESSAGE-FILE, SYNTAX-FILE, REP-FILE and SUBSYSTEM-INFO-FILE operands, the subsystem’s installation user ID is searched for the files.
Changes to the INIT-ROUTINE, CLOSE-CTRL-ROUTINE, STOPCOM-ROUTINE and DEINIT-ROUTINE operands are accepted only if they do not impair the functioning of the subsystem.
If a change cannot be made, a message to that effect is sent to SYSOUT. Messages relating to accepted changes are written to the CONSLOG file.
Example
Version 9.0 of the ARCHIVE subsystem is to be started up automatically as soon as the first SVC call is issued:
/MODIFY-SUBSYSTEM-PARAMETER SUBSYSTEM-NAME=ARCHIVE,VERSION='09.0', - CREATION-TIME=*AT-SUBSYSTEM-CALL
/