What does the STATUS field on the LQ output mean?
The job failed with a system abend. The nnn is the abend code. The job needs to be restarted, force completed, or canceled.
The job failed with a user abend. The nnnn is the abend code. The job needs to be restarted, force completed, or canceled.
The job completed successfully and is going through completion processing. If jobs remain in the request queue with this status, check the browse data set for error messages.
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 7 log, the OS console, or to the trailer queue for the job (in which case it can be displayed using LQ,JOB=x,LIST=ALL).
Indicates the job encountered an error in the ARF processing. Do a LARFQ command for the job to get more specific information.
Indicates the job has been requeued to the request queue because the CA 7 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.
Indicates this job is in the request queue with zero maste rrequirements. At the time the command was issued, CA 7 was processing a SAVE or REPL function on the QM.5 (QJCL) panel for this job.
The job failed with a condition code test made at the step level. The nnnn is the failing condition code. The job needs to be restarted, force completed, or canceled.
The job failed with a condition code test made at the job level. The nnnn is the failing condition code. The job needs to be restarted, force completed, or canceled.
If the job is in the request queue with this status, then there was either a runtime JCL error, a syntax JCL error, or a UJV exit canceled the job.
If a job is in the request queue with this status, then there was no USERID that could be associated with this job for job submission and SUBNOID=NO is on the SECURITY statement in the initialization file. If QJCL is in the SUBUID hierarchy, then edit the QJCL and do an SR. If the job is non-executable and has no JCL attached, then do a top line QJCL, an FE function for that job name, and a SR from the blank text editor.
Indicates the job has been requeued to the request queue using the REQUEUE command or the Q function on the QM.1 panel.
A job with this status had an error accessing the security segment in the trailer queue. The job needs to be canceled and DEMANDed or force completed.
While the job was active, another track was needed in the trailer queue to hold output data to be processed at job completion. At the time the attempt was made to get another track, either the trailer queue was out of available tracks or an I/O error occurred. You may need to increase the size of the trailer queue. A job with this status has to be force completed to tell CA 7 that it has successfully completed. Some of the data set creations from this job may not have been processed to the database, and may have to be manually posted for jobs using the data sets created by this job.
A dynamic allocation error occurred during attach of JCL for this job. At user-specified time intervals, a retry of the JCL attach will occur.
Indicates the RUSH command was entered for this job.
If a job remains in RQMT-INC status, an error occurred trying to attach requirements for this job. Check the browse data set for error messages. The job may need to be reloaded.
If a job remains in SKELETON status, an error occurred trying to attach the JCL for this job. Check the browse data set for error messages. The job needs to be canceled with a FORCE=YES and DEMANDed.
Indicates a job is in the ready queue waiting on a resource that is unavailable.
Indicates the job has been requeued because multiple JOB statements were found within the job's JCL while the current security settings prevent this.
Indicates a job submitted by CA Workload Automation SE and queued for submission to an agent that is not active at this time.
Indicates the node is in a STOP status in the CA Workload Automation SE internal node table.
Indicates the CA Workload Automation SE Tracker is not defined or active in this CA Workload Automation SE such that cross-platform tracking may occur. Instead of submitting the job when no tracking facility is available, CA Workload Automation SE places the job in this status.
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 Workload Automation SE 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.