JCLCheck Control-M Interface: //DAJOBLST - IKJ56225I DATA SET ALREADY IN USE, TRY LATER
search cancel

JCLCheck Control-M Interface: //DAJOBLST - IKJ56225I DATA SET ALREADY IN USE, TRY LATER

book

Article ID: 131025

calendar_today

Updated On:

Products

JCLCheck Workload Automation

Issue/Introduction

Using the JCLCheck Resolve feature for the Control-M variables with CLIST EJCK, and gets errors:  
...
IKJ56225I DATA SET BMC.dsname.JOBLIST ALREADY IN USE, TRY LATER+ 
IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER 
IEFA110I DATA SET CONTENTION 
DATA SET BMC.dsname.JOBLIST IN USE BY  
...
IOAD9CE ALLOCATION FAILED FOR DDNAME : DAJOBLST 
IOAEAAE CALL TO IOALOC FAILED 
...

The JCL validation ends abnormally.   How to bypass this error?  

 

Environment

JCLCheck Workload Automation release 12.0 

BMC Control-M

Resolution

JCLCheck does not require a DAJOBLST allocation.
Modify CLIST EJCK as follows: 

1. Allocate DAJOBLST to a nullfile at the beginning of the CLIST: ALLOC FI(DAJOBLST) DUMMY 
2. Free DAJOBLST at the end of the CLIST (prior to EXIT):          FREE FI(DAJOBLST)