Performing User Tasks › How Moving an Element Between Inventory Locations Works › How Moving Elements with History Works

How Moving Elements with History Works

When you move an element with history using the Move Elements action, CA Endevor SCM performs the following actions and causes these effects:

1. Determines if the element exists at the source and target location, if the ACKNOWLEDGE ELEMENT JUMP option applies, if source management is necessary, and if processor management is necessary (meaning, a restart situation). If necessary, CA Endevor SCM issues messages in the API Message report.
2. Performs source management by moving the element to the target stage. The processing that CA Endevor SCM performs depends on whether the elements exists at the TO location.
   • If the element does not exist at the target, CA Endevor SCM performs the following steps:
     • Searches the map for subsequent occurrences of the element. If the element is found farther along the map, the base level of the element to be moved is compared with the current level of the subsequent element.
     • If the two levels are in sync, CA Endevor SCM copies back (or fetches) the element up the map to the target location with all delta levels intact.
     • If the two levels are not in sync, CA Endevor SCM issues a warning message and does not perform the copy (as long as the SYNC=N option was specified on the move action). If the SYNC=Y option was specified for the move action and the two are not in synch, CA Endevor SCM issues a warning message and copies the element back to the target location and creates a sync level at the target. The new sync level reflects the differences between the base level of the source element and the current level of the fetched element.

     Note: You can restrict the SYNC=Y option to prevent it from copying the element back to the target by activating the feature DO_NOT_SYNC_AT_TARGET=ON in the optional features table (ENCOPTBL).

     Moves the element with the current level of the source element being moved to the target location, and the source element delta levels are appended to the target.

     If the element is found at a stage that is not included in the map, a warning message is issued, and the search continues for the element in a stage that is included in the map.

   • If the element exists at the target location, CA Endevor SCM performs level-matching. During level-matching, CA Endevor SCM determines the sync point of the source and target elements by comparing the level timestamp of the base level of the source element with the current level of the target element. If the two timestamps do not match, CA Endevor SCM checks the next oldest level of the source element, and so on.
     • If the sync point is found, CA Endevor SCM moves the element from the FROM location to the TO location, appending the FROM location delta levels after the sync-point element.
     • If the two levels are different and SYNC=Y, CA Endevor SCM first creates a sync level at the target reflecting the differences between the base level of the FROM element and the target, and then moves the element to the TO location and appends the FROM location delta levels to the target.
     • If the element does not exist at the target, CA Endevor SCM moves the element from the source to the target location with all delta levels intact.
3. Completes source management after the element base and change levels have been moved by updating the Master Control File (MCF) to reflect the move.

   Note: The value specified for Signout Upon Fetch (the SOFETCH parameter) in the CA Endevor SCM Defaults table (C1DEFLTS) will effect how the MCF for the element copied back will be updated. If Signout Upon Fetch is in effect, the element will be signed out to you unless it is already signed out to someone else. If Signout Upon Fetch is not in effect, the element will not be signed out to you.

4. Completes processor management by determining the processor group last associated with the element, and then executes the move or generate processor in that group if one has been specified. After the processor has been run for the element, CA Endevor SCM updates the processor information in the Master Control file.
5. If the DELETE FROM ELEMENT option is set to Y, CA Endevor SCM executes standard delete processing for the element.