LREQ,ST=HELD,SEQ=JOB
LREQ JOB=ACPBA01W DATE=YY.DDD PAGE 0001 JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOB NAME NAME NUM DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS ACPBA01W REQ 0016 084/1649 084/1549 084/1649 SY2- 001 DEMD 000 LATE SLIF-00 REQUEST COMPLETED AT 16:57:15 on YY.DDD
This panel contains the following fields:
Indicates the name of the job as defined in the database. See NAME field on the job definition panel.
Indicates the queue where this job record currently resides. Values are REQ for request queue, RDY for ready queue, and ACT for active queue.
Indicates the CA WA CA 7 Edition assigned job number.
Indicates a calculated time by which this job should be active on the CPU to be completed by the due-out time.
For a job in the request queue, this is the time of a submit time requirement. If there is a value for a job in the ready queue, then this is the time that the JCL was written to the submit data set or internal reader. Until the first SMF step termination record is received, this field shows *NONE* for a job in the active queue.
Indicates the due-out time for the job.
Indicates two values. The SPEC value is what CPU this job should be submitted to (see MAINID field on DB.1 panel). The RUN value is the system where it ran.
For XPJOB jobs this field displays XPJ for SPEC. When the job begins execution, the RUN field displays 7XPJ.
For agent jobs, this field displays the agent job type for SPEC. When the job begins execution, the RUN field displays AGJ.
Indicates the schedule ID assigned when this job was brought into the request queue.
Indicates how the job was brought into the queue. Values are the following:
ARF recovery job.
Triggered job.
Demanded job.
Job submitted external to CA WA CA 7 Edition.
Job record to be loaded (brought in by the LOAD command).
Job submitted by Personal Scheduling System.
Repeated job.
Job brought in by the RUN command.
Job record brought in by schedule scan.
Job brought in by the DEMAND command from an XPS client.
Job brought in from an XPS client using the RUN command with the REF option.
Job brought in from an XPS client using the RUN command.
Note: If ARF detects an exception condition for the job, the last character of this field has an asterisk as in the following: DEM*
Indicates the number of outstanding master requirements for a job record.
Indicates the job's current disposition. Values are the following:
Indicates the job has failed with a system abend.
Indicates the job has failed with a user abend.
Indicates the job has completed successfully and is going through completion processing.
Indicates an error occurred during the attempt to attach ARF definitions. This can result if the ARFSET specified is not defined. A diagnostic message may have been written to the CA WA CA 7 Edition log, the OS console, or to the trailer queue for the job (in which case you can view it using LQ,JOB=x,LIST=ALL).
Indicates the job has been requeued to the request queue because the CA WA CA 7 Edition job submission task was unable to read a security segment for the job.
Indicates the job has not either started by the DEADLINE DAY/TIME or has not completed by its DUE-OUT DAY/TIME.
Indicates the job completed execution of a LOAD-only run and is completing the LOAD process. This status is for jobs in the request queue.
For XPJOB jobs, indicates that the node to which this job should be directed could not be contacted through CAICCI Services. For agent jobs, indicates that a problem occurred contacting the agent.
For agent jobs, indicates a problem exists with component CA IAS (Integrated Agent Services) or that AGENTJOB=NO is specified or defaulted in the initialization file.
Indicates the node is in an offline status in the CA WA CA 7 Edition internal node table. There are no alternate nodes defined, or if there are, those alternates are also in an offline status or could not be contacted through CAICCI Services.
Indicates the node is in a STOP status in the CA WA CA 7 Edition internal node table.
Indicates the CA WA CA 7 Edition Tracker is not defined or active in this CA WA CA 7 Edition such that cross-platform tracking may occur. Instead of submitting the job when no tracking facility is available, CA WA CA 7 Edition places the job in this status.
Indicates this job is in the request queue with zero master requirements. At the time the command was issued, CA WA CA 7 Edition was processing a SAVE or REPL function on the QM.5 (QJCL) panel for this job.
Indicates the job has failed a condition code test made at the step level.
Indicates the job has failed a condition code test made at the job level.
If the job is in the request queue with this status, then there was either a runtime JCL error (for example, data set not found) or an IEFUJV exit canceled the job. If the job is in the ready queue with this status, then a job purge record was received before a job initialization record.
Indicates the job has been requeued because multiple JOB statements were found within job's JCL while the current security settings prevent this.
During submission, if no valid USERID is available, a check of the SUBNOID parameter is done to determine if a job can be submitted without an ID. With SUBNOID set to NO, the job is moved back to the request queue with a status of R-NOUID.
Indicates the job has been requeued to the request queue using the REQUEUE command or the Q function on the QM.1 panel.
At the time the job was active, CA WA CA 7 Edition required another track to be obtained from the trailer queue to hold outputs. At the time that CA WA CA 7 Edition tried to get another track, either an out of space condition or an I/O error occurred.
Indicates a dynamic allocation error occurred during attach of JCL for this job. At a user-specified time interval, a retry of the JCL attach occurs.
Indicates a job record is in the queue without its requirements attached.
Indicates the RUSH command was entered for this job.
Indicates a job record is in the queue without JCL attached.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|