(1) (2) (3) 2010/07/13 14:06 CA MII Job Requeue Report PAGE 1 (4) System: SYSA (5) Jobname: MIMGR (6)Release: 11.9 (7) Service Level: 0000 (8) From: 2009/10/25 00:00 (9) Each: RECORD (10)To: 2010/03/12 10:52 (11)Shift: 00:00 24:00 (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) Jobname Job ID Requeue Time Release Time Hold Time REQ Owner System OWN Dataset Name -------- -------- ---------------- ---------------- --------- --- -------- -------- --- ------------------------------------------- BATCHJBA JOB00941 2010/03/08 11:19 2010/03/08 11:40 20m 32s EXC BATCHJBB SYSB SHR MIMGR.REQUEUE.DSN
|
Field |
Description |
|---|---|
|
(1) |
Date and time the report was created. |
|
(2) |
Report title. |
|
(3) |
Report page number. |
|
(4) |
System name of the CA MII image as defined by the DEFSYS statement. |
|
(5) |
Name of the CA MII started task. |
|
(6) |
The CA MII release number. |
|
(7) |
The CA MII service level. |
|
(8) |
Date and timestamp of the earliest record in the reporting interval. |
|
(9) |
Summary level for the data line. In this example, each RECORD is displayed in the detail line. If each HOUR was specified, then the detail line would be a summary of the hour's activity. |
|
(10) |
Date and timestamp of the latest record in the recording interval. |
|
(11) |
Range of records included in the report. |
|
Jobname (12) |
Job name of the job that was canceled and re‑queued by CA MII due to a conflict with another job or jobs for one or more data sets. |
|
Job ID (13) |
JES2 assigned JOBID of the job that was re‑queued. |
|
Requeue Time (14) |
Date and time that the job was canceled and re‑queued for execution. |
|
Release Time (15) |
Date and time that the job was released from hold status by CA MII and was eligible for selection for execution. Selection for execution depends on available initiators, the execution selection priority of the released job in relation to other jobs queued for execution, and so forth. |
|
Hold Time (16) |
The amount of time in the form hh:mm:ss (hours, minutes, and seconds, respectively) that the specified job was not available for execution selection due to data set conflicts. |
|
REQ (17) |
The scope of control that the re‑queued job requires for the named data set. EXC is exclusive control while SHR is shared control. |
|
Owner (18) |
The jobname of the job that currently owns the requested data set. |
|
System (19) |
The system as defined by a DEFSYS statement, upon which the data set owner is actively executing. |
|
OWN (20) |
The scope of control that the data set owner currently maintains. EXC is exclusive control while SHR is shared control. |
|
Data Set Name (21) |
The name of the data set in conflict. |
|
Copyright © 2014 CA.
All rights reserved.
|
|