You can use all AOF variable types in EOS rules. You can use the following unique AOF event variables in the )PROC section of a EOS rule, and you can manually interrogate the corresponding OPSLOG display field as an aid in debugging or implementing rule logic.
The value of the EXEC statement account keyword or a null string if no EXEC accounting is specified. This field is a character string, where a comma separates each accounting field.
Data Type: Character, read-only
Sample Value: PROD,HR,,05210
The color that the message text has 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 EOS.COLOR variable.
OPSLOG Browse Column: COLOR
The condition code of the current step that has ended. The format is the same as EOS.MAXCC and may be the same value. The value for this field is derived from SMF30SCC in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: 00008 (Condition code 8)
The amount of CPU time, in hundredths of seconds, that was consumed by the step while running in SRB mode. This is roughly equivalent to the amount of CPU time to service I/O requests by the application. This value is field SMF30CPS in the type 30 SMF record.
Data Type: Integer, read-only
Sample Value: 20 (.2 seconds of SRB time consumed)
The amount of CPU time, in hundredths of seconds, that was consumed by the step while running under a z/OS TCB. This is roughly equivalent to the CPU usage of the application program. This value is field SMF30CPT in the type 30 SMF record.
Data Type: Integer, read-only
Sample Value: 910 (9.1 seconds of CPU time consumed)
The total number of data blocks transferred from I/O channel program executions. This is a measure of the amount of I/O completed by the step. This value is field SMF30TEP in the type 30 SMF record.
Data Type: Integer, read-only
Sample Value: 400 (400 blocks transferred)
The JES job class for an initiated batch job. This value is field SMF30C18 in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: A
The name of the job or started task whose step has ended. JOB NAME is taken from the identification section of SMF type 30 record.
Data Type: Character, read-only
Sample Value: IBMUSER
OPSLOG Browse Column: JOB NAME
The maximum condition code of any step executed, up to and including the current step. This value is always a 5-character value. The condition code has the following formats:
System abends are considered the highest values, followed by user abends and normal return codes. FLUSH is only returned if all steps, up to and including the current step, were not executed.
Data Type: Character, read-only
Sample Value: S00C7 (System abend 0C7)
The number of non-specific tape mounts for the step. This value is field SMF30PTM in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: 2
The Open MVS UNIX sub-step number that is incremented by 1 each time the OMVS EXEC function is invoked. This field is 0 for z/OS programs. This value is field SMF30SSN in the type 30 SMF record.
Data Type: Integer, read-only
Sample Value: 25
The name of the job step program specified in the PGM keyword of the JCL EXEC statement. For an OMVS UNIX program, this field may be 16 characters in length and reflects the file name specified at the end of the UNIX path specification. This value is field SMF30PGM in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: IEBGENER
The programmer name field from the JOB statement. This value is field SMF30USR in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: JOHN DOE
If the EXEC statement invokes a catalogued procedure, this variable is the name of the EXEC statement. Otherwise, it is a null string. This value is field SMF30PSN in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: ASMHCLG
If an abend occurs in the terminating step, the value passed in register 15 is sometimes a reason code for the abend. The value for this field is derived from SMF30ARC in the type 30 SMF record.
Data Type: Integer, read-only
Sample Value: 12 (Reason code 12)
The WLM resource group name for the job if the system is using the z/OS Workload Manager for system management. This value is field SMF30GRN in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: ALLCICS
The security group ID taken from the ACEE. This value is field SMF30GRP in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: OPERS
The security user ID taken from the ACEE. This value is field SMF30GRP in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: OPER1
The WLM service class for the job if the system is using the z/OS Workload Manager for system management. This value is field SMF30SCN in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: SPEEDY
The address of the SMF type 30 record. This address may be used with the OPSTORE function of OPS/REXX to access any field in the type 30 record to obtain data not provided by the EOS event variables. The IBM macro IFASMFR (30) generates the assembler DSECT for the SMF type 30 record.
Data Type: 4-byte binary (unprintable), read-only
Sample Value: '00702C00'X
The number of volume specific tape mounts for the step. This value is field SMF30TPR in the type 30 SMF record.
Data Type: Integer, read-only
Sample Value: 6
The date on which the system began execution of this step
Data Type: Character, read-only
Sample Value: YYYY/MM/DD
The time that the system begins execution of this job or started task step. The time value is measured in hundredths of seconds, starting from 12 a.m.
Data Type: Character, read-only
Sample Value: 3600000 (10AM)
The step name of the job step that terminated. This value is field SMF30STM in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: LKED
The step number of the job step that terminated. The first step has number 1, and so forth. This value is from field SMF30STN in the type 30 SMF record.
Data Type: Integer, read-only
Sample Value: 2
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
The symbolic name of the TSO terminal for a TSO session. This value is field SMF30TSN in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: OPSS1
OPSLOG Browse Column: TERMNAME
The OPSLOG message text that describes the end of step event, including the maximum condition code
Data Type: Character, read-only
Sample Value: PAYJOB JOB00123 STEP 1 PAYPROC.STEP1 PGM=P
OPSLOG Browse Column: Text is always displayed.
An 8-byte variable providing communication between rules executing for the same EOS 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:
OPSLOG Browse Column: USER
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 EOS.USERCOM.
The WLM workload name of the job if the system is using the z/OS Workload Manager for system management. This value is field SMF30WLM in the type 30 SMF record.
Data Type: Character, read-only
Sample Value: PRODCICS
|
Copyright © 2014 CA.
All rights reserved.
|
|