Running CA JCLCheck, both in batch or EJCK, against a JCL stream produces either messages or reports about the condition of your JCL, and job submission, if your execution method and options allow.
It can happen that, asking to scan and validate a JCL with additional jcl lines added after the first // (EOJ statement), the JCLCheck execution ends with ‘LAST CC 64', even if the message CAY6000 says 'NO STATEMENTS FLAGGED'.
For example, using online EJCK:
EDIT JCL.LIB(JOB1) - 01.67 LAST CC WAS 64
Command ===> Scroll ===> CSR
000012 //ALLOC EXEC PGM=IEFBR14
000013 //TEST DD DSN=DATA.SET.NAME,
000014 // DSNTYPE='PDS',
000015 // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(1,1)),
000016 // DCB='RECFM=FB,BLKSIZE=6160,LRECL=80'
Why CC=64 if no error has been found in the JCL validation and how to reset it to 0?