This section details messages generated by CA Endevor SCM in the course of processing, along with possible causes and corrective actions to take in error situations.
Reason:
An unload request was submitted that specified a ddname that could not be opened.
Action:
Make sure that the ddname was specified correctly.
Reason:
You are not authorized to perform unload/reload processing for the Environment and System identified in this message.
Action:
Contact your administrator.
Reason:
Internal error. A VSAM I/O error occurred while accessing the VSAM cluster identified in the message.
Action:
Check the VSAM feedback code for the action.
Reason:
Informational message. Unload/Reload processing began for the System identified in the message.
Action:
None.
Reason:
No Environment and System combinations were unloaded because all eligible combinations were bypassed due to the Exclude clauses specified on the Unload SCL.
Action:
None.
Reason:
Informational message. Unload/Reload processing has begun for the System, Subsystem, and Stage IDentified in the message.
Action:
None.
Reason:
Informational message. Unload/Reload processing was completed for the Subsystem identified in the message.
Action:
None.
Reason:
An error occurred while attempting to allocate the base library defined for the type identified in the message.
Action:
See the allocation error message that preceded this message.
Reason:
An error occurred while attempting to allocate the delta library defined for the type identified in the message.
Action:
See the allocation error message that preceded this message.
Reason:
Informational message. Unload/Reload processing was completed for the Environment and System identified in the message.
Action:
None.
UNABLE TO FIND A MATCHING TYPE FOR TYPEID type id
Reason:
During Unload processing an Element was found that does not have a type definition.
Action:
Contact your administrator.
Reason:
Informational message. Unload/Reload processing has been completed for the Element identified in the message.
Action:
None.
Reason:
Informational message. Unload/Reload processing has started for the Element and type identified in the message.
Action:
None.
Reason:
Informational message. Unload/Reload processing has started for the Stage IDentified in the message.
Action:
None.
Reason:
Informational message. Unload/Reload processing has started for the Environment identified in the message.
Action:
None.
Reason:
The Element identified in this message has failed validation. Preceding messages provide more information about the cause of the validation failure. This Element will not be unloaded.
Action:
See preceding messages for corrective action.
Reason:
Informational message. An error was detected during component list base/delta validation. Unload/Reload processed the Element without the component list.
Action:
None.
Reason:
Informational message. Unload/Reload processing has begun validating the Element of the type identified in the message.
Action:
None.
Reason:
Informational message. The data set identified in the message has been opened successfully.
Action:
None.
Reason:
Informational message. Indicates beginning of Unload/Reload processing for the Package data set.
Action:
None.
Reason:
Informational message. Indicates completion of Unload/Reload processing for the Package data set.
Action:
None.
Reason:
Informational message. Indicates completion of Unload/Reload processing for the Package identified in the message.
Action:
None.
Reason:
Informational message. Unload/Reload is processing the data set identified in the message.
Action:
None.
Reason:
Informational message. Indicates completion of Unload/Reload processing for the destination identified in the message.
Action:
None.
Reason:
An error was detected writing the named Package to the Package file.
Action:
See associated messages for corrective action.
Reason:
An error was detected writing the named destination to the Package file.
Action:
See associated messages for corrective action.
Reason:
The unload/reload utility has found but cannot open the C1SCL1 ddname.
Action:
Make sure that the DDNAME is specified correctly in the JCL.
Reason:
The unload data set LRECL is too small for the named type.
Action:
Make sure that the unload data set LRECL is at least 84 bytes larger than the largest type record length that will be unloaded.
Reason:
CA Endevor SCM unload processing has terminated and one or more critical errors were encountered during processing.
Action:
Check for E-level messages in the unload output. Some inventory areas may have been unloaded successfully while others may have been unloaded partially or not at all. Correct the errors and rerun a full unload or an incremental unload of the inventory areas that were not unloaded successfully.
Reason:
CA Endevor SCM has encountered a critical error during reload processing and terminated execution.
Action:
Check for previous E-level messages in message log and fix. Contact your administrator.
Reason:
An abend has occurred during unload or reload processing.
Action:
Contact your administrator.
Reason:
The named type is missing from the named Environment.
Action:
Make sure that you've spelled the type name correctly. Otherwise, contact your administrator.
Reason:
The unload data set must be a variable block file.
Action:
Specify a variable blocked data set or redefine this data set as "VB".
PROCESSING FOR ENV Environment name SYSTEM System name TERMINATED
Reason:
An attempt to reload an Element from a backup tape failed. The inventory location was found, but there is a conflict between the Element on disk and the Element on tape. The validation routine determined the Element on disk is newer than the Element being reloaded and failed the action.
Action:
Performing this action will cause regression of this Element. If it is absolutely necessary to reload the backup version, delete the existing version from the inventory area and re-execute the RELOAD action.
Reason:
Internal error. An entry for this Element is missing from the catalogue. This error was detected by the UNLOAD utility.
Action:
Contact your administrator.
Reason:
While uploading this Element, it was determined that the FROM data set information does not exist. This may be a normal condition, depending upon how this Element was created.
Action:
None.
Reason:
While uploading this Element, it was determined that the TO data set information does not exist. This may be a normal condition, depending upon how this Element was created.
Action:
None.
Reason:
The Environment and System identified in the message was excluded from Unload processing because of an Exclude clause in the Unload SCL.
Action:
None.
No Environment/Systems were unloaded, because all eligible Environment and System combinations were bypassed due to the specified EXCLUDE clauses.
Reason
Informational message. This is an explanatory message that follows a Package error message during Unload. It is issued due to the incorrect termination of the last Package action (either Reset, Commit or Delete) which caused the previous error.
Action
Either reload the backup version of the Package, or re-execute the last Package action that did not complete correctly.
Reason:
A syntax error was found in the unload SCL. If the "checkpoint only" option is specified, "unload full" must also be specified.
Action:
Correct the syntax and rerun the job.
Reason:
There are no Systems which match "System name mask" for the named Environment.
Action:
Make sure that the Environment/System combination was correctly specified.
Reason:
The named System is not defined to the named Environment.
Action:
Make sure that you have specified the Environment and System names correctly. Define the System to the named Environment if necessary.
Reason:
No Environments have been defined to CA Endevor SCM that meet the criteria of the name mask in the message.
Action:
Make sure that you have specified the name mask correctly.
Reason:
Either you do not have access to this Environment, or the Environment does not exist.
Action:
Correct input request and resubmit.
Reason:
The input request does not specify an Environment and/or a System and/or a ddname.
Action:
Correct the input request and resubmit.
Reason:
You are not authorized to access the Environment specified in the message.
Action:
Contact your administrator.
Reason:
No footprint was found for the member or CSECT.
Action:
Determine the cause of this error before proceeding.
Reason:
The named CSECT has been zapped.
Action:
None.
Reason:
No Elements were found in the MCF with the same name as the Element referenced in the footprint.
Action:
Determine the cause of this error before proceeding.
Reason:
No Elements were found in the MCF with a generate or move date/time that matches the date/time in the footprint.
Action:
Determine the cause of this error before proceeding.
Reason:
The footprint date and time only matched an Element record from an MCF for a previous Stage.
Action:
Determine the cause of this error before proceeding.
Reason:
The footprint date and time only matched an Element record from an MCF for a previous Stage.
Action:
Determine the cause of this error before proceeding.
Reason:
CA Endevor SCM could not find the Environment/Stage location contained in the footprint.
Action:
Determine the cause of this error before proceeding.
Reason:
In the first case the Environment and Stage referenced in the footprint are not on the map route where the Element currently resides. In the second case the Package component validation function has found an explicit component match, but System, Subsystem, or type names change across map locations, so a more recent version of the component may exist at an intermediate Stage.
Action:
In the first case, see your administrator to determine if the footprint Environment and Stage are on another map. In the second case, check intermediate Stages for the presence of the component. If you find the component, regenerate the Element containing the component to pick up the more recent version.
Reason:
The footprint Environment/Stage correlates to an Environment/Stage location higher in the map than the current location of the Element.
Action:
Determine the cause of this error before proceeding.
Reason:
Informational. Displays the CA Endevor SCM interface software level.
Action:
None.
Reason:
Informational message. The tape that has been loaded is not recognized as an unload tape.
Action:
Make sure that the correct tape has been loaded.
Reason:
Informational message. The tape that has been loaded is not recognized as an unload tape.
Action:
Make sure correct tape is loaded.
Reason:
Reload processing terminated for the Environment and System identified in the message because a data set defined on a type definition for that System could not be found.
Action:
Make sure that the data set identified in the message is properly allocated and cataloged.
Reason:
One or more of the data sets defined to the type identified in the message could not be found. This message will be preceded by allocation error messages.
Action:
Make sure that the data sets identified in the preceding message is (are) properly allocated and cataloged.
Reason:
Data set name identified in the message could not be found.
Action:
Make sure that the data set is properly allocated and cataloged.
Reason:
Reload has successfully restored the Element identified in the message to the inventory location identified in the message.
Action:
None.
Reason:
Informational message. The Element was deleted by reload processing because it did not exist at the specified location at the time the unload file was created, and had a create date prior to when the unload file was created. However, if the Element was created after the unload file was created the Element would not be deleted.
Action:
None.
Reason:
Informational message. Reload processing has completed the deletion of the Element identified in the previous message.
Action:
None.
Reason:
One or more Environment/System combinations specified on the Reload request did not exist in the reload input.
Action:
Make sure that the correct Unload/Reload processing occurred and if it did not correct the Environment/System specifications.
Reason:
The reload program detected that no updates were performed. This message can be issued as a result of Environment or System not found.
Action:
None.
Reason:
Informational message. Associated with other messages that more explicitly identify the problem.
Action:
None.
Reason:
The number of statements contained in the base member of the Element is out of sync with the Element Master record.
Action:
If the Element can be browsed, retrieve it, delete it, and add it back into CA Endevor SCM. If the Element cannot be browsed, delete it, and then Restore it from an earlier unload tape or archive file.
Reason:
The Element delta is missing the CA Endevor SCM logical end of file control statement.
Action:
If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and then regenerate the Element to recreate the component list. If the control record for an Element delta is missing, delete the Element and restore it from a prior unload tape or archive file.
Reason:
A CA Endevor SCM control record was found missing from either an Element delta or a component list delta. Subsequent messages will identify which is the case.
Action:
If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and then regenerate the Element to recreate the component list.
If the control record for an Element delta is missing, delete the Element and restore it from a prior unload tape or archive file.
Reason:
A control record was found missing from either an Element delta or a component list delta. Subsequent messages will identify which is the case.
Action:
If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and then regenerate the Element to recreate the component list.
If the control record for an Element delta is missing, delete the Element and restore it from a prior unload tape or archive file.
Reason:
A delta level contains a logically incorrect number of statement inserts and/or deletes.
Action:
If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and then regenerate the Element to recreate the component list.
If the control record for an Element delta is missing, delete the Element and restore it from a prior unload tape or archive file.
Reason:
A delta member contains levels that are physically out of sequence.
Action:
If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and then regenerate the Element to recreate the component list.
If the control record for an Element delta is missing, delete the Element and restore it from a prior unload tape or archive file.
Reason:
The footprint associated with the identified member failed validation.
Action:
If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and then regenerate the Element to recreate the component list.
If the error is associated with the Element, delete the Element and restore it from a prior unload tape or archive file.
Reason:
Informational message. This message is issued to identify an Element that contained errors.
Action:
See associated error messages.
Reason:
Informational message. This message is issued to identify a data set name and member that contained errors.
Action:
See associated error messages.
Reason:
The member identified in the message was found to be empty.
Action:
If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and then regenerate the Element to recreate the component list.
If the error is associated with the Element, delete the Element and restore it from a prior unload tape or archive file.
Reason:
The last level contained in an Element delta member is out of sync with the Element Master record.
Action:
If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and then regenerate the Element to recreate the component list.
If the control record for an Element delta is missing, delete the Element and restore it from a prior unload tape or archive file.
Reason:
The statement count contained in the last level of an Element delta member is out of sync with the Element Master record.
Action:
If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and then regenerate the Element to recreate the component list.
If the control record for an Element delta is missing, delete the Element and restore it from a prior unload tape or archive file.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|