How to reset the CC=64 in JCLCheck execution?
Article ID: 10963
Updated On:
Products
Issue/Introduction
Sample EDCHEK session:
EDIT JCLCHK.PDS2(IEFBR14) - 01.02 LAST CC WAS 64
Command ===> Scroll ===> HALF
****** ***************************** Top of Data ******************************
==MSG> CAY6000 NO STATEMENTS FLAGGED IN JOB "STEP10" MAXIMUM SEVERITY WAS 0
==MSG>
==MSG>
==MSG>
000001 //STEP10 EXEC PGM=IEFBR14
000002 //*******************************************************************
000003 //**** PROGRAM - IEFBR14 ***
000004 //**** TITLE - CREATE FILES ***
000005 //*******************************************************************
000006 //SYSUT1 DD DUMMY
000007 //SYSUT2 DD DUMMY
000008 //SYSPRINT DD SYSOUT=*
000009 //
000010 //*******************************************************************
000011 //STEP20 EXEC PGM=IEFBR14
000012 //*******************************************************************
000013 //*******************************************************************
000014 //SYSUT1 DD DUMMY
000015 //SYSUT2 DD DUMMY
000016 //SYSPRINT DD SYSOUT=*
****** **************************** Bottom of Data ****************************
Why CC=64 if no error has been found, and how to reset the condition code to 00?
Environment
Release: 12.0
Component: JCLCheck Workload Automation
Cause
CC=64 is issued when a NULL or EOJ statement is found in the validating JCL.
Resolution
Use runtime option FLUSHRC(00).
The FLUSHRC option sets the return code for JCLCheck when JCL is flushed.
This option has the following format:
FLUSHrc(nn)|NOFLushr
Default: FLUSHrc (64)
Should JCL exist between a NULL or EOJ statement and the next JOB statement, it is flushed when submitted for execution. When this condition is detected, JCLCheck uses a return code of 64 upon termination.
To override the return code value (1-256), use the FLUSHRC(nn) option.
Using FLUSHRC(0) suppresses message CAY6408I.
When FLUSHRC(8) is specified and JCLCheck issues an error message with a return code of 8, JCLCheck terminates using the greater value, in this example 8. In other words, using the FLUSHRC option does not cause JCLCheck to use a lower return code than it would have already issued
Feedback
