Move Syntax

Processing Element Actions › The Move Statement › Move Syntax

Move Syntax

►►─ MOVe ELEment ─ element-name ─┬──────────────────────────────┬─ FROm ──────►
                                 └─┬─ THRough ─┬─ element-name ─┘
                                   └─ THRu ────┘

 ►─ ENVironment ─ env-name ─ SYStem ─ sys-name ─ SUBsystem ─ subsys-name ─────►

 ►─ TYPe ─ type-name ─┬─ STAge ─ stage-id ────────┬───────────────────────────►
                      └─ STAge NUMber ─ stage-no ─┘

 ►─┬──────────────────────────────┬───────────────────────────────────────────►
   └─ WHEre ─ ¤ ─┬──────────┬─ ¤ ─┘
                 ├─┤ CCID ├─┤
                 └─┤ PRO ├──┘

 ►─┬────────────────────────────────────────────────┬─ . ─────────────────────►◄
   └─ OPTion ─ ¤ ─┬───────────────────────────┬─ ¤ ─┘
                  ├─ CCId ─ ccid ─────────────┤
                  ├─ COMment ─ comment ───────┤
                  ├─ SYNchronize ─────────────┤
                  ├─ WITh HIStory ────────────┤
                  ├─ BYPass ELEment DELete ───┤
                  ├─┬─ SIGnin ◄ ────────────┬─┤
                  │ ├─ RETAin SIGNOut ──────┤ │
                  │ └─ SIGNOut TO ─ userid ─┘ │
                  └─ JUMp ────────────────────┘

Expansion of CCID

                                                     ┌─ , ────┐
├── CCId ─┬──────────────────────┬─┬───────────┬─ ( ─▼─ ccid ─┴─ ) ────────────┤
          └─ OF ─┬─ CURrent ◄ ─┬─┘ ├─ EQual ◄ ─┤
                 ├─ ALL ───────┤   └─ = ───────┘
                 └─ RETrieve ──┘

Expansion of PRO

                                  ┌─ , ──────────┐
├── PROcessor GROup ─┬─ EQ ─┬─ ( ─▼─ group name ─┴─ ) ─────────────────────────┤
                     └─ = ──┘

MOVE ELEMENT element-name

Indicates the element(s) to be moved. Code the required syntax and enter the appropriate element name. In addition, you can use a name mask with the element name.

THROUGH (THRU) element-name

Indicates that a range of elements should be moved, beginning with the element coded in the MOVE ELEMENT statement, up to and including the element specified in this statement. You can use a name mask with the element name.

FROM ENVIRONMENT env-name

SYSTEM sys-name

SUBSYSTEM subsys-name

TYPE type-name

STAGE stage id

STAGE NUMBER stage-no

The FROM clause indicates the location of the element being moved. CA Endevor SCM uses both the FROM clause in an action and any preceding SET FROM clause to determine the "from" criteria for that action.

A FROM clause in an action overrides values in a SET FROM clause that precedes the action.
If the SET FROM clause contains values that are not included in the FROM clause, CA Endevor SCM uses these values.

You must specify an environment, system, subsystem, type, and stage. You can use a name mask with the system, subsystem and type. The environment name and stage information must be explicit. The stage specification can be either one of the following:

STAGE ID-Enter a single alphanumeric stage identifier.
STAGE NUMBER-Enter either 1 or 2.

Moving sourceless elements: When the Move element is sourceless, the element’s last level timestamp is checked against the next sourced element found up the map. If the timestamps are the same, a sourceless element record will be created at the target location if no element exists. The processor uses the element source data from the next sourced element for its GEN process. If the timestamps are not the same, the move action fails. You will need to take corrective action at this point. You can either delete the sourceless element or regenerate the sourceless element and then follow this by a move.

When the target location has a sourceless element, its last level timestamp is compared with the next sourced element. If the timestamps are not equal, the action fails unless the SYNC option is used.

WHERE

Use the WHERE clause to further qualify element selection criteria. CA Endevor SCM uses both the WHERE clause in an action and any preceding SET WHERE clause to determine the "where" criteria for that action.

A WHERE clause in an action overrides values in a SET WHERE clause that precedes the action.
If the SET WHERE clause contains values that are not included in the WHERE clause, CA Endevor SCM uses these values.

WHERE CCID OF ccid -Limits the processing to those elements that match one of the supplied CCIDs. You can use a name mask in this field.

CURRENT-Tells CA Endevor SCM to look through the CCID fields in the MCF (Master Control File) to find a specified CCID(s). This is the default.
ALL-Tells CA Endevor SCM to search both the Master Control File and the SOURCE DELTA levels for a specified CCID(s). If you have ACM, CA Endevor SCM also searches the COMPONENT LIST DELTA levels for the specified CCID(s). If the element is sourceless , the source element delta level CCID checks are not done, because the element source and delta files are not present.
RETRIEVE-Tells CA Endevor SCM to use the CCID in the Master Control File RETRIEVE CCID field.

If you need to select elements identified under more than one CCID, you can specify multiple CCIDs by enclosing the CCIDs with parentheses and separating them with commas. The CCIDs may extend over multiple lines if necessary.

The next examples illustrate the use of this clause.

  Example 1:  WHERE CCID OF CURRENT (PROJ001, PROJ002, PROJ004)
  Example 2:  WHERE CCID OF ALL (PROJ00V)

WHERE PROCESSOR GROUP group name-This clause allows you to select elements according to a specified processor group. You can use a name mask when specifying the processor group name.

If you need to select elements identified under more than one processor group, you can specify multiple distinct processor group selectors by enclosing the processor groups with parentheses and separating them with commas. The processor groups may extend over multiple lines if necessary.

The next examples illustrate the use of this clause.

  Example 1:  WHERE PROCESSOR GROUP  (COBVS, COBII)
  Example 2:  WHERE PROCESSOR GROUP  (COBV)

OPTIONS

OPTIONS clauses allow you to further specify requests.

CCID ccid/COMMENT comment-You can enter a 1- to 12- character CCID and/or a 1- to 40-character comment.

CCIDs and/or comments may be required. If you do not provide a required CCID and/or comment, the MOVE action fails.

When you specify a CCID and/or comment in a MOVE action, CA Endevor SCM updates the CCID and/or COMMENT fields differently, depending on whether you specify the MOVE action with history or without history.

When you specify a CCID and/or comment in a MOVE action without history, CA Endevor SCM uses this CCID and/or comment to set the last action CCID and/or COMMENT fields. CA Endevor SCM also:

Sets the source and generate CCID and/or COMMENT fields to their value at the source location of the move.
Sets the source and component list delta CCID and/or COMMENT fields to their last value at the source location of the move.
Clears the retrieve CCID and/or COMMENT field.

When you specify a CCID and/or comment in a MOVE action using the WITH HISTORY option, CA Endevor SCM uses this CCID and/or comment to set the last action CCID and/or COMMENT fields.

CA Endevor SCM also does the following:

Sets the source and generate CCID and/or COMMENT fields to their value at the source location of the move.
Clears the retrieve CCID and/or COMMENT fields.
Moves source delta CCIDs and comments with their respective delta levels.
Moves the current version/level of the Component List.
For more information, see Monitoring Components in a Move Processor in the Automated Configuration Option Guide.

SYNCHRONIZE- The SYNCHRONIZE option compensates for differences between the base level of a source element and the current level of a target element. CA Endevor SCM 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. If CA Endevor SCM finds a sync level, it compares the two and creates a new level at the target that reflects the differences. If CA Endevor SCM cannot find a sync level and you specify SYNC, CA Endevor SCM issues an out of sync message. CA Endevor SCM 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.

When moving with history, 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 is specified, 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, then moves the element to the TO location and appends the FROM location delta levels to the target.

WITH HISTORY-The WITH HISTORY option preserves source element change history. If you request MOVE WITH HISTORY, CA Endevor SCM first ensures that the current level of the target element is the same as the base level of the source element. It then moves all levels of the element from source to target, appending the source change history to the target change history.

If you do not code this option, CA Endevor SCM moves the element(s) without history. When you move the element without history CA Endevor SCM searches through the element levels at the source location to find a matching level at the target location. CA Endevor SCM then compares the two and creates a new level at the target location that reflects the differences.

If the base level of the source element differs from the current level at the target, the move fails unless you code the SYNCHRONIZE option.

BYPASS ELEMENT DELETE-This option tells CA Endevor SCM to retain the element in the source stage after successfully completing the move.

SIGNIN-Default. This option tells CA Endevor SCM to sign in all elements at the target stage after successfully completing the move. You must code this option to override SET OPTION RETAIN SIGNOUT or SET OPTION SIGNOUT TO clauses.

RETAIN SIGNOUT-This option tells CA Endevor SCM to retain the source location signouts for all elements at the target location. This option applies only if the element was signed out at the target before the MOVE.

If the element was signed out at the target before the MOVE, it will be signed out to that same ID-at the target-after the MOVE.

If the element was not signed out at the target before the MOVE, it will not be signed out at the target after the MOVE.

If you do not use this option, the element at the target location is not signed out, regardless of whether it was signed out at the target before the MOVE took place.

SIGNOUT TO userid-This option tells CA Endevor SCM to sign all elements out to the specified user ID at the target stage.

JUMP-The JUMP option tells CA Endevor SCM to move elements across environments even if the element exists at an intermediate stage that is not on the map. If the element exists at an intermediate stage, the move fails if REQ ELM JUMP ACKNOWLEDGE=Y at the system level and the JUMP option is not coded.

In either case, CA Endevor SCM issues a message informing you that the element exists in a non-map stage between the source and target stages of the move.

Example: Move SCL

This SCL moves an element from Stage 1. The element history will be retained at the target stage.

MOVE ELEMENT 'PAYRPT17'
     FROM ENVIRONMENT 'PROD'
          SYSTEM 'PAYROLL'
          SUBSYSTEM 'REPORTS'
          TYPE 'COBOL'
          STAGE NUMBER 1
     OPTIONS CCID REQ#43034
          COMMENT 'MOVE INTO PRODUCTION'

          WITH HISTORY.