This section details messages generated by footprint validation in the course of processing. It also describes the possible causes and corrective actions to take in error situations.
Reason:
The input component validation processing has detected an error.
Action:
Review the other validation messages for details.
Reason:
The input component validation processing has detected an error.
Action:
Review the other validation messages for details.
Reason:
CA Endevor SCM has found no Master Control File records that match the Element name in the footprint.
Action:
Contact your administrator.
Reason:
No Master Control File records for the Element match the location and event information in the footprint.
Action:
Contact your administrator.
Reason:
Another copy of this component exists at an inventory location prior to the current Stage. This indicates someone may be making changes to this component.
Action:
None. Make sure the changes are unrelated to your changes.
Reason:
Another copy of this component exists at an inventory location prior to the current Stage. This indicates someone may be making changes to this component.
Action:
None. Make sure the changes are unrelated to your changes.
Reason:
The last level date and time information on the footprint do not match the date and time information from the Master Control File.
Action:
Contact your administrator.
Reason:
CA Endevor SCM cannot find the Environment and Stage named in the footprint.
Action:
Contact your administrator.
Reason:
The input component validation processing has detected an error. The Environment and Stage names found in the footprint do not exist in the current C1DEFLTS table.
Action:
Review the other validation messages for details.
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, contact 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 of the component that was used matches a component located in the map, but there is another copy of this component in a prior location of the map that should have been used instead.
Action:
Recompile the program to use the first copy of the component that is found in the map.
Reason:
Internal error. The header of the footprint validation block is invalid.
Action:
Contact your administrator.
Reason:
The processor failed flag is set for this component. This flag is set when the Generate or Move processor associated with this Element fails, or if the NO GENERATE action option was enabled when the Element was added or updated.
Action:
Regenerate this Element, and use the ACM query facility to determine where this Element is used. Regenerate each of the parent Elements.
Reason:
An Element is moved up the map and one of its components was either not generated or its Generate processor has failed. Action completes.
Action:
Verify this Element's components and take appropriate action, if necessary.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|