Processing Element Actions › The Validate Statement › Validate Statement Syntax

Validate Statement Syntax

►►─ VALidate ELEment ─ element-name ─FROm ─ ENVironment ─ env-name ───────────►
 ►─  SYStem ─ sys-name ─ SUBsystem ─ subsys-name ─ TYPe ─ type-name ──────────►
 ►─┬─ STAge ─ stage-id ────────┬─┬──────────────────────────────┬─────────────►
   └─ STAge NUMber ─ stage-no ─┘ └─ WHEre ─ ¤ ──┤ CCID ├──── ¤ ─┘
►►─ OPTions ─ ¤ ─┬─ ELEment ─┬──────────┬──────────────────────┬─ ¤ ─ . ─────►◄
                 │           └─ MASter ─┘                      │
                 ├─ SYNCHRONIZAtion ───────────────────────────┤
                 ├─ COMPonent  ─┬──────────────┬───────────────┤
                 │              └─ VALIDATIon ─┘               │
                 └─ TERse ───┬────────────┬────────────────────┘
                             └─ MESsages ─┘                    
►─ .─────────────────────────────────────────────────────────────────────────►◄

Expansion of CCID

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

VALidate ELEment element-name

Indicates the element to be validated.

FROM

The FROM clause indicates the location of the element being validated. A check is performed to ensure the element exists at the location specified in the action. If not, an E level message is issued.

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.

ENVIRONMENT env-name
SYSTEM sys-name
SUBSYSTEM subsys-name
TYPE type-name
STAGE stage-id | STAGE NUMBER stage-no

The stage specification can be either one of the following:

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

Note: 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.

WHERE

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

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

Although the foreground SCL Generation panel allows you to filter the selection list by using a single CCID, the SCL supports multiple CCIDs.

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)

OPTIONS

OPTIONS clauses allow you to further specify action requests. The Validate Action statement requires at least one of the options Element Master, Synchronization, or Component Validation. If none of these are coded, then a warning message is issued to inform you of this situation and the action is processed assuming all three options are enabled.

ELEMENT MASTER

Checks to make sure the element is generated correctly. If this option is enabled the following checks are performed. If any of these conditions are detected, error messages are issued.

• If the processor is unknown, an error message is issued. This condition may occur when the last action is a RESTORE and the NOGEN option was specified.
• If the element is not generated or the last generate failed, an error message is issued. An exception to this rule is if the last processor is a delete processor.
• If this element is currently locked in a package, an error message is issued.

SYNCHRONIZATION

Checks to make sure that an out-of synch condition is not caused by the action being performed. If this option is enabled, the following checks are performed;

• A check is performed to determine if a second copy of this element exists up the logical map.
• If a second copy of this element exists up the logical map, the two copies of the element are used as input for the synchronization check processing. The location of the second copy of the element will be displayed in the C1MSGS messages file along with synchronization messages to indicate the results of the check.
• If the synchronization check is performed, an additional check is also performed to see if another copy of the element exists at a physical location in-between the two copies that were used as input in the synchronization checking. If a copy is found at an in-between location information messages are written to the C1MSGS report file.

The synchronization logic for this feature looks up the logical map for another copy of this element, starting at the inventory location specified in the action. It ignores other parallel maps that are defined in the C1DEFLTS table.

The synchronization logic determines if a second copy of this element resides up the logical map. If a second copy is not found, an informational message is written to the report and the synchronization logic is complete. The physical map is not searched.

COMPONENT VALIDATION

Checks to make sure that all the components exist and are valid. The CA Endevor SCM Automated Configuration option must be installed at your site in order to use the component validation option. If this option is enabled, the following checks are performed:

• The components of the element (parent) specified in the action are obtained and added to the list of elements that must be validated.
• The footprints of each component element are compared against the actual location of that element to ensure the latest copy of each component is included in the parent element and that the component exists.

Footprint error messages are issued for any component found to be in error. Totals are displayed as to how many components were verified and how many contained errors.

TERSE MESSAGES

Limits the amount of message detail that is written to the C1MSGS1 report file for those messages that result from the Validate action. All action output produced by the VALIDATE action is written to the C1MSGS1 report file. The terse messages option controls the amount of message detail that is written to that file. It will only write key I level messages and non-I level messages to the C1MSGS report file. If this option is not specified, then all messages are written to the C1MSGS report file.

Example: Validate Action Syntax with All Options

This Validate action SCL validates all the inventory located in the DEV environment PAYROLL sandbox subsystem. All available action options are specified.

VALIDATE ELEMENT 'PAYRPT17' 
FROM ENVIRONMENT 'DEV' 
SYSTEM 'FINANCE' 
SUBSYSTEM 'PAYROLL' 
TYPE * 
STAGE NUMBER *
OPTIONS ELEMENT MASTER 
SYNCHRONIZATION
COMPONENT VALIDATION
TERSE .