In the past some PTFs were published for old releases of CA7 in order to cure the error CA-7.MAIN - LENGTH CHECK FAILED, R0=nnnnnnnn R1=nnnnnnnn .
If all these PTFs are applied or there isn’t any PTF published for this abend, it is necessary to get the CA7 internal log data spanning the timeframe of the problem and research in it if any command looking like:
has been issued at the same time of the abend.
Here a sample as it can be found in the CA7 log data:
If this is the case, we can say that this command could have caused the abend S0C3.
In fact this possibility is documented in the CA 7 Command Guide, Chapter 2: Commands,
Section 'CANCEL Command' - 'Request, Ready or Active Queue Jobs',
(Optional) Specifies to force the cancellation of the job. If the job to dump the log data set is to be canceled, FORCE=YES must be specified to prevent the job from being resubmitted. FORCE=YES must be used when a job to be canceled shows a status of SKELETON or RETRY. FORCE=YES must be used to cancel a job with connected resources.
Important! Use of this option can potentially cause CA Workload Automation SE to abend; therefore, it should only be used as a last resort
If this is not applicable here, Please open a Case with CA Support.