| Previous | Contents | Index |
This example shows how to define four different keys and associate them with a state named ALTERED:
Deletes command definitions established with the DEFINE/COMMAND command.
DELETE/COMMAND symbol-name[,symbol-name...]
symbol-name
Specifies the name of a command symbol whose definition is to be deleted. This symbol must have been defined with a previous DEFINE/COMMAND command.
None.
| #1 |
|---|
VDE„ DELETE/COMMAND FOO, FEE
|
This example shows how to delete the command definitions for symbols FOO and FEE.
Deletes key definitions that have been established by the DEFINE/KEY command. The /KEY qualifier is required and must precede any other qualifiers.
DELETE/KEY [key-name]
key-name
Specifies the name of the key to be deleted. If you specify this parameter, do not use the /ALL qualifier.
/ALL
Deletes all key definitions in the specified state; the default is the current state. (Use the /STATE qualifier to specify states.) If you use the /ALL qualifier, do not specify a key name./LOG (default)
/NOLOG
Controls whether messages are displayed indicating that the specified key definitions have been deleted. /LOG causes such messages to be displayed and /NOLOG suppresses them./STATE=(state-name[,...])
/NOSTATE (default)
Specifies the name of the state for which the specified key definition is to be deleted. The default state is the current state. If you specify only one state name, you can omit the parentheses. State names can be any appropriate alphanumeric string.
| #1 |
|---|
VDE„ DEFINE/KEY PF3 "SHOW LIBRARY" /TERMINATE
%VDE-I-DEFKEY, DEFAULT key PF3 has been defined
VDE„ [PF3]
VDE„ SHOW LIBRARY
Library LIBNAME in root directory DEV$:[PROJDIR]
VDE„ DELETE/KEY PF3
%VDE-I-DELKEY, DEFAULT key PF3 has been deleted
VDE„ [PF3]
VDE„
|
In this example, the DEFINE/KEY command defines the PF3 key on the keypad as SHOW LIBRARY. Later the DELETE/KEY command undefines the PF3 key. When the user presses PF3 thereafter, only the VDE prompt is displayed.
| #2 |
|---|
VDE„ DELETE/KEY/ALL
%VDE-I-DELKEY, DEFAULT key PF1 has been deleted
%VDE-I-DELKEY, DEFAULT key PF2 has been deleted
%VDE-I-DELKEY, DEFAULT key PF3 has been deleted
%VDE-I-DELKEY, DEFAULT key PF4 has been deleted
VDE„
|
Keys PF1 through PF4 had been defined for state DEFAULT. In this example, the DELETE/KEY command deletes all key definitions in the current state, that is, state DEFAULT. The log messages show what key definitions have been deleted.
Deletes one or more architecture table entries in the VDE database. Each architecture table entry...Requires the DELARCH privilege.
ARCHITECTURE support is not fully implemented.
DELETE ARCHITECTURE arch-name [, arch-name...]
arch-name
The name of the architecture to be deleted. This name may be up to 39 characters long and must follow VDE name syntax.
Under Construction...
/CONFIRM (default)
/NOCONFIRM
Under Construction.../LOG (default)
/NOLOG
Under Construction.../REMARK="string"
Specifies a remark string to be stored for the deleted architecture. The quoted remark string, which can be up to 132 characters long, may contain any explanatory remark about the architecture. that you want stored in the VDE database. Typically the remark describes the function or purpose of the architecture.
| #1 |
|---|
VDE„ DELETE ARCHITECTURE VAXPDP/REMARK="Version n"
VDE„
|
Under Construction...
Deletes one or more build jobs from the current VDE database.
DELETE BUILD_JOB stream-name [, stream-name...]
stream-name
The name of a development stream. One or more build jobs in this stream are deleted from the database. Use the /IDENTIFICATION qualifier to specify the build jobs to delete. If you do not specify this qualifier, the most recent build job in the stream is deleted.You can delete build jobs for more than one stream by using wildcard characters in the stream name. The percent sign (%) in a name matches any single character in the position it occupies and the asterisk (*) matches zero or more characters in the position it occupies. Build jobs are deleted for those streams whose names match the wildcard pattern.
The DELETE BUILD_JOB command deletes each build job that matches the specified stream name and build job identification numbers. When a build job is deleted, all information about that build job is deleted from the database of the current VDE library. You cannot delete a build job that is queued for execution or that is currently running. To delete such a build job, stop it using the STOP BUILD_JOB command before you delete it.
/CONFIRM
/NOCONFIRM (default)
Controls whether VDE asks you to confirm that you want each build job deleted. The /CONFIRM qualifier causes VDE to print a message for each build job asking whether you want that build job deleted. If you answer YES (or Y), the build job is deleted from the database. If you answer NO (or N), the build job is not deleted. The /NOCONFIRM qualifier causes VDE to delete the specified build jobs without asking for confirmation./IDENTIFICATION=id-range
Specifies the job identification numbers of the build jobs to be deleted from the specified stream. The id-range parameter can be a single integer value, a range of integers, or a wildcard character. If the parameter is a single integer (for example, /IDENT=5), VDE deletes the build job with that identification number. If the parameter is a range of integers (specified as two build job identification numbers separated by a colon as in /IDENT=3:5), VDE deletes all build jobs with identification numbers in that range. Finally, if the id-range parameter is the asterisk wildcard (as in /IDENT=*), VDE deletes all build jobs for the specified stream.If you specify a zero or negative build job identification number in the id-range parameter, that number is relative to the identification number of the most recent build job in the stream. For example, if the most recent build job is job 5, then /IDENT=0 is equivalent to /IDENT=5 and /IDENT=--1 is equivalent to /IDENT=4.
If you do not use the /IDENTIFICATION qualifier, VDE deletes the most recent build job for the specified stream.
/LOG (default)
/NOLOG
Controls whether log messages are printed after each build job is deleted. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. The messages indicate that the build job has been deleted from the database and that the database transaction has successfully committed./REMARK="string"
Specifies a deletion remark string to be stored in the database for the deleted build job. The quoted remark string, which can be up to 132 characters long, may contain any explanatory remark that you want to store in the database.
| #1 |
|---|
VDE„ DELETE BUILD_JOB V2.0-3/IDENTIFICATION=7
%VDE-I-BLDJOBDEL, build job 7 for stream V2.0-3 deleted from database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
In this example, build job 7 for stream V2.0-3 is deleted from the VDE database. The log messages confirm that the build job was deleted and that the database transaction successfully completed.
Deletes one or more contexts from the current VDE library. Each context can be used to specify the default development stream, default architecture and default facility for a VDE session.
DELETE CONTEXT ctx-name [, ctx-name...]
ctx-name
The name of a context to be deleted from the current VDE library. You can delete more than one context at a time by using wildcard characters in the context name. The percent sign (%) in a name matches any single character in the position it occupies and the asterisk (*) matches zero or more characters in the position it occupies. Those contexts whose names match the wildcard pattern are deleted.
The DELETE CONTEXT command deletes each specified context from the current VDE database. The command deletes either public contexts or your private contexts, depending on whether you specify the /PUBLIC or the /PRIVATE qualifier.
/CONFIRM
/NOCONFIRM (default)
Controls whether VDE asks you to confirm that you want each context deleted. The /CONFIRM qualifier causes VDE to print a message for each context asking whether you want that context deleted. If you answer YES (or Y), that context is deleted from the database. If you answer NO (or N), the context is not deleted. If you enter a context name with a wildcard specification, VDE asks you to confirm the deletion of each context whose name matches the wildcard specification. The /NOCONFIRM qualifier causes VDE to delete the specified contexts without asking for confirmation./LOG (default)
/NOLOG
Controls whether log messages are printed after each context has been deleted. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate that the context has been deleted from the database and that the database transaction has successfully committed./PRIVATE (default)
/PUBLIC
Controls whether a private or public context is deleted. The /PRIVATE qualifier causes VDE to delete a context that is private to you. The /PUBLIC qualifier causes VDE to delete a context that is available to all users of the library. You must have the CRECTX privilege to use the /PUBLIC qualifier./REMARK="string"
Specifies a deletion remark string to be stored in the database for the deleted context. The quoted remark string, which can be up to 132 characters long, may contain any explanatory remark that you want stored in the database.
| #1 |
|---|
VDE„ DELETE CONTEXT V2RMS
%VDE-I-CTXDEL, context V2RMS deleted from the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
This example deletes the context V2RMS from the database. Because the /PUBLIC qualifier is not specified, VDE deletes the private context by this name.
Deletes one or more delete-enabled facilities from the current VDE library.
DELETE FACILITY facil-name [, facil-name...]
facil-name
The name of a facility to be deleted from the current VDE library. You can delete more than one facility at a time by using wildcard characters in the facility name. The percent sign (%) in a name matches any single character in the position it occupies and the asterisk (*) matches zero or more characters in the position it occupies. Those facilities whose names match the wildcard pattern are deleted.
The DELETE FACILITY command deletes each specified facility from the current VDE database and commits the transaction. It then deletes all disk directories associated with each facility. When the deletion command completes, the files and CMS library associated with the facility will have been vaporized. Should protection violations or other errors occur, VDE can be prevented from deleting all associated files and directories, and VDE will generate one or more informational messages that will provide additional details.You can only delete a facility if the delete attribute is enabled on the facility. If this attribute is disabled, you must enable this attribute, using the MODIFY FACILITY /DELETE command, before you will be able to delete the facility.
/CONFIRM
/NOCONFIRM (default)
Controls whether VDE asks you to confirm that you want each facility deleted. The /CONFIRM qualifier causes VDE to print a message for each facility asking whether you want that facility deleted. If you answer YES (or Y), that facility is deleted from the library. If you answer NO (or N), the facility is not deleted. If you enter a facility name with a wildcard specification, VDE asks you to confirm the deletion of each facility whose name matches the wildcard specification. The /NOCONFIRM qualifier causes VDE to delete the specified facilities without asking for confirmation./LOG (default)
/NOLOG
Controls whether log messages are printed after each facility has been deleted. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate that the facility has been deleted from the library and that the database transaction has successfully committed./REMARK="string"
Specifies a remark string to be stored in the database for the deleted facility. The quoted remark string, which can be up to 132 characters long, may contain any explanatory remark that you want to store in the database.
| #1 |
|---|
VDE„ DELETE FACILITY ACCTNG
%VDE-I-FACDEL, facility ACCTNG deleted from the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
In this example, facility ACCTNG is deleted from the current VDE library. The log messages confirm that the facility was deleted and that the database transaction successfully completed.
| #2 |
|---|
VDE„ DELETE FACILITY FAC1, FAC2, FAC3
%VDE-I-FACDEL, facility FAC1 deleted from the database
%VDE-I-FACDEL, facility FAC2 deleted from the database
%VDE-I-FACDEL, facility FAC3 deleted from the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
This example shows how you can delete multiple facilities from a library. The log messages list the facilities that are deleted.
Deletes one or more fold records from the VDE database. A fold record is a reminder that a source change should be manually "folded" into a given development stream in order to propagate the change.
DELETE FOLD mod-name [, mod-name...]
mod-name
Specifies a module for which a fold record is to be deleted. The module name consists of an optional facility name enclosed in square brackets, a module name, and an optional type name preceded by a period (such as [FACIL]MOD1.MAR). If the facility name is omitted, the module is assumed to belong to the default facility. If the type name is omitted, VDE deletes fold records for all source modules with the specified module name in the given facility.You can delete fold records for more than one module by using wildcard characters in any of the three components of the module name. The percent sign (%) in a name matches any single character in the position it occupies and the asterisk (*) matches zero or more characters in the position it occupies. VDE deletes fold records for all source modules whose names match the wildcard pattern.
A fold record is a reminder that a source change should be manually folded into a given development stream in order to propagate the change into that stream. The DELETE FOLD command deletes each specified fold record from the VDE database. This command is a synonym for the CANCEL FOLD command.
/CONFIRM
/NOCONFIRM (default)
Controls whether VDE asks you to confirm that you want each fold record deleted. The /CONFIRM qualifier causes VDE to print a message for each fold record asking whether you want that record deleted. If you answer YES (or Y), that fold record is deleted from the database. If you answer NO (or N), the fold record is not deleted. If you enter a module name with a wildcard specification, VDE asks you to confirm the deletion of fold records for each module whose name matches the wildcard specification. The /NOCONFIRM qualifier causes VDE to delete the specified fold records without asking for confirmation./IDENTIFICATION=fold-ident
Specifies the fold record to be deleted. This qualifier is required when you have multiple fold records for the same module in the same stream. The fold-ident parameter is the fold identifier of the fold record to be deleted. The fold identifier is the identifier you specified or VDE assigned when you created the fold record, usually a small integer value. Use the SHOW FOLD command to determine the fold identifier of each fold record./LOG (default)
/NOLOG
Controls whether log messages are printed after each fold record has been deleted. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate that the fold record has been deleted and that the database transaction has successfully committed./STREAM=stream-name
Specifies the development stream for which fold records should be deleted. The stream-name parameter gives the name of the stream. If this qualifier is omitted, VDE deletes fold records for the default development stream only./USERNAME=username
Specifies that fold records are to be deleted on behalf of another user. The username parameter specifies the OpenVMS username of the other user. You must have the USERNAME privilege to use this qualifier.
| #1 |
|---|
VDE„ DELETE FOLD [CODE]X.FOR/IDENT=1
%VDE-I-FOLDDEL, fold record 1 for module [CODE]X.FOR has been deleted
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
This example deletes fold record 1 for module [CODE]X.FOR. The log messages confirm that the fold record has been successfully deleted.
Deletes the most recent generation of a specified module from a specified development stream.
DELETE GENERATION mod-name [, mod-name...]
mod-name
The name of a module whose latest generation in the specified development stream is to be deleted. The module name consists of an optional facility name enclosed in square brackets, a module name, and an optional type name preceded by a period, such as [FACIL]MOD1.MAR. If no facility name is specified, the default facility is assumed. If no type name is specified, the latest generations of all source modules of the specified module name in the given facility are deleted.You can delete the latest generations of more than one module by using wildcard characters in any of the three components of the module name. The percent sign (%) in a name matches any single character in the position it occupies and the asterisk (*) matches zero or more characters in the position it occupies. VDE deletes the latest generation in the specified stream of each module whose name matches the wildcard pattern.
Using the /GENERATION qualifier, you can also delete a generation that does not belong to any stream.
The DELETE GENERATION command removes the latest generation of a specified module from a specified development stream and makes the previous generation (the next most recent generation) into the latest generation for the stream. The result is that the most recent generation is discarded from the stream, so that the effect of the REPLACE operation that created that generation is undone.The removed generation remains in the VDE database as long as it remains reachable from at least one development stream or has at least one successor generation. However, once a removed generation becomes unreachable from all streams and has no successors, the DELETE GENERATION command deletes it completely from the VDE database and library.
You cannot delete the first generation of a module (generation 1) using this command. The only way to delete the first generation is to delete the whole module with the DELETE MODULE command.
If the specified module is currently reserved in the specified stream, VDE terminates that reservation since it is based on a module generation that no longer is the latest generation for the stream. VDE sends a mail message to notify the owner of the reservation that the reservation is lost.
If you want to delete a module generation that does not belong to any development stream, use the /GENERATION qualifier. Do not use the /GENERATION qualifier for a generation that belongs to a stream; VDE will not delete any generation that belongs to a stream or that is not a leaf node in the generation tree.
/CONFIRM
/NOCONFIRM (default)
Controls whether VDE asks you to confirm that you want each generation deleted. The /CONFIRM qualifier causes VDE to print a message for the latest generation of each module giving the name of the generation and asking whether you want to delete the generation. If you answer YES (or Y), the generation is deleted. If you answer NO (or N), the generation is not deleted. The /NOCONFIRM qualifier causes VDE to delete each generation without asking for confirmation./GENERATION=gen-expr
Specifies that the generation with the CMS generation expression given by the gen-expr parameter be deleted. If you specify this qualifier, do not specify the /STREAM qualifier./LOG (default)
/NOLOG
Controls whether log messages are printed after generations are deleted. The /LOG qualifier causes such messages to be printed and /NOLOG suppresses them. The messages indicate that the generations have been deleted from the specified development stream and that the database transaction has successfully committed./REMARK="string"
Specifies a remark string that explains why you deleted the generation. The quoted remark string can be up to 132 characters long./STREAM=stream-name
Specifies that the latest generation in the development stream given by the stream-name parameter be deleted. If both this qualifier and the /GENERATION qualifier are omitted, VDE prompts you for the stream name.
| #1 |
|---|
VDE„ DELETE GENERATION [FACIL]MODNAM.C /STREAM=V2.0
%VDE-I-GENDEL, generation [FACIL]MODNAM.C;5(5) deleted from stream V2.0
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
VDE„ SHOW GENERATION [FACIL]MODNAM.C
Generation [FACIL]MODNAM.C;4(4) by user SMITH on 9-MAY-1990 19:43
VDE„
|
This example deletes the latest generation of module [FACIL]MODNAM.C from stream V2.0. The log message shows that generation 5 was deleted. The subsequent SHOW GENERATION command shows that generation 4 is now the latest generation of the module in the stream.
| Previous | Next | Contents | Index |