CDD/Plus CDO DELETE — VMS CDD+_4.1A
Additional information available:
DATABASEDICTIONARYDIRECTORYFIELDGENERIC
PROTECTIONRECORDRMS_DATABASE
DATABASE
Deletes the physical RMS database from disk and its CDD$DATABASE entity from the dictionary. To delete the CDD$DATABASE entity for an Rdb/VMS database from the dictionary, use the CDO command DELETE GENERIC. DELETE_DATABASE ──┬──────────>────┬───────────> database-name ───> . ├──>
/
L
O
G ──────┤ └──>
/
N
O
L
O
G ────┘
Additional information available:
database-nameQualifiersExamples
database-name
The name of the physical RMS database.
Qualifiers
Additional information available:
/LOG
/LOG /NOLOG (default) Controls whether or not an informational message is displayed on the terminal screen after the database is deleted. The default is /NOLOG, where no informational message is displayed after the database is deleted.
Examples
The following command deletes a physical RMS database, EMP_FILE, which is stored in the RMS file EMP.DAT. Notice that the DELETE DATABASE command without the /LOG qualifier gives you a message that only the physical file EMP.DAT is deleted. CDO> DELETE DATABASE EMP_FILE;1 deleting file USR02:[PERSONNEL.EMPLOYEE]EMP.DAT; proceed? [Y/N] (N) Y %CDO_I_FILEDEL, file USR02:[PERSONNEL.EMPLOYEE]EMP.DAT; deleted CDO> In the following example, DELETE DATABASE/LOG gives you an additional message that the CDD$DATABASE entity SSG_FILE is deleted from the CDO dictionary as well as the physical file EMP_DAT: CDO> DELETE DATABASE/LOG SSG_FILE. deleting file USR02:[MCGUIRE.RDB]EMP.DAT;, proceed? [Y/N] (N)y %CDO-I-FILEDEL, file USR02:[MCGUIRE.RDB]EMP.DAT; deleted %CDO-I-ENTDEL, entity USR02:[MCGUIRE.DICT]SSG_FILE;3 deleted CDO>
DICTIONARY
Deletes a CDO dictionary. DELETE DICTIONARY ─┬────>─────┬──┬─> dictionary-name ─┬─> . ├> typebox (/)
L
O
G ───┤ └──────── , <────────┘ └> typebox (/)
N
O
L
O
G ─┘ Only the owner of a dictionary or the system manager can delete the dictionary. The DELETE DICTIONARY command deletes all files in the specified VMS anchor directory, including any files that you may have stored there. User-created files should not be stored in a VMS directory that contains a CDO dictionary.
Additional information available:
dictionary-nameQualifiersExamples
dictionary-name
The anchor of the dictionary you want to delete. The DELETE DICTIONARY command deletes all files in the specified anchor directory, including any user files stored there. Therefore, before you use this command, check the anchor directory to be sure you do not delete user-created files unintentionally.
Qualifiers
Additional information available:
/LOG
/LOG /NOLOG (default) Controls whether or not an informational message is displayed on the terminal screen after the dictionary is deleted. The default is /NOLOG, where no informational message is displayed after the dictionary is deleted. Only the owner of a dictionary or the system manager can delete the dictionary.
Examples
The following command deletes a dictionary with an anchor of DISK1:[BOB.DICT]. CDO> DELETE DICTIONARY DISK1:[BOB.DICT]. CDO> The following example shows how to use the /LOG qualifier when deleting a dictionary with an anchor of DISK1:[BOB.DICT]. CDO> DELETE DICTIONARY/LOG DISK1:[BOB.DICT]. %CDO-I-DICDEL, dictionary DISK1:[BOB.DICT] deleted CDO>
DIRECTORY
Deletes a CDO directory. DELETE DIRECTORY ───┬─────>────┬────┬─> directory-name ─┬─> ├> typebox (/)
L
O
G ───┤ └──────── , <───────┘ └> typebox (/)
N
O
L
O
G ─┘
Additional information available:
directory-nameQualifiersExamples
directory-name
The name of the directory you want to delete.
Qualifiers
Additional information available:
/LOG
/LOG /NOLOG (default) Controls whether or not an informational message is displayed on the terminal screen after the directory is deleted. The default is /NOLOG, where no informational message is displayed after the directory is deleted. Only the owner of a directory or the system manager can delete the directory.
Examples
The following command deletes an empty directory named PROSPECTS: CDO> DELETE DIRECTORY PROSPECTS. CDO> The following example shows how to use the /LOG qualifier when deleting an empty directory: CDO> DELETE DIRECTORY/LOG PROSPECTS. %CDO-I-DIRDEL, directory PROSPECTS deleted CDO> The following command deletes an empty directory named LAYOFFS: CDO> DELETE DISK1:[CORPORATE.PERSONNEL]EMPLOYEES.LAYOFFS CDO>
FIELD
Deletes a field definition from a dictionary. DELETE FIELD ─┬─┬─────────>─────────┬─┬───┬─> field-name ─┬─> . │ ├─> typebox (/)
D
E
S
C
E
N
D
A
N
T
S ───┤ │ └────── , <─────┘ │ ├─> typebox (/)
N
O
D
E
S
C
E
N
D
A
N
T
S ─┤ │ │ ├─> typebox (/)
L
O
G ───────────┤ │ │ └─> typebox (/)
N
O
L
O
G ─────────┘ │ └───────────<───────────┘
Additional information available:
field-name
The field definition you want to delete.
Qualifiers
Additional information available:
/DESCENDANTS
/DESCENDANTS /NODESCENDANTS (default) Controls whether or not the field definition alone is deleted. If you specify /DESCENDANTS, the field definition and those entities that are members of a relationship with the field definition but not of any other relationship are deleted. When you specify /NODESCENDANTS, only the field definition is deleted. This is the default.
/LOG
/LOG /NOLOG (default) Controls whether or not an informational message is displayed on the terminal screen after the field definition is deleted. The default is /NOLOG, where no informational message is displayed after the dictionary is deleted.
Examples
This command deletes the field ORDER_NUMBER and provides a message that the field is deleted. CDO> DELETE FIELD/LOG ORDER_NUMBER. %CDO-I-ENTDEL, entity ORDER_NUMBER deleted CDO> This command deletes the field ORDER_NUMBER and those entities that are members of a relationship with ORDER_NUMBER but not of any other relationships. CDO> DELETE FIELD/DESCENDANTS ORDER_NUMBER. CDO> The following command deletes all versions of the field FIRST_NAME: CDO> DELETE FIELD FIRST_NAME;* CDO>
GENERIC
Deletes an entity definition based on an entity protocol. DELETE GENERIC ────> protocol-name ──┬─────────>────────┬───┐ ├> typebox (/)
D
E
S
C
E
N
D
A
N
T
S ───┤ │ ├> typebox (/)
N
O
D
E
S
C
E
N
D
A
N
T
S ─┤ │ ├> typebox (/)
L
O
G ───────────┤ │ └> typebox (/)
N
O
L
O
G ─────────┘ │ ┌─────────────────────────<─────────────────────────────────┘ └──┬─> entity-name ──┬──> . └─────── , <──────┘
Additional information available:
protocol-nameentity-nameQualifiersExamples
protocol-name
The name of the protocol on which the entity definition is based.
entity-name
The name of the entity that you are deleting.
Qualifiers
Additional information available:
/DESCENDANTS
/DESCENDANTS /NODESCENDANTS (default) Controls whether or not the entity alone is deleted. If you specify /DESCENDANTS, the entity and those entities that are members of a relationship with the entity but not of any other relationship are deleted. When you specify /NODESCENDANTS, only the entity is deleted. This is the default.
/LOG
/LOG /NOLOG (default) Controls whether or not an informational message is displayed on the terminal screen after the entity is deleted. The default is /NOLOG, where no informational is displayed after the entity is deleted.
Examples
The following DELETE GENERIC command deletes the entity OUTPUT_MODULE, which is based on the CDD$SOURCE_MODULE protocol. CDO> DELETE GENERIC CDD$SOURCE_MODULE OUTPUT_MODULE. CDO> The following command deletes all the versions of the entity MY_PROGRAM: CDO> DELETE GENERIC CDD$EXECUTABLE_IMAGE MY_PROGRAM;*. CDO> The following command deletes the CDD$DATABASE definition for the Rdb/VMS database DEPT1 from the dictionary: CDO> DELETE GENERIC CDD$DATABASE DEPT1. CDO>
PROTECTION
Deletes an access control list entry (ACE) or the entire access control list (ACL) for a CDO definition or dictionary directory. DELETE PROTECTION ─┬────>─────┬> Ftypebox (O)typebox (R) ─┬>
D
I
R
E
C
T
O
R
Y ─────────────┬──┐ ├> typebox (/)
L
O
G ───┤ ├>
F
I
E
L
D ─────────────────┤ │ └> typebox (/)
N
O
L
O
G ─┘ ├>
R
E
C
O
R
D ────────────────┤ │ └>
G
E
N
E
R
I
C protocol-name ─┘ │ ┌────────────────────────────────<─────────────────────────────────┘ └┬> object-name ─┬──┬─────>────────┬──> . └─────── , <────┘ ├>
P
O
S
I
T
I
O
N n ─┤ └─┬─> id ─┬────┘ └── typebox (+) <─┘
Additional information available:
protocol-nameobject-namenidQualifiersExamples
protocol-name
The name of the protocol that the generic entity whose ACE or entire ACL you want to delete is based on.
object-name
The name of the dictionary object or directory whose ACE or entire ACL you want to delete.
n
The relative position in the ACL of the ACE you want to delete.
id
The identifiers which specify the ACE you want to delete.
Qualifiers
Additional information available:
/LOG
/LOG /NOLOG (default) Controls whether or not an informational message is displayed on the terminal screen after the ACE or ACL is deleted. The default is /NOLOG, where no informational message is displayed after the ACE or ACL is deleted.
Examples
The following command deletes the fifth ACE in the ACL for record CAR_POOL: CDO> DELETE PROTECTION FOR RECORD CAR_POOL POSITION 5. CDO> The following command deletes the ACE with the identifier [23,56] for record CAR_POOL: CDO> DELETE PROTECTION FOR RECORD CAR_POOL [23,56]. CDO> This command deletes the entire ACL for record CAR_POOL. CDO> DELETE PROTECTION FOR RECORD CAR_POOL. CDO>
RECORD
Deletes a record definition in the dictionary. DELETE RECORD ──┬─┬─────────>────────┬─┬───┬─> record-name ─┬──> . │ ├> typebox (/)
D
E
S
C
E
N
D
A
N
T
S ───┤ │ └────── , <──────┘ │ ├> typebox (/)
N
O
D
E
S
C
E
N
D
A
N
T
S ─┤ │ │ ├> typebox (/)
L
O
G ───────────┤ │ │ └> typebox (/)
N
O
L
O
G ─────────┘ │ └──────────<───────────┘
Additional information available:
record-name
The name of the record definition you want to delete.
Qualifiers
Additional information available:
/DESCENDANTS
/DESCENDANTS /NODESCENDANTS (default) Controls whether or not the record definition alone is deleted. If you specify /DESCENDANTS, the record definition and those entities that are members of a relationship with the record definition but not of any other relationship are deleted. When you specify /NODESCENDANTS, only the record definition is deleted. This is the default.
/LOG
/LOG /NOLOG (default) Controls whether or not an informational message is displayed on the terminal screen after the record definition is deleted. The default is /NOLOG, where no informational message is displayed after the record definition is deleted.
Examples
The following command deletes the record CUSTOMER_ORDERS and provides a message that the record is deleted. CDO> DELETE RECORD/LOG CUSTOMER_ORDERS. %CDO-I-ENTDEL, entity CUSTOMER_ORDERS deleted CDO> This command deletes the record CUSTOMER_ORDERS and those entities that are members of a relationship with CUSTOMER_ORDERS but no other relationships. CDO> DELETE RECORD/DESCENDANTS CUSTOMER_ORDERS. CDO> The following command deletes all the versions of the record FULL_NAME: CDO> DELETE RECORD FULL_NAME;* CDO>
RMS_DATABASE
Deletes an RMS database definition from the dictionary. DELETE RMSDATABASE ─┬───────────┬─> rms-database-name ──> . ├─> typebox (/)
L
O
G ───┤ └─> typebox (/)
N
O
L
O
G ─┘
Additional information available:
rms-database-nameRestrictionsQualifiersExamples
rms-database-name
The name of an RMS database definition.
Restrictions
You can only delete an RMS database definition from the dictionary when it is no longer being used by a physical RMS database on disk. You must delete all physical RMS databases that use an RMS database definition before you can delete the RMS database definition from the dictionary.
Qualifiers
Additional information available:
/LOG
/LOG /NOLOG (default) Controls whether or not an informational message is displayed on the terminal screen that the CDD$DATABASE entity has been deleted from the CDO dictionary. The default /NOLOG suppresses the message.
Examples
The following example shows what happens when you attempt to delete an RMS database definition, EMPLOYEE_STORAGE from the dictionary, while it is being used by a physical RMS database on disk. You must first delete the database, DISG_FILE that is using the RMS database definition before the DELETE RMS_DATABASE command will succeed. When the DELETE RMS_DATABASE command succeeds, the CDO> prompt returns, unless you use the /LOG qualifier. To verify that EMPLOYEE_STORAGE;2 was deleted, use the DIRECTORY command. CDO> DELETE RMS_DATABASE EMPLOYEE_STORAGE;2. %CDD-E-INUSE, element is the member of a relationship; it cannot be deleted CDO> DELETE DATABASE DISG_FILE;2. deleting file USR02:[MCGUIRE]EMP.DAT;, proceed? [Y/N] (N)Y %CDO-I-FILEDEL, file USR02:[MCGUIRE]EMP.DAT; deleted CDO> DELETE RMS_DATABASE EMPLOYEE_STORAGE. CDO> CDO> DIR Directory USR02:[MCGUIRE.EMPLOYEE] CDD$PROTOCOLS DIRECTORY DBS_FILE;1 CDD$DATABASE DISG_FILE;1 CDD$DATABASE EMPLOYEE_REC;2 RECORD EMPLOYEE_REC;1 RECORD EMPLOYEE_STORAGE;1 CDD$RMS_DATABASE EMP_ID;2 FIELD EMP_ID;1 FIELD FIRST_NAME;2 FIELD FIRST_NAME;1 FIELD LAST_NAME;2 FIELD LAST_NAME;1 FIELD SSG_FILE;1 CDD$DATABASE CDO> In the following example, DELETE RMS_DATABASE/LOG gives you a message that EMPLOYEE_DATABANK has been deleted from the CDO dictionary before the CDO> prompt returns: CDO> DELETE RMS_DATABASE/LOG EMPLOYEE_DATABANK. %CDO-I-ENTDEL, entity USR02:[MCGUIRE.DICT]EMPLOYEE_DATABANK;2 deleted CDO>