The CONVERT command copies a DMU format definition from the DMU side of the dictionary to the CDO side of the dictionary. The CONVERT command leaves the definition in the DMU side of the dictionary. The CONVERT/REPOSITORY command allows you to perform a minor upgrade (from a Version 5.n repository to a later Version 5.n, a Version 6.1, or a Version 7.0 repository). Using this command requires SYSPRV or BYPASS privilege. Be sure you have an adequate backup of the repository before issuing this command. NOTE The CONVERT command is not the same as the CONVERT/REPOSITORY command, which allows you to perform a minor upgrade of a repository. For details on upgrading repositories using the CONVERT/REPOSITORY command, see the Upgrade_Procedure topic in DCL level help or the instructions for upgrading a dictionary or repository provided in Using Oracle CDD/Repository on OpenVMS Systems. Unless you specify a different path name, the CONVERT command copies a DMU definition into your default CDO directory. When you convert a DMU definition, unless you specify the version number, CDO converts the highest version of the definition. An error occurs if you specify a destination name that is the name of an existing definition in the CDO destination directory. If you convert an Oracle Dictionary Management Utility (DMU) record definition that consists of a single field description statement, CDO converts the record definition to a CDO field definition. When you convert an Oracle Dictionary Management Utility (DMU) format definition that includes a description clause for the definition and another description clause for a structure within the definition, only the structure description clause appears in the CDO format definition. If you have a version of DIGITAL DATATRIEVE prior to Version 5.0 installed on your system, and you are converting a DMU definition that contains a VALID FOR DATATRIEVE IF field attribute or a COMPUTED BY DATATRIEVE field attribute clause, CDO omits these clauses from the resulting CDO definition. If the DMU record that you are converting has a different processing name from the DMU directory name, then the resulting CDO record definition retains the old processing name. However, if both the processing and directory names are the same for the DMU definition, then the resulting CDO record definition retains the same name for both the processing and directory names. When you convert an Oracle Dictionary Management Utility (DMU) definition, CDO creates a default ACL for it. See Using Oracle CDD/Repository on OpenVMS Systems for more information on default protection. To display or manipulate a converted field within a record description with a CDO command, you must assign it a directory name. Use the ENTER command to assign this name. When you convert an Oracle Dictionary Management Utility (DMU) definition to a CDO definition, CDO converts the DMU access rights to CDO access rights. However, because DMU protection is different from CDO protection, there is no CDO equivalent for some DMU access rights. Therefore, CDO must convert some DMU rights to the closest CDO access right. Conversion of Oracle Dictionary Management Utility (DMU) Access Rights to CDO Access Rights shows how CDO converts DMU access rights to the closest CDO equivalent. DMU access rights that are not listed in the table are not translated because no equivalent CDO access right is appropriate. Table 1-1 Conversion of Oracle Dictionary Management Utility (DMU) Access Rights to CDO Access Rights Oracle Dictionary Management Utility (DMU) Access Right Equivalent CDO Access Right CONTROL CONTROL DELETE DELETE Local or global DTR MODIFY MODIFY (confirms that CHANGE access can be granted) DTR READ READ (confirms that SHOW access can be granted) DTR WRITE WRITE (confirms that DEFINE access can be granted) SEE SHOW UPDATE CHANGE + DEFINE