COBOL - Endevor - Move Element - www.cadcobol.com.br



Desenvolvido por DORNELLES Carlos Alberto - Analista de Sistemas - Brasília DF. - cad_cobol@hotmail.com

COBOL - Endevor - Move Element

Moving an Element Between Inventory Locations Using the Move Elements Action

To move an element from one inventory location (environment, stage) to the next location on a map route, you use the Move Elements action (available in foreground, batch, and in packages). Consider the following information when moving elements:

  • You can move elements either with history or without history.
  • You can only move elements from one environment to another if the elements start in Stage 2 of the source environment.
    For example, to move an element from Stage 1 of the Development environment into Stage 1 of the QA environment, you have to move the element to Stage 2 in Development, and then move it into Stage 1 in QA.

This section contains information for performing this development task in the foreground only.

Note: For more information about how to perform this element action in batch, see the SCL Reference Guide.

Another way to move an element is by using packages.
Packages offer some advantages over the Move Elements action, such as being able to validate the package components and prevent elements from being moved until the elements have been assembled, compiled, and linked with current versions of all their dependencies.
Promotion packages are a type of package that contain move actions only and the from environment and stage locations on all the move actions are the same.

Note: For more information about how to move elements using packages, see the Packages Guide.

Note: The Add, Move, Generate, and Signin actions can be performed from the Quick-Edit Option panel, if the CA Endevor SCM Quick Edit option is enabled at your site.
For more information about Quick-Edit, see the Quick Edit Option User Guide.

Considerations When Moving Elements Using a Generate Processor

You can use move processors for the following reasons:

  • To copy outputs (load modules and listings) from the source to the target stage.

  • To recreate load modules at the target stage.
    This happens when a generate processor is used as a move processor.
    If you want to use a generate processor as a move processor, enter G in the PROCESSOR TO USE FOR THE MOVE ACTION option for the appropriate processor group.

Note: Do not recreate load modules at the target stage by coding a compile and link step in a move processor.
If you do, the load module footprint does not sync with Master Control File (MCF) information for the element.
Use the generate processor at the target stage, which will execute the compile and link and update the element's Master Control File.

How Moving Elements Between Inventory Locations Works

When you move an element from one inventory location (environment, stage) to the next location on a map route, the product performs as many of the following processes as necessary.

  • Source management, which involves the actual move of the element and the Master Control File (MCF) updates.

  • Processor management, which involves executing (at the target location) the Move processor of the source processor group or the Generate processor at the target processor group.
    This is determined by the processor group setting at the source location.
    Processing may include writing to a source output library and to the appropriate processor output libraries.

  • Delete processing, which involves executing the Delete processor and deleting the element at the source location of the move.

Note: If a Move action fails, first respond to the error, and then resubmit your request.
When you restart a Move action after a source management failure, the product performs source management, processor management, and delete processing.
After a processor management failure, the product performs processor management and delete processing.
After a delete failure, the product performs delete processing.

How Moving Elements with History Works

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

  1. Determines if the element exists at the source and target location, if the ACKNOWLEDGE ELM JUMP option applies, if source management is necessary, and if processor management is necessary (meaning, a restart situation).
    If necessary, the product issues messages.

  2. Performs source management by moving the element to the target stage.
    The processing that the product performs depends on whether the element exists at the TO location.
    • If the element does not exist at the target, the product 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, the product 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, the product 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 sync, the product 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, the product performs level-matching. During level-matching, the product 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, the product checks the next oldest level of the source element, and so on.
      • If the sync point is found, the product 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, the product 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, the product 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 Defaults table (C1DEFLTS) affects 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. Performs processor management by writing a copy of the element to a source output library, if one is defined for the associated element type at the target location.
    If EXPAND INCLUDES = Y (on the Type Definition panel), the product expands INCLUDE statements in the source.

  5. 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, the product updates the processor information in the Master Control file.

  6. If the DELETE FROM ELEMENT option is set to Y, the product executes standard delete processing for the element.

How Moving Elements Without History Works

You can move an element without history using the Move Elements action by setting the WITH HISTORY option to N in your request.
The product executes the request and attempts to find a sync level between the source and target elements beginning with the first level at the source and working forward through the deltas.
When you move elements without history, the product performs the following actions:

  • If a sync level is found, the elements are compared and a new level is created at the target that reflects the differences.

  • If a sync level cannot be found and you set the SYNC option to N, a message is issued saying that the elements are "out of sync" and the MOVE action terminates.

  • If a sync level cannot be found and you set the SYNC option to Y, an out-of-sync message is issued.
    The product then compares the last level of the source and last level of the target, and creates a new level at the target that reflects the differences.

How Moving Elements Affects the Signout Status

Your site administrator can enable a signout capability on a system-by-system basis.
When you move an element from one inventory location (environment, stage) to the next location on a map route, the product performs the following actions and causes these effects:

  • If the element exists up the map, a fetch is performed.
    • If your site administrator has enabled Signout Upon Fetch, the fetched (source) element (the element at the FROM location of the fetch) is signed out to you, if the element is not signed out to someone else.
      In addition, the target element is signed in.

    • If your site administrator has not enabled Signout Upon Fetch, the fetched (source) element is signed out to you, if the element is not signed out to someone else.
      In addition, the target element is signed in.
  • |
  • If the element does not exist up the map, a fetch is not performed.
    • If your site administrator has enabled Signout Upon Fetch, the target element is signed in.

    • If your site administrator has not enabled Signout Upon Fetch, the target element is signed in

    Note: For more information about Signout Upon Fetch, see the Administration Guide.

How Moving Elements Affects CCIDs and Comments

When you move an element from one inventory location (environment, stage) to the next location on a map route using the Move Elements action (with history and without history), you can specify a CCID and comment.
If you specify a CCID and comment, the product performs the following actions and causes these effects:

  • If you use the Move Elements Action (with history):
    • The Source CCID/Comment is set from the start location value (Stage 1 value).
    • The Generate CCID/Comment is set from the start location value (Stage 1 value).
    • The Last Action CCID/Comment is set.
    • The Retrieve CCID/Comment is cleared.
    • The Source Delta CCID/Comment is carried with delta levels.
    • The Component Delta CCID/Comment is carried with delta levels.

  • If you use the Move Elements Action (without history):
    • The Source CCID/Comment is set from the start location value (Stage 1).
    • The Generate CCID/Comment is set from the start location value (Stage 1).
    • The Last Action CCID/Comment is set.
    • The Retrieve CCID/Comment is cleared.
    • The Source Delta CCID/Comment is set from the last start location delta value.
    • The Component Delta CCID/Comment is set from the last start location delta value.

Move an Element

To move an element from one inventory location (environment, stage) to the next location on a map route, you use the Move Elements action.

Note: Another way to move an element is by using packages.
Packages offer some advantages over the Move Elements action, such as being able to validate the package components and prevent elements from being moved until the elements have been assembled, compiled, and linked with current versions of all their dependencies.
Promotion packages are a type of package that contain move actions only and the from environment and stage locations on all the move actions are the same.
For more information about how to move elements using packages, see the Packages Guide.

Follow the below steps to move an element into different stages.

  1. Start the product using the instructions provided by your site administrator.

    The Primary Options panel appears.

  2. Enter 2 (Foreground) and press Enter.

    The Foreground Options menu appears.

  3. Enter 5 (Move) and press Enter.

    The Move Elements panel appears.

    Note: For more information about a field or option on the panel, press PF1.

  4. Specify the element you want to move, and enter a comment to explain the move.

  5. Complete the following fields:

    Sync

    Enter Y (Yes) or N (No) to indicate whether you want the MOVE action performed when the base level of the element at the source location is different from the current level of the element at the target.
    When you enter Y, the product creates a "sync" level at the target that reflects the differences between the base level at the source location and the current level at the target.
    The move fails if these levels are different and you have specified SYNC = N.

    With History

    Enter Y (Yes) or N (No) to indicate whether you want to move the element with history.
    When you move the element without history, the product searches through the element levels at the source location to find a matching level at the target location.
    The product then compares the two, and creates a new level at the target location that reflects the differences.

    Signout To

    Enter the TSO userid of the person at the target location for which you want to sign out the element.
    If the RETAIN SIGNOUT option is set to Y, you cannot use this option.

    Delete from Element

    Enter Y (Yes) or N (No) to indicate whether you want the product to delete the elements at the source location after moving them.

  6. Press Enter.

    The element is moved to the next location on a map route.


© Copyright CA Technologies.