How to reset the CC=64 in JCLCheck execution, both batch or EJCK, even if message CAY6000 says 'NO STATEMENTS FLAGGED' is got.

Document ID : KB000010963
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

 

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.

 

Background:

 

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'       

 

000017 //                                                        

 

000018 //*                                                       

 

000019 // 

 

                                                    

 

Why CC=64 if no error has been found in the JCL validation and how to reset it to 0?

 

Environment:
CA JCLCheck 12.0
Instructions:

 

CA JCLCheck generates the RC 64 indicating additional JCL was found in a member after a // (EOJ statement) was encountered, and prior to another JOB card statement.

 

In the example used to document this issue, the //* and additional // statements are flushed and JCLCheck processing resumes when a JOB card is found.

If it is not possible to remove the additional statements, use the FLUSHRC(00) CA JCLCheck Runtime Option to prevent the RC 64.

 

FLUSHRC(nn) sets the return code for CA JCLCheck when JCL is flushed and FLUSHRC(64) is the default.

 

The FLUSHRC option is documented in CA JCLCheck Workload Automation Command Reference Guide, Chapter 3.