EJCK and !JCK show a correct error message but it’s in the wrong location
Article ID: 223887
Updated On:
Products
Issue/Introduction
Sample EDCHEK output:
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD DSN=&DATALIB(INPUT1),DISP=SHR
//SYSIN DD DSN=&DATALIB(INPUT1),DISP=SHR
SUBST JCL - DSN=PUBLIC.JCK.CNTLIB(INPUT1),DISP=SHR
DELETE PUBLIC.S2106.PTFLIB PURGE
XELETE PUBLIC.S2101.PTFLIB PURGE
CAY6006S VERB "XELETE" IS UNKNOWN
DELETE PUBLIC.S2104.PTFLIB PURGE
// DD DSN=&DATALIB(INPUT2),DISP=SHR
// DD DSN=&DATALIB(INPUT2),DISP=SHR
SUBST JCL - DSN=PUBLIC.JCK.CNTLIB(INPUT2),DISP=SHR ==> this member contains XDELETE command
// DD DSN=&DATALIB(INPUT3),DISP=SHR
// DD DSN=&DATALIB(INPUT3),DISP=SHR
SUBST JCL - DSN=PUBLIC.JCK.CNTLIB(INPUT3),DISP=SHR
/*
Error CAY6006S is generated correctly, but does not identify the SYSIN member that contains the statement in error.
Need to have easier way to identify the control member(s) in error.
Environment
Release : 12.0
Component : JCLCheck Workload Automation
Resolution
Apply PTFs LU03796 and LU04182.
These PTFs add a new option CTLSCAN(CONCatms), and new messages (CAY6617I / CAY6618I) to JCLCheck.
Sample EDCHEK messages when using new option CTLSCAN(CONCatms):
XELETE PUBLIC.S2101.PTFLIB PURGE
CAY6006S VERB "XELETE" IS UNKNOWN
CAY6617I STMT FROM MEM: "INPUT2" DSN: "PUBLIC.JCK.CNTLIB"
Feedback
