Coding Each AOF Rule Type › Global Variable Rules › AOF Variables Available in a GLV Rule

AOF Variables Available in a GLV Rule

You can use all AOF variable types in GLV rules. You can use the following unique AOF event variables in the )PROC section of a GLV rule. You can also manually interrogate the corresponding OPSLOG display field as an aid in debugging or implementing rule logic.

GLV.FUNCTION

The OPSVALUE function code that caused the GLV rule to execute.

Data Type: Character, read-only

Notes:

• For global variable delete events, the parameter GLVDELETERULES must be set to YES.
• This variable must be used to distinguish between updates and deletes.
• The function codes for deletes are R (remove), 4 (variable mask delete), and 6 (single variable delete).
• For Sysplex variable events, the parameter GLVNOTIFYRULES must be set to YES. The function codes are one of: CREATE, UPDATE, or DELETE.

Sample Value: U

OPSLOG Browse Column: DSPNAME

GLV.JOBNAME

The job name of the address space that originated the GLV event.

Data Type: Character, read-only

Sample Value: OPSPROD

Note: For Sysplex variable events, the value of GLV.JOBNAME is the job name on the originating system on which the variable value change first occurred.

OPSLOG Browse Column: JOBNAME

GLV.MSFID

The Multi-System Facility or CAICCI ID of the system, either local or remote, that caused the global variable event to be invoked by setting a global variable to a value.

Data Type: Character, read-only

Sample Value: SYSA

Note: For Sysplex variable events, the value of GLV.MSFID is always the local system MSF or CCI ID.

OPSLOG Browse Column: MSFID

GLV.NAME

The 1- to 50-byte derived name of the global variable whose modification triggered this event.

Data Type: Character, read-only

Sample Value: GLOBAL.CICS.ACTIVE

OPSLOG Browse Column: Text is always displayed.

GLV.NEWVALUE

The value of the global variable after modification

Data Type: Character, read-only

Notes:

• The standard REXX definitions apply to variables that have never been referenced before or have been dropped.
• This value can or cannot be the current value of the variable, since a subsequent update can have changed its value again.

OPSLOG Browse Column: Text is always displayed.

GLV.OLDVALUE

The value that the global variable had before the global variable event modified it.

Data Type: Character, read-only

Notes:

• The standard REXX definitions apply to variables that have never been referenced before or have been dropped.
• For the Sysplex variables, the OLDVALUE is never provided or always null.

OPSLOG Browse Column: Text is always displayed.

GLV.PROGRAM

The name of the program or rule that triggered the current global variable event rule.

Data Type: Character, read-only

Sample Value: PROD.VTAM

Notes:

• If a REXX program running in a TSO address space triggered the global variable event, GLV.PROGRAM is the member name of the program. If a rule triggered the event, GLV.PROGRAM has the value ruleset.rule.
• For Sysplex variable events, the value of GLV.PROGRAM is set to blanks.

OPSLOG Browse Column: TEXT

GLV.SYNA

The name of the system on which the GLV event originated.

Data Type: Character, read-only

Sample Value: PRODS1

Note: For Sysplex variable events, the value of GLV.SYNA is the system name on which the variable value change first occurred.

OPSLOG Browse Column: SYSNAME

GLV.TEXT

The message text as seen in OPSLOG Browse, which is taken from these values of:

• GLV.NAME
• GLV.PROGRAM
• GLV.OLDVALUE
• GLV.NEWVALUE.

Data Type: Character, read-only

Notes:

• CA OPS/MVS truncates GLV.TEXT at 100 characters. So, in some cases this variable can contain only part of the GLV.OLDVALUE value and part or none of the GLV.NEWVALUE value of the variable.
• The GLV.TEXT variable is documented here for completeness. Do not use it for automation.

OPSLOG Browse Column: Text is always displayed.

GLV.USER

An 8-byte variable providing communication between rules executing for the same global variable 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:

• Before AOF processing, this variable is initialized to binary zeros. This variable is then passed to each rule that executes for the same global variable event. Each rule can look at or can change the variable contents before passing the variable to the next rule for the global variable event.
• The primary purpose for the USER variable is to provide a method to pass a small amount of data between the rules. This data can be binary or mixed case. The USER field can also be used for filtering in the OPSLOG. However, USER data that is used for OPSLOG filtering must be uppercase and displayable.

OPSLOG Browse Column: USER

More information:

AOF Rule Tools