Allows you to assign directory names to existing dictionary objects so
 you can share their definitions and display them with the DIRECTORY
 command.

 Use this command to assign directory names to field definitions and
 record definitions within an Rdb/VMS database definition and to field
 definitions or structure definitions within record definitions
 converted from a DMU dictionary.  When an object (such as a field
 definition) has a directory name, that object can be included in other
 definitions (for example, field definitions with directory names can be
 used as Rdb global fields).

 ENTER ─┬─> 
F
I
E
L
D ─────────────────┬──> name1  ─────────────────┐
        ├─> 
R
E
C
O
R
D ────────────────┤                            │
        └─> 
G
E
N
E
R
I
C protocol-name ─┘                            │
 ┌─────────────────────────────────<────────────────────────────┘
 └─┬─> 
F
R
O
M ─┬─> 
R
E
C
O
R
D ────────────────┬─> name2 ──────┬──>
   │         ├─> 
D
A
T
A
B
A
S
E ──────────────┤               │
   │         └─> 
G
E
N
E
R
I
C protocol-name ─┘               │
   │                                                    │
   └─> 
F
O
R name3 ───────────────────────────────────────┘

Additional information available:

protocol-namename1name2name3Examples

 The name of the protocol on which the generic entity definition is
 based.

 When you are using the FROM clause, name1 is the processing name of a
 field, record, or a generic entity definition for which you are
 creating a directory name in a CDO dictionary.  In this case, you are
 assigning a directory name to a definition that does not have one.

 When you are using the FOR clause, name1 is a new directory name for a
 field, record, or generic entity definition that already has a
 directory name.  Do not use wildcard characters when referring to the
 processing name of a field, record, or generic entity definition.

 The name of the record or database that owns name1; or the name of the
 protocol on which the generic entity definition is based.

 The processing name of the field, record, or genric entity definition
 for which you are creating a new directory name.

 The following command causes a directory name of PART_NUMBER to be
 entered in your default CDO directory for field definition PART_NUMBER
 from the PARTS database:

 CDO> ENTER FIELD PART_NUMBER FROM DATABASE PARTS
 CDO>

 In the following example, CUSTOMER_RECORD is a CDO record definition
 that has been converted from DMU, CUSTOMER is a structure definition
 within CUSTOMER_RECORD, and ACCOUNT_NUMBER is a field definition within
 CUSTOMER.  The first ENTER command causes a directory name of CUSTOMER
 to be entered in your default CDO directory for structure definition
 CUSTOMER.  After the ENTER command executes, the CDO command DIRECTORY
 lists CUSTOMER as being a definition of type RECORD.  The second ENTER
 command causes a directory name of ACCOUNT_NUMBER to be entered in your
 default directory for field definition ACCOUNT_NUMBER.  The second
 DIRECTORY command shows that ACCOUNT_NUMBER is now listed as a
 definition of type FIELD:

 CDO> ENTER RECORD CUSTOMER FROM RECORD CUSTOMER_RECORD
 CDO> DIRECTORY

 Directory DISK5:[BINNS.DICT]CORPORATE

 CUSTOMER;1                           RECORD
 CUSTOMER_RECORD;1                    RECORD

 CDO> ENTER FIELD ACCOUNT_NUMBER FROM RECORD CUSTOMER

 CDO> DIRECTORY

 Directory DISK5:[BINNS.DICT]CORPORATE

 ACCOUNT_NUMBER;1                     FIELD
 CUSTOMER;1                           RECORD
 CUSTOMER_RECORD;1                    RECORD
 CDO>

 In the following example, the ENTER command assigns SALARY_CLASS as a
 new directory name for the field definition WAGE_CLASS.

 CDO> ENTER FIELD SALARY_CLASS FOR WAGE_CLASS.