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, and you can manually interrogate the corresponding OPSLOG display field as an aid in debugging or implementing rule logic.

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

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 may or may not be the current value of the variable, since a subsequent update may 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

Note: The standard REXX definitions apply to variables that have never been referenced before or have been dropped.

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

Note: 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.

OPSLOG Browse Column: TEXT

GLV.TEXT

The message text as seen in OPSLOG Browse, taken from the values of GLV.NAME, GLV.PROGRAM, GLV.OLDVALUE, and GLV.NEWVALUE

Data Type: Character, read-only

Notes:

• CA OPS/MVS truncates GLV.TEXT at 100 characters. So, in some cases this variable may 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. It is then passed to each rule that executes for the same global variable event; each rule can look at or 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 may be binary or mixed case. The USER field may also be used for filtering in the OPSLOG. However, USER data used for OPSLOG filtering must be uppercase and displayable.

OPSLOG Browse Column: USER

More information:

AOF Rule Tools