CDD/Plus CDO SHOW — VMS CDD+_4.1A
Additional information available:
ALLDATABASEDEFAULTFIELDGENERICKEYMESSAGES
PRIVILEGESPROTECTIONPROTOCOLRECORDRMS_DATABASE
UNUSEDUSED_BYUSESVERSIONWHAT_IF
ALL
Displays every CDO definition in the default directory. SHOW ALL ───┬─┬─────────────>─────────────┬─┬───> │ ├> typebox (/)
A
L
L ────────────────────┤ │ │ ├> typebox (/)
A
U
D
I
T ───┬─────>────┬───┤ │ │ │ └─>
=
A
L
L ──┘ │ │ │ ├> typebox (/)
B
R
I
E
F ──────────────────┤ │ │ └> typebox (/)
F
U
L
L ───────────────────┘ │ └───────────────<───────────────┘
Additional information available:
Qualifiers
Additional information available:
/ALL
For each definition in the directory, the user-specified and system-specified attributes are displayed, members of relationships owned by the definition are displayed, and user-specified and system-specified attributes of the member objects are displayed.
/AUDIT
For each object in the directory, the history list entries are displayed.
/AUDIT=ALL
Displays the history list for all entities owned by each object in the directory.
/BRIEF (default)
For each definition in the directory, the user defined attributes and the names of objects that are direct members of relationships owned by the definition are displayed.
/FULL
Displays the user-specified attributes for every object in the directory.
Examples
The following command displays each field, record, database, and generic entity definition in the default directory: CDO> SHOW ALL Definition of field EMPLOYEE_ID | Datatype unsigned numeric digits 9 Definition of field INCR_LEVEL | Datatype unsigned numeric digits 1 Definition of field JOB_CLASS | Datatype unsigned numeric digits 3 Definition of record SALARY_RECORD | Description ' contains sensitive salary information on all employees ' | Contains field EMPLOYEE_ID | Contains record PAY Definition of field WEEKLY_SALARY | Datatype unsigned numeric digits 8 | Edit_string "9(6)V99" CDO> The SHOW ALL/ALL command displays system- and user-specified attributes for each object in the default directory: CDO> SHOW ALL/ALL Definition of field EMPLOYEE_ID;1 | acl (IDENTIFIER=[VCD,JONES],ACCESS=READ+WRITE+MODIFY+ERA SE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMINIS TRATOR) | Created time 6-MAY-1987 09:07:06.01 | Modified time 6-MAY-1987 09:07:06.01 | Owner JONES | Datatype unsigned numeric digits 9 | | History entered by JONES ([VCD,JONES]) | | using CDO V1.0 | | to CREATE definition on 6-MAY-1987 09:07:02.53 Definition of field INCR_LEVEL;1 | acl (IDENTIFIER=[VCD,JONES],ACCESS=READ+WRITE+MODIFY+ERA SE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMINIS TRATOR) | Created time 6-MAY-1987 09:07:51.58 | Modified time 6-MAY-1987 09:07:51.58 | Owner JONES | Datatype unsigned numeric digits 1 | | History entered by JONES ([VCD,JONES]) | | using CDO V1.0 | | to CREATE definition on 6-MAY-1987 09:07:51.16 Definition of field JOB_CLASS;1 | acl (IDENTIFIER=[VCD,JONES],ACCESS=READ+WRITE+MODIFY+ERA SE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMINIS TRATOR) | Created time 6-MAY-1987 09:07:22.82 | Modified time 6-MAY-1987 09:07:22.82 | Owner JONES | Datatype unsigned numeric digits 3 | | History entered by JONES ([VCD,JONES]) | | using CDO V1.0 | | to CREATE definition on 6-MAY-1987 09:07:21.77 Definition of record SALARY_RECORD;1 | acl (IDENTIFIER=[VCD,JONES],ACCESS=READ+WRITE+MODIFY+ERA SE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMINIS TRATOR) | Created time 6-MAY-1987 09:23:08.22 | Description 'contains sensitive salary information on all employees' | Modified time 6-MAY-1987 09:23:08.22 | Owner JONES | | History entered by JONES ([VCD,JONES]) | | using CDO V1.0 | | to CREATE definition on 6-MAY-1987 09:22:58.52 | Contains field EMPLOYEE_ID | | Datatype unsigned numeric digits 9 | | | History entered by JONES ([VCD,JONES]) | | | using CDO V1.0 | | | to CREATE definition on 6-MAY-1987 09:07:02.53 | Contains record PAY | | Contains field JOB_CLASS | | | Datatype unsigned numeric digits 3 | | | | History entered by JONES ([VCD,JONES]) | | | | using CDO V1.0 | | | | to CREATE definition on 6-MAY-1987 09:07:21.77 | | Contains field INCR_LEVEL | | | Datatype unsigned numeric digits 1 | | | | History entered by JONES ([VCD,JONES]) | | | | using CDO V1.0 | | | | to CREATE definition on 6-MAY-1987 09:07:51.16 | | Contains field WEEKLY_SALARY | | | Datatype unsigned numeric digits 8 | | | Edit_string "9(6)V99" | | | | History entered by JONES ([VCD,JONES]) | | | | using CDO V1.0 | | | | to CREATE definition on 6-MAY-1987 09:11:21.10 Definition of field WEEKLY_SALARY;1 | acl (IDENTIFIER=[VCD,JONES],ACCESS=READ+WRITE+MODIFY+ERA SE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMINIS TRATOR) | Created time 6-MAY-1987 09:11:21.37 | Modified time 6-MAY-1987 09:11:21.37 | Owner JONES | Datatype unsigned numeric digits 8 | Edit_string "9(6)V99" | | History entered by JONES ([VCD,JONES]) | | using CDO V1.0 | | to CREATE definition on 6-MAY-1987 09:11:21.10 CDO>
DATABASE
Displays the definition of a physical database. SHOW_DATABASE ─┬─┬────────────>──────────────┬─┬─┬────────>────────┬─> │ ├──> typebox (/)
A
L
L ─────────────────┤ │ └> database-name ─┘ │ ├──> typebox (/)
A
U
D
I
T ─┬─────>────┬───┤ │ │ │ └─>
=
A
L
L ──┘ │ │ │ ├──>
/
B
R
I
E
F ────────────────┤ │ │ └──>
/
F
U
L
L ────────────────┘ │ └─────────────<─────────────────┘
Additional information available:
database-nameQualifiersRdb ExamplesRMS Examples
database-name
The name of a physical database on disk.
Qualifiers
Additional information available:
/ALL
For an RMS database, displays the database name and description, record definition, file organization, fully qualified path name, and system-specified attributes. For a VAX Rdb/VMS database, displays the database name, file name, and fully qualified path name, as well as the system-specified attributes.
/AUDIT
Displays the history list entries for the database definition.
/AUDIT=ALL
Displays the history list for all entities owned by the database.
/BRIEF (default)
For an RMS database, displays the database name and description, record name, fully qualified path name, and file organization attributes. For a VAX Rdb/VMS database, displays the database name, file name, and fully qualified path name.
/FULL
For an RMS database, displays the database name and description, record definition attributes, file organization attributes, and fully qualified path name. For a VAX Rdb/VMS database, displays the database name, file name, and fully qualified path name.
Rdb Examples
In the following example, the SHOW DATABASE command with the /FULL qualifier displays the database name, file name, and fully qualified path name of a VAX Rdb/VMS database DEPT5: CDO> SHOW DATABASE/FULL DEPT5 Definition of database DEPT5 | database uses RDB database DEPT5 | database in file DEPT5 | | fully qualified file USR02:[MCGUIRE.PERSONNEL]DEPT5.RDB; CDO> In the following example, the SHOW DATABASE command with the /ALL qualifier displays the system-specified attributes as well as the database name, file name, and fully qualified path name of the VAX Rdb/VMS database definition DEPT5: CDO> SHOW DATABASE/ALL DEPT5 Definition of database DEPT5 | acl (IDENTIFIER=[VCD,MCGUIRE],ACCESS=READ+ | WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ | ADMINISTRATOR) | (IDENTIFIER=[*,*],ACCESS=READ+WRITE+ | MODIFY+ERASE+SHOW+OPERATOR+ADMINISTRATOR) | | Created time 6-JAN-1988 10:16:19.69 | Modified time 6-JAN-1988 10:28:12.07 | Owner [VCD,MCGUIRE] | database uses RDB database DEPT5 | database in file DEPT5 | | fully qualified file USR02:[MCGUIRE.PERSONNEL]DEPT5.RDB; CDO> In the following example, the SHOW DATABASE command with the /AUDIT=ALL qualifier displays the history list for all entities owned by the VAX Rdb/VMS database definition MY_RDB_DB: CDO> SHOW DATABASE/AUDIT=ALL MY_RDB_DB Definition of MY_RDB_DB (Type : CDD$DATABASE) | Contains CDD$DATABASE_FILE | | MY_RDB_DB (Type : CDD$FILE) | Contains CDD$DATABASE_SCHEMA | | MY_RDB_DB (Type : CDD$RDB_DATABASE) | | | Contains CDD$RDB_DATA_ELEMENT | | | | FIELD_A (Type : CDD$DATA_ELEMENT) | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | using CDO V1.0 | | | | | | to CREATE definition on | | | | | | 2-FEB-1988 10:03:00.69 | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | using CDO V1.0 | | | | | | to MODIFY on | | | | | | 2-FEB-1988 12:23:51.74 | | | Contains CDD$RDB_DATA_ELEMENT | | | | FIELD_B (Type : CDD$DATA_ELEMENT) | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | using CDO V1.0 | | | | | | to CREATE definition on | | | | | | 2-FEB-1988 10:03:02.89 | | | Contains CDD$RDB_DATA_ELEMENT | | | | FIELD_C (Type : CDD$DATA_ELEMENT) | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | using CDO V1.0 | | | | | | to CREATE definition on | | | | | | 2-FEB-1988 10:03:03.68 | | | Contains CDD$RDB_DATA_AGGREGATE | | | | RECORD_A (Type : CDD$DATA_AGGREGATE) | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | using CDO V1.0 | | | | | | to CREATE definition on | | | | | | 2-FEB-1988 10:03:04.83 | | | | | Contains CDD$DATA_AGGREGATE_CONTAINS | | | | | | FIELD_A (Type : CDD$DATA_ELEMENT) | | | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | | | using CDO V1.0 | | | | | | | | to CREATE definition on | | | | | | | | 2-FEB-1988 10:03:00.69 | | | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | | | using CDO V1.0 | | | | | | | | to MODIFY on | | | | | | | | 2-FEB-1988 12:23:51.74 | | | Contains CDD$RDB_DATA_AGGREGATE | | | | RECORD_B (Type : CDD$DATA_AGGREGATE) | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | using CDO V1.0 | | | | | | to CREATE definition on | | | | | | 2-FEB-1988 10:03:06.97 | | | | | Contains CDD$DATA_AGGREGATE_CONTAINS | | | | | | FIELD_B (Type : CDD$DATA_ELEMENT) | | | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | | | using CDO V1.0 | | | | | | | | to CREATE definition on | | | | | | | | 2-FEB-1988 10:03:02.89 | | | Contains CDD$RDB_DATA_AGGREGATE | | | | RECORD_C (Type : CDD$DATA_AGGREGATE) | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | using CDO V1.0 | | | | | | to CREATE definition on | | | | | | 2-FEB-1988 10:03:08.22 | | | | | Contains CDD$DATA_AGGREGATE_CONTAINS | | | | | | FIELD_C (Type : CDD$DATA_ELEMENT) | | | | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | | | | using CDO V1.0 | | | | | | | | to CREATE definition on | | | | | | | | 2-FEB-1988 10:03:03.68 CDO>
RMS Examples
In the following example, SHOW DATABASE/ALL displays the complete definition of the physical RMS database definition DBS_FILE: CDO> SHOW DATABASE/ALL DBS_FILE Definition of database DBS_FILE | acl (IDENTIFIER=[VCD,MCGUIRE],ACCESS=READ+WRITE | +MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR | +ADMINISTRATOR) | (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY | +ERASE+SHOW+OPERATOR+ADMINISTRATOR) | Created time 7-DEC-1987 10:36:44.69 | Description 'CONTAINS CURRENT EMPLOYEE NAMES AND | IDENTIFICATION NUMBERS' | 'FOR MARLBORO' | Modified time 7-DEC-1987 10:36:44.69 | Owner MCGUIRE | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | using CDO V1.0 | | to CREATE definition on 7-DEC-1987 10:36:43.68 | | Explanation: | | UPDATED MONTHLY-- LAST UPDATE 12/88 | database in file USR02:[MCGUIRE.RMS]EMP.DAT | | fully qualified file USR02:[MCGUIRE.RMS]EMP.DAT; | database uses RMS database EMPLOYEE_STORAGE | | database uses record EMPLOYEE_REC | | | acl (IDENTIFIER=[VCD,MCGUIRE],ACCESS=READ+ | | | WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL | | | +OPERATOR+ADMINISTRATOR) | | | (IDENTIFIER=[*,*],ACCESS=READ+WRITE+ | | | MODIFY+ERASE+SHOW+OPERATOR+ADMINISTRATOR) | | | Created time 3-DEC-1987 14:00:08.42 | | | Modified time 3-DEC-1987 14:00:08.42 | | | Owner MCGUIRE | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | using CDO V1.0 | | | | to CREATE definition on 3-DEC-1987 14:00:06.65 | | | Contains field LAST_NAME | | | | acl (IDENTIFIER=[VCD,MCGUIRE], | | | | ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE | | | | +CONTROL+OPERATOR+ADMINISTRATOR) | | | | (IDENTIFIER=[*,*],ACCESS=READ | | | | +WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMINISTRATOR) | | | | Created time 3-DEC-1987 13:59:58.12 | | | | Modified time 3-DEC-1987 13:59:58.12 | | | | Owner MCGUIRE | | | | Datatype text size is 30 characters | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | using CDO V1.0 | | | | | to CREATE definition on 3-DEC-1987 13:59:46.01 | | | Contains field FIRST_NAME | | | | acl | | | | (IDENTIFIER=[VCD,MCGUIRE], | | | | ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE | | | | +CONTROL+OPERATOR+ADMINISTRATOR) | | | | (IDENTIFIER=[*,*],ACCESS=READ+ | | | | WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMINISTRATOR) | | | | Created time 3-DEC-1987 14:00:00.94 | | | | Modified time 3-DEC-1987 14:00:00.94 | | | | Owner MCGUIRE | | | | Datatype text size is 20 characters | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | using CDO V1.0 | | | | | to CREATE definition on 3-DEC-1987 13:59:59.42 | | | Contains field EMP_ID | | | | acl (IDENTIFIER=[VCD,MCGUIRE], | | | | ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+ | | | | DELETE+CONTROL+OPERATOR+ADMINISTRATOR) | | | | (IDENTIFIER=[*,*],ACCESS=READ | | | | +WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMINISTRATOR) | | | | Created time 3-DEC-1987 14:00:05.55 | | | | Modified time 3-DEC-1987 14:00:05.55 | | | | Owner MCGUIRE | | | | Datatype unsigned longword | | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | | using CDO V1.0 | | | | | to CREATE definition on | | | | | 3-DEC-1987 14:00:01.99 | | file definition | | | file allocation 200 | | | file contiguous | | | file organization index sequential | | | key 0 | | | | key changes | | | | key duplicates | | | | segment LAST_NAME IN EMPLOYEE_REC | | | key 1 | | | | key changes | | | | segment EMP_ID IN EMPLOYEE_REC CDO> In the following example, SHOW DATABASE/FULL displays the attributes for all of the definitions used by the physical RMS database definition DBS_FILE: CDO> SHOW DATABASE/FULL DBS_FILE Definition of database DBS_FILE | Description 'CONTAINS CURRENT EMPLOYEE NAMES AND | IDENTIFICATION NUMBERS' | 'FOR MARLBORO' | database in file USR02:[MCGUIRE.RMS]EMP.DAT | | fully qualified file USR02:[MCGUIRE.RMS]EMP.DAT; | database uses RMS database EMPLOYEE_STORAGE | | database uses record EMPLOYEE_REC | | | Contains field LAST_NAME | | | | Datatype text size is 30 characters | | | Contains field FIRST_NAME | | | | Datatype text size is 20 characters | | | Contains field EMP_ID | | | | Datatype unsigned longword | | file definition | | | file allocation 200 | | | file contiguous | | | file organization index sequential | | | key 0 | | | | key changes | | | | key duplicates | | | | segment LAST_NAME IN EMPLOYEE_REC | | | key 1 | | | | key changes | | | | segment EMP_ID IN EMPLOYEE_REC CDO>
DEFAULT
Displays the current default CDO directory. SHOW DEFAULT ─────────────────────────>
Additional information available:
Examples
The following command displays the current default CDO directory. CDO> SHOW DEFAULT DISK1:[CORPORATE.PERSONNEL]EMPLOYEES.SALARIED CDO> The following SHOW DEFAULT command shows the names of dictionary areas specified by the logical name MY_DICT: CDO> SET DEFAULT MY_DICT CDO> SHOW DEFAULT DISK1:[CORPORATE.PERSONNEL]EMPLOYEES.CONTRACT FARWAY::DISK2:[REMOTE.DICTIONARY]SECURITY CDO>
FIELD
Displays the specified field definition or definitions. If you do not specify a field name, this command displays all field definitions in the default directory that you have privilege to display. SHOW FIELD ─┬─┬───────────>─────────┬─┬─┬─────────>────────┬─┐ │ ├> typebox (/)
A
L
L ──────────────┤ │ └┬─> field-name ─┬─┘ │ │ ├> typebox (/)
A
U
D
I
T ─┬────>───┬─┤ │ └─────── , <────┘ │ │ │ └>
=
A
L
L ─┘ │ │ │ │ ├> typebox (/)
B
R
I
E
F ────────────┤ │ │ │ └> typebox (/)
F
U
L
L ─────────────┘ │ │ └─────────────<───────────┘ │ ┌───────────────────────<───────────────────────────────────┘ └─┬────────────────>───────────────┬──> └─>
F
R
O
M
D
A
T
A
B
A
S
E database-name ─┘
Additional information available:
field-namedatabase-nameQualifiersExamples
field-name
The name of one or more field definitions. You can display multiple field definitions from a CDO dictionary, separating the field names with commas. To display one or more field definitions from an Rdb/VMS database, you must use the FROM DATABASE clause. You can display a single field definition from an Rdb/VMS database by supplying the name of the field definition for "field-name". You can display all the field definitions from a database by specifying the asterisk (*) wildcard character for "field-name". No other wildcard character is valid for the "field-name".
database-name
The name of the Rdb/VMS database that contains the field definition you want to display. You can use wildcard characters in the database-name.
Qualifiers
Additional information available:
/ALL
Displays the field definition and system attributes, as well as the history list and the description used in the field definition.
/AUDIT
Displays the history list entries for the field definition. This qualifier cannot be used when displaying field definitions from a database.
/AUDIT=ALL
Displays the history list for all entities owned by the field definition.
/BRIEF (default)
Displays the user-specified field attributes used in the field definition. If the field definition inherited some of its attributes from another field definition through a BASED_ON attribute, the inherited attributes are displayed as if they were defined under the named field definition.
/FULL
Displays the user-specified field attributes and the description of the field definition.
Examples
In the following example, SHOW FIELD/FULL displays the user-specified attributes of the CORPORATE_ZIPCODE field definition from the Rdb database DEPT3: CDO> SHOW FIELD/FULL CORPORATE_ZIPCODE FROM DATABASE DEPT3 Definition of field CORPORATE_ZIPCODE | Based on POSTAL_CODE | | Description 'POSTAL CODE IN USA IS ZIP CODE' | | Datatype text size is 5 characters | | Missing_value " " CDO> The following SHOW FIELD/AUDIT command displays the history list for the field definition CORPORATE_ZIPCODE: CDO> SHOW FIELD/AUDIT CORPORATE_ZIPCODE Definition of CORPORATE_ZIPCODE (Type : CDD$DATA_ELEMENT) | History entered by MCGUIRE ([VCD,MCGUIRE]) | using CDO V1.0 | to CREATE definition on 30-DEC-1987 09:39:09.72 CDO> The following SHOW FIELD/AUDIT=ALL command displays the history list for all entities owned by the field definition CORPORATE_ZIPCODE: CDO> SHOW FIELD/AUDIT=ALL CORPORATE_ZIPCODE Definition of CORPORATE_ZIPCODE (Type : CDD$DATA_ELEMENT) | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | using CDO V1.0 | | to CREATE definition on 30-DEC-1987 09:39:09.72 | Contains CDD$DATA_ELEMENT_BASED_ON | | POSTAL_CODE (Type : CDD$DATA_ELEMENT) | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | using CDO V1.0 | | | | to CREATE definition on 30-DEC-1987 09:37:27.48 CDO> The following SHOW FIELD command displays each field definition in your current default directory: CDO> SHOW FIELD Definition of field BADGE_NUMBER | Datatype packed decimal digits 8 Definition of field CITY | Datatype text size is 25 characters Definition of field CORPORATE_ZIPCODE | Datatype text size is 5 characters Definition of field FIRST_NAME | Datatype text size is 15 characters Definition of field LAST_NAME | Datatype text size is 100 characters Definition of field MANAGER_BADGE_NUMBER | Valid if (MANAGER_BADGE_NUMBER GT 1000) | Datatype packed decimal digits 8 Definition of field MIDDLE_INITIAL | Datatype text size is 1 characters Definition of field STATE | Datatype text size is 2 characters Definition of field STREET | Datatype text size is 25 characters Definition of field SUPERVISOR_BADGE_NUMBER | Valid if (SUPERVISOR_BADGE_NUMBER GT 500) | Datatype packed decimal digits CDO> In the following example, SHOW FIELD/ALL displays the complete definition of the field EMPLOYEE_ID from the PERSONNEL database: CDO> SHOW FIELD/ALL EMPLOYEE_ID FROM DATABASE PERSONNEL Definition of field EMPLOYEE_ID | acl (IDENTIFIER=[VCD,MCGUIRE],ACCESS=READ+WRITE | +MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ | ADMINISTRATOR) | (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ | ERASE+SHOW+OPERATOR+ADMINISTRATOR) | Created time 22-DEC-1987 09:04:26.75 | Modified time 22-DEC-1987 09:04:26.75 | Owner MCGUIRE | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | using CDO V1.0 | | to CREATE definition on 22-DEC-1987 09:04:26.06 | Based on ID_NUMBER | | Datatype text size is 5 characters | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | using CDO V1.0 | | | to CREATE definition on 22-DEC-1987 09:03:30.24 CDO>
GENERIC
Displays the definition of one or more entities of the specified protocol. SHOW GENERIC ─> protocol-name ─┬─┬────────────>──────────────┬─┬─┐ │ ├> typebox (/)
A
L
L ────────────────────┤ │ │ │ ├> typebox (/)
A
U
D
I
T ───┬─────>────┬───┤ │ │ │ │ └─>
=
A
L
L ──┘ │ │ │ │ ├> typebox (/)
B
R
I
E
F ──────────────────┤ │ │ │ └> typebox (/)
F
U
L
L ───────────────────┘ │ │ └───────────────<───────────────┘ │ ┌─────────────────────────────────<──────────────────────────────┘ └─┬──────────>───────┬───┬────────────────>────────────────┬─> └┬─> entity-name ─┬┘ └──>
F
R
O
M
D
A
T
A
B
A
S
E database-name ─┘ └─────── , <─────┘
Additional information available:
protocol-nameentity-namedatabase-nameQualifiersExamples
protocol-name
The protocol of the entity definitions you want to display.
entity-name
The name of one or more entity definitions of the specified protocol.
database-name
The name of the Rdb/VMS database that contains the definition you want to display.
Qualifiers
Additional information available:
/ALL
Displays the complete definition of the generic entity. Objects that are members of a relationship with the definition are also displayed, as well as their attributes.
/AUDIT
Displays the history list entries for the generic entity definition. History list entries are displayed only if the CDD$HISTORY_LIST relationship was specified as part of this generic entity definition's protocol definition.
/AUDIT=ALL
Displays the history list for all entities owned by the generic definition. History list entries are displayed only if the CDD$HISTORY_LIST relationship was specified as part of this generic entity definition's protocol definition.
/BRIEF (default)
Displays the attributes used in the generic definition and the names of objects that are members of a direct relationship with the definition.
/FULL
Displays all user-specified attributes used in the generic definition. The description of the definition is displayed only if the CDD$DESCRIPTION attribute was specified in this generic entity's protocol definition.
Examples
In the following example, the SHOW GENERIC command with /BRIEF qualifier displays the brief definition of the field definition JOB_CODE: CDO> SHOW GENERIC CDD$DATA_ELEMENT/BRIEF JOB_CODE Definition of JOB_CODE (Type : CDD$DATA_ELEMENT) | CDD$DESCRIPTION A 1 CHARACTER TEXT FIELD THAT WILL ! BE USED WITH A VARIANT | CDD$DATA_ELEMENT_DATATYPE 14 | CDD$DATA_ELEMENT_LENGTH 1 CDO> In the following example, SHOW GENERIC displays the brief definition of the VAX Rdb/VMS database definition called MY_RDB_DB. CDO> SHOW GENERIC CDD$DATABASE MY_RDB_DB Definition of MY_RDB_DB (Type : CDD$DATABASE) | Contains CDD$DATABASE_FILE | | MY_RDB_DB (Type : CDD$FILE) | Contains CDD$DATABASE_SCHEMA | | MY_RDB_DB (Type : CDD$RDB_DATABASE) CDO> In the following example, the SHOW GENERIC command with the /FULL qualifier displays the complete definition of the VAX Rdb/VMS database definition MY_RDB_DB: CDO> SHOW GENERIC CDD$DATABASE/FULL MY_RDB_DB Definition of MY_RDB_DB (Type : CDD$DATABASE) | Contains CDD$DATABASE_FILE | | MY_RDB_DB (Type : CDD$FILE) | | | CDD$QUALIFIED_NAME USR$DISK:[RICK.NEWDICT]MY_RDB_DB.RDB; | Contains CDD$DATABASE_SCHEMA | | MY_RDB_DB (Type : CDD$RDB_DATABASE) | | | Contains CDD$RDB_DATA_ELEMENT | | | | FLD_A (Type : CDD$DATA_ELEMENT) | | | | | CDD$DATA_ELEMENT_DATATYPE 8 | | | Contains CDD$RDB_DATA_ELEMENT | | | | FLD_B (Type : CDD$DATA_ELEMENT) | | | | | CDD$DATA_ELEMENT_DATATYPE 14 | | | | | CDD$DATA_ELEMENT_LENGTH 10 | | | Contains CDD$RDB_DATA_ELEMENT | | | | FLD_C (Type : CDD$DATA_ELEMENT) | | | | | CDD$DATA_ELEMENT_DATATYPE 14 | | | | | CDD$DATA_ELEMENT_LENGTH 15 | | | Contains CDD$RDB_DATA_AGGREGATE | | | | REC_A (Type : CDD$DATA_AGGREGATE) | | | | | CDD$DESCRIPTION FIRST CHANGE | | | | | Contains CDD$DATA_AGGREGATE_CONTAINS | | | | | | FIELD_A (Type : CDD$DATA_ELEMENT) | | | | | | | CDD$DATA_ELEMENT_DATATYPE 8 | | | Contains CDD$RDB_DATA_AGGREGATE | | | | RECORD_B (Type : CDD$DATA_AGGREGATE) | | | | | Contains CDD$DATA_AGGREGATE_CONTAINS | | | | | | FIELD_B (Type : CDD$DATA_ELEMENT) | | | | | | | CDD$DATA_ELEMENT_DATATYPE 14 | | | | | | | CDD$DATA_ELEMENT_LENGTH 10 | | | Contains CDD$RDB_DATA_AGGREGATE | | | | REC_C (Type : CDD$DATA_AGGREGATE) | | | | | Contains CDD$DATA_AGGREGATE_CONTAINS | | | | | | FIELD_C (Type : CDD$DATA_ELEMENT) | | | | | | | CDD$DATA_ELEMENT_DATATYPE 14 | | | | | | | CDD$DATA_ELEMENT_LENGTH 15 CDO> In the following example, SHOW GENERIC with the /FULL qualifier displays the user-specified attributes for the generic entity MY_PROGRAM: CDO> SHOW GENERIC CDD$EXECUTABLE_IMAGE/FULL MY_PROGRAM Definition of MY_PROGRAM (Type : CDD$EXECUTABLE_IMAGE) | Contains CDD$IMAGE_DERIVED_FROM | | INPUT_MODULE (Type : CDD$COMPILED_MODULE) | | | Contains CDD$COMPILED_DERIVED_FROM | | | | INPUT_MODULE (Type : CDD$SOURCE_MODULE) | Contains CDD$IMAGE_DERIVED_FROM | | OUTPUT_MODULE (Type : CDD$COMPILED_MODULE) | | | Contains CDD$COMPILED_DERIVED_FROM | | | | OUTPUT_MODULE (Type : CDD$SOURCE_MODULE) CDO> In the following example, the SHOW GENERIC command with the /AUDIT=ALL qualifier displays the history list for the program definition MY_PROGRAM and for all of the entities it owns: CDO> SHOW GENERIC CDD$EXECUTABLE_IMAGE/AUDIT=ALL MY_PROGRAM Definition of MY_PROGRAM (Type : CDD$EXECUTABLE_IMAGE) | | History entered by SMITH ([VCD,SMITH]) | | using CDO V1.0 | | to CREATE definition on 14-DEC-1987 11:24:56.34 | Contains CDD$IMAGE_DERIVED_FROM | | INPUT_MODULE (Type : CDD$COMPILED_MODULE) | | | Contains CDD$COMPILED_DERIVED_FROM | | | | INPUT_MODULE (Type : CDD$SOURCE_MODULE) | | | | | | History entered by SMITH ([VCD,SMITH]) | | | | | | using CDO V1.0 | | | | | | to CREATE definition on | | | | | | 14-DEC-1987 10:28:51.42 | Contains CDD$IMAGE_DERIVED_FROM | | OUTPUT_MODULE (Type : CDD$COMPILED_MODULE) | | | Contains CDD$COMPILED_DERIVED_FROM | | | | OUTPUT_MODULE (Type : CDD$SOURCE_MODULE) | | | | | | History entered by SMITH ([VCD,SMITH]) | | | | | | using CDO V1.0 | | | | | | to CREATE definition on | | | | | | 14-DEC-1987 10:28:52.84 CDO> The following command displays the brief definition of the field definition EMPLOYEE_ID: CDO> SHOW GENERIC CDD$DATA_ELEMENT EMPLOYEE_ID Definition of EMPLOYEE_ID (Type : CDD$DATA_ELEMENT) | CDD$ACCESS_CONTROL_LIST (IDENTIFIER=[VCD,MCGUIRE],ACCESS=REA D+WRITE+MODIFY+ERASE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINIST RATOR) | (IDENTIFIER=[*,*],ACCESS=READ+WRITE+ MODIFY+ERASE+SHOW+OPERATOR+ADMINISTRATOR) | CDD$CREATED_TIME 22-DEC-1987 09:04:26.75 | CDD$MODIFIED_TIME 22-DEC-1987 09:04:26.75 | CDD$OWNER MCGUIRE | Contains CDD$DATA_ELEMENT_BASED_ON | | ID_NUMBER (Type : CDD$DATA_ELEMENT) CDO>
KEY
Displays the key definition for the specified key or, if no key-name is specified, for all keys. Key definitions are strings equated to specified keys; they are created using the DEFINE KEY command. SHOW KEY ──┬──────────>─────────┬──┬───────>──────┬───> ├> typebox (/)
A
L
L ─────────────┤ └─> key-name ──┘ ├> typebox (/)
B
R
I
E
F ───────────┤ ├> typebox (/)
N
O
B
R
I
E
F ─────────┤ ├> typebox (/)
D
I
R
E
C
T
O
R
Y ───────┤ ├> typebox (/)
F
U
L
L ────────────┤ ├> typebox (/)
N
O
F
U
L
L ──────────┤ ├> typebox (/)
S
T
A
T
Etypebox (=)key-state ─┤ └> typebox (/)
N
O
S
T
A
T
E ─────────┘
Additional information available:
key-name
Specifies the name of the key whose definition is to be displayed.
Qualifiers
Additional information available:
/ALL/BRIEF/DIRECTORY/FULL/STATE
/ALL
Displays all key definitions in a key state. You cannot use /ALL if you specify one or more key-names.
/BRIEF
/BRIEF (default) /NOBRIEF /BRIEF displays only the key definition and state. /NOBRIEF displays the key definition and state, and all qualifiers associated with the key definition. The /NOBRIEF and /FULL qualifiers are equivalent.
/DIRECTORY
Displays the names of all states for which keys have been defined. If you have no keys defined the SHOW KEY/DIRECTORY command displays nothing. If you have not specified a state with a key definition, the SHOW KEY/DIRECTORY command displays DEFAULT for the state. If you specify /DIRECTORY, you cannot specify any other SHOW KEY qualifiers.
/FULL
/FULL /NOFULL (default) Displays the key definition and state, and any qualifiers that are associated with the requested key definition. The default is /NOFULL, where only the key definition and state are displayed. The /FULL and /NOBRIEF qualifiers are equivalent.
/STATE=key-state
/STATE=key-state /NOSTATE (default) /STATE displays key definitions in the specified state. The default is /NOSTATE, which displays key definitions in the current state.
Examples
The following command displays both the definition and the state of the definition for the PF3 key: CDO> SHOW KEY PF3 DEFAULT keypad definitions: PF3 = "set default [SMITH.DICT]" CDO> The following command displays the definition and the state of the definition of the PF4 key, and also the qualifiers associated with the PF4 key definition: CDO> SHOW KEY/FULL PF4 DEFAULT keypad definitions: PF4 = "show default" (echo,noterminate,nolock,noprotected) CDO> The display from the following command shows that you have not specified a state with your key definitions: CDO> SHOW KEY/DIRECTORY DEFAULT CDO>
MESSAGES
Displays the messages at the specified object or objects. SHOW MESSAGES ───────┬─> object-name ──┬──────────────> └─────── , <──────┘
Additional information available:
object-nameRdb ExamplesRMS Examples
object-name
The name of the object or objects.
Rdb Examples
The following figure shows a CDO definition of an Rdb/VMS database
called MY_RDB_DB that contains CDO field definitions and record
definitions. The following examples refer to the definitions in this
figure:
MY_RDB_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RDB_DB (CDD$FILE) MY_RDB_DB (CDD$RDB_DATABASE)
|
----------------------------------------
| | |
REC_A REC_B REC_C
| | |
FLD_A FLD_B FLD_C
The database MY_RDB_DB was created in RDO using a CDD/Plus path name,
causing three entities to be created in the dictionary. These are:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RDB_DATABASE - describes the logical definition of the
file.
o CDD$FILE - describes the physical location of the
database on disk.
If you use the CHANGE FIELD command to change field definition FLD_A in
place, CDO advises you that the database MY_RDB_DB may have to be
integrated with the dictionary because of the CHANGE in place:
CDO> CHANGE FIELD FLD_A
cont> DATATYPE IS SIGNED LONGWORD.
CDO-I-DBMBR, database USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 may need
to be INTEGRATED
CDO>
The CHANGE in place made to field definition FLD_A in the previous
example causes a possibly invalid message to be sent to database
definition MY_RDB_DB. You can use the SHOW MESSAGES command to display
the message at MY_RDB_DB:
CDO> SHOW MESSAGES MY_RDB_DB
USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 is possibly invalid, triggered
by CDD$DATA_ELEMENT USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_A;1
CDO>
When you use the DEFINE FIELD command to create a new version of field
definition FLD_B, CDO sends new version messages to ancestors of FLD_B.
In the following set of examples:
o The DEFINE FIELD command creates a new version of field definition
FLD_B.
o The first SHOW MESSAGES command shows the new version message
received by record definition REC_B when the new version of FLD_B
was created.
o The second SHOW MESSAGES command shows two messages at CDD$DATABASE
definition MY_RDB_DB. The CHANGE FIELD command sends one message
on behalf of field definition FLD_A above, and the DEFINE FIELD
command sends a new version message on behalf of the new version of
field definition FLD_B. When you ask CDO to display messages on
MY_RDB_DB, the messages on CDD$DATABASE definition MY_RDB_DB are
displayed.
CDO> DEFINE FIELD FLD_B
cont> DATATYPE SIGNED LONGWORD.
CDO> SHOW MESSAGES REC_B
USR$DISK:[RICK.NEWDICT]GLOBAL.REC_B;1 uses an entity which has new
versions, triggered by CDD$DATA_ELEMENT USR$DISK:[RICK.NEWDICT]
GLOBAL.FLD_B;1
CDO> SHOW MESSAGES MY_RDB_DB
USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 uses an entity which has
new versions, triggered by CDD$DATA_ELEMENT USR$DISK:[RICK.NEWDICT]
GLOBAL.FLD_B;1
USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 is possibly invalid,
triggered by CDD$DATA_ELEMENT USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_A;1
CDO>
You can use the CLEAR MESSAGES command to clear the messages at
MY_RDB_DB:
CDO> CLEAR MESSAGES MY_RDB_DB
CDO>
To verify that you cleared the messages at MY_RDB_DB, use the SHOW
MESSAGES command. If you ask to see messages at an object that has no
messages, CDO advises you that the object has no messages:
CDO> SHOW MESSAGES MY_RDB_DB
%CDO-I-NOMESSAGES, USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 has no
messages
CDO>
RMS Examples
The following figure shows a CDO definition of an RMS database called
MY_PHYSICAL_RMS_DB that contains one CDO record definition. The
following examples refer to the definitions in this figure:
MY_PHYSICAL_RMS_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RMS_DB (CDD$FILE) MY_RMS_DB (CDD$RMS_DATABASE)
|
|
RECORD_E
|
-----------------------------------------
| | |
| | |
FIELD_F FIELD_G FIELD_H
The database MY_PHYSICAL_RMS_DB was created using the RMS database
definition MY_RMS_DB on the disk location DISK1:[SMITH.DICT]MY_RMS_DB.
Creating MY_PHYSICAL_RMS_DB also causes the following three entities to
be created in the dictionary:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RMS_DATABASE - describes the logical definition
of the database.
o CDD$FILE - describes the physical location
of the database on disk.
In the following example, the output from the SHOW MESSAGES command
indicates that the RMS database, MY_PHYSICAL_RMS_DB has not received
any possibly invalid messages:
CDO> SHOW MESSAGES MY_PHYSICAL_RMS_DB
%CDO-I-NOMESSAGES, DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1 has no
messages
CDO>
In the the following example, the CHANGE RECORD command deletes the
field definition FIELD_H from the record definition, RECORD_E:
CDO> CHANGE RECORD RECORD_E.
cont> DELETE FIELD_H.
cont> END RECORD.
CDO>
The SHOW MESSAGES command now displays the message that the previous
CHANGE RECORD command sent to MY_PHYSICAL_RMS_DB:
CDO> SHOW MESSAGES MY_PHYSICAL_RMS_DB
DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1 is possibly invalid, triggered
by CDD$DATA_AGGREGATE DISK1:[SMITH.DICT]RECORD_E;1
CDO>
PRIVILEGES
Displays your access rights for the named object or objects. SHOW PRIVILEGES FOR ─────┬─>
F
I
E
L
D ─────────────────┬─────┐ ├─>
R
E
C
O
R
D ────────────────┤ │ └─>
G
E
N
E
R
I
C protocol-name ─┘ │ ┌───────────────────────────<───────────────────────────┘ └──┬─> object-name ─┬─> └──────── , <────┘
Additional information available:
protocol-nameobject-nameExample
protocol-name
The protocol on which the generic entity definition whose access rights you want to display is based. To display your privileges for a protocol definition, use the SHOW PROTOCOL command.
object-name
The name of one or more objects for which you want to display your access rights.
Example
The following command displays your access rights for the field
definition CURRENT_SALARY.
CDO> SHOW PRIVILEGES FOR FIELD CURRENT_SALARY
Directory MY$DISK:[SMITH.DICT]PERSONNEL
CURRENT_SALARY;1
(IDENTIFIER=[VCD,SMITH],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW
+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR)
CDO>
PROTECTION
Displays the access control list (ACL) for the named object or objects. SHOW PROTECTION FOR ───────┬─>
D
I
R
E
C
T
O
R
Y ─────────────┬─────┐ ├─>
F
I
E
L
D ─────────────────┤ │ ├─>
R
E
C
O
R
D ────────────────┤ │ └─>
G
E
N
E
R
I
C protocol-name ─┘ │ ┌─────────────────────────────<──────────────────────────┘ └───┬─> object-name ─┬─> └──────── , <────┘
Additional information available:
protocol-nameobject-nameExample
protocol-name
The protocol on which the generic entity definition whose ACL you want to display is based. To display the access control list for a protocol definition, use the SHOW PROTOCOL command.
object-name
The name of one or more dictionary objects or directories for which you want to display the ACL.
Example
The following command displays the access control list for the field
definition CURRENT_SALARY.
CDO> SHOW PROTECTION FOR FIELD CURRENT_SALARY
Directory MY$DISK:[SMITH.DICT]PERSONNEL
CURRENT_SALARY;1
(IDENTIFIER=[VCD,SMITH],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW
+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR)
(IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+
ADMINISTRATOR)
CDO>
PROTOCOL
Displays the definition of the specified protocol or protocols. SHOW PROTOCOL ─┬─┬──────────>──────────┬─┬─┬─> protocol-name ─┬─> │ ├> typebox (/)
A
L
L ──────────────┤ │ └─────── , <───────┘ │ ├> typebox (/)
B
R
I
E
F ────────────┤ │ │ └> typebox (/)
F
U
L
L ─────────────┘ │ └────────────<────────────┘
Additional information available:
protocol-nameQualifiersmessage actionsExamples
protocol-name
The name of one or more protocols.
Qualifiers
Additional information available:
/ALL
Displays all the possible relationships the protocol can own, as well as the access control list for the protocol.
/FULL
Displays all of the possible relationships this protocol can own.
/BRIEF (default)
Displays the relationships most commonly owned by this protocol.
message actions
When you display a relationship protocol with the SHOW PROTOCOL command, you can examine the value of the CDD$MESSAGE_ACTION attribute. Each relationship protocol in the dictionary has a CDD$MESSAGE_ACTION attribute with a value of BLOCK, SUCCESS, or SIGNAL. All instances of a particular relationship protocol have the message action value specified by the protocol's CDD$MESSAGE_ACTION attribute. A relationship's message action determines what instances of the relationship protocol will do they receive a message. The subtopics BLOCK, SUCCESS, and SIGNAL explain the meaning of these message actions.
Additional information available:
BLOCK
If a relationship has a message action value of BLOCK, CDO does not forward a message from the member of the relationship to the owner. CDO blocks the message regardless of whether you are changing the object with the CHANGE command or defining new versions of the object. Therefore, when a relationship has a message action of BLOCK, it is as though the relationship does not exist for the purpose of passing messages.
SIGNAL
When a relationship has a message action value of SIGNAL and you change the member of the relationship with the CHANGE command or you define a new version of the member, CDO displays a message at both the owners and the ancestors of the relationship. When you create a new version of a member, CDO also sends messages to the ancestors until CDO encounters a relationship with the CDD$MESSAGE_ACTION value of BLOCK or until there are no more ancestors.
SUCCESS
When a relationship has a message action value of SUCCESS, and you change the member of the relationship with the CHANGE command, CDO does not send messages to the owner of the relationship. Instead, CDO sends messages to the owner's ancestors, provided that the ancestors are members of a relationship with the message action value of SIGNAL. CDO sends these messages until the member you are changing has no more ancestors or until CDO encounters a relationship with a message action value of BLOCK. When a relationship has a message action value of SUCCESS, and you create a new version of the member, CDO sends messages to both the owner of the relationship and the owner's ancestors. CDO sends these messages until there are no more ancestors or until CDO encounters a relationship with a message action of BLOCK.
Examples
In the following SHOW PROTOCOL command, the definition of the relationship protocol CDD$DATA_AGGREGATE_CONTAINS is displayed. The message action (identified by the CDD$MESSAGE_ACTION attribute) of this relationship protocol is SUCCESS: CDO> SHOW PROTOCOL CDD$DATA_AGGREGATE_CONTAINS Definition of protocol CDD$DATA_AGGREGATE_CONTAINS (Type : CDD$ELEMEN T_TYPE) | CDD$$RDB_RELATION CDD$$O187 | CDD$GROUPING_RELATION GROUPING | CDD$MESSAGE_ACTION SUCCESS | CDD$OBJECT_KIND CDD$RELATIONSHIP | CDD$PROTOCOL_MAJOR 1 | CDD$PROTOCOL_MINOR 0 | CDD$TAG 2818564 | CDD$ACCESS_CONTROL_LIST (IDENTIFIER=[SYSTEM],ACCESS=READ+ WRITE+MODIFY+ERASE+SHOW+CHANGE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMIN ISTRATOR) | CDD$HAS_ATTRIBUTE | | CDD$OWNER (Type : CDD$ATTRIBUTE_TYPE) | | CDD$ACCESS_CONTROL_LIST (Type : CDD$ATTRIBUTE_TYPE) | | CDD$DATA_AGGREGATE_ALIGNMENT (Type : CDD$ATTRIBUTE_TYPE) | | CDD$DESCRIPTION (Type : CDD$ATTRIBUTE_TYPE) | | CDD$MODIFIED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$CREATED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$DATA_SEQUENCE_NUMBER (Type : CDD$ATTRIBUTE_TYPE) | CDD$OWNS_RELATIONSHIP | | CDD$DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | CDD$RELATIONSHIP_MEMBER | | CDD$DATA_OVERLAY_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_ELEMENT (Type : CDD$ELEMENT_TYPE) CDO> In the following command, the relationship protocol CDD$DATABASE_SCHEMA is displayed. The message action (identified by the CDD$MESSAGE_ACTION attribute) of this relationship protocol is SIGNAL: CDO> SHOW PROTOCOL CDD$DATABASE_SCHEMA Definition of protocol CDD$DATABASE_SCHEMA (Type : CDD$ELEMEN T_TYPE) | CDD$$RDB_RELATION CDD$$O613 | CDD$GROUPING_RELATION NO_GROUPING | CDD$MESSAGE_ACTION SIGNAL | CDD$OBJECT_KIND CDD$RELATIONSHIP | CDD$PROTOCOL_MAJOR 1 | CDD$PROTOCOL_MINOR 0 | CDD$TAG 2818865 | CDD$ACCESS_CONTROL_LIST (IDENTIFIER=[SYSTEM],ACCESS=READ+ WRITE+MODIFY+ERASE+SHOW+CHANGE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMIN ISTRATOR) | CDD$HAS_ATTRIBUTE | | CDD$CREATED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$MODIFIED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$ACCESS_CONTROL_LIST (Type : CDD$ATTRIBUTE_TYPE) | | CDD$DESCRIPTION (Type : CDD$ATTRIBUTE_TYPE) | | CDD$OWNER (Type : CDD$ATTRIBUTE_TYPE) | CDD$OWNS_RELATIONSHIP | | CDD$DATABASE (Type : CDD$ELEMENT_TYPE) | CDD$RELATIONSHIP_MEMBER | | CDD$RMS_DATABASE (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DATABASE (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) CDO> The output of the following command displays the record protocol: CDO> SHOW PROTOCOL RECORD Definition of protocol CDD$DATA_AGGREGATE (Type : CDD$ELEME NT_TYPE) | CDD$$RDB_RELATION CDD$$O183 | CDD$GROUPING_RELATION NO_GROUPING | CDD$MESSAGE_ACTION unknown | CDD$OBJECT_KIND CDD$ENTITY | CDD$PROTOCOL_MAJOR 1 | CDD$PROTOCOL_MINOR 0 | CDD$TAG 2818561 | CDD$ACCESS_CONTROL_LIST (IDENTIFIER=[SYSTEM],ACCESS=READ+ WRITE+MODIFY+ERASE+SHOW+CHANGE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMIN ISTRATOR) | CDD$HAS_ATTRIBUTE | | CDD$VERSION (Type : CDD$ATTRIBUTE_TYPE) | | CDD$MODIFIED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_EBCDIC (Type : CDD$ATTRIBUTE_TYPE) | | IDB$OWNER (Type : CDD$ATTRIBUTE_TYPE) | | CDD$OWNER (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESSING_NAME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$DESCRIPTION (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_PLI (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_PAS (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_RPG (Type : CDD$ATTRIBUTE_TYPE) | | CDD$CREATED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | IDB$MODIFIED_DATE (Type : CDD$ATTRIBUTE_TYPE) | | CDD$ACCESS_CONTROL_LIST (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_BAS (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_COB (Type : CDD$ATTRIBUTE_TYPE) | CDD$OWNS_RELATIONSHIP | | CDD$HISTORY_LIST (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_CONTAINS (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_BASED_ON (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_ARRAY_HAS_DIMENSION (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_COMPUTED_VAL (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DA_DERIVED_FROM (Type : CDD$ELEMENT_TYPE) | CDD$RELATIONSHIP_MEMBER | | CDD$DATA_AGGREGATE_BASED_ON (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_CONTAINS (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_INSTANCE_PATH (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_INSTANCE_ROOT (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_OVERLAY_CONTAINS (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$RMS_DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | IDB$DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$DATABASE_SCHEMA (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DA_DERIVED_FROM (Type : CDD$ELEMENT_TYPE) | CDD$OBJECT_VALIDATION | | CDD$UNIQ_DAC_SEQ_NUM (Type : CDD$VALIDATION) | | CDD$UNIQ_ARRAY_ORDER (Type : CDD$VALIDATION) CDO> The output from the following command displays all of the possible relationships the record protocol can own: CDO> SHOW PROTOCOL/FULL RECORD Definition of protocol CDD$DATA_AGGREGATE (Type : CDD$ELEME NT_TYPE) | CDD$$RDB_RELATION CDD$$O183 | CDD$GROUPING_RELATION NO_GROUPING | CDD$MESSAGE_ACTION unknown | CDD$OBJECT_KIND CDD$ENTITY | CDD$PROTOCOL_MAJOR 1 | CDD$PROTOCOL_MINOR 0 | CDD$TAG 2818561 | CDD$HAS_ATTRIBUTE | | IDB$MODIFIED_DATE (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_PAS (Type : CDD$ATTRIBUTE_TYPE) | | CDD$OWNER (Type : CDD$ATTRIBUTE_TYPE) | | IDB$OWNER (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_EBCDIC (Type : CDD$ATTRIBUTE_TYPE) | | CDD$ACCESS_CONTROL_LIST (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_RPG (Type : CDD$ATTRIBUTE_TYPE) | | CDD$MODIFIED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_PLI (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_BAS (Type : CDD$ATTRIBUTE_TYPE) | | CDD$VERSION (Type : CDD$ATTRIBUTE_TYPE) | | CDD$CREATED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_COB (Type : CDD$ATTRIBUTE_TYPE) | | CDD$DESCRIPTION (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESSING_NAME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$$DIRECTORY_NAME (Type : CDD$ATTRIBUTE_TYPE) | CDD$OWNS_RELATIONSHIP | | CDD$DATA_ARRAY_HAS_DIMENSION (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_COMPUTED_VAL (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DA_DERIVED_FROM (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_CONTAINS (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_BASED_ON (Type : CDD$ELEMENT_TYPE) | | CDD$HISTORY_LIST (Type : CDD$ELEMENT_TYPE) | CDD$RELATIONSHIP_MEMBER | | CDD$DATA_INSTANCE_ROOT (Type : CDD$ELEMENT_TYPE) | | CDD$COMPILED_DEPENDS_ON (Type : CDD$ELEMENT_TYPE) | | IDB$DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$RMS_DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_CONTAINS (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DA_DERIVED_FROM (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_INSTANCE_PATH (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_OVERLAY_CONTAINS (Type : CDD$ELEMENT_TYPE) | | CDD$SOURCE_DEPENDS_ON (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_BASED_ON (Type : CDD$ELEMENT_TYPE) | | CDD$DATABASE_SCHEMA (Type : CDD$ELEMENT_TYPE) | CDD$OBJECT_VALIDATION | | CDD$UNIQ_DAC_SEQ_NUM (Type : CDD$VALIDATION) | | CDD$UNIQ_ARRAY_ORDER (Type : CDD$VALIDATION) | CDD$HAS_LINK | | *** name is unspecified *** (Type : CDD$LINK_TYPE) CDO> The output from the following command displays all the possible relationships the record protocol can own, as well as the access control list for the record protocol: CDO> SHOW PROTOCOL/ALL RECORD Definition of protocol CDD$DATA_AGGREGATE (Type : CDD$ELEME NT_TYPE) | CDD$$RDB_RELATION CDD$$O183 | CDD$GROUPING_RELATION NO_GROUPING | CDD$MESSAGE_ACTION unknown | CDD$OBJECT_KIND CDD$ENTITY | CDD$PROTOCOL_MAJOR 1 | CDD$PROTOCOL_MINOR 0 | CDD$TAG 2818561 | CDD$ACCESS_CONTROL_LIST (IDENTIFIER=[1,4],ACCESS=READ+WRITE+ MODIFY+ERASE+SHOW+CHANGE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ | ADMINISTRATOR) | CDD$HAS_ATTRIBUTE | | IDB$MODIFIED_DATE (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_PAS (Type : CDD$ATTRIBUTE_TYPE) | | CDD$OWNER (Type : CDD$ATTRIBUTE_TYPE) | | IDB$OWNER (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_EBCDIC (Type : CDD$ATTRIBUTE_TYPE) | | CDD$ACCESS_CONTROL_LIST (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_RPG (Type : CDD$ATTRIBUTE_TYPE) | | CDD$MODIFIED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_PLI (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_BAS (Type : CDD$ATTRIBUTE_TYPE) | | CDD$VERSION (Type : CDD$ATTRIBUTE_TYPE) | | CDD$CREATED_TIME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESS_NAME_COB (Type : CDD$ATTRIBUTE_TYPE) | | CDD$DESCRIPTION (Type : CDD$ATTRIBUTE_TYPE) | | CDD$PROCESSING_NAME (Type : CDD$ATTRIBUTE_TYPE) | | CDD$$DIRECTORY_NAME (Type : CDD$ATTRIBUTE_TYPE) | CDD$OWNS_RELATIONSHIP | | CDD$DATA_ARRAY_HAS_DIMENSION (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_COMPUTED_VAL (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DA_DERIVED_FROM (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_CONTAINS (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_BASED_ON (Type : CDD$ELEMENT_TYPE) | | CDD$HISTORY_LIST (Type : CDD$ELEMENT_TYPE) | CDD$RELATIONSHIP_MEMBER | | CDD$DATA_INSTANCE_ROOT (Type : CDD$ELEMENT_TYPE) | | CDD$COMPILED_DEPENDS_ON (Type : CDD$ELEMENT_TYPE) | | IDB$DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$RMS_DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_CONTAINS (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DA_DERIVED_FROM (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_INSTANCE_PATH (Type : CDD$ELEMENT_TYPE) | | CDD$RDB_DATA_AGGREGATE (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_OVERLAY_CONTAINS (Type : CDD$ELEMENT_TYPE) | | CDD$SOURCE_DEPENDS_ON (Type : CDD$ELEMENT_TYPE) | | CDD$DATA_AGGREGATE_BASED_ON (Type : CDD$ELEMENT_TYPE) | | CDD$DATABASE_SCHEMA (Type : CDD$ELEMENT_TYPE) | CDD$OBJECT_VALIDATION | | CDD$UNIQ_DAC_SEQ_NUM (Type : CDD$VALIDATION) | | CDD$UNIQ_ARRAY_ORDER (Type : CDD$VALIDATION) | CDD$HAS_LINK | | *** name is unspecified *** (Type : CDD$LINK_TYPE) CDO>
RECORD
Displays the specified record definition or definitions. If you do not specify a record name, this command displays all record definitions in the default directory that you have privilege to display. SHOW RECORD ──┬─┬────────────>──────────────┬─┬─┬─────────>────────┬─┐ │ ├> typebox (/)
A
L
L ────────────────────┤ │ └┬─> record-name ─┬┘ │ │ ├> typebox (/)
A
U
D
I
T ───┬─────>────┬───┤ │ └────── , <──────┘ │ │ │ └─>
=
A
L
L ──┘ │ │ │ │ ├> typebox (/)
B
R
I
E
F ──────────────────┤ │ │ │ └> typebox (/)
F
U
L
L ───────────────────┘ │ │ └─────────────<─────────────────┘ │ ┌───────────────────────────<────────────────────────────────────────┘ └─┬──────────────────>─────────────────┬──> └─>
F
R
O
M
D
A
T
A
B
A
S
E ──> database-name ─┘
Additional information available:
record-namedatabase-nameQualifiersExamples
record-name
The name of one or more record, relation, or view definitions. You can display multiple records from a CDO dictionary, separating the record names with commas. To display one or more record definitions from an Rdb/VMS database, you must use the FROM DATABASE clause. You can display a single record definition from an Rdb/VMS database by supplying the name of the record definition for "record-name". You can display all the record definitions from a database by specifying the asterisk (*) wildcard character for "record-name". No other wildcard character is valid for the "record-name".
database-name
The name of the Rdb/VMS database that contains the record definition you want to display. You can use wildcard characters in the database-name.
Qualifiers
Additional information available:
/ALL
Displays the user-specified and system attributes used in the record definition. The names and attributes of objects owned by the record definition and the names and attributes of descendants of these objects are displayed. The record description and history list entries are also displayed.
/AUDIT
Displays the history list entries for the record definition. This qualifier cannot be used when displaying record definitions from a database.
/AUDIT=ALL
Displays the history list for all entities owned by the record definition. This qualifier cannot be used when displaying record definitions from a database.
/BRIEF (default)
The names of objects owned by the specified record definition are displayed.
/FULL
Displays the user-specified attributes used in the record definition. The names and attributes of objects owned by the record definition and the names and attributes of descendants of these objects are also displayed.
Examples
The following command displays the brief definition of the FULL_NAME record. CDO> SHOW RECORD FULL_NAME Definition of record FULL_NAME | Contains field LAST_NAME | Contains field FIRST_NAME | Contains field MIDDLE_INITIAL CDO> The following command displays the history list entries for the record definition FULL_NAME: CDO> SHOW RECORD/AUDIT FULL_NAME Definition of record FULL_NAME | History entered by SMITH ([VCD,SMITH]) | using CDO V1.0 | to CREATE definition on 5-MAY-1987 15:11:07.07 CDO> The following command displays the complete record definition for ADDRESS_RECORD: CDO> SHOW RECORD/ALL ADDRESS_RECORD Definition of record ADDRESS_RECORD | acl IDENTIFIER=[VCD,SMITH],ACCESS=READ+WRITE+MODIFY+ERA SE+SHOW+DEFINE+CHANGE+DELETE+CONTROL+OPERATOR+ADMINISTRATOR) (IDENTIFIER=[*,*],ACCESS=READ+WRITE+MODIFY+ERASE+SHOW+OPERATOR+ADMINI STRATOR) | Created time 8-MAY-1987 14:05:24.76 | Modified time 8-MAY-1987 14:05:24.76 | Owner SMITH | | History entered by SMITH ([VCD,SMITH]) | | using CDO V1.0 | | to CREATE definition on 8-MAY-1987 14:05:20.56 | Contains field STREET | | Datatype text size is 25 characters | | | History entered by SMITH ([VCD,SMITH]) | | | using CDO V1.0 | | | to CREATE definition on 8-MAY-1987 14:04:33.57 | Contains field CITY | | Datatype text size is 25 characters | | | History entered by SMITH ([VCD,SMITH]) | | | using CDO V1.0 | | | to CREATE definition on 8-MAY-1987 14:04:44.57 | Contains field STATE | | Datatype text size is 2 characters | | | History entered by SMITH ([VCD,SMITH]) | | | using CDO V1.0 | | | to CREATE definition on 8-MAY-1987 14:04:55.08 | Contains field ZIP_CODE | | Description ' a 5 digit postal code ' | | Datatype unsigned numeric digits 5 | | | History entered by SMITH ([VCD,SMITH]) | | | using CDO V1.0 | | | to CREATE definition on 24-APR-1987 14:37:29.02 | | | Explanation: | | | this will change eventually | | | History entered by SMITH ([VCD,SMITH]) | | | using CDO V1.0 | | | to modify an ACL entry on 25-APR-1987 16:44:12.85 | | | History entered by SMITH ([VCD,SMITH]) | | | using CDO V1.0 | | | to modify an ACL entry on 25-APR-1987 16:49:02.52 | | | History entered by SMITH ([VCD,SMITH]) | | | using CDO V1.0 | | | to modify an ACL entry on 25-APR-1987 16:50:35.98 CDO> The following command displays each record definition in your current default directory: CDO> SHOW RECORD Definition of record ADDRESS_RECORD | Contains field STREET | Contains field CITY | Contains field STATE | Contains field ZIP_CODE Definition of record FULL_NAME | Contains field LAST_NAME | Contains field FIRST_NAME | Contains field MIDDLE_INITIAL CDO> In the following example, SHOW RECORD/FULL with the FROM DATABASE clause displays the user-specified attributes for the record definition EMPLOYEES from the Rdb/VMS database DEPT3: CDO> SHOW RECORD/FULL EMPLOYEES FROM DATABASE DEPT3 Definition of record EMPLOYEES | Contains field EMPLOYEE_ID | | Based on ID_NUMBER | | | Datatype text size is 5 characters | Contains field LAST_NAME | | Datatype text size is 14 characters | Contains field FIRST_NAME | | Datatype text size is 10 characters | Contains field MIDDLE_INIT | | Datatype text size is 1 characters | | Edit_string "X" | | Missing_value " " | Contains field ADDRESS_DATA_1 | | Datatype text size is 25 characters | | Missing_value " " | Contains field ADDRESS_DATA_2 | | Datatype text size is 20 characters | | Missing_value " " | Contains field CITY | | Datatype text size is 20 characters | | Missing_value " " | Contains field STATE | | Datatype text size is 2 characters | | Missing_value " " | Contains field POSTAL_CODE | | Datatype text size is 5 characters | | Missing_value " " | Contains field SEX | | Datatype text size is 1 characters | | Missing_value "?" | | Valid if ((SEX EQ "M") OR ((SEX EQ "F") OR (SEX MISSING))) | Contains field BIRTHDAY | | Based on STANDARD_DATE | | | Datatype date | | | Edit_string "DD-MMM-YYYY" | | | Missing_value "17-NOV-1858 00:00:00.00" CDO> The following example displays the history lists for all of the entities owned by the record EMPLOYEE_REC: CDO> SHOW RECORD/AUDIT=ALL EMPLOYEE_REC Definition of EMPLOYEE_REC (Type : CDD$DATA_AGGREGATE) | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | using CDO V1.0 | | to CREATE definition on 3-DEC-1987 14:00:06.65 | Contains CDD$DATA_AGGREGATE_CONTAINS | | LAST_NAME (Type : CDD$DATA_ELEMENT) | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | using CDO V1.0 | | | | to CREATE definition on 3-DEC-1987 13:59:46.01 | Contains CDD$DATA_AGGREGATE_CONTAINS | | FIRST_NAME (Type : CDD$DATA_ELEMENT) | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | using CDO V1.0 | | | | to CREATE definition on 3-DEC-1987 13:59:59.42 | Contains CDD$DATA_AGGREGATE_CONTAINS | | EMP_ID (Type : CDD$DATA_ELEMENT) | | | | History entered by MCGUIRE ([VCD,MCGUIRE]) | | | | using CDO V1.0 | | | | to CREATE definition on 3-DEC-1987 14:00:01.99 CDO>
RMS_DATABASE
Displays the logical definition of an RMS database. SHOW_RMSDATABASE ─┬─┬──────────>──────────┬─┬─┬──────────>──────────┬> │ ├> typebox (/)
A
L
L ─────────────┤ │ └> rms-database-name ─┘ │ ├> typebox (/)
A
U
D
I
T ─┬────>────┬┤ │ │ │ └─>
=
A
L
L ─┘│ │ │ ├> typebox (/)
B
R
I
E
F ────────────┤ │ │ └> typebox (/)
F
U
L
L ─────────────┘ │ └───────────<─────────────┘
Additional information available:
rms-database-nameQualifiersExamples
rms-database-name
The name of a logical RMS database definition.
Qualifiers
Additional information available:
/ALL
Displays the user-specified and system attributes used in the logical RMS database definition. The names and attributes of objects owned by the RMS database definition and the names and attributes of descendants of these objects are displayed. The RMS database description and history list entries are also displayed.
/AUDIT
Displays the history list entries for the RMS database definition.
/AUDIT=ALL
Displays the history list for all entities owned by the logical RMS database definition.
/BRIEF (default)
Displays the file organization attributes for the RMS database definition.
/FULL
Displays the file organization attributes, the record definition, and the description for the logical RMS database definition.
Examples
The following example displays the user-specified attributes of the logical RMS database definition EMPLOYEE_STORAGE: CDO> SHOW RMS_DATABASE/FULL EMPLOYEE_STORAGE Definition of RMS database EMPLOYEE_STORAGE | Description 'CORPORATE STANDARD FOR NAMES AND EMPLOYEE' | 'IDENTIFICATION NUMBERS' | 'OF CURRENT EMPLOYEES' | database uses record EMPLOYEE_REC | | Contains field LAST_NAME | | | Datatype text size is 30 characters | | Contains field FIRST_NAME | | | Datatype text size is 20 characters | | Contains field EMP_ID | | | Datatype unsigned longword | file definition | | file allocation 200 | | file contiguous | | file organization index sequential | | key 0 | | | key changes | | | key duplicates | | | segment LAST_NAME IN EMPLOYEE_REC | | key 1 | | | key changes | | | segment EMP_ID IN EMPLOYEE_REC CDO> The next example displays the history list of the logical RMS database definition EMPLOYEE_STORAGE: CDO> SHOW RMS_DATABASE/AUDIT EMPLOYEE_STORAGE Definition of EMPLOYEE_STORAGE (Type : CDD$RMS_DATABASE) | History entered by MCGUIRE ([VCD,MCGUIRE]) | using CDO V1.0 | to CREATE definition on 7-DEC-1987 10:30:55.69 | Explanation: | MIDDLE INITIAL WILL BE ADDED IN 7/88 CDO> The following command displays each RMS database definition in your current default directory: CDO> SHOW RMS_DATABASE Definition of RMS database EMPLOYEE_STORAGE | Description 'CORPORATE STANDARD FOR NAMES AND EMPLOYEE' | 'IDENTIFICATION NUMBERS' | 'OF CURRENT EMPLOYEES' | database uses record EMPLOYEE_REC | file definition | | file allocation 200 | | file contiguous | | file organization index sequential | | key 0 | | | key changes | | | key duplicates | | | segment LAST_NAME IN EMPLOYEE_REC | | key 1 | | | key changes | | | segment EMP_ID IN EMPLOYEE_REC CDO>
UNUSED
Determines whether an object is an ancestor or descendant of other objects in the dictionary. SHOW UNUSED ┬┬──────────────────>──────────────────┬┬┬> object-name ─┬─> │├> typebox (/)
T
Y
P
Etypebox (=) ( ─┬─> protocol-name ─┬> ) ─┤│└───── , <──────┘ ││ └───────── , <─────┘ ││ │├> typebox (/)
B
R
I
E
F ────────────────────────────┤│ │└> typebox (/)
F
U
L
L ─────────────────────────────┘│ └───────────────────<───────────────────┘
Additional information available:
protocol-nameobject-nameQualifiersRestrictionsRdb Examples
RMS Examples
protocol-name
The name of one or more protocols.
object-name
The name of one or more objects in the dictionary.
Qualifiers
Additional information available:
/TYPE=(protocol-name,...)
You can specify the names of one or more entity or relationship protocols. If this qualifier is used, only objects that are not used by and do not use any relationships or entities of the specified protocols are displayed. You cannot use wildcard characters in the protocol-name.
/BRIEF (default)
Determines whether the specified object has any immediate ancestors or descendants. An immediate ancestor is an object that owns a relationship of which the specified object is a member. An immediate descendant is an object that is a member of a relationship owned by the specified object. Objects are displayed only if they are not directly used by or do not directly use any relationships or entities in the dictionary.
/FULL
Determines whether the specified object has any ancestors or descendants. Objects are displayed only if they are not used by or do not use any relationships or entities in the dictionary.
Restrictions
This command lists only the names of unused objects that have directory names.
Rdb Examples
The following figure shows a CDO definition of an Rdb/VMS database
called MY_RDB_DB that contains CDO field definitions and record
definitions. The following examples refer to the definitions in this
figure:
MY_RDB_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RDB_DB (CDD$FILE) MY_RDB_DB (CDD$RDB_DATABASE)
|
----------------------------------------
| | |
REC_A REC_B REC_C
| | |
FLD_A FLD_B FLD_C
The database MY_RDB_DB was created in RDO using a CDD/Plus path name,
causing the following three entities to be created in the dictionary:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RDB_DATABASE - describes the logical definition
of the database.
o CDD$FILE - describes the physical location
of the database on disk.
The output from the SHOW UNUSED command shows that the database
MY_RDB_DB has either immediate ancestors or descendants:
CDO> SHOW UNUSED MY_RDB_DB
USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 is referenced by or
references other entity(s)
CDO>
In the next two examples, the SHOW USES and SHOW USED_BY commands are
used to find out the names of the immediate ancestors or descendants of
the database definition MY_RDB_DB.
The output from the SHOW USES command shows that the database
definition MY_RDB_DB does not have immediate ancestors.
CDO> SHOW USES MY_RDB_DB
CDO>
The output from the SHOW USED_BY command shows that the database
definition MY_RDB_DB does have two immediate descendants. The
descendants are CDD$FILE and CDD$RDB_DATABASE:
CDO> SHOW USED_BY MY_RDB_DB
Members of USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1
| MY_RDB_DB (Type : CDD$FILE)
| | via CDD$DATABASE_FILE
| MY_RDB_DB (Type : CDD$RDB_DATABASE)
| | via CDD$DATABASE_SCHEMA
CDO>
In the next example, the output from the SHOW UNUSED command shows that
the field definition FLD_A has immediate ancestors or descendants:
CDO> SHOW UNUSED FLD_A
USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_A;1 is referenced by or references
other entity(s)
CDO>
In the next example, the DEFINE FIELD command creates the field
definition FLD_B;2. The output from the SHOW UNUSED command shows that
the new version of FLD_B does not have any immediate ancestors or
descendants:
CDO> SHOW UNUSED FLD_B;2
USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_B;2 (Type : FIELD)
CDO>
In the following example, the output from the SHOW UNUSED command
indicates that FLD_B;1 does have either immediate ancestors or
descendants:
CDO> SHOW UNUSED FLD_B;1
USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_B;1 is referenced by or references
other entity(s)
CDO>
RMS Examples
The following figure shows a CDO definition of an RMS database called
MY_PHYSICAL_RMS_DB that contains one CDO record definition. The
following examples refer to the definitions in this figure:
MY_PHYSICAL_RMS_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RMS_DB (CDD$FILE) MY_RMS_DB (CDD$RMS_DATABASE)
|
|
RECORD_E
|
-----------------------------------------
| | |
| | |
FIELD_F FIELD_G FIELD_H
The database MY_PHYSICAL_RMS_DB was created using the RMS database
definition MY_RMS_DB on the disk location DISK1:[SMITH.DICT]MY_RMS_DB.
Creating MY_PHYSICAL_RMS_DB also causes the following three entities to
be created in the dictionary:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RMS_DATABASE - describes the logical definition
of the database.
o CDD$FILE - describes the physical location
of the database on disk.
The SHOW UNUSED command shows that the RMS physical database definition
has either immediate ancestors or descendants:
SHOW UNUSED MY_PHYSICAL_RMS_DB
DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1 is referenced by or
references other entity(s)
CDO>
In the following two examples, the SHOW USES and SHOW USED_BY commands
are used to find out the names of the immediate ancestors or
descendants of the physical database definition MY_PHYSICAL_RMS_RDB.
The output from the SHOW USES command shows that the database
definition MY_PHYSICAL_RMS_DB does not have immediate ancestors.
CDO> SHOW USES MY_PHYSICAL_RMS_DB
CDO>
The output from the SHOW USED_BY command shows that the physical
database definition MY_PHYSICAL_RMS_DB does have two immediate
descendants. The descendants are CDD$FILE and CDD$RMS_DATABASE:
SHOW USED_BY MY_PHYSICAL_RMS_DB
Members of DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1
| DISK1:[SMITH.DICT]MY_RMS_DB (Type : CDD$FILE)
| | via CDD$DATABASE_FILE
| DISK1:[SMITH.DICT]MY_RMS_DB;1 (Type : CDD$RMS_DATABASE)
| | via CDD$DATABASE_SCHEMA
CDO>
In the next example, the DEFINE FIELD command creates the field
definition FIELD_F;2. The output from the SHOW UNUSED command shows
that the new version of FIELD_F does not have any immediate ancestors
or descendants:
CDO> SHOW UNUSED/FULL FIELD_F;2
DISK1:[SMITH.DICT]FIELD_F;2 (Type : FIELD)
CDO>
In the next example, the SHOW UNUSED command with the /FULL and
/TYPE=(RECORD) qualifiers shows that the physical RMS database
definition MY_PHYSICAL_RMS_DB has either ancestors or descendants that
are records (protocol type of CDD$DATA_AGGREGATE):
CDO> SHOW UNUSED/FULL/TYPE=(RECORD) MY_PHYSICAL_RMS_DB
DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1 is referenced by or
references other entity(s)
CDO>
USED_BY
Displays the CDO objects that are used by the specified object or objects. The display includes a listing of the descendant objects, the type of each object, and the relationship of which each listed object is a member. SHOW USEDBY ─┬─┬──────────────────>─────────────────┬─┬─┬──┐ │ ├> typebox (/)
T
Y
P
Etypebox (=) ( ─┬> protocol-name ─┬> ) ─┘ │ │ │ │ │ └─────── , <──────┘ │ │ │ │ ├> typebox (/)
B
R
I
E
F ─────────────────────────────┤ │ │ │ └> typebox (/)
F
U
L
L ──────────────────────────────┘ │ │ └────────────────────<─────────────────────┘ │ ┌───────────────────────────<──────────────────────────┘ └─┬> object-name ─┬─> └────── , <─────┘
Additional information available:
protocol-nameobject-nameQualifiersRdb ExamplesRMS Examples
protocol-name
The names of one or more protocols.
object-name
The names of one or more objects that may use other objects.
Qualifiers
Additional information available:
/TYPE=(protocol-name,...)
Displays only the objects of the specified protocol that are used by the object specified in object-name. You cannot use wildcard characters in the protocol-name.
/BRIEF (default)
Displays each object that is an immediate descendant of the specified object. An immediate descendant is a member of a relationship with the specified object. The name of each immediate descendant, its type, and the relationship it is a member of is listed.
/FULL
Displays each object that is a descendant of the specified object. The name of every descendant, its type, and the relationship that it is a member of is displayed.
Rdb Examples
The following figure shows a CDO definition of an RDB/VMS database
called MY_RDB_DB that contains CDO field definitions and record
definitions. The following examples refer to the definitions in this
figure:
MY_RDB_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RDB_DB (CDD$FILE) MY_RDB_DB (CDD$RDB_DATABASE)
|
----------------------------------------
| | |
REC_A REC_B REC_C
| | |
FLD_A FLD_B FLD_C
The database MY_RDB_DB was created in RDO using a CDD/Plus path name,
causing three entities to be created in the dictionary. These are:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RDB_DATABASE - describes the logical definition of the
file.
o CDD$FILE - describes the physical location of the
database on disk.
The following command displays the dictionary definitions that are
immediate descendants of the database definition MY_RDB_DB:
CDO> SHOW USED_BY/BRIEF MY_RDB_DB
Members of USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1
| MY_RDB_DB (Type : CDD$FILE)
| | via CDD$DATABASE_FILE
| MY_RDB_DB (Type : CDD$RDB_DATABASE)
| | via CDD$DATABASE_SCHEMA
CDO>
The following command displays all descendants of the database
definition MY_RDB_DB:
CDO> SHOW USED_BY/FULL MY_RDB_DB
Members of USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1
| MY_RDB_DB (Type : CDD$FILE)
| | via CDD$DATABASE_FILE
| MY_RDB_DB (Type : CDD$RDB_DATABASE)
| | via CDD$DATABASE_SCHEMA
| | USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_A;1 (Type : FIELD)
| | | via CDD$RDB_DATA_ELEMENT
| | USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_B;1 (Type : FIELD)
| | | via CDD$RDB_DATA_ELEMENT
| | USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_C;1 (Type : FIELD)
| | | via CDD$RDB_DATA_ELEMENT
| | USR$DISK:[RICK.NEWDICT]GLOBAL.REC_A;1 (Type : RECORD)
| | | via CDD$RDB_DATA_AGGREGATE
| | | USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_A;1 (Type : FIELD)
| | | | via CDD$DATA_AGGREGATE_CONTAINS
| | USR$DISK:[RICK.NEWDICT]GLOBAL.REC_B;1 (Type : RECORD)
| | | via CDD$RDB_DATA_AGGREGATE
| | | USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_B;1 (Type : FIELD)
| | | | via CDD$DATA_AGGREGATE_CONTAINS
| | USR$DISK:[RICK.NEWDICT]GLOBAL.REC_C;1 (Type : RECORD)
| | | via CDD$RDB_DATA_AGGREGATE
| | | USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_C;1 (Type : FIELD)
| | | | via CDD$DATA_AGGREGATE_CONTAINS
CDO>
The following command displays all field definitions that are
descendants of MY_RDB_DB. All the fields are displayed at the same
indentation level, indicating that they do not have the same path:
CDO> SHOW USED_BY/TYPE=(FIELD)/FULL MY_RDB_DB
Members of USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1
| USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_C;1 (Type : FIELD)
| | via CDD$RDB_DATA_ELEMENT ( 1 unshown intermediate nodes)
| USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_B;1 (Type : FIELD)
| | via CDD$RDB_DATA_ELEMENT ( 1 unshown intermediate nodes)
| USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_A;1 (Type : FIELD)
| | via CDD$RDB_DATA_ELEMENT ( 1 unshown intermediate nodes)
| USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_C;1 (Type : FIELD)
| | via CDD$DATA_AGGREGATE_CONTAINS ( 2 unshown intermediate nodes)
| USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_B;1 (Type : FIELD)
| | via CDD$DATA_AGGREGATE_CONTAINS ( 2 unshown intermediate nodes)
| USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_A;1 (Type : FIELD)
| | via CDD$DATA_AGGREGATE_CONTAINS ( 2 unshown intermediate nodes)
CDO>
If a definition has no descendants, you are returned the CDO> prompt:
CDO> SHOW USED_BY/BRIEF FIELD_D
CDO>
RMS Examples
The following figure shows a CDO definition of an RMS database called
MY_PHYSICAL_RMS_DB that contains one CDO record definition. The
following examples refer to the definitions in this figure:
MY_PHYSICAL_RMS_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RMS_DB (CDD$FILE) MY_RMS_DB (CDD$RMS_DATABASE)
|
|
RECORD_E
|
-----------------------------------------
| | |
| | |
FIELD_F FIELD_G FIELD_H
The database MY_PHYSICAL_RMS_DB was created using the RMS database
definition MY_RMS_DB on the disk location DISK1:[SMITH.DICT]MY_RMS_DB.
Creating the database also caused the following three entities to be
created in the dictionary:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RMS_DATABASE - describes the logical definition
of the database.
o CDD$FILE - describes the physical location
of the database on disk.
The SHOW USED_BY command with the /FULL qualifier displays all the
descendants of the physical RMS database definition MY_PHYSICAL_RMS_DB:
CDO> SHOW USED_BY/FULL MY_PHYSICAL_RMS_DB
Members of DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1
| DISK1:[SMITH.DICT]MY_RMS_DB (Type : CDD$FILE)
| | via CDD$DATABASE_FILE
| DISK1:[SMITH.DICT]MY_RMS_DB;2 (Type : CDD$RMS_DATABASE)
| | via CDD$DATABASE_SCHEMA
| | DISK1:[SMITH.DICT]RECORD_E;1 (Type : RECORD)
| | | via CDD$RMS_DATA_AGGREGATE
| | | DISK1:[SMITH.DICT]FIELD_F;1 (Type : FIELD)
| | | | via CDD$DATA_AGGREGATE_CONTAINS
| | | DISK1:[SMITH.DICT]FIELD_G;1 (Type : FIELD)
| | | | via CDD$DATA_AGGREGATE_CONTAINS
| | *** name is unspecified *** (Type : CDD$FILE_DEFINITION)
| | | via CDD$RMS_FILE_DEFINITION
CDO>
In the following example, the SHOW USED_BY command displays the
dictionary definitions that are the immediate descendants of the
physical RMS database definition MY_PHYSICAL_RMS_DB:
CDO> SHOW USED_BY MY_PHYSICAL_RMS_DB
Members of DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1
| DISK1:[SMITH.DICT]MY_RMS_DB (Type : CDD$FILE)
| | via CDD$DATABASE_FILE
| DISK1:[SMITH.DICT]MY_RMS_DB;1 (Type : CDD$RMS_DATABASE)
| | via CDD$DATABASE_SCHEMA
CDO>
USES
Displays the CDO objects that use the specified object or objects. The display includes a list of the ancestor objects, the type of each object, and the relationship of which each listed object is an owner. SHOW USES ──┬─┬───────────────────>────────────────┬─┬─┬───┐ │ ├> typebox (/)
T
Y
P
Etypebox (=) ( ─┬> protocol-name ─┬> ) ─┘ │ │ │ │ │ └─────── , <──────┘ │ │ │ │ ├> typebox (/)
B
R
I
E
F ─────────────────────────────┤ │ │ │ └> typebox (/)
F
U
L
L ──────────────────────────────┘ │ │ └────────────────────<─────────────────────┘ │ ┌────────────────────────<──────────────────────────┘ └────┬> object-name ─┬────> └────── , <─────┘
Additional information available:
protocol-nameobject-nameQualifiersRdb ExamplesRMS Examples
protocol-name
The name of one or more protocols.
object-name
The name of one or more objects that may be used by other objects.
Qualifiers
Additional information available:
/TYPE=(protocol-name,...)
Displays only the objects of the specified protocol that use the object specified in object-name. You cannot use wildcard characters in the protocol-name.
/BRIEF (default)
Displays each object that is an immediate ancestor of the specified object. An immediate ancestor is the owner of a relationship with the specified object. The name of each immediate ancestor, its type, and the relationship it owns is listed.
/FULL
Displays each object that is an ancestor of the specified object. The name of every ancestor, its type, and the relationship that the ancestor owns is displayed.
Rdb Examples
The following figure shows a CDO definition of an RDB/VMS database
called MY_RDB_DB that contains CDO field definitions and record
definitions. The following examples refer to the definitions in this
figure:
MY_RDB_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RDB_DB (CDD$FILE) MY_RDB_DB (CDD$RDB_DATABASE)
|
----------------------------------------
| | |
REC_A REC_B REC_C
| | |
FLD_A FLD_B FLD_C
The database MY_RDB_DB was created in RDO using a CDD/Plus path name,
causing three entities to be created in the dictionary. These are:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RDB_DATABASE - describes the logical definition of the
file.
o CDD$FILE - describes the physical location of the
database on disk.
The following command displays the dictionary definitions that are
immediate ancestors of field definition FLD_C:
CDO> SHOW USES FLD_C
Owners of USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_C;1
| USR$DISK:[RICK.NEWDICT]GLOBAL.REC_C;1 (Type : RECORD)
| | via CDD$DATA_AGGREGATE_CONTAINS
| MY_RDB_DB (Type : CDD$RDB_DATABASE)
| | via CDD$RDB_DATA_ELEMENT
CDO>
The following command displays all ancestors of the field definition
FLD_C:
CDO> SHOW USES/FULL FLD_C
Owners of USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_C;1
| USR$DISK:[RICK.NEWDICT]GLOBAL.REC_C;1 (Type : RECORD)
| | via CDD$DATA_AGGREGATE_CONTAINS
| | MY_RDB_DB (Type : CDD$RDB_DATABASE)
| | | via CDD$RDB_DATA_AGGREGATE
| | | USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 (Type : CDD$DATAB
ASE)
| | | | via CDD$DATABASE_SCHEMA
| MY_RDB_DB (Type : CDD$RDB_DATABASE)
| | via CDD$RDB_DATA_ELEMENT
| | USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 (Type : CDD$DATABASE)
| | | via CDD$DATABASE_SCHEMA
CDO>
The following command displays record definitions that are immediate
ancestors of the field definition FLD_B:
CDO> SHOW USES/TYPE=(RECORD) FLD_B
Owners of USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_B;1
| USR$DISK:[RICK.NEWDICT]GLOBAL.REC_B;1 (Type : RECORD)
| | via CDD$DATA_AGGREGATE_CONTAINS
CDO>
The following command displays all record definitions that are
ancestors of the field definition FLD_B:
CDO> SHOW USES/FULL/TYPE=(RECORD) FLD_B
Owners of USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_B;1
| USR$DISK:[RICK.NEWDICT]GLOBAL.REC_B;1 (Type : RECORD)
| | via CDD$DATA_AGGREGATE_CONTAINS
CDO>
If there are no ancestors to display, you are returned the CDO> prompt:
CDO> SHOW USES/TYPE=(RECORD) FIELD_D
CDO>
RMS Examples
The following figure shows a CDO definition of an RMS database called
MY_PHYSICAL_RMS_DB that contains one CDO record definition. The
following examples refer to the definitions in this figure:
MY_PHYSICAL_RMS_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RMS_DB (CDD$FILE) MY_RMS_DB (CDD$RMS_DATABASE)
|
|
RECORD_E
|
-----------------------------------------
| | |
| | |
FIELD_F FIELD_G FIELD_H
The database MY_PHYSICAL_RMS_DB was created using the RMS database
definition MY_RMS_DB on the disk location DISK1:[SMITH.DICT]MY_RMS_DB.
Creating the database also caused the following three entities to be
created in the dictionary:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RMS_DATABASE - describes the logical definition
of the database.
o CDD$FILE - describes the physical location
of the database on disk.
In the following example, the SHOW USES command returns the CDO prompt
because MY_PHYSICAL_RMS_DB does not have ancestors:
CDO> SHOW USES MY_PHYSICAL_RMS_DB
CDO>
In the following example, the SHOW USES command with the /FULL
qualifier displays all the ancestors of MY_RMS_DB:
CDO> SHOW USES/FULL MY_RMS_DB
Owners of DISK1:[SMITH.DICT]MY_RMS_DB;1
| DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA
CDO>
In the following example, the SHOW USES command displays the immediate
ancestors of RECORD_E:
CDO> SHOW USES RECORD_E
Owners of DISK1:[SMITH.DICT]RECORD_E;1
| DISK1:[SMITH.DICT]MY_RMS_DB;1 (Type : CDD$RMS_DATABASE)
| | via CDD$RMS_DATA_AGGREGATE
CDO>
In the following example, the SHOW USES command with the /FULL
qualifier displays all the ancestors of FIELD_H:
CDO> SHOW USES/FULL FIELD_H
Owners of DISK1:[SMITH.DICT]FIELD_H;1
| DISK1:[SMITH.DICT]RECORD_E;1 (Type : RECORD)
| | via CDD$DATA_AGGREGATE_CONTAINS
| | DISK1:[SMITH.DICT]MY_RMS_DB;1 (Type : CDD$RMS_DATABASE)
| | | via CDD$RMS_DATA_AGGREGATE
CDO>
In the following example, the SHOW USES command with the
/TYPE=(CDD$DATABASE) qualifier displays the immediate ancestors of
MY_RMS_DB that are physical databases:
CDO> SHOW USES/TYPE=(CDD$DATABASE) MY_RMS_DB;1
Owners of DISK1:[SMITH.DICT]MY_RMS_DB;1
| DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA
CDO>
VERSION
If you do not invoke a dictionary during your CDO session, this command displays only the version of CDO, CDD/Plus, and the fully qualified name of your dictionary. If you invoke at least one dictionary during your CDO session, this command displays the major and minor version numbers, the fully qualified names of the dictionaries that you invoked during your CDO session, and the version of CDO and CDD/Plus that your dictionaries use. If you want to display the major and minor version numbers that your dictionary uses, you must first use a CDO command that invokes your dictionary. CDO commands such as DEFINE FIELD or SHOW FIELD invoke a dictionary. CDO commands such as SET DEFAULT and SHOW DEFAULT do not invoke a dictionary. The CDO command DIRECTORY does not invoke a dictionary that contains only directories. SHOW VERSION ──>
Additional information available:
reporting problemsversion number changesmoving your dictionaryExamples
reporting problems
When you report a dictionary problem to DIGITAL, be sure to include the major and minor version numbers of the dictionary you are using.
version number changes
Major version numbers change when the on-disk structure of the dictionary changes, requiring you to upgrade your dictionary. Minor version numbers change when DIGITAL software adds protocols to your dictionary; however, you can still run your new software on the old dictionary on-disk structure without an upgrade.
moving your dictionary
Before moving your dictionary from one cluster to another cluster, use the SHOW VERSION command to make certain that the dictionary on the target cluster has the same major version number as the dictionary on the source cluster. If the dictionary installed on the target cluster has a different major version number, you will not be able to access your dictionary.
Examples
In the following example, the user does not issue a CDO command that
invokes a dictionary before using the SHOW VERSION command; therefore,
all the version information for the dictionary is not displayed:
CDO> SHOW DEFAULT
USR02:[SMITH.DICT]
CDO> SHOW VERSION
CDO V1.0
CDD/Plus V4.0
CDO>
In the following example, the user issues the SHOW FIELD command, which
invokes a dictionary, before using the SHOW VERSION command; therefore,
all the version information for the dictionary is displayed:
CDO> SHOW FIELD FIRST_NAME
Definition of field FIRST_NAME
| Datatype text size is 20 characters
CDO> SHOW VERSION
CDO V1.0
CDD/Plus V4.0
Dictionary USR02:[SMITH.DICT]CDD$DATABASE;1
Major Version 14
Minor Version 3
CDO>
In the following example, two dictionaries were invoked during a CDO
session, and the SHOW VERSION command displays the major and minor
version numbers of both dictionaries:
CDO> SHOW VERSION
CDO V1.0
CDD/Plus V4.0
Dictionary USR$DISK:[MCGUIRE.NEWDICT]CDD$DATABASE;1
Major Version 14
Minor Version 3
Dictionary USR$DISK:[MCGUIRE.DICT]CDD$DATABASE;1
Major Version 14
Minor Version 3
CDO>
WHAT_IF
Displays the ancestor objects that can be affected if the specified dictionary object is modified by the CHANGE command. SHOW WHATIF ─┬─┬──────────────────>─────────────────┬─┬─┬───┐ │ ├> typebox (/)
T
Y
P
Etypebox (=) ( ─┬> protocol-name ─┬> ) ─┘ │ │ │ │ │ └─────── , <──────┘ │ │ │ │ ├> typebox (/)
F
U
L
L ──────────────────────────────┤ │ │ │ └> typebox (/)
B
R
I
E
F ─────────────────────────────┘ │ │ └────────────────────<─────────────────────┘ │ ┌─────────────────────────<───────────────────────────┘ └──┬> object-name ─┬──> └────── , <─────┘ Ancestor objects are only displayed if the relationship between them and the specified object has a CDD$MESSAGE_ACTION attribute value of SIGNAL. For more information on the CDD$MESSAGE_ACTION attribute, see the subtopic "message_actions" under the SHOW PROTOCOL help topic. The display includes a listing of the ancestor objects that can be affected, the type of each object, and the relationship of which each object listed is an owner. Each object listed receives a possibly invalid message if you modify the specified object using the CHANGE command.
Additional information available:
protocol-nameobject-nameQualifiersRdb ExamplesRMS Examples
protocol-name
The name of one or more protocols.
object-name
The name of one or more objects that you are considering changing.
Qualifiers
Additional information available:
/TYPE=(protocol-name,...)
Displays only the objects of the specified protocol that will receive a possibly invalid message if the specified object is changed in place with the CHANGE command. You cannot use wildcard characters in the protocol-name.
/BRIEF (default)
Displays the immediate ancestors to the specified object that will receive a possibly invalid message if the specified object is changed in place with the CHANGE command.
/FULL
Displays all ancestors to the specified object that will receive a possibly invalid message if the specified object is changed in place with the CHANGE command.
Rdb Examples
The following figure shows a CDO definition of an RDB/VMS database
called MY_RDB_DB that contains CDO field definitions and record
definitions. The following examples refer to the definitions in this
figure:
MY_RDB_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RDB_DB (CDD$FILE) MY_RDB_DB (CDD$RDB_DATABASE)
|
----------------------------------------
| | |
REC_A REC_B REC_C
| | |
FLD_A FLD_B FLD_C
The database MY_RDB_DB was created in RDO using a CDD/Plus path name,
causing three entities to be created in the dictionary. These are:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RDB_DATABASE - describes the logical definition of the
file.
o CDD$FILE - describes the physical location of the
database on disk.
The following command lists the ancestors that will receive a possibly
invalid message if field definition FLD_A is changed in place with the
CHANGE command:
CDO> SHOW WHAT_IF/FULL FLD_A
Signaled owners of USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_A;1
| USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA ( 1 unshown intermediate nodes)
| USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA ( 2 unshown intermediate nodes)
CDO>
The following command shows the ancestors of type CDD$DATABASE that
will receive a possibly invalid message if FLD_A is changed in place
with the CHANGE command:
CDO> SHOW WHAT_IF/FULL/TYPE=(CDD$DATABASE) FLD_A
Signaled owners of USR$DISK:[RICK.NEWDICT]GLOBAL.FLD_A;1
| USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA ( 1 unshown intermediate nodes)
| USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA ( 2 unshown intermediate nodes)
CDO>
If no immediate ancestors will receive a possibly invalid message if a
definition is changed in place with the CHANGE command, the CDO prompt
is returned:
CDO> SHOW WHAT_IF/BRIEF FLD_A
CDO>
In the following example, the SHOW WHAT_IF/FULL command lists all
ancestors that will receive a possibly invalid message if record
definition REC_A is changed in place with the CHANGE command:
CDO> SHOW WHAT_IF/FULL REC_A
Signaled owners of USR$DISK:[RICK.NEWDICT]GLOBAL.REC_A;1
| USR$DISK:[RICK.NEWDICT]GLOBAL.MY_RDB_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA ( 1 unshown intermediate nodes)
CDO>
RMS Examples
The following figure shows a CDO definition of an RMS database called
MY_PHYSICAL_RMS_DB that contains one CDO record definition. The
following examples refer to the definitions in this figure:
MY_PHYSICAL_RMS_DB (CDD$DATABASE)
|
----------------------------
| |
MY_RMS_DB (CDD$FILE) MY_RMS_DB (CDD$RMS_DATABASE)
|
|
RECORD_E
|
-----------------------------------------
| | |
| | |
FIELD_F FIELD_G FIELD_H
The database MY_PHYSICAL_RMS_DB was created using the RMS database
definition MY_RMS_DB on the disk location DISK1:[SMITH.DICT]MY_RMS_DB.
Creating the database MY_PHYSICAL_RMS_DB causes the following three
entities to be created in the dictionary:
o CDD$DATABASE - describes logical and physical
information about the database.
o CDD$RMS_DATABASE - describes the logical definition
of the database.
o CDD$FILE - describes the physical location
of the database on disk.
In the following example, the SHOW WHAT_IF command with the /FULL
qualifier displays all the ancestors of field definition FIELD_F that
receive a possibly invalid message if the CHANGE command changes
FIELD_F in place:
CDO> SHOW WHAT_IF/FULL FIELD_F
Signaled owners of DISK1:[SMITH.DICT]FIELD_F;1
| DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA ( 2 unshown intermediate nodes)
CDO>
In the following example, the SHOW WHAT_IF command with the /FULL
qualifier displays all the ancestors of record definition RECORD_E that
receive a possibly invalid message if the CHANGE command changes
RECORD_E in place:
CDO> SHOW WHAT_IF/FULL RECORD_E
Signaled owners of DISK1:[SMITH.DICT]RECORD_E;1
| DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA ( 1 unshown intermediate nodes)
CDO>
In the next example, there is no output from the SHOW WHAT_IF command.
This means that record definition RECORD_E does not have any immediate
ancestors or descendants to receive a possibly invalid message if the
CHANGE command changes RECORD_E in place:
CDO> SHOW WHAT_IF RECORD_E
CDO>
In the next example, the SHOW WHAT_IF command with the /FULL qualifier
displays the ancestor of the RMS database definition that receive a
possibly invalid message if the CHANGE command changes MY_RMS_DB in
place:
CDO> SHOW WHAT_IF/FULL MY_RMS_DB
Signaled owners of DISK1:[SMITH.DICT]MY_RMS_DB;1
| DISK1:[SMITH.DICT]MY_PHYSICAL_RMS_DB;1 (Type : CDD$DATABASE)
| | via CDD$DATABASE_SCHEMA
CDO>