c D SCHEDULE Automated Job Submission System Guide and Reference Manual D SCHEDULE
Automated Job Submission System
Guide and Reference Manual
X E.3 History file fields
A The HISTORY file contains a record of all scheduling queue state 5 changes. For example when a job that has been waiting H for a certain file and then finds that file. It is posted into the next @ scheduling queue and an record is written into the history file.
B Not all the components are filled in for all types of events. The G amount of data is controlled by the event code. The various components * of the history record are described below:
J - EVENT_TYPE: The EVENT TYPE is a letter A through V with represents the queue that was exited.B
- LOG_DATE: The LOG DATE is the time and date when the event occurred. D
- INDEX: The INDEX is the schedule queue entry number that was - assigned during the processing of this job. H
- SUBMIT: When a job is submitted several items of information are saved. They are listed below:
/ - QUEUE: Batch QUEUE job submitted into. K
- ENTRY: The ENTRY number is the batch execution queue entry number. I
- SET_TAG: The SET TAG is one of the two text fields that has been F passed from one job in a set to the next. This field contains the tag value at the time of the event. F
- SET_ID: The SET ID is the set number that was assigned to the H job set either automatically or manually. A set is just a collection of 1 jobs that work together to perform some function. L
- SET_PARAMETER: The SET PARAMETER is one of the two text fields that G has been passed from one job in a set to the next. This field contains - the parameter value at the time of the event. L
- STEP: The STEP is the job step value inside the job. This value is ? modified by explicit commands inside a job. It is then used E during restarts to reposition a command file to the point of failure.
H - COMPLETION: When a job completes several bits of information are . captured and record. These are listed below:
; - START: This is the time the job started execution. G
- ELAPSE: This is the elapse time that the job was in execution. G
- CPU_TIME:: This is the total amount of CPU time use in 100 ms
units.G
- IO_COUNT: This is the total number of buffered and direct I/O operations that took place. :
- STATUS: This is the completion status of the job.J
- PID: This is the PID number assigned to the job during execution.F
- PPAGING: This is the peak paging file activity that occurred $ during the execution of the job.I
- PGEFLTS: This is the number of page faults that occurred during the execution of the job.
V E.4 History file layout
" define record HST_record using 01 HST_record. 7 02 HST_b_key_grp_id usage is byte . 6 02 HST_t_key_directory_1 pic x(25) . 6 02 HST_t_key_filler0 pic x(1) . 6 02 HST_t_key_directory_2 pic x(25) . 6 02 HST_t_key_filler1 pic x(1) . 7 02 HST_b_key_search_section usage is byte . 6 02 HST_t_key_name pic x(39) . 6 02 HST_t_key_filler2 pic x(1) . 7 02 HST_b_key_type usage is byte . 7 02 HST_b_key_index usage is byte . 7 02 HST_q_key_date usage is date . 7 02 HST_i_key_set_id usage is long . 7 02 HST_i_event_type usage is long . 7 02 HST_q_log_date usage is date . 6 02 HST_t_sub_queue pic x(39) . 7 02 HST_i_sub_entry_no usage is long . 6 02 HST_t_sub_set_tag pic x(32) . 7 02 HST_i_sub_set_id usage is long . 6 02 HST_t_sub_set_parameter pic x(57) . 7 02 HST_i_sub_step usage is long . 7 02 HST_q_cmp_start usage is date . 7 02 HST_i_cmp_elapse usage is long . 7 02 HST_i_cmp_cpu_time usage is long . 7 02 HST_i_cmp_io_count usage is long . 7 02 HST_i_cmp_status usage is long . 7 02 HST_i_cmp_pid usage is long . 7 02 HST_i_cmp_ppaging usage is long . 7 02 HST_i_cmp_pgeflts usage is long . 7 02 HST_i_index usage is long . 6 02 HST_t_node pic x(6) . |