LQ LQUE,ST=LATE,SEQ=JOB LQUE,LIST=STATUS,JOB=15 LQ,JOB=MYJOB1,LIST=ALL LQ,JOB=MY* LQ,ST=HELD,SEQ=CA7 LQ,SEQ=CA7
LQ Command
LQ 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 HISTORY REQ 0105 098/1025 *NONE* 098/1025 ALL- 001 DEMD 002 CA7LJESX REQ 0102 098/1024 098/1000 098/1030 ALL- 001 SSCN 001 C7TST001 REQ 0106 098/1025 *NONE* 098/1025 ALL- 001 DEMD 001 C7TST002 REQ 0107 098/1025 *NONE* 098/1025 ALL- 001 DEMD 001 C7TST003 ACT 0110 098/1029 098/0929+098/1029 ALL-XE79 001 DEMD 000 SLIF-00 REQUEST COMPLETED AT 09:29:03 on YY.DDD
LQ,JOB=DUSAZZ01,LIST=RQMT Command
LQ,JOB=DUSAZZ01,LIST=RQMT LIST=RQMT JOB=DUSAZZ01 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 DUSAZZ01 REQ 0005 128/1611 *NONE* 128/1611 /SY2- 001 DEMD 003 LATE ---------------------------REQUIREMENTS STATUS --------------------- _ _ _ _ JCL OVERRIDES REQUIRED _ _ _ _ INTERNAL JOB=DUSAZZ13 DATE/TIME=YYDDD/HHMM SLIF-00 REQUEST COMPLETED AT 16:35:41 on YY.DDD
LQ,JOB=DUSAZZ01,LIST=JCL
LQ,JOB=DUSAZZ01,LIST=JCL LIST=JCL JOB=DUSAZZ01 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 DUSAZZ01 REQ 0005 128/1611 *NONE* 128/1611 /SY2- 001 DEMD 004 R-REQUE ---------------------------- JCL INFORMATION ----------------------- //DUSAZZ01 JOB HE67YFSH,PAYROLL,REGION=40K,TIME=0003,CLASS=B 0010 /*ROUTE PRINT RMT2 0020 /*JOBPARM ROOM=543 0030 //*UCC7RESTART UCC7
LQ,JOB=215,SEG=QDESC Command
LQ,JOB=215,SEG=QDESC LIST=PROS CA-7#=0215 DATE=YY.DDD PAGE 0001 SEG=(QDESC) 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 CA07XX01 REQ 0215 173/1943 *NONE* 173/1943 ALL- 001 DEMD 001 -------------------------- PROSE INFORMATION -------------------------- *** JOB CA07XX01 *** SCHEDULED JOB, FIRST IN THE NETWORK *** FIRST STEP
LQ,LIST= Command
LQ,LIST= LIST= DATE=YY.DDD PAGE 0001 JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOB NAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS JOEJOB1 RDY 0002 288/1135 *NONE* 288/1135 ALL- 001 DEMD 000 W-RSRC JOEJOB15 RDY 0008 288/1327 *NONE* 288/1327 ALL- 001 DEMD 000 W-RSRC SCA1003D RDY 0021 295/0954 295/0919 295/1000 ALL- 099 SSCN 000 LATE TESTJOBA RDY 0024 295/1116 *NONE* 295/1116 ALL- 001 DEMD 000 W-RSRC SLIF-00 REQUEST COMPLETED AT 13:35:53 on 09.295
This panel contains the following fields:
Identifies the name of the job as defined in the database. See NAME field on the job definition panel.
Identifies the queue where this job record currently resides. Values are REQ for request queue, RDY for ready queue, and ACT for active queue.
Identifies the CA Workload Automation SE assigned job number.
Identifies 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. (The requirement can be manually posted, leaving a date/time value with no outstanding submit time requirement.) If there is a value for a job in the ready queue, 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 is *NONE* for a job in the active queue. A plus sign displayed immediately after the field indicates that the job's start time is normalized to the time zone of the running CA Workload Automation SE.
Identifies the due-out time for this job.
Identifies the SPEC value is what CPU this job should be submitted to (see MAINID field on DB.1 panel). The RUN value is what CPU the job has been submitted to. For 7UNI jobs, the RUN value can be 7UWT, which indicates that the process has not started on the submitted to platform.
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.
Identifies the schedule ID assigned when this job was brought into the request queue.
Identifies how the job was brought into the queue. Values are the following:
Indicates an ARF recovery job.
Indicates a triggered job.
Indicates a demanded job.
Indicates a job submitted external to CA Workload Automation SE.
Indicates a job record to be loaded (brought in by the LOAD command).
Indicates a job submitted by Personal Scheduling System.
Indicates a repeated job.
Indicates a job brought in by the RUN command.
Indicates a job record brought in by schedule scan.
Indicates a job brought in by the DEMAND command from an XPS client.
Indicates a job brought in from an XPS client using the RUN command with the REF option.
Indicates a 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 indication of the job's current disposition. Values and their meanings 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 Workload Automation SE 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 encountered an error in the ARF processing. Issue a LARFQ command for the job to get more specific information.
Indicates the job has been requeued to the request queue because the CA Workload Automation SE 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 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.
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.
Indicates this job is in the request queue with zero master requirements. At the time the command was issued, CA Workload Automation SE 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 the job's JCL while the current security settings prevent this.
Indicates 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 moves 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.
Indicates at the time the job was active, CA Workload Automation SE required another track to be obtained from the trailer queue to hold outputs. At the time that CA Workload Automation SE 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.
Indicates a job that CA Workload Automation SE submitted and queued for submission to an agent that is not active currently.
Note: This status is sometimes seen even when the CA IAS interface is not active. The difference is that CA IAS received the job request. If a job reflects status N-IAS, this status indicates that the job has not been sent to CA IAS for processing.
Indicates a job is in the ready queue waiting on a resource that is unavailable.
LQ,LIST=XPJOB Panel
LQ,JOB=CA7XPJOB,LIST=XPJOB LIST=XPJOB JOB=CA7XPJOB DATE=YY.DDD PAGE 0001 JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOB NAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS C7TST003 ACT 0110 098/1029 098/0929+098/1029 ALL-XE79 001 DEMD 000 ------------------------- XPJOB INFORMATION ------------------------- P Node: UNIX001 State: Fail A Node: SU Type: Y Trace: N Entry#: Userid: Domain: Exec : calc.exe
This panel contains the following fields under XPJOB INFORMATION:
Identifies the primary node for this job. The job is routed to this node if the node is available.
Identifies the state of the primary node following the latest attempt to route the job to the indicated node. Values are the following:
Specifies that the node is available and data can be sent.
Specifies that the node is unavailable due to a manual command. Data can be sent to alternate nodes if defined.
Specifies that the node and its alternates are not available due to a manual command. No attempts are made to send data to this node or its alternate nodes.
Specifies that the node is unavailable due to a communications failure. Data can be sent to alternate nodes if defined.
Specifies that no attempts have been made to send data to this node. For example, the job was submitted with an initial HOLD and has not been released.
Identifies the alternate node that has been used by this job. If present, it indicates that the primary node was not available and that the job has been routed to the indicated alternate node.
Identifies the type of switch user (SU) option to use on the target node.
Identifies whether activity for this job is being traced.
Identifies a CA Workload Automation SE generated value used to uniquely identify this job submission.
Identifies the user ID under which the executable runs.
Identifies the domain ID under which the executable runs.
Identifies the executable that is run on the target node.
LQ,LIST=AGJOB Panel
LQ,JOB=CA7AGJOB,LIST=AGJOB LIST=AGJOB CA-7#=0005 DATE=YY.DDD PAGE 0001 JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOB NAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS CA7AGJOB REQ 0005 317/0708 317/0608 317/0708 WIN-AGJ 001 DEMD 002 R-JCLERR -------------------------- AGENT INFORMATION -------------------------- Job Type: NT_JOB JobNo: 8612 Agent: UNIXAGT01 Status: SUBERROR Logon failure: unknown user name User: user01 SLIF-00 REQUEST COMPLETED AT 13:35:53 on YY.DDD
This panel contains the following fields under AGENT INFORMATION:
Identifies the type of agent job.
Identifies the job number assigned at the agent. Certain job types are not assigned job numbers:
Identifies the distributed platform where the job runs.
Identifies the last reported status of the agent job.
Identifies the user ID under which the executable is to run.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|