This section details messages generated in the course of processing, along with possible causes and corrective actions to take in error situations.
Reason:
CA Endevor SCM was unable to obtain sufficient working storage for the component indicated by return code. Reason codes and their meanings are as follows:
Action:
Resubmit the request, specifying a larger region size on the job statement. If the error occurred during foreground processing, log on to TSO with a larger region size.
Reason:
The PARM= value in a processor step is greater than 100 characters in length. The maximum is 100 characters.
Action:
Reduce the value of the PARM= parameter and resubmit the request.
Reason:
The request specified a CA Endevor SCM Stage name which was not defined, or was specified incorrectly.
Action:
Verify the Stage name specification in the request. If necessary, contact your administrator.
Reason:
The USERID or JOBNAME attempting the request was not defined to CA Endevor SCM. If this message was generated in a background request, the JOBNAME corresponds to a USERID that was not defined to CA Endevor SCM.
Action:
Contact your administrator to define the USERID or JOBNAME, or both.
Reason:
The USERID associated with the request is not authorized for the requested action for the System, Subsystem, or Element specified in the request. Access to a System, Subsystem, or Element is defined on the basis of USERID for one or more actions and one or more Systems and Subsystems in the Environment. Native security - action violation.
Action:
Verify that the System, Subsystem, and Element name were specified correctly in the request. If necessary, contact your administrator to request access privileges.
Reason:
Informational message. This user is not authorized to perform a function of Environment/System/Subsystem.
Action:
None.
Reason:
The user specified in the request is not authorized to access the specified Element at the specified location. Native security - resource violation.
Action:
Verify that the Element name, System and Subsystem were specified correctly in the request. If necessary, contact your administrator to request access privileges.
Reason:
Informational message. This user is not authorized to access Environment/System/Subsystem.
Action:
None.
Reason:
A security violation was detected. The user is not allowed to perform this action based on the ESI security rules defined.
Action:
Verify all the information you specified is correct. If so, have your CA Endevor SCM or security administrator view the security violation written to the security violation log to determine the reason for the violation.
Reason:
Informational message. Previous messages in the report contain detailed information relating to the security violation.
Action:
None.
Reason:
The Environment name specified is not defined in the defaults table or users are attempting to access an Environment for which they are not authorized.
Action:
Contact your administrator, if required.
Reason:
Informational message. This user is not authorized to access this resource.
Action:
None.
Reason:
Internal error. A problem occurred when CA Endevor SCM attempted to resolve a symbolic parameter in the data set or path name.
Action:
Contact your administrator.
Reason:
The data set named in the message was not defined on the type record named in the message.
Action:
Define the data set on the type record.
Reason:
The data set [DSN] has an organization [DSORG] which is not supported by CA Endevor SCM. Supported data set types are partitioned, sequential, CA Librarian, and CA Panvalet. The requested action cannot be performed.
Action:
Make sure that the data set was correctly specified. If necessary, correct the request and resubmit.
Reason:
The data set dsname has a record format that is not consistent with the action requested.
Action:
Make sure that the data set was correctly specified. If necessary, correct the request and resubmit.
Reason:
A data set dsname associated with the processing of requests for Element type name has attributes which are not valid for this request. No further processing was attempted for all Elements remaining in the request data set member for type name.
Action:
Make sure that the data set was correctly specified. If necessary, correct the request and resubmit.
Reason:
An action request specified an Element type that was not defined for the named System and Stage.
Action:
Verify the Element type definition for the requested System at both Stages. Make sure that the action requested specified the Element type correctly. Resubmit the request if necessary. If a type must be defined, or a type definition must be modified, contact your administrator.
Reason:
A step in the current processor which executes a copy procedure was not executed. The source data set for the copy is identified by ddname1 (record format format1), and the destination by ddname2 (record format format2). The Copy request was not be executed because format1 and format2 were not compatible with each other.
Action:
Verify the attributes of both data sets, and make sure that both are correctly specified. Contact your administrator to correct any data sets which may be incorrectly specified. Resubmit the request after the data sets in question are corrected.
Reason:
Internal error.
Action:
Check to make sure that the C1DEFLTS order matches the map order.
Reason:
A dynamic allocation error occurred for data set [DSN] whose return code is [RRRR] and whose reason code is [NNNN in decimal). Refer to the appropriate IBM documentation for your operating System for a definition of the return and reason codes.
Action:
Correct the condition indicated by the return and reason codes and resubmit the request. If the problem continues, contact the appropriate Systems programming personnel.
Reason:
An attempt to perform an action against a member of a partitioned data set that is currently in use by another user is not permitted until the other user finishes using the member in question. It is also possible that the Element is in use by you if you are in split-screen mode.
Action:
Wait until the user finishes using the member you are attempting to perform an action against, and then retry the action.
Reason:
An improper Stage definition was attempted against the VSAM data set name shown in the message. The specified data set name may be improperly allocated.
Action:
Review steps required to define Stages as described in the Administrator Guide.
Reason:
The CONDELE utility cannot process data sets with the attributes of the named data set.
Action:
Adjust the attributes of the named data set then resubmit the action request.
Reason:
CA Endevor SCM attempted to read from or write to a data set but was unsuccessful.
Action:
If the library accessed was a CA Panvalet or a CA Librarian library, the C1DEFLTS table is not properly defined. Review steps required to define access to CA Panvalet or CA Librarian as described in the Administrator Guide. If the C1DEFLTS table contains proper definition for CA Panvalet or CA Librarian access, make sure that the correct C1DEFLTS load module is accessed.
Reason:
CA Endevor SCM attempted to read from or write to a data set but was unsuccessful. This is a continuation of message C1E0120E.
Action:
If the library accessed was a CA Panvalet or a CA Librarian library, the C1DEFLTS table is not properly defined. Review steps required to define access to CA Panvalet or CA Librarian as described in the Administrator Guide. If the C1DEFLTS table contains proper definition for CA Panvalet or CA Librarian access, make sure that the correct C1DEFLTS load module is accessed.
Reason:
The named DSORG is invalid for the named data set.
Action:
Reallocate the data set with the correct data set organization.
Reason:
The U record format is not supported for the named data set.
Action:
Reallocate the data set with another record format.
Reason:
The processor group specified for the action was not located.
Action:
Specify a valid processor group name, and then resubmit the request.
Reason:
"No" was specified for the foreground execution option on the processor group.
Action:
Contact your administrator to determine why this processor cannot run in foreground, or rerun the action in batch.
Reason:
You are attempting to access a member that is currently in use by another user. CA Endevor SCM will attempt to access this member several times, and then fail if the member is still in use.
Action:
None. If the job fails, try again later.
Reason:
The retrieve action is not compatible with ELIB files.
Action:
Correct the data set specification in the request and resubmit the request.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|