This section lists ECAP messages generated during Concurrent Action Processing, along with possible causes and corrective actions to take in error situations.
Reason:
This message, written before the actions are dispatched, indicates that parallel processing will be used for ADD, UPDATE, MOVE, DELETE, SIGNIN, RETRIEVE, GENERATE, and TRANSFER (CA Endevor SCM to CA Endevor SCM) actions.
Action:
None.
Reason:
A reference to an uncatalogued data set was found in the SCL. Concurrent Action Processing will not be used to process actions. An uncatalogued data set can be a temporary data set, a SYSOUT data set, or a data set with a disposition of NEW. The data set name or the ddname specified is described in text.
Action:
None.
Reason:
This message appears if the user has requested Concurrent Action Processing by specifying a SPAWNCNT greater than zero on C1DEFLTS or by using an EN$CAPnn DD statement on the job JCL, but Global Type Sequencing has not been enabled. CA Endevor SCM will terminate.
Action:
Enable Global Type Sequencing and resubmit the job.
Reason:
You are not authorized to request that Concurrent Action processing be used. Element actions will be processed serially.
Action:
Change the request so that it does not request Concurrent Action Processing, or contact your CA Endevor SCM administrator.
Reason:
The last two digits of the ENCAP$nn DD statement are not valid. The last two digits are used to specify the number of Concurrent Action Processing action request regions to be spawned. The digits must be a two-digit numeric value of 00 or a number between 02 and the SPAWNMAX as defined in C1DEFLTS.
Action:
CA Endevor SCM uses the default number of action request processing regions as specified in the C1DEFLTS SPAWNCNT value.
Reason:
An ENCAP$nn DD statement, which specifies the number of Concurrent Action Processing servers, has been allocated. However Concurrent Action Processing is not enabled because the C1DEFLTS SPAWN parameter is N. The job will continue using nonparallel processing.
Action:
Remove the ENCAP$nn DD statement, or contact your CA Endevor SCM Administrator regarding the C1DEFLTS SPAWN parameter value.
Reason:
An ENCAP$nn DD statement exists in the JCL, but the last two digits specify a value, nn, that exceeds the SPAWNMAX value in C1DEFLTS. The SPAWNCNT value will be used.
Action:
None.
Reason:
A failure occurred when program program-name issued a CAICCI communication request. The #CCI return code and error description are displayed. Concurrent Processing is terminated. Any requests currently being processed are allowed to terminate before CA Endevor SCM terminates.
Action:
Contact your CA Endevor SCM administrator.
Reason:
CA Endevor SCM is terminating because an action ended with a return code that exceeded the STOPRC value, or a server has terminated abnormally.
Action:
Examine the C1MSG1 data set to determine the reason for termination. If the termination occurred because the STOPRC value was exceeded, correct the problem and try again. If a Concurrent Action Processing error occurred, contact your CA Endevor SCM administrator.
Reason:
A failure occurred in the message management component of Concurrent Action Processing.
Action:
Contact your CA Endevor SCM administrator.
Reason:
The action request region has been created. The cci-id uniquely identifies the server.
Action:
None
Reason:
CA Endevor SCM was unable to spawn an action request processing region. The #CCI return code and error description are displayed. CA Endevor SCM terminates. Cci-id identifies the unique name that would have been assigned to the action request region.
Action:
Contact your CA Endevor SCM administrator.
Reason:
The action request region has terminated. To determine the reason it ended unexpectedly, check the previous messages in C1MSGS1 in both the request routing region and action request region, as well as the JES log of the action request processing address space.
Action:
Contact your CA Endevor SCM administrator.
Reason:
The maximum response time for an action was nnnn seconds. The action that incurred this time is Action # Statement#. This message is displayed after concurrent action processing completes.
Action:
None.
Reason:
The average response time across all action requests, that were processed by concurrent action processing is nnnn seconds.
Action:
None.
Reason:
The minimum response time for an action was nnnn seconds. The action that incurred this time was Action # Statement#.
Action:
None.
Reason:
The total of all response time values for all actions that were processed using Concurrent Action Processing.
Action:
None.
Reason:
The amount of time that elapsed between the dispatch of the first action processed until the completion of the last action processed by Concurrent Action Processing.
Action:
None.
Reason:
The action request region has terminated.
Action:
None.
Reason:
The Concurrent Action Processing Facility has terminated. All acquired resources have been released.
Action:
None.
Reason:
The C1DEFLTS module in the action request region is not the same C1DEFLTS used in the request routing region. The timestamp value is used to determine whether the modules match.
Action:
Either change the started task procedure or change the request routing region job’s JCL.
Reason:
Not all C1MSGS1 messages for action #nnnn statement #nnnn were received from the action request region. This was probably due to an error in that address space.
Action:
Examine the output of the action request region for any error messages. Contact your CA Endevor SCM administrator.
Reason:
Although Concurrent Action processing was requested, it cannot be used, for the reason explained in reason. Actions will be performed serially.
Action:
Correct the problem described in the message.
Reason:
An unexpected error occurred in module routine. The error is explained in description.
Action:
Contact your CA Endevor SCM administrator.
Reason:
This message shows the complete 30 character CAICCI ID of an action request region. It follows those messages that display server information but list only the abbreviated 8 byte id of the action request region.
Action:
None.
Reason:
The Command Handler task, which receives and processes MVS commands for Concurrent Action Processing, has ended unexpectedly. The text contains the failure reason.
Action:
Contact your CA Endevor SCM administrator.
Reason:
An EN$CAP01 DD statement was specified in the JCL. The number of action request regions must be 0 or a number between 2 and the SPAWNMAX as defined in C1DEFLTS. Actions will be processed serially.
Action:
Correct the EN$CAPnn DD statement.
Reason:
You issued an MVS Modify command to the Concurrent Action Processing main job. The text shows the command you entered. The command will be processed and the results displayed.
Action:
None.
Reason:
Concurrent Action Processing was requested for the Element actions, but the SCL specified only one action that was eligible for concurrent processing. Because this action contains no wildcards or placeholders, only one Element will be processed. There would be no benefit in using Concurrent Action Processing to process one Element, and so it is not used. Actions are processed serially.
Action:
Remove the EN$CAPnn DD card from the job to request serial processing of actions or include more actions that are eligible for Concurrent Action Processing (ADD, UPDATE, DELETE, RETRIEVE, MOVE, GENERATE, SIGNIN, TRANSFER from CA Endevor SCM to CA Endevor SCM).
Reason:
A spawned action has exceeded the timeout limit.
Action:
The message indicates the jobname and job number of the spawned STCs that timed out. Use this information to search the main job log to see the action, Element, and inventory location of the timed-out action. Information is also available in C1MSGS1.
Reason:
One or more spawned actions have exceeded the timeout limit. A quiesce of all STCs is forced and the tasks are terminated.
Action:
The main job log and ECAP033I messages in C1MSGS1 provide information about the timed-out STCs. Check the main job and the STCs to try to determine the source of the contention.
Reason:
This message lists the eight-byte abbreviated CCI ID for the request routing region address space, as well as the jobname and jobnumber.
Action:
None.
Reason:
This message is issued at the very beginning of every new action that runs in a spawned STC, identifying the jobname and the STC number of the STC where the action is being processed.
Action:
None.
Reason:
The action and statement number associated with the error message immediately preceding this message.
Action:
None.
Reason:
The user issued an MVS MODIFY command but the syntax of the message was not recognized. The first 30 bytes of the invalid command are shown in text.
Action:
Enter a valid command.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|