| Previous | TContents | YIndex |
H The SCHEDULE history database can be used in a report by specifying the following source parameters:
|
" SRCRTN = SCHEDULEH_DB_IO SRCSHR = SCHEDULESHR |
D All the fields in the SCHEDULE History Database are listed in Table 8 Table 15-2.
| Name | Type | Width | &Description |
|---|---|---|---|
| CONSTANT_1 | L | 1 | always a 1 |
| CPU_TIME | L | 10 | cpu time in seconds |
| DIRECTORY | T | 40 | directory name |
| ELAPSE_TIME | L | 9 | elapse time |
| ENTRY | L | 5 | queue index used |
| EXE_ENTRY | L | 5 | submit entry number |
| EXE_QUEUE | T | 20 | job queue name |
| FULL_NAME | T | 60 | full name |
| IO_COUNT | L | 7 | i/o count |
| JOB_NAME | T | 20 | name of job |
| LOG_DATE | QD | 25 | date of event execution |
| PAGE_FAULTS | L | 7 | number of paging faults |
| PEAK_PAGING | L | 7 | peak paging |
| PID | L | 12 | job PID number |
| SCH_EVENT | T | 15 | event description |
| SET_ID | L | 7 | set id |
| SET_PARAMETER | T | 40 | set parameter |
| SET_TAG | T | 20 | set tag |
| START_TIME | QD | 25 | ! date job started to execute |
| STATUS | LU | 12 | job completion status |
| STEP | L | 3 | job step setting |
| NODE | T | 50 | source node |
| Previous | VNext | TContents | YIndex |