Running CA JCLCheck, foreground or batch, against a jcl stream, we can get an abend S0C7 in module CAZ1SSF followed by an abend S0C4 in module CAZ2CJCL and the scan activity abnormal terminates.

Document ID:  TEC1941834
Last Modified Date:  07/14/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA JCLCheck Workload Automation

Releases

  • CA JCLCheck Workload Automation:Release:12.0

Components

  • CA JCLCheck workload Automation:JCLCHK
Issue:

Running CA JCLCheck, foreground or batch, against a jcl stream, we can get an abend S0C7 in module CAZ1SSF followed by an abend S0C4 in module CAZ2CJCL and the scan activity abnormal terminates, as below reported:

 

2:14:27 ACF9CCCD USERID U000000 IS ASSIGNED TO THIS JOB - JOBJCLJB 
12:14:27 IEF403I JOBJCLJB - STARTED - TIME=12.14.27 
12:14:28 IRX0250E System abend code 0C7, reason code 00000000. 
12:14:28 IRX0254E Abend in external subroutine CAZ1JRXI. 
12:14:28 IEA995I SYMPTOM DUMP OUTPUT 
12:14:28 SYSTEM COMPLETION CODE=0C7 REASON CODE=00000000 
12:14:28 TIME=12.14.28 SEQ=00124 CPU=0000 ASID=0037 
12:14:28 PSW AT TIME OF ERROR 078D1000 80171518 ILC 4 INTC 07 
12:14:28 ACTIVE LOAD MODULE ADDRESS=0016F870 OFFSET=00001CA8 
12:14:28 NAME=CAZ1SSF 
12:14:28 DATA AT PSW 00171512 - 30004F10 D2788910 000158F0 
12:14:28 AR/GR 0: 00000000/00000000 1: 00000000/00108200 
12:14:28 2: 00000000/00111010 3: 00000000/2130078C 
12:14:28 4: 00000000/00000001 5: 00000000/213006B0 
12:14:28 6: 00000000/213006B0 7: 00000000/000FDC70 
12:14:28 8: 00000000/21301BAC 9: 00000000/2130181C 
12:14:28 A: 00000000/00170870 B: 00000000/0016F870 
12:14:28 C: 00000000/00108000 D: 00000000/00111770 
12:14:28 E: 00000000/8016FBB0 F: 07000000/009F8460 
12:14:28 END OF SYMPTOM DUMP 
12:14:28 IRX0040I Error running CAZ1REXX, line 52: Incorrect call to routine 
12:14:28 IEA995I SYMPTOM DUMP OUTPUT 
12:14:28 SYSTEM COMPLETION CODE=0C4 REASON CODE=00000004 
12:14:28 TIME=12.14.28 SEQ=00125 CPU=0000 ASID=0037 
12:14:28 PSW AT TIME OF ERROR 078D0000 0009043A ILC 4 INTC 04 
12:14:28 ACTIVE LOAD MODULE ADDRESS=00010088 OFFSET=000803B2 
12:14:28 NAME=CAZ2CJCL 
12:14:28 DATA AT PSW 00090434 - 317ABFAF CB7C4780 317A41AA 
12:14:28 GR 0: 00000010 1: 00134138 
12:14:28 2: 00107148 3: 000903B8 
12:14:28 4: 00000000 5: 00000000 
12:14:28 6: 00134138 7: 00000000 
12:14:28 8: 00000000 9: 00000000 
12:14:28 A: 00109AC0 B: 00000000 
12:14:28 C: 00000000 D: 001347D8 
12:14:28 E: 00FDA9D8 F: 000903B8 
12:14:28 END OF SYMPTOM DUMP 
12:14:28 IEF450I JOBJCLJB JCLCHECK - ABEND=S0C4 U0000 REASON=00000004 
12:14:28 TIME=12.14.28 
12:14:28 AMS0000I: STEP END JOBJCLJB.JCLCHECK RC=S0C4 CPU= 0.20 SEC. 
12:14:28 IEF404I JOBJCLJB - ENDED - TIME=12.14.28 

 

How to correct this situation? 

Environment:
CA JCLCheck 12.0, CA ACF2
Cause:

To correctly setup CA JCLCheck, it is necessary to validate and eventually customize the default ‘Runtime Options’ provided at installation time, per the local standards.

These options define checking capabilities for things such as the security environment, the source of the JCL, alternate processing activities, or the report types you want CA JCLCheck to issue after it checks your JCL.

Runtime options are an integral part of CA JCLCheck and are covered in detail in CA JCLCheck Runtime Options section of the CA JCLCheck 12.0 Command Reference Guide. They can be changed using the following methods:

? ISPF online panels

? Supplementary OPTIONS file (OPTS=), if one is available

? PARM= field in the CA JCLCheck execution JCL EXEC statement

 

There are some very rare cases in which, a wrong setup of these options can generate an abnormal termination of CA JCLCheck activity against jcl streams but no evident messages are got about the wrong option values set. 

An abend in module CAZ1SSF is probably related to a wrong setup of Security Validation Options. 

Resolution:

The SECURE Runtime option requests support of the pre-validation of the security environment. This option has the following format: 

SECurity(options)|NOSECure

Default: NOSECure

Use options to modify security checking. Specifying the Security option automatically activates various pre-validation checks.

 

If this option is in effect, You can specify also the runtime options DATEFMT(EURO) and RUNDATE for future run date and time to use for security validation in a date format which is not the default US layout mm/dd/yy. They are only valid for ACF2 security product.

If runtime option DATEFMT(EURO) is in effect but RUNDATE is not specified or it is specified without a valid date/time value, then every CA JCLCheck scan against a jcl stream, both batch and foreground, abnormally ends with the abend S0C7 in CAZ1SSF, followed by a S0C4 in CAZ2CJCL.

To bypass this abend there are two possibilities:

 

1.    If DATEFMT(EURO) should be used, then it is mandatory to correctly setup the Runtime option RUNDATE, providing a valid date/time value as documented in our CA JCLCheck 12.0 Command Reference Guide.

2.    Otherwise both DATEFMT(EURO) and RUNDATE runtime options should be removed so that the default values NODAtemf and NORUNDt are used.

 

If, after this suggestion, the message occurs again, please open a Case with CA Support.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >