Why do I receive CAY6564 "MAXCC" CHANGED TO "0" for JCLCheck?

Products

• JCLCheck Workload Automation

Issue/Introduction

Why do I receive the message CAY6564I "MAXCC" CHANGED TO "16" with JCLCheck?
 

Environment

Release: 12.0
Component: JCLCheck Workload Automation

Resolution

You will receive the message CAY6564I "MAXCC" CHANGED TO "16" when checking IDCAMS control cards with SET condition code statement.  For example;

//STEPA    EXEC PGM=IDCAMS                                          
//SYSPRINT DD  SYSOUT=*                                             
//SYSIN DD  *                                                       
 DEL STRGR01.IDCAMS.DEF1.MASTER1                                    
CAY6079S DATA SET "STRGR01.IDCAMS.DEF1.MASTER1" SPECIFIED AS OLD OR 
         SHR, BUT CANNOT BE FOUND                                   
 IF MAXCC = 8 THEN SET MAXCC = 16                                    
CAY6564 "MAXCC" CHANGED TO "16"                                     
CAY6441I SET COMMAND ALTERED SEVERITY OF PRIOR MESSAGES      

Note:   The CAY6079S message severity is changed to an S which is CC 16.  End of step, and end of job RC will be 16.   

To bypass the propagation of the IDCAMS SET MAXCC  return code to the end of step or end of job, or to bypass the changing of the message severity, use runtime option NOSETPRP.