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, and you can manually interrogate the corresponding OPSLOG display field as an aid in debugging or implementing rule logic.
- EOM.ASID
-
The address space ID of the terminating address space, taken from the SSENASID field of the SSOB extension
Data Type: 2-byte binary (unprintable), read-only
Sample Value: '003E'X
Notes:
- Use the OPS/REXX C2X function to convert this variable to printable hexadecimal characters.
- 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 and, 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, 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, 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.
- Through the WORD function of OPS/REXX, you can extract the first word of the EOM.TEXT string and check it to determine the current address space type.
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. It is then passed to each rule that executes for the same EOM event; each rule can look at or 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 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
