►►─ TRAnsfer ELEment ─ element-name ─┬─────────────────────┬──────────────────► └─ VERsion ─ version ─┘ ►─┬─────────────────┬─┬──────────────────────────────┬─ FROm ─┤ DEF ├────────► └─ LEVel ─ level ─┘ └─┬─ THRough ─┬─ element-name ─┘ └─ THRU ────┘ ►─ TO ─┤ DEF ├─┬──────────────────────────┬─┬──────────────────────┬─────────► └─ ELEment ─ element-name ─┘ └─ WHEre ─┬──────────┬─┘ ├─┤ CCID ├─┤ └─┤ PRO ├──┘ ►─┬──────────────────────────────────────────────────────────┬─ . ───────────►◄ └─ OPTION ─┬─────────────────────────────────────────────┬─┘ ├─ CCId ─ ccid ───────────────────────────────┤ ├─ COMment ─ comment ─────────────────────────┤ ├─ NEW VERsion ─ version ─────────────────────┤ ├─ IGNore generate failed ────────────────────┤ ├─ OVErride SIGNOut ──────────────────────────┤ ├─ WITh HIStory ──────────────────────────────┤ ├─ SYNchronize ───────────────────────────────┤ ├─┬─ BYPass GENerate PROcessor ─────────────┬─┤ │ └─ PROcessor GROup ─┬─ EQ ─┬─ group-name ─┘ │ │ └─ = ──┘ │ ├─┬─ BYPass ELEment DELete ───┬───────────────┤ │ └─ BYPass DELete PROcessor ─┘ │ └─┬─ SIGnin ◄ ────────────┬───────────────────┘ ├─ RETain SIGNOut ──────┤ └─ SIGNOut TO ─ userid ─┘
Expansion of DEF
├── ENVIronment ─ environment-name ─ SYStem ─ system-name ────────────────────► ►─ SUBSYStem ─ subsystem-name ─ TYPe ─ type-name ────────────────────────────► ►─┬─ STAge ─ stage-id ────────┬───────────────────────────────────────────────┤ └─ STAge NUMber ─ stage-no ─┘
Expansion of CCID
┌─ , ────┐ ├── CCId ─┬──────────────────────┬─┬───────────┬─ ( ─▼─ ccid ─┴─ ) ────────────┤ └─ OF ─┬─ CURrent ◄ ─┬─┘ ├─ EQual ◄ ─┤ ├─ ALL ───────┤ └─ = ───────┘ └─ RETrieve ──┘
Expansion of PRO
┌─ , ──────────┐ ├── PROcessor GROup ─┬─ EQ ─┬─ ( ─▼─ group name ─┴─ ) ─────────────────────────┤ └─ = ──┘
TRANSFER ELEMENT element-name
Identifies the elements to be transferred. Code the required syntax and enter the appropriate element name. In addition, you can use a name mask with the element name.
Indicates the version and level number you want to transfer. If you want to indicate a version and level, code a full element name. If you use the THROUGH clause, you cannot enter this clause i Acceptable Version numbers are 1-99. Acceptable Level numbers are 00-99. VERSION and LEVEL must be specified together.
If you do not specify a VERSION LEVEL clause, the TRANSFER action transfers all levels to the target location. If you specify this clause, only the VERSION LEVEL you indicate gets transferred.
If the specified VERSION LEVEL is not the current level, the generate processor executes at the target location, regardless of the processor group definition setting.
THROUGH (THRU) element-name
Indicates a range of elements for transfer. The range begins with the element coded in the TRANSFER 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 system-name
SUBSYSTEM subsys-name
TYPE type-name
STAGE stage-id
STAGE NUMBER stage-no
The FROM clause indicates the location of the element being transferred. 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.
Specify an environment, system, subsystem, type, and stage. The environment name must be explicit. You can use a name mask with the system, subsystem, type, and stage. The stage specification can be either one of the following:
TO ENVIRONMENT env-name SYSTEM system-name SUBSYSTEM subsys-name TYPE type-name STAGE stage-id STAGE NUMBER stage-no ELEMENT element-name
The TO clause indicates where the element is being transferred. CA Endevor SCM uses both the TO clause in an action and any preceding SET TO clause to determine the "to" criteria for that action.
The stage specification can be either one of the following:
Enter a different element name if you want to change the element name specified in the TRANSFER ELEMENT clause. If you do not enter an element name here, CA Endevor SCM assigns the FROM location element name.
WHERE
Use WHERE clauses 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.
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.
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 following examples illustrate the use of this clause.
Example 1: WHERE CCID OF CURRENT (PROJ__1, PROJ__2, PROJ__4) Example 2: WHERE CCID OF ALL (PROJ___)
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 following examples illustrate the use of this clause.
Example 1: WHERE PROCESSOR GROUP (COBVS, COBII) Example 2: WHERE PROCESSOR GROUP (COB_)
OPTIONS
OPTIONS clauses allow you to further specify action 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 TRANSFER action fails.
When you specify a CCID and/or comment in a TRANSFER action, CA Endevor SCM updates CCID and/or COMMENT fields differently, depending on whether you specify the TRANSFER request without history, with history, or with synchronization.
When you specify a CCID and/or comment in a TRANSFER action without history, CA Endevor SCM uses this CCID and/or comment to:
CA Endevor SCM also:
When you specify a CCID and/or comment in a TRANSFER action using the WITH HISTORY option, CA Endevor SCM uses the CCID and/or comment to:
CA Endevor SCM also:
When you specify a CCID and/or comment in a TRANSFER action using the SYNCHRONIZE option, CA Endevor SCM uses this CCID and/or comment to:
If you use BYPASS GENERATE PROCESSOR, the TRANSFER action will not set the generate or component list delta CCID and/or COMMENT field.
NEW VERSION version-By default, the version number of the FROM location element-at the time it is transferred-is assigned to the TO location element. Use this option to assign a different version number to the TO location element; simply enter the number (1-99) inclusive, leading zeros optional) that you want to use.
CA Endevor SCM allows only one version of an element at each location. Therefore, if the element currently exists at the target location, you cannot update it with another version. For example, if you try to transfer Version 2 of an element to a target location that already has an existing Version 1, you must archive or delete the current Version 1 before you transfer the Version 2. If the element exists at the target location or at a location up the mapped route, the TRANSFER action fails.
IGNORE GENERATE FAILED-This option applies to the *FAILED* flag previously set for the element. If the TRANSFER action is unsuccessful, you receive a message indicating that "the generate failed." Processing for the action normally is terminated at this point.
If you enter this option, however, you can perform the action whether or not the element was previously generated or moved successfully.
BYPASS GENERATE PROCESSOR-Select this option if you do not want the generate/move processor (depending on the processor group option chosen) executed for the element.
PROCESSOR GROUP EQ/= group name-Select this option to specify a predefined group of processors. If you do not specify a processor group, CA Endevor SCM defaults to the processor group last used for this element. However, the keywords PROCESSOR GROUP EQ and BYPASS GENERATE PROCESSOR are mutually exclusive (you can code one or the other). If both are coded, the default BYPASS GENERATE PROCESSOR is used.
If the FROM element is associated with a processor group that does not specify BYPASS GENERATE PROCESSOR, the processor group may be overridden with the processor group clause. Otherwise, a message will be issued saying that the processor group cannot be overridden.
OVERRIDE SIGNOUT-If the element has been signed out to a person other than yourself, you must code this option in order to perform the this action. Use OVERRIDE SIGNOUT with caution to avoid regressing changes made by another user.
BYPASS ELEMENT DELETE-This option tells CA Endevor SCM to retain the element in the FROM location after it is transferred. When you select this option, the delete processor is also bypassed.
BYPASS DELETE PROCESSOR-If you select this option, CA Endevor SCM does not execute the delete processor.
WITH HISTORY-The WITH HISTORY option preserves source element change history. If you request TRANSFER 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 transfers 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 transfers the element(s) without history. When you transfer 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 TRANSFER fails unless you code the SYNCHRONIZE option.
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 of the source and works 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.
SIGNIN-This option tells CA Endevor SCM to sign in all elements at the target stage after successfully completing the move. Use 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 source before the TRANSFER.
SIGNOUT TO userid-This option tells CA Endevor SCM to sign all elements out to the specified user ID at the target stage.
|
Copyright © 2014 CA.
All rights reserved.
|
|