Diagnosing Endevor message ECAP012S with RC 63

Products

• Endevor

Issue/Introduction

CAP processing (Concurrent Action Processing) requires to start a number of started tasks that process the actions in parallel

The start of these task might raise error message

ECAP012S Concurrent Action Processing cannot spawn <STC_name>  RC 63 Spawned process ended abnormally.

How to do to diagnose the problem?

Cause

The job that requests CAP processing has asked CCI component (which is part of Common Components) to spawn (start) a number of started tasks that will interact with the job and process the actions in parallel

The invoklved STC is properly defined to the CCI Spawn service so it issues a MVS START command to start the STC's. Upon startup, the STC's must respond to CCI to announce that they are ready to process requests.

RC 63 from CCI means that the START command has been successfully issued but there is no response from the spawned STC. The possible causes are:

• The STC failed due to JCL error
• The STC abended during early initialization before having a chance to respond to CCI

Resolution

Look in the JES2 queues for any output produced by "STC_name". If it abended, the output will likely show information about the abend.

If no outputs are found, check MVS SYSLOG for the time since the job requesting CAP processing started until it issued the ECAP012S message.

You should see the "S STC_name" commands issued by CCI from the ENF started task

Right after that, there should be some information about the failure, for example:

• The JCL for the STC could not be found in any PROCLIB library
• The STC failed by JCL error
• If the STC abended, at the very least there will be some message in SYSLOG

This information should allow you to pull the thread and see where the failure is.