Coding Each AOF Rule Type › End-of-Memory Rules › AOF Variables Available in an EOM Rule

AOF Variables Available in an EOM Rule

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

EOM.ABNORMAL

An integer value indicting whether the address space terminated abnormally. This value is derived from the SSENTYPE flag in the SSOB extension.

Data Type: Integer, read-only

Possible values are:

• 0 = normal termination
• 1 = abnormal termination.

Abnormal does not include all abends. S222 abends are not considered abnormal. Abend S069 reason code 4 for ASCRE failure is considered abnormal.

Sample Value: 0

EOM.ASID

The address space ID of the terminating address space, which is taken from the SSENASID field of the SSOB extension.

Data Type: 2-byte binary (unprintable), read-only

Sample Value: '003E'X

Notes:

• To convert this variable to printable hexadecimal characters, use the OPS/REXX C2X function.
• Using this variable, you can check to see if an address space is terminating. For example, suppose that an automation application keeps a list of critical address spaces and their ASIDs. You can write an EOM rule that compares the list entries against the ASID of the currently terminating address space. If a match is found, restarts the address space or takes another recovery action.

OPSLOG Browse Column: ASID

EOM.JOBNAME

The job name of the terminated address space, which is taken from one of these sources:

• TSO users: The OUCBUSRD (user ID) field of the OUCB; the value is the user ID for time sharing address spaces
• Started tasks: The OUCBTRXN (transaction name) field of the OUCB; the value is the started task name for started task address spaces

Data Type: Character, read-only

Sample Value: VTAM

Note: The EOM.JOBNAME variable determines which EOM rules execute for an EOM event.

OPSLOG Browse Column: JOBNAME

EOM.TEXT

Description of the terminated address space, which is taken from the OUCBSUBN (subsystem name) field of the OUCB and from the EOM.JOBNAME variable.

Data Type: Character, read-only

Sample Value: TSO USERA

Notes:

• The type of terminated address space is either TSO for a TSO user or STC for a started task.
• You can extract the first word of the EOM.TEXT string to determine the current address space type use the OPS/REXX WORD function.

OPSLOG Browse Column: Text is always displayed.

EOM.USER

An 8-byte variable providing communication between rules executing for the same EOM 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 EOM event. Each rule can look at or can change the variable contents before passing the variable to the next rule for the EOM 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