You can use all AOF variable types in CMD rules. The following unique AOF event variables are available in the )PROC section of a CMD rule. Also listed are the corresponding OPSLOG display field that you can manually interrogate as an aid in debugging or implementing rule logic.
A value indicating whether CA OPS/MVS issued the current command from within an AOF rule
Data Type: Integer, read-only
Possible Values:
Sample Value: 1
Notes:
OPSLOG Browse Column: Second bit of OPSFLAGS when the EVENT column indicates a CMD event
The name of the console from which the command was issued Data Type: Character, read-only
Sample Value: MASTSYSA
Note: For commands originating in the subsystem interface, CMD.CONSNAME contains the console name.
OPSLOG Browse Column: CONSNAME
The ID of the IMS control region that issued this command, or NONE for non-IMS commands. The CMD.IMSID variable is available only if the IOF is licensed, installed, and active at your site (that is, the INITIMS parameter must be set to YES).
Data Type: Character, read-only
Sample Value: IMSA
OPSLOG Browse Column: IMSID
Indicates whether the command prefix is a JES3 sysplex scope prefix. Set to 1 if the original JES3 command prefix is defined as a sysplex scope prefix (PLEXSYN).
Data Type: Character, read-only
Possible Values:
Sample Value: 1
Note: This variable is only meaningful for JES3 commands in a JES3 environment.
OPSLOG Browse Column: Eighth bit of OPSFLAGS when the event column indicates a CMD event, and a JES command prefix was used.
The original JES3 prefix used on the JES3 command
Data Type: Character, read-only
Possible Values: Any valid JES3 system or sysplex command prefix, which can be from 1 to 8 characters in length. With the special exception of the character 8, JES3 command prefixes cannot start with a numeric character.
Sample Value: *
Note: This variable is only meaningful for JES3 commands in a JES3 environment.
OPSLOG Browse Column: AUTOTOKN when the event column indicates a command event, and a JES command prefix is used.
Indicates whether the command prefix is a JES3 system scope prefix. Set to 1 if the original JES3 command prefix is a system scope prefix (SYN).
Data Type: Character, read-only
Possible Values:
Sample Value: 0
Note: This variable is only meaningful for JES3 commands in a JES3 environment.
OPSLOG Browse Column: Seventh bit of OPSFLAGS when the event column indicates a CMD event, and a JES command prefix was used.
The name of the job or the TSO user who issued the command
Data Type: Character, read-only
OPSLOG Browse Column: JOBNAME
The MSF system name of the copy of CA OPS/MVS that issued the command
Data Type: Character, read-only
Sample Value: OPSP
Note: For all commands issued from sources other than remote copies of CA OPS/MVS, the value of CMD.MSFID is the MSF ID of the local copy of CA OPS/MVS.
OPSLOG Browse Column: MSFID
The system name from which the command originated. This variable enables you to identify the origin of commands routed to this system through the ROUTE command. CMD.ORIGINSYS can only return the correct information when the SSICMD product parameter is set to YES. When SSICMD is set to NO, this variable and the SYSNAME column in OPSLOG are set to UNKNOWN.
Data Type: Character, read-only.
Sample Value: SYSA
OPSLOG Browse Column: SYSNAME
The original text of the command, unmodified by subsequent rule processing
Data Type: Character, read-only
A value indicating whether CA OPS/MVS issued the current command
Data Type: Integer, read-only
Possible Values: 0 (if CA OPS/MVS did not issue the command) or 1 (if CA OPS/MVS issued the command)
Sample Value: 1
Notes:
OPSLOG Browse Column: First bit of OPSFLAGS when the EVENT column indicates a CMD event
A value indicating whether System State Manager issued the current command
Data Type: Integer, read-only
Possible Values:
Sample Value: 1
Notes:
OPSLOG Browse Column: Third bit of OPSFLAGS when the EVENT column indicates a CMD event
The JES3 console name that submitted the current command, or the string NONE if the current JES3 command is not associated with a JES3 console
Notes:
Data Type: Character, read-only
OPSLOG Browse Column: TERMNAME
The command text as it will execute, taken from:
Data Type: Character, read/write
Sample Value: 'D TS,L'
Notes:
OPSLOG Browse Column: Text is always displayed.
The exit environment where the command was trapped
Data Type: Character, read-only
Possible Values:
OPSLOG Browse Column: Not applicable
An 8-byte variable providing communication between rules executing for the same command event. The variable can contain any installation data that these rules need, and it can store a character string displayable through OPSLOG Browse.
Data Type: User-defined, read/write
Notes:
OPSLOG Browse Column: USER
The security user ID of the command issuer for the security product on your system. This value is usually the CA ACF2, CA Top Secret, or RACF user ID from the UTOKEN associated with the command. If the command was issued from CA Remote Console, this value is the user ID of the particular RCS user who issued the command.
Data Type: Character, read-only
Sample Value: TSOID01
Note: The CMD.USERID variable may contain the same value as the JOBNAME (which is typical for a TSO address space). These values need not match; for example, user IDs and the job names for batch jobs or started tasks may differ.
OPSLOG Browse Column: USERID
The command verb as CA OPS/MVS extracts it
Sample Value: DISPLAY
Data Type: Character, read-only
Notes:
OPSLOG Browse Column: MSGID
The decimal value corresponding to the 4-byte extended console ID of the console that issued the command. This field is not set for IMS commands.
Data Type: Integer, read-only
Sample Value: 16777253
Note: The XCONID column in OPSLOG displays this value as a hexadecimal value. For example, an extended console ID of 16777253 will be displayed in the XCONID column in OPSLOG as M01000025.
OPSLOG Browse Column: XCONID
|
Copyright © 2011 CA.
All rights reserved.
|
|