Why do I get a S0C1 when issuing JCLCheck EJCK or !JCK commands?
search cancel

Why do I get a S0C1 when issuing JCLCheck EJCK or !JCK commands?

book

Article ID: 91926

calendar_today

Updated On:

Products

JCLCheck Workload Automation

Issue/Introduction

SOC1 abend occurs when issuing the JCLCheck EJCK or !JCK command. 

Environment

Release: All
Component: JCLCheck Workload Automation

Cause

Most likely due to out-of-sync pointers between module CAZ2CJCL and its aliases.  

Out-of-sync pointers may occur when modules are copied from one load library to another using the TSO/ISPF copy function.

Resolution

  1. Browse the JCLCheck load library for module CAZ2CJCL and note the module SIZE and the TTR values.  
  2. Enter SORT ALIAS on the command line, and scroll up until you see CAZ2CJCL in the column 'Alias-of'.
  3. Compare the size and TTR values of each alias module to CAZ2CJCL.  The module size and TTR values of the alias must be identical to CAZ2CJCL.  If not, copy the correct CAZ2CJCL into your current JCLCheck load library using the IEBCOPY utility.