Usage

Entity Descriptor Identification

MODIFY, DELETE, DISPLAY, and PUNCH entity identification considerations. If any part of the entity-identification (NAME, TYPE and VERSION) is not specified, or is specified with name masking, CA Endevor/DB processing will be accomplished against all occurrences meeting the criteria of the information specified. The combinations can be:

Name, type and version all specified exactly. The combination identifies one (or zero) specific entity descriptor.
Name and type specified, version defaults to *. This combination identifies all entity descriptors in the CCDB which match the specified name and type, regardless of the version number.
Name specified, type defaults to *, version defaults to *. This combination identifies all entity descriptors in the CCDB which match the specified name, regardless of the type and version.
Type specified, name defaults to * , version defaults to *. This combination identifies all entity descriptors in the CCDB which match the specified type, regardless of the name and version.
No specification. Name defaults to *, type defaults to *, version defaults to *. This combination identifies all entity descriptors in the CCDB.
Name mask specified instead of name in any of the cases above will identify a set of entity names. Refer to Chapter 1 for a description of the name-mask rules.

STATUS

CA Endevor/DB will execute the Status clause against each entity selected by the command. It is used to establish a status for the entity occurrence at a global level and/or within the context of a CCID. For instance, you may wish to assign separate status associations for an entity to control its migration selections. For example,

ADD ENTITY SELECTION-DATE TYPE ELEMENT VER 100
    STATUS ( FOR CCID "INSTALL" IS "ALWAYS-MIGRATE"
                 CCID "PROMOTE" IS "NEVER-MIGRATE").

DELETE with FORCE

If FORCE is specified on a DELETE command, all Change Log Entries (CLEs) associated with the ENTITY are also deleted. A CLE is generated automatically anytime an entity is updated.

Note: Prior to requesting this option, it is recommended that the Archive and Compress Utility, NDVRARCO, be run against the CCDB to avoid possible errors.