Previous Topic: The Delete StatementNext Topic: The Generate Statement


Delete Syntax

►►─ DELete ELEment ─ element-name ─┬──────────────────────────────┬───────────►
                                   └─┬─ THRough ─┬─ element-name ─┘
                                     └─ THRu ────┘

 ►─ FROm ─ 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 ─┤
                  ├─ ONLy COMPonent ────┤
                  └─ OVErride SIGNOut ──┘

Expansion of CCID

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

Expansion of PRO

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

Indicates the element(s) to be deleted. 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 deleted, beginning with the element coded in the DELETE ELEMENTS 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 deleted. 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.

You must 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:

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.

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).

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 EQ/= 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 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 DELETE action fails.

ONLY COMPONENTS

Applicable for CA Endevor SCM ACM users only. Indicates whether you want to delete both the element component list and the element, or the element component list only. Y (yes-delete just the element component list) or N (no-delete the element as well as the element component list).

OVERRIDE SIGNOUT

If the element has been signed out to a person other than yourself, you must code this option in order to perform this action. This option updates the SIGNOUT ID at the appropriate stage with the user ID of the person performing the override. Use OVERRIDE SIGNOUT with caution to avoid regressing changes made by another user.

Example: Delete SCL

This SCL deletes an element from Stage 2. The signout will be overridden, if necessary.

   DELETE ELEMENT 'PAYRPT03'
      FROM ENVIRONMENT 'PROD'
      	  SYSTEM 'PAYROLL'
      	  SUBSYSTEM 'REPORTS'
      	  TYPE 'COBOL'
      	  STAGE NUMBER 2
   	  OPTIONS CCID REQ#43034
      	  COMMENT 'DELETE AN OBSOLETE PAYROLL PROGRAM'
      	  OVERRIDE SIGNOUT .