Format { FIELD } ENTER { RECORD } name1 [ qualifier ] { GENERIC type-name } { } { {DATABASE } } { FROM {RECORD } name2 } { {GENERIC type-name } } { { } } { FOR name3 }
1 – Parameters
1.1 – type-name
Specifies the type of a generic element.
1.2 – name1
Specifies the processing name of the field, record, or generic element. You can use an asterisk (*) wildcard character to indicate all element names or a specific element name. Afer the ENTER command executes, CDO creates a directory name that is the same as the processing name.
1.3 – name2
Specifies the database, record, or generic element that owns name1.
1.4 – name3
Specifies an additional directory name you are designating for the field, record, or generic element.
2 – Qualifiers
2.1 /RDB_METADATA
Format options: /RDB_METADATA /NORDB_METADATA (default) Specifies whether CDO enters a directory name for Oracle Rdb system relations. The /NORDB_METADATA qualifier is the default. This qualifier is synonymous with the SHOW /[NO]SYSTEM qualifier.
3 – Description
The ENTER command assigns a directory name or an additional directory name to a field, record, or generic element. The FROM clause assigns a directory name to an element that does not have a directory name. For example, field and record elements within an Oracle Rdb database definition may not have directory names. Without a directory name, the DIRECTORY command cannot display an element, and you cannot include the element as part of other elements. For example, you would not be able to include a field element without a directory name in an Oracle Rdb global field definition. The FOR clause assigns an additional directory name to an element that has a directory name. This functionality allows you to give an element different names on a local node and a remote node. You must issue the ENTER command with the FOR clause for an element before you can reserve that element in a distributed environment. See Using Oracle CDD/Repository on OpenVMS Systems for information on reserving elements in a distributed environment. CDO enters directory names in your currect default directory. The ENTER command fails if an element in that directory has a directory name that is the same as the processing name you specify. RESTRICTION The ENTER command does not apply a default ACL to the object being entered. Therefore, if the object did not have an ACL prior to being entered, it will not have one after being entered in the directory system. Setting the desired ACLs is left to the discretion of the user. You cannot issue the ENTER command to enter fields or records within a variant of CDO record definitions that were converted from DMU definitions. Field definitions and record definitions that exist only within the context of a variant cannot be given directory names. Use this command to assign directory names to field definitions or structure definitions within record definitions converted from DMU. 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 Oracle Rdb global fields).
4 – Examples
1.CDO> ENTER FIELD PART_NUMBER FROM DATABASE PARTS In this example, the ENTER command enters a PART_NUMBER directory name for the PART_NUMBER field element from the database element PARTS. 2.CDO> ENTER FIELD SALARY_CLASS FOR WAGE_CLASS In this example, the ENTER command assigns SALARY_CLASS as an alternative directory name for the WAGE_CLASS field element. 3.CDO> ENTER GENERIC MCS_COLLECTION CORP_DATA_DEFS con> FOR CORPORATE:CORP_DATA_DEFS CDO> RESERVE GENERIC MCS_COLLECTION CORP_DATA_DEFS In this example, the ENTER command assigns the alternative directory name CORP_DATA_DEFS on a local node for the collection CORPORATE:CORP_DATA_DEFS.