This section details messages generated by the Load Utility in the course of processing, along with possible causes and corrective actions to take in error situations.
Reason:
Informational message. This message appears in the CA Endevor SCM Load Execution Log and indicates that the load procedure completed successfully.
Action:
None.
Reason:
An error was found when parsing the input data or attempting to load or footprint members. Processing was terminated.
Action:
Correct the problems related to parsing the input data, loading, or footprinting members. See also the preceding messages.
Reason:
Data errors were found in the request designated in the message. This message is followed by a second message indicating the exact problem.
Load execution is not attempted when data errors exist.
Action:
Correct the problem indicated by the message, and then resubmit.
Reason:
An invalid action was specified in the syntax request. The only valid action is LOAD MEMBER; this is a required clause. You can also request that the members be footprinted, by using the optional FOOTPRINT clause.
Action:
Respecify the request, and then resubmit.
Reason:
The (first) member requested contains invalid characters.
Action:
Check your data and enter the member name again.
Reason:
The THROUGH member name specified contains invalid characters.
Action:
Check your data and reenter the name.
Reason:
Either a FROM DSNAME contains invalid characters, or it was not specified in a SET FROM DSNAME statement and it was not entered in the actual LOAD request.
Action:
Reenter a valid FROM DSNAME statement with this action.
Reason:
This Environment name contains invalid characters.
Action:
Check your data and reenter the name.
Reason:
This System name contains invalid characters.
Action:
Check your data and reenter the name.
Reason:
This Subsystem name contains invalid characters.
Action:
Check your data and reenter the name.
Reason:
This type name contains invalid characters.
Action:
Check your data and reenter the name.
Reason:
This processor group does not exist in the Environment specified in the LOAD request.
Action:
Check your data and enter an appropriate group name.
Reason:
This Environment name does not exist in the C1DEFLTS Table.
Action:
Check your data and either add this name to the C1DEFLTS Table or change the Environment name.
Reason:
Either the security Package at your installation or CA Endevor SCM authorization denied access to this Environment.
Action:
For more information about setting up both native security and external security interfaces, see the Security Guide.
Reason:
This System does not exist in the Environment specified in the LOAD request.
Action:
Check your data and enter an appropriate System name.
Reason:
This Subsystem does not exist in the Environment specified in the LOAD request.
Action:
Check your data and enter an appropriate Subsystem name.
Reason:
This type does not exist in the Environment specified in the LOAD request.
Action:
Check your data and enter an appropriate type name.
Reason:
This member name cannot be found in the FROM data set specified in the LOAD request.
Action:
Check to see where the member exists and reenter the member or the FROM data set, as appropriate.
Reason:
The data set name specified in the LOAD request is not a valid data set type.
Action:
Specify a data set that is either a partitioned data set, a CA Librarian file, a CA Panvalet file, or a sequential data set.
Reason:
The data set specified cannot be allocated by the LOAD utility.
Action:
For complete information about data set allocation, see the Installation Guide.
Reason:
The data set specified in this message was allocated by the LOAD utility, but cannot be deallocated successfully.
Action:
Contact your administrator.
Reason:
A FOOTPRINT data set was not previously established by a SET FOOTPRINT statement, nor was it entered in the actual LOAD request. If you enter the FOOTPRINT clause, you must specify a data set name.
Action:
Specify a data set name, and then resubmit.
Reason:
The data set specified in the FOOTPRINT clause cannot be found in your System catalog.
Action:
Check your entry and code an appropriate data set name.
Reason:
The Stage specified in the LOAD request was not defined in the Environment specified for the request.
Action:
Check your data and enter the appropriate Stage ID.
Reason:
This processor group name contains invalid characters.
Action:
Make sure you know the correct name and reenter the name.
Reason:
Informational message. This message appears after each LOAD request in the Data Report, and lists the total number of errors found in each request.
Action:
None.
Reason:
Informational message. This message lists the total number of errors found in all LOAD requests in the CA Endevor SCM Data Validation Report.
Action:
None.
Reason:
An attempt to open the data set related to the specified DDname failed.
Action:
Refer to the appropriate IBM documentation for your operating System for a list of applicable return codes and their meanings.
Reason:
Informational message. When requests are flushed, the return code is 0004. This is a warning that a request was ignored and processing continues.
Action:
None.
Reason:
Starting member location (PDS range) must be less than that of the end member.
Action:
Check input and change member specifications as necessary.
Reason:
Informational message. This message indicates the beginning of the load execution process for a particular LOAD request. The request number is automatically assigned by the System for identification purposes only.
Action:
None.
Reason:
Informational message.
Action:
None.
Reason:
Informational message. This message indicates when load processing actually begins for the LOAD request.
Action:
None.
Reason:
Informational message. This message indicates that the member specified was loaded successfully.
Action:
None.
Reason:
The load process failed for the member specified and processing terminated for this member. Processing continues for the remaining members (if any) in the request.
Action:
None.
Reason:
Informational message. This message indicates that the load process ended for this particular LOAD request. For the return code for this request, see the CA Endevor SCM Load Execution Summary report.
Action:
None.
Reason:
The member shown was already loaded into the Environment designated in the LOAD request. Processing continues for the remaining members (if any), beginning with the next member in the request.
Action:
None.
Reason:
Informational message. This message indicates that the member shown is currently being footprinted in the data set specified.
Action:
None.
Reason:
Informational message. This message indicates that the member shown was footprinted successfully.
Action:
None.
Reason:
The footprint process failed for the member shown.
Action:
Review the accompanying messages to see why the member was not footprinted.
Reason:
Informational message. This message indicates that processing completed for this particular load request, with the return code shown.
Return codes are defined as follows:
Action:
None.
Reason:
Informational message. This message reflects the total number of members processed for this load request.
Action:
None.
Reason:
Informational message. This message shows, out of the total number of members requested, the number of members loaded successfully and the number of members for which the load failed.
Action:
None.
Reason:
Informational message. The LOAD utility attempts to footprint only those members eligible for footprinting; that is, those members loaded successfully and for which a FOOTPRINT clause or SET FOOTPRINT statement was coded. This message lists the total number of members for which footprinting was attempted, as well as the number of (eligible) members for which footprinting failed.
Action:
None.
Reason:
Informational message. A return code of greater than 12 caused the job to terminate.
Action:
None.
Reason:
The load utility failed while deallocating either one of the footprint data sets or the FROM data set.
Action:
Contact your administrator.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|