CA JCLCheck Endevor processing: JCLCheck step ended with RC 12, and error message:
CAY6361S ERROR DURING 'EXECUTION' PHASE OF THE REXX INTERFACE. CODE= '0000, REXX OPTION NEGATED'
CA JCLCheck runtime option STDREXX(rexxexec) is specified. The Rexx Exec member name exists in the SYSEXEC DD allocation, but contains only one statement:
/* REXX */
Release : 12.0
Component : CA JCLCheck workload Automation
Remove CA JCLCheck runtime option STDREXX(rexxexec) when the REXX interface is not used.
Explanation: CA JCLCheck PTF SO07766 added logic to issue a CAY6361S error when JCLCheck fails to initialize the REXX interface. The failure could be due to REXX Exec member not found from the SYSEXEC DD allocation, or an invalid JCLCheck REXX Exec as in this case.
++HOLD comment from PTF SO07766:
This PTF introduces a JCLCheck behavior change.
A new STDREXX call before JCL processing now
occurs. This is a RAW call with $CA.RSTYPE = OPTS.
If the JCLCheck USERDATA option is used the value
will be available in REXX in the $CA.USERDATA variable.
Due to this call occurring before the JCL is read, any
errors in REXX initialization, such as a REXX program
missing from the SYSEXEC DD PDS, will result in JCLCheck
terminating before JCL is read. A CAY6361S error
message will be issued to explain the cause of the
Prior to this change, these errors would only occur
after JCL processing had started and the error would
disable the REXX processing and allow the JCL to
continue. Since this error happens earlier, it prevents
running JCLCheck without the requested STDREXX program.
- Runtime option STDREXX is documented here:
- Sample CA JCLCheck REXX Exec member names are CAZ1REXX and CAZ1REX2 in the CAZ2CLS0 library.