You can use all AOF variable types in EOJ rules. You can use the following unique AOF event variables in the )PROC section of a EOJ rule, and you can manually interrogate the corresponding OPSLOG display field as an aid in debugging or implementing rule logic.
The value of the job card accounting field. This field is a character string where each accounting field is separated by a comma.
Data Type: Character, read-only
Sample Value: 12 (Reason code 12)
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 EOJ.COLOR variable.
OPSLOG Browse Column: COLOR
The condition code of the last step of the job that was executed. The format is the same as EOJ.MAXCC and is often 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: 0008 (Condition code 8)
The amount of CPU time (measured in hundredths of seconds) that was consumed by the job 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 (measured in hundredths of seconds) that was consumed by the job 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 done by the job. 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 job name or started task that has ended. JOBNAME is taken from the identification section of the SMF type 30 record.
Data Type: Character, read-only
Sample Value: IBMUSER
OPSLOG Browse Column: JOBNAME
The maximum condition code of any step executed during the job. This value is always five characters.
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 of the job are not executed.
Data Type: Character, read-only
Sample Value: S00C7 (system abend 0C7)
Note: EOSRULES needs to be set to YES for the EOJ.MAXCC to work properly. The end-of-step cc is tracked to place the proper data in this variable.
The number of non-specific tape mounts for the job. This value is field SMF30PTM in the type 30 SMF record.
Data Type: Integer, read-only
Sample Value: 2
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 an abend occurs in the last executed step of the job, the reason code 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 SMF30RUD 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 that is not provided by the EOJ 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 job. This value is field SMF30TPR in the type 30 SMF record.
Data Type: Integer, read-only
Sample Value: 6
The sample value date that the system began execution of this job or started task. The date is in the format YYYY/MM/DD.
Data Type: Character, read-only
Sample Value: 2000/05/12
The time that the system began execution of this job or started task. The time value is in hundredths of seconds since midnight.
Data Type: Character, read-only
Sample Value: 3600000 (10AM)
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 a job event including the maximum condition code
Data Type: Character, read-only
Sample Value: IBMUSER JOB00123 ENDED MAXCC=00000 SUBSYS=TSO
OPSLOG Browse Column: Text is always displayed
An 8-byte variable providing communication between rules executing for the same EOJ 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 EOJ event; each rule can look at or change the variable contents before passing the variable to the next rule for the EOJ 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
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 EOJ.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 © 2011 CA.
All rights reserved.
|
|