Parameters › Command-related Parameters › SSICMD Parameter
SSICMD Parameter
This parameter determines whether CA OPS/MVS processes commands before or after subsystems such as JES, DB2, and NetView. CA recommends that you set the value of the SSICMD parameter to YES.
Keep these points in mind when setting SSICMD:
- If the subsystem processes the command before CA OPS/MVS, then command text changes specified in a command rule are ignored. Conversely, if CA OPS/MVS processes the command first, the command that the subsystem processes is the changed version; that is, it is the command as modified by the rule. If SSICMD is set to YES, CA OPS/MVS processes commands first; if SSICMD is set to NO, CA OPS/MVS processes commands after nearly all of the other subsystems have done so (depending on the order of the subsystems).
- To effectively intercept a command before any other subsystem processes it, perform the following steps:
- Set the SSICMD parameter to YES.
- Within the CMD rule logic, set the cmd.text environmental variable to null (cmd.text='') before exiting the rule with a RETURN 'ACCEPT.' For an example of intercepting and processing a JES2 command, see the AOF rule sample member JES2$TJ .
For a sample program that displays the names of all subsystems in use, see the SCANSSCT REXX program, which is distributed with CA OPS/MVS.
- Default value
-
YES
This value causes CA OPS/MVS to process commands first. YES is the recommended setting.
- Other possible values
-
NO
This value causes CA OPS/MVS to process commands after other subsystems.
- Set or modify this parameter…
-
At initialization
Example: SSICMD
This function enables CA OPS/MVS command rules to process commands after other subsystems.
OPSPRM('SET','SSICMD','NO')