Agent Troubleshooting › CA WA CA 7 Edition Troubleshooting › JCL Error Status: Which Side?

JCL Error Status: Which Side?

If a job fails with a JCLERR status, the question arises who issued the error: CA WA CA 7 Edition or the agent?

LQ                                                                             
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    
                                                                               
SCWAL001 REQ 0244 223/1421 241/0357 223/1421 UNIX-AGJ  001 DEMD  001  R-JCLERR
EROCAG01 REQ 0422 253/1411  *NONE*  253/1411  WIN-     001 DEMD  002  R-JCLERR
                                                                               
SLIF-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd                                

First look at the CPU SPEC/RUN column. If no AGJ is in the RUN column, it indicates that CA WA CA 7 Edition issued the error. If AGJ is present, then the job was submitted to the agent and thus the agent issued the error. If CA WA CA 7 Edition issued the error, validate the parameters using the LJCK command.

Next examine the security information. Is user ID in the job definition valid (issue AGPSWD LIST command on the user ID)? Is external security active? If so, are the proper rules defined in the security system?

If the job was submitted to the agent, examine the status field using LQ,JOB=#,LIST=ALL. Was the command found? Is there a security error on the agent side? The LQ command has only room for a limited number of bytes for the status. The agent can also return a “long status” field. The complete status information can be displayed through the following command:

AGFILE,JOB=jobname,TYPE=INFO