This section details messages generated by CA Endevor SCM reporting utilities in the course of processing, along with possible causes and corrective actions to take in error situations.
Reason:
An invalid base or delta record was encountered for the named Element.
Action:
Contact your administrator.
Reason:
Indicates that the report processing initialization logic encountered an error. This message may or may not be preceded by one of the errors documented in this manual.
Action:
If another message does precede C1BR1000:E001, see the description of that message for instruction to resolve the problem. Otherwise, contact your administrator.
Reason:
Indicates that the report processing (command analysis phase) encountered an error.
Action:
Note that this message is preceded by another message, which is documented elsewhere in this manual. See the description of that first error message for instruction to resolve the problem.
Reason:
Indicates that the report processing (data extraction phase) encountered an error.
Action:
Note that this message is preceded by another message, which is documented elsewhere in this chapter. See the description of that first error message for instruction to resolve the problem.
Reason:
Indicates that the report processing (data formatting phase) encountered an error.
Action:
Note that this message is preceded by another message, which is documented elsewhere in this chapter. See the description of that first error message for instruction to resolve the problem.
Reason:
You specified report or extract number nnnnn, which is not supported.
Action:
Be sure that the copy of CA Endevor SCM that you are running is the same as is documented in the User Guide; correct the input and resubmit the job.
Reason:
Indicates that the data extraction phase of report processing encountered an error while reading the Master Control File.
Action:
This message is preceded by another message, which is documented elsewhere in this chapter. See the description of that first error message for instruction to resolve the problem.
Reason:
Indicates that the data extraction phase of report processing encountered an error while reading the BSTSMF data file.
Action:
This message is preceded by another message, which is documented elsewhere in this chapter. See the description of that first error message for instruction to resolve the problem.
Reason:
Indicates that the data extraction phase of report processing encountered an error while reading the BSTPDS data file.
Action:
This message is preceded by another message, which is documented elsewhere in this chapter. See the description of that first error message for instruction to resolve the problem.
Reason:
Indicates that the data extraction phase of report processing encountered an error while reading the Package data set for the Environment.
Action:
This message is preceded by another message, which is documented elsewhere in this chapter. See the description of that first error message for instruction to resolve the problem.
Reason:
Indicates that the data extraction phase of report processing encountered an error while reading the Master Control file (during unload) or the BSTUNLD file (during reload).
Action:
This message is preceded by another message, which is documented elsewhere in this chapter. See the description of that first error message for instruction to resolve the problem.
Reason:
An unexpected status was received from an internal $IMR request, returning the message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, and then resubmit your request.
Reason:
An unexpected status was received from an internal $IMR request, returning the message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, and then resubmit your request.
Reason:
An unexpected status was received from an internal $IMR request, returning the message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, and then resubmit your request.
Reason:
An unexpected status was received from an internal $IMR request, returning the message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, and then resubmit your request.
Reason:
An unexpected status was received from an internal $IMR request, returning the message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, and then resubmit your request.
Reason:
An unexpected status was received from an internal $IMR request, returning the message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, and then resubmit your request.
Reason:
An unexpected status was received from an internal $IMR request, returning the message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, and then resubmit your request.
Reason:
An unexpected status was received from an internal $IMR request, returning the message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, and then resubmit your request.
Reason:
An unexpected status was received from an internal $IMR request, returning the message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, then resubmit your request.
Reason:
CA Endevor SCM was unable to open the extract data set from BC1PFOOT.
Action:
Make sure that the footprint DDname in the SCL is the same as the DDNAME specification in the JCL.
Reason:
CA Endevor SCM requires the footprint file to be a sequential data set.
Action:
Ensure that the DCB attributes refer to a sequential data set.
The following messages are generated by the Package shipment utility in the course of processing. Possible causes and recommended corrective actions are described along with each message.
Reason:
Informational message. This message identifies the Package id being shipped. See other message(s) associated with it.
Action:
None.
Reason:
Warning message. This message indicates that a USS file of a Package being shipped has been superseded by another Package. The USS path and file name follows this message.
Action:
Verify the status of this file.
Reason:
The path name identified in the message prior to this message was found to be excluded by the mapping rule for the shipment to the named destination.
Action:
See the Package Guide.
Reason:
A path name mapping rule was applied to a host CA Endevor SCM output path and the resultant remote path name was found to be invalid. The path name is shown on the message prior to this one.
Action
Examine the path name for errors. Correct the path mapping rule or add a more specific rule to handle this particular name.
Reason:
The Path name listed in the message prior to this one did not pass validation. The host path name may not exist. See prior errors for more detail.
Action:
See prior messages for more detailed information.
Reason:
An error occurred when writing UNIX shell commands to the STDPARM DD statement dataset during Package shipment.
Action:
More information may be available prior to this message. If the problem cannot be resolved contact CA technical support..
Reason:
While attempting to create the PAX dataset for shipment of host USS staging files, the BPXBATCH utility either abended or encountered an abnormal situation.
Action:
Check the STDERR data set for the reason. Also examine all prior messages and the JES log for further information.
Reason:
The ship request was denied for the specified Package, because the specified Element was last changed outside of Package processing.
Action:
Create a new Package relationship for the Element through the Cast and Execute actions.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|