Coding Each AOF Rule Type › Time Limit-Exceeding Rules › AOF Variables Available in a TLM Rule

AOF Variables Available in a TLM Rule

You can use all AOF variable types in TLM rules, as described in the chapter “AOF Rule Tools.” You can use the following unique AOF event variables in the )PROC section of a TLM rule, and you can manually interrogate the corresponding OPSLOG display field as an aid in debugging or implementing rule logic.

TLM.COLOR

The color that the message text will have in OPSLOG browse

Data Type: 1-byte binary (unprintable), read/write

Sample Value: '00'X

Note: Use the OPSCOLOR function of OPS/REXX to set the TLM.COLOR variable.

OPSLOG Browse Column: COLOR

TLM.CPUCOUNT

The number of extensions for CPU time-limit-exceeding that has been granted thus far by TLM rules. This variable is incremented each time a non-zero extension is granted by TLM rules.

Data Type: Integer, read-only

Sample Value: 3 (3 extensions granted)

TLM.CPUSECS

The number of CPU seconds that have been granted thus far by TLM rule extensions. Each time a non-zero extension is granted by TLM rules, the number of seconds is added to this variable.

Data Type: Integer, read-only

Sample Value: 600 (10 minutes of extension)

TLM.EXTEND

The number of CPU or elapsed time seconds to add to the CPU or wait time limit to allow the job to continue. If this value remains zero, the job is canceled by the system.

Data Type: Integer, read/write

Sample Value: 120 (2 minute extension)

TLM.JOBNAME

The name of the job that has exceeded the CPU/wait time limit taken. JOBNAME is taken from JMRJOB in the JMR control block

Data Type: Character, read-only

Sample Value: IBMUSER

OPSLOG Browse Column: JOBNAME

TLM.JMRADDR

The address of the JMR control block passed to IEFUTL SMF exit. This address may be used with the OPSTORE function of OPS/REXX to access any field in the JMR to obtain data that is not provided by the TLM event variables. The IBM macro IEFJMR maps the contents of the JMR.

Data Type: 4-byte (unprintable), binary

Sample Value: '00ABC004'X

TLM.LIMIT

The type of time limit that has been exceeded by this job

Data Type: Character, read-only

Possible Values:

• JOB-Job processor time limit exceeded
• STEP-Step processor time limit exceeded
• WAIT-SMF continuous wait time limit exceeded
• Sample Value: WAIT (TSO user went home without logging off)

TLM.RDRDATE

The date on which the system input reader recognized the JCL JOB statement for this job. The value is seven digits long, with the high order four digits set to the year, and the low order three digits set to the day of the year.

Data Type: Character, read-only

Sample Value: 2003023

TLM.RDRTIME

The time at which the system input reader recognizes the JCL JOB statement for this job. The time value is in hundredths of seconds since midnight.

Data Type: Character, read-only

Sample Value: 3976655

TLM.SUBSYS

The subsystem name of the job used by SMF for workload accounting. Subsystem names are defined in the SMFPRMxx member of parmlib and extracted from the OUCBSUBN field of the OUCB control block.

Data Type: Character, read-only

Sample Value: TSO

TLM.TEXT

The OPSLOG message text that describes the time-limit-exceeding event for the above JOBNAME

Data Type: Character, read-only

Sample Value: IBMUSER EXCEEDED WAIT TIME LIMIT

OPSLOG Browse Column: Text is always displayed

TLM.USER

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

TLM.USERCOM

The value contained in the JMRUCOM of the JMR control block. This field is sometimes used to point to tables or control blocks used by installation SMF exits.

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

Sample Value: '0A002CFC'X

Note: Use the OPSTORE function of OPS/REXX to access any storage pointed to by TLM.USERCOM.

TLM.WAITCOUNT

The number of extensions for wait time limit-exceeding that has been granted thus far by TLM rules. This variable is incremented each time a non-zero extension is granted by TLM rules.

Data Type: Integer, read-only

Sample Value: 3 (3 extensions granted)

TLM.WAITSECS

The number of wait time seconds that have been granted thus far by TLM rule extensions. Each time a non-zero extension is granted by TLM rules, the number of seconds is added to this variable.

Data Type: Integer, read-only

Sample Value: 600 (10 minutes of extension)