JCLCheck Missing CAY6099W messages

Products

• JCLCheck Workload Automation

Issue/Introduction

After upgrade to JCLCheck r12.0 S1607 with some PTFs and We found missing CAY6099W to GDG dataset with CSI option .
But, the CAY6099W were issued with VSAM option.

 

The SAMPLE JCL the follows;

//STEP1 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DUMMY
//SYSUT2 DD DISP=(,CATLG,DELETE),UNIT=SYSDA,
// DSN=TEST.GDG(+1),SPACE=(TRK,(1,1)),
// DCB=(TEST.MODELDS,RECFM=VB,LRECL=27994,BLKSIZE=27998)
//SYSIN DD DUMMY
//**************************************************
//STEP2 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=TEST.GDG,DISP=SHR
//SYSUT2 DD DSN=TEST.TESTXXX,UNIT=SYSDA,
// DISP=(,CATLG,DELETE),
// DCB=(RECFM=VB,LRECL=27994,BLKSIZE=27998),
// SPACE=(CYL,(30,15),RLSE)
//SYSIN DD DUMMY

 

- JCLCheck with CSI option (Missing CAY6099W)

STEP1
CAY6061E DSNAME 'TEST.MODELDS' NOT FOUND IN CATALOG
CAY6186E GDG INDEX NOT BUILT 'TEST.GDG'
STEP2
CAY6066E DATA SET 'TEST.TST' NOT FOUND ON VOLUME 'VOL001'


- JCLCheck with VSAM option

STEP1
CAY6061E DSNAME 'TEST.MODELDS' NOT FOUND IN CATALOG
CAY6186E GDG INDEX NOT BUILT 'TEST.GDG'
STEP2
CAY6099W GENERATION DATA GROUP 'TEST.GDG' SPECIFIED WITHOUT A GENERATION

 

Why does not issue the CAY6099W when CSI option used?

Environment

Release:
Component: JCLCHK

Resolution

This is design of CSI option.

If no GDG base is defined('TEST.MODELDS'). When the GDG base has been defined, both VSAM and CSI give the same messages:

7.  CAY6061E DSNAME 'TEST.MODELDS' NOT FOUND IN CATALOG
12. CAY6099W GENERATION DATA GROUP 'TEST.GDG' SPECIFIED WITHOUT A GENERATION NUMBER - ALL MEMBERS SELECTED

When the GDG base has not been defined, then the CAY6099W is not issued since CSI does not find that the file is a GDG and it does not exist. VSAM based the check on the previous allocation even though it failed. Since CSI's messages are based on the catalog, it is more accurate.