Why the message 'LAST CC WAS 64' appears in a JCL with more than one null statement?
Article ID: 27083
Updated On:
Products
Issue/Introduction
When using EDCHECK in a JCL with more than one null statement (// ), message 'LAST CC WAS 64' is issued, and message CAY6000 NO STATEMENTS FLAGGED is returned.
Example:
SYS1 PUBLIC.JCL.LIB(JOB1) - 01.01 LAST CC WAS 64
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ******************************
==MSG> CAY6000 NO STATEMENTS FLAGGED IN JOB "JOB1" MAXIMUM SEVERITY WAS 0
==MSG>
==MSG> CAY6000 NO ERRORS WERE SUPPRESSED
==MSG>
==MSG> CAY6408I JCL STATEMENTS FLUSHED FOR JOBNAME "JOB1"
==MSG> CAY6000 NO STATEMENTS FLAGGED IN JOB "JOB2" MAXIMUM SEVERITY WAS 0
==MSG>
==MSG> CAY6000 NO ERRORS WERE SUPPRESSED
==MSG>
==MSG>
000100 //JOB1 JOB (111100000),'TEST',MSGCLASS=X,CLASS=K
000130 //JS010 EXEC PGM=IEFBR14
000131 //DD1 DD DSN=PUBLIC.TEST.DATA,
000133 // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,1),
000134 // DCB=(RECFM=FB,BLKSIZE=27920,LRECL=80)
000140 //
000160 //* THIS IS A COMMENT
000170 //
000180 //JOB2 JOB (111100000),'TEST',MSGCLASS=X,CLASS=K
000200 //JS010 EXEC PGM=IEFBR14
****** **************************** Bottom of Data ****************************
Environment
Release: 12.0
Component: JCLCheck Workload Automation
Cause
JCLCheck issues the RC 64 to indicate that additional JCL statement(s) was found after a // (EOJ statement) was encountered, and prior to another JOB card statement.
In the above example, //* and // statements are flushed and JCLCheck processing resumes when a JOB card is found.
Resolution
Use JCLCheck runtime option FLUSHRC(00) to eliminate the RC 64, and informational message CAY6408I JCL STATEMENTS FLUSHED.
The FLUSHRC option is documented here:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/automation/ca-jclcheck-workload-automation/12-0/reference/jclcheck-runtime-options/description-of-runtime-options/flushrc.html
Feedback
