Why am I getting the message SPO7-13 "UNABLE TO ATTACH JCL" for one job only?

Products

• CA 7 Workload Automation

Issue/Introduction

When a certain job is attempting to enter the queue and one of the following messages is produced:

SATO-38 JOB jobname (nnnn) NOT ENTERED INTO REQUEST 'Q'. 0000841C JCL ***
SPO7-13 UNABLE TO ATTACH JCL (nnnn) - JOB jobname
SCNJ-18 JOB jobname NOT ENTERED INTO REQUEST 'Q'

The messages point to the size of the trailer queue, but if your trailer queue is not out of space, it could be that this job has too many lines of JCL

 

Environment

Release:
Component: 7

Resolution

When CA 7 brings a job into the request queue, the JCL for that job is written to the trailer queue. If the JCL member is so large that it takes more than 31 tracks from the trailer queue, it will not successfully schedule into the queue. Instead of inline JCL, break the executables into procedures executed by this JCL.

That said, if the error got is the following :

SPO7-13  UNABLE TO ATTACH JCL (005C) - JOB jobname 

then this means that the dynamic allocation failed for the JCL data set because someone/something had it in exclusive control, probably due to the fact that this library was heavily used at that time so CA-7 could not successfully  access it during the demand . 

This is usually caused by some process  external to CA7 that is holding the library exclusively, preventing CA7ONL from accessing it (compress, etc.)       

Possible causes are :

- something or someone is editing that data set    
- a Reserve on the volume where the library exist is in place

Additional Information

As always, please contact CA Technologies support for CA 7 if you have further questions.