Jobs with a JCL ERROR remaining in CA 7 RDY Queue

Products

• CA 7 Workload Automation

Issue/Introduction

Why do some jobs with a JCL ERROR remain in the CA 7 Ready Queue, while some other jobs with JCL ERROR too are flagged as such and returned to the Request Queue?

 

Environment

Release:
Component: 7

Resolution

Jobs that fail with a JCL ERROR during z/OS interpreter conversion do not automatically generate an SMF Purge record, hence CA 7 Edition has flagged the job as being submitted but never receives any communication from the operating system that the job has started, completed, or purged. For this reason the job will remain in the RDY queue until it is manually requeued to the request queue and actions are taken to correct the JCL.

Jobs that fail with a JCL ERROR after being initiated (DATA SET NOT FOUND, for example) do create a SMF record and are flagged accordingly and returned to the request queue.