Through the use of an input command file it is possible to limit a compare run to specific entity types and/or vary the output report format. NDVRDCMP will parse the input files for only the type(s) specified.
►►────── SIGnon ──┬─────────────────────────────────┬────────────────────────►
├─ DBNAme ──────┬── is dictname ──┘
└─ DICtName ────┘
►────┬─────────────────────────┬───┬──────────────────────────┬─────────────►◄
└─ USEr name is user-id ──┘ └─ PASsword is password ───┘
►►────┬─────────────────────────────────────────────┬────────────────────────►◄
└─ REPort CHAnges ─┬─ ONLy ◄─────────┬─ . ────┘
└─ And DETails ───┘
►►────┬──────────────────────────────────────────────────┬───────────────────►◄
└─ COMpare TYPes is ─┬─ ALL ◄──────────────┬─ . ───┘
├─ type ──────────────┤
│ ┌─── , ───┐ │
└─ ( ─▼─ type ──┴─ ) ─┘
►►─┬────────────────────────────────────────────────────────────────────┬────►◄
│ ┌───────────────────────────────────────────────────────────────┐ │
└─▼─ SET TARget ─┬── IDMsdddl SESsion ─┬─ OPTions options ──── . ─┴──┘
├── IDMsdddl RECord ──┤
├── IDMsdddl ELEment ─┤
├── SCHema ───────────┤
└── SUBschema ────────┘
The option text referred to in the syntax above identifies option values that are not validated by CA Endevor/DB. When the option values are specified, CA Endevor/DB simply inserts them into the appropriate CA compiler command. Also, if a SET OPTIONS command is repeated, only the last one specified will be used.
The SIGNON command is fed directly to the IDMSDDDL and other CA utility programs, and is used to identify the dictionary, CA IDMS user and password which will be used to extract entity definitions. Note that this is CA IDMS SIGNON and it specifies an CA IDMS user, not an CA Endevor/DB user. The SIGNON commands processed by all other CA Endevor/DB utilities are CA Endevor/DB SIGNON commands - this implementation is unique to the NDVRDCMP program.
The REPORT command is optionally used to vary the printed results in the NDVRLST file.
|
Option |
Meaning |
|---|---|
|
CHANGES ONLY |
Only the inserted and deleted lines will display (same as stand-alone option C as described above). This is the default setting. |
|
CHANGES AND DETAILS |
The contents of the target dictionary for each entity are displayed with the inserted and deleted lines in context (same as the stand-alone option H as described above). |
The COMPARE command is optionally used to limit the compare to specified entity types.
|
Option |
Meaning |
|---|---|
|
TYPES = ALL |
All the entities contained in the input files under dd statement NDVRSRC are compared to the target dictionary. This is the default setting. |
|
TYPES = (type, ...) |
A single entity type or list of entity types can also be specified. The allowable types are:
For example, when COMPARE TYPES = (MAP, SUBSCHEMA). is coded, only the Maps and Subschema from the input files will be compared to the target dictionary. |
Note: To accurately compare the differences between the source and target dictionaries, this set of options must be identical to the 'SET SOURCE IDMSDDDL SESSION OPTIONS' specified for NDVRDLVR in Chapter 8.
This command allows changes to the default session options used by CA Endevor/DB for the target dictionary.
CA Endevor/DB sets the following target IDMSDDDL session options:
SET SESSIONS OPTIONS QUOTE IS ' DEFAULT IS ON INPUT 1 THRU 72 OUTPUT 80.
These options can be overridden or added to by specifying the SET TARGET IDMSDDDL SESSION OPTIONS command. For example, the command:
SET TARGET IDMSDDDL SESSION OPTIONS REGISTRATION NO OVERRIDE.
will cause a second SET SESSION OPTIONS command to be used, which will turn off entity occurrence security.
Refer to the CA IDMS IDD DDDL Reference Guide for a full discussion of IDD session options.
Note: To accurately compare the differences between the source and target dictionaries, this set of options must be identical to the 'SET SOURCE IDMSDDDL RECORD OPTIONS' specified for NDVRDLVR in Chapter 8.
This command allows changes to the default punch record options specified by CA Endevor/DB when punching record definitions from the target dictionary. The following options are set by default when punching record definitions from the target dictionary.
PUNCH RECORD record-name VERSION version-nr ALSO WITH FILES ELEMENTS SUBORDINATE ELEMENTS.
Note that the 'ALSO WITH' indicates that these options are to be added to the target IDD session options.
The punch record options can be overridden by specifying the SET SOURCE IDMSDDDL RECORD OPTIONS command. If you specify any options here, you must specify them all. The option text specified must begin with the 'ALSO WITH' or 'WITHOUT' or 'WITH' text. For example, the command:
SET TARGET IDMSDDDL RECORD OPTIONS ALSO WITH OLQ HEADERS.
includes OLQ headers in the punched record output.
With this command, the following punch record command is issued:
PUNCH RECORD record-name VERSION version-nr ALSO WITH OLQ HEADERS.
Refer to the CA IDMS IDD DDDL Reference Guide for a full discussion of DDDL PUNCH RECORD options.
Note: To accurately compare the differences between the source and target dictionaries, this set of options must be identical to the 'SET SOURCE IDMSDDDL ELEMENT OPTIONS' specified for NDVRDLVR in Chapter 8.
This command allows changes to the default options specified by CA Endevor/DB when punching element definitions from the target dictionary. The following options are set by default when punching element definitions from the target dictionary:
Punch element element-name version version-nr.
These punch element options can be overridden by specifying the SET TARGET IDMSDDDL ELEMENT OPTIONS command. If you specify any options here, you must specify them all. The options text specified must begin with the 'ALSO WITH' or 'WITH' or 'WITHOUT' text. For example, the command:
SET TARGET IDMSDDDL ELEMENT OPTIONS ALSO WITH subordinate elements SYNONYMS ATTRIBUTES.
will include subordinate elements, element synonyms, and attributes in the punched element output.
With this command, the following punch element command is issued:
PUNCH ELEMENT element-name VERSION version-nr ALSO WITH SUBORDINATE ELEMENTS SYNONYMS ATTRIBUTES.
Refer to the CA IDMS IDD DDDL Reference Guide for a full discussion of DDDL PUNCH ELEMENT options.
Note: To accurately compare the differences between the source and target dictionaries, this set of options must be identical to the 'SET SOURCE IDMSDDDL SCHEMA OPTIONS' specified for NDVRDLVR in Chapter 8.
This command allows changes to the default options specified by CA Endevor/DB when punching schema definitions from the target dictionary.
The following options are set by default when punching schema definitions from the target dictionary:
PUNCH SCHEMA schema-id VERSION version-nr.
These punch schema options can be overridden by specifying the SET TARGET SCHEMA OPTIONS command. If you specify any options here, you must specify them all. The options text specified must begin with 'ALSO WITH' or 'WITHOUT' or 'WITH' text. For example, the command:
SET TARGET SCHEMA OPTIONS ALSO WITH HISTORY.
includes all history information for the schema.
With this command, the following punch schema command is issued:
PUNCH SCHEMA schema-id VERSION version-nr ALSO WITH HISTORY.
Refer to the CA IDMS Database Administration Guide for a full discussion of PUNCH SCHEMA options.
To accurately compare the differences between the source and target dictionaries, this set of options must be identical to the 'SET SOURCE IDMSDDDL SUBSCHEMA OPTIONS' specified for NDVRDLVR in Chapter 8.
This command allows changes to the default options specified by CA Endevor/DB when punching subschema definitions from the target dictionary.
The following options are set by default when punching subschema definitions from the target dictionary:
PUNCH SUBSCHEMA subschema-id.
These punch subschema options can be overridden by specifying the SET TARGET SUBSCHEMA OPTIONS command. If you specify any options here, you must specify them all. The options text specified must begin with the 'ALSO WITH' or 'WITHOUT' or 'WITH' text. For example, the command:
SET TARGET SUBSCHEMA OPTIONS ALSO WITH HISTORY.
will include the date and time the subschema was created or last modified.
With this command, the following punch subschema command is issued:
PUNCH SUBSCHEMA subschema-id ALSO WITH HISTORY.
Refer to the CA IDMS Database Administration Guide for a full discussion of PUNCH SUBSCHEMA options.
|
Copyright © 2013 CA.
All rights reserved.
|
|