| Previous[ | Contents] | Index |
HThis example shows how to define four different keys and associate them with a state named ALTERED:
HDeletes command definitions established with the DEFINE/COMMAND command.
5DELETE/COMMAND symbol-name[,symbol-name...]
symbol-name
ASpecifies 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.
6
| #1 |
|---|
VDEä DELETE/COMMAND FOO, FEE |
EThis example shows how to delete the command definitions for symbols FOO and FEE.
EDeletes key definitions that have been established by the DEFINE/KEY Ccommand. The /KEY qualifier is required and must precede any other qualifiers.
DELETE/KEY [key-name]
key-name
ASpecifies the name of the key to be deleted. If you specify this )parameter, do not use the /ALL qualifier.
/ALL
GDeletes all key definitions in the specified state; the default is the Hcurrent state. (Use the /STATE qualifier to specify states.) If you use .the /ALL qualifier, do not specify a key name./LOG (default)
/NOLOG
FControls whether messages are displayed indicating that the specified Ckey definitions have been deleted. /LOG causes such messages to be %displayed and /NOLOG suppresses them."/STATE=(state-name[,...])
/NOSTATE (default)
GSpecifies the name of the state for which the specified key definition Ais to be deleted. The default state is the current state. If you Gspecify only one state name, you can omit the parentheses. State names +can be any appropriate alphanumeric string.
6
| #1 |
|---|
-VDEä DEFINE/KEY PF3 "SHOW LIBRARY" /TERMINATE/%VDE-I-DEFKEY, DEFAULT key PF3 has been definedVDEä [PF3]VDEä SHOW LIBRARY0Library LIBNAME in root directory DEV$:[PROJDIR]VDEä DELETE/KEY PF3/%VDE-I-DELKEY, DEFAULT key PF3 has been deletedVDEä [PF3]VDEä |
6CIn this example, the DEFINE/KEY command defines the PF3 key on the Gkeypad as SHOW LIBRARY. Later the DELETE/KEY command undefines the PF3 8key. 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 deletedVDEä |
AKeys PF1 through PF4 had been defined for state DEFAULT. In this Cexample, the DELETE/KEY command deletes all key definitions in the Fcurrent 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...0Requires the DELARCH privilege.
?ARCHITECTURE support is not fully implemented.
8DELETE ARCHITECTURE arch-name [, arch-name...]
arch-name
FThe name of the architecture to be deleted. This name may be up to 39 0characters long and must follow VDE name syntax.
&Under Construction...
/CONFIRM (default)
/NOCONFIRM
&Under Construction.../LOG (default)
/NOLOG
&Under Construction.../REMARK="string"
ESpecifies a remark string to be stored for the deleted architecture. FThe quoted remark string, which can be up to 132 characters long, may Econtain 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.
6
| #1 |
|---|
2VDEä DELETE ARCHITECTURE VAXPDP/REMARK="Version n"VDEä |
&Under Construction...
=Deletes one or more build jobs from the current VDE database.
9DELETE BUILD_JOB stream-name [, stream-name...]
stream-name
HThe name of a development stream. One or more build jobs in this stream Dare deleted from the database. Use the /IDENTIFICATION qualifier to Hspecify the build jobs to delete. If you do not specify this qualifier, 3the most recent build job in the stream is deleted.EYou can delete build jobs for more than one stream by using wildcard Fcharacters in the stream name. The percent sign (%) in a name matches Fany single character in the position it occupies and the asterisk (*) Hmatches zero or more characters in the position it occupies. Build jobs Eare deleted for those streams whose names match the wildcard pattern.
EThe DELETE BUILD_JOB command deletes each build job that matches the Cspecified stream name and build job identification numbers. When a Fbuild job is deleted, all information about that build job is deleted 9from the database of the current VDE library. You cannot Edelete a build job that is queued for execution or that is currently Frunning. 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 8build job deleted. The /CONFIRM qualifier causes VDE to Fprint a message for each build job asking whether you want that build Ejob deleted. If you answer YES (or Y), the build job is deleted from Ethe 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
ASpecifies the job identification numbers of the build jobs to be Adeleted from the specified stream. The id-range Cparameter can be a single integer value, a range of integers, or a Gwildcard 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 H(specified as two build job identification numbers separated by a colon 3as in /IDENT=3:5), VDE deletes all build jobs with 6identification numbers in that range. Finally, if the Did-range parameter is the asterisk wildcard (as in 8/IDENT=*), VDE deletes all build jobs for the specified stream.EIf you specify a zero or negative build job identification number in Hthe id-range parameter, that number is relative to the Fidentification number of the most recent build job in the stream. For Aexample, 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 3the most recent build job for the specified stream.
/LOG (default)
/NOLOG
BControls whether log messages are printed after each build job is Gdeleted. The /LOG qualifier causes such messages to be printed and the G/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"
HSpecifies a deletion remark string to be stored in the database for the Ddeleted build job. The quoted remark string, which can be up to 132 Echaracters long, may contain any explanatory remark that you want to store in the database.
6
| #1 |
|---|
-VDEä DELETE BUILD_JOB V2.0-3/IDENTIFICATION=7E%VDE-I-BLDJOBDEL, build job 7 for stream V2.0-3 deleted from database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
CIn this example, build job 7 for stream V2.0-3 is deleted from the :VDE database. The log messages confirm that the build job Ewas deleted and that the database transaction successfully completed.
;Deletes one or more contexts from the current VDE library. DEach context can be used to specify the default development stream, <default architecture and default facility for a VDE session.
1DELETE CONTEXT ctx-name [, ctx-name...]
ctx-name
9The name of a context to be deleted from the current VDE Alibrary. You can delete more than one context at a time by using Hwildcard characters in the context name. The percent sign (%) in a name Amatches any single character in the position it occupies and the @asterisk (*) matches zero or more characters in the position it Doccupies. Those contexts whose names match the wildcard pattern are deleted.
CThe DELETE CONTEXT command deletes each specified context from the 8current VDE database. The command deletes either public Hcontexts 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 Ddeleted. If you answer YES (or Y), that context is deleted from the Fdatabase. If you answer NO (or N), the context is not deleted. If you =enter a context name with a wildcard specification, VDE asks Cyou to confirm the deletion of each context whose name matches the <wildcard specification. The /NOCONFIRM qualifier causes VDE Ato delete the specified contexts without asking for confirmation./LOG (default)
/NOLOG
FControls whether log messages are printed after each context has been Gdeleted. The /LOG qualifier causes such messages to be printed and the C/NOLOG qualifier suppresses them. These messages indicate that the Acontext has been deleted from the database and that the database 'transaction has successfully committed./PRIVATE (default)
/PUBLIC
FControls 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 Hthat is available to all users of the library. You must have the CRECTX 'privilege to use the /PUBLIC qualifier./REMARK="string"
HSpecifies a deletion remark string to be stored in the database for the Bdeleted context. The quoted remark string, which can be up to 132 Bcharacters long, may contain any explanatory remark that you want stored in the database.
6
| #1 |
|---|
VDEä DELETE CONTEXT V2RMS6%VDE-I-CTXDEL, context V2RMS deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
FThis 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.
6DELETE FACILITY facil-name [, facil-name...]
facil-name
:The name of a facility to be deleted from the current VDE Blibrary. You can delete more than one facility at a time by using Dwildcard characters in the facility name. The percent sign (%) in a Fname matches any single character in the position it occupies and the @asterisk (*) matches zero or more characters in the position it Foccupies. Those facilities whose names match the wildcard pattern are deleted.
EThe DELETE FACILITY command deletes each specified facility from the :current VDE database and commits the transaction. It then Edeletes all disk directories associated with each facility. When the 5deletion command completes, the files and CMS library? associated with the facility will have been vaporized. Should 9 protection violations or other errors occur, VDE can be C prevented from deleting all associated files and directories, and ; VDE will generate one or more informational messages that ! will provide additional details.HYou can only delete a facility if the delete attribute Dis enabled on the facility. If this attribute is disabled, you must 8enable this attribute, using the MODIFY FACILITY /DELETE8command, 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 Ba message for each facility asking whether you want that facility Edeleted. If you answer YES (or Y), that facility is deleted from the Flibrary. If you answer NO (or N), the facility is not deleted. If you 9enter a facility name with a wildcard specification, VDE Easks 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
GControls whether log messages are printed after each facility has been Gdeleted. The /LOG qualifier causes such messages to be printed and the C/NOLOG qualifier suppresses them. These messages indicate that the Afacility has been deleted from the library and that the database 'transaction has successfully committed./REMARK="string"
GSpecifies a remark string to be stored in the database for the deleted Ffacility. The quoted remark string, which can be up to 132 characters Glong, may contain any explanatory remark that you want to store in the database.
6
| #1 |
|---|
VDEä DELETE FACILITY ACCTNG8%VDE-I-FACDEL, facility ACCTNG deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
6=In this example, facility ACCTNG is deleted from the current <VDE library. The log messages confirm that the facility was Adeleted and that the database transaction successfully completed.
| #2 |
|---|
%VDEä DELETE FACILITY FAC1, FAC2, FAC36%VDE-I-FACDEL, facility FAC1 deleted from the database6%VDE-I-FACDEL, facility FAC2 deleted from the database6%VDE-I-FACDEL, facility FAC3 deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
AThis 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 Bfold 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
HSpecifies a module for which a fold record is to be deleted. The module Hname consists of an optional facility name enclosed in square brackets, Ga module name, and an optional type name preceded by a period (such as A[FACIL]MOD1.MAR). If the facility name is omitted, the module is Hassumed to belong to the default facility. If the type name is omitted, 9VDE deletes fold records for all source modules with the ,specified module name in the given facility.GYou can delete fold records for more than one module by using wildcard Bcharacters in any of the three components of the module name. The Hpercent sign (%) in a name matches any single character in the position Hit occupies and the asterisk (*) matches zero or more characters in the 7position it occupies. VDE deletes fold records for all 6source modules whose names match the wildcard pattern.
DA fold record is a reminder that a source change should be manually Hfolded into a given development stream in order to propagate the change Finto 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 Bprint a message for each fold record asking whether you want that Frecord deleted. If you answer YES (or Y), that fold record is deleted Cfrom the database. If you answer NO (or N), the fold record is not Cdeleted. If you enter a module name with a wildcard specification, 9VDE 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
DSpecifies the fold record to be deleted. This qualifier is required Dwhen you have multiple fold records for the same module in the same >stream. The fold-ident parameter is the fold Hidentifier of the fold record to be deleted. The fold identifier is the :identifier you specified or VDE assigned when you created Bthe fold record, usually a small integer value. Use the SHOW FOLD =command to determine the fold identifier of each fold record./LOG (default)
/NOLOG
EControls whether log messages are printed after each fold record has Hbeen deleted. The /LOG qualifier causes such messages to be printed and Gthe /NOLOG qualifier suppresses them. These messages indicate that the Cfold record has been deleted and that the database transaction has successfully committed./STREAM=stream-name
BSpecifies the development stream for which fold records should be Fdeleted. The stream-name parameter gives the name of ;the stream. If this qualifier is omitted, VDE deletes fold 0records for the default development stream only./USERNAME=username
CSpecifies 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.
6
| #1 |
|---|
$VDEä DELETE FOLD [CODE]X.FOR/IDENT=1E%VDE-I-FOLDDEL, fold record 1 for module [CODE]X.FOR has been deleted>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
CThis example deletes fold record 1 for module [CODE]X.FOR. The log Dmessages confirm that the fold record has been successfully deleted.
@Deletes the most recent generation of a specified module from a specified development stream.
4DELETE GENERATION mod-name [, mod-name...]
mod-name
>The name of a module whose latest generation in the specified Ddevelopment stream is to be deleted. The module name consists of an Goptional facility name enclosed in square brackets, a module name, and Han optional type name preceded by a period, such as [FACIL]MOD1.MAR. If Fno facility name is specified, the default facility is assumed. If no Htype name is specified, the latest generations of all source modules of <the specified module name in the given facility are deleted.GYou can delete the latest generations of more than one module by using Gwildcard characters in any of the three components of the module name. CThe percent sign (%) in a name matches any single character in the ?position it occupies and the asterisk (*) matches zero or more 8characters in the position it occupies. VDE deletes the Dlatest generation in the specified stream of each module whose name matches the wildcard pattern.
GUsing the /GENERATION qualifier, you can also delete a generation that does not belong to any stream.
AThe DELETE GENERATION command removes the latest generation of a Cspecified module from a specified development stream and makes the Fprevious generation (the next most recent generation) into the latest >generation for the stream. The result is that the most recent Cgeneration is discarded from the stream, so that the effect of the 9REPLACE operation that created that generation is undone.;The removed generation remains in the VDE database as long Gas it remains reachable from at least one development stream or has at Cleast one successor generation. However, once a removed generation Gbecomes unreachable from all streams and has no successors, the DELETE 6GENERATION command deletes it completely from the VDE database and library.
HYou cannot delete the first generation of a module (generation 1) using Gthis command. The only way to delete the first generation is to delete 0the whole module with the DELETE MODULE command.
GIf the specified module is currently reserved in the specified stream, 7VDE terminates that reservation since it is based on a Bmodule 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.
FIf you want to delete a module generation that does not belong to any Bdevelopment stream, use the /GENERATION qualifier. Do not use the A/GENERATION qualifier for a generation that belongs to a stream; <VDE will not delete any generation that belongs to a stream 2or that is not a leaf node in the generation tree.
/CONFIRM
/NOCONFIRM (default)
<Controls whether VDE asks you to confirm that you want each 9generation deleted. The /CONFIRM qualifier causes VDE to Dprint a message for the latest generation of each module giving the Aname of the generation and asking whether you want to delete the Hgeneration. If you answer YES (or Y), the generation is deleted. If you @answer NO (or N), the generation is not deleted. The /NOCONFIRM 7qualifier causes VDE to delete each generation without asking for confirmation./GENERATION=gen-expr
GSpecifies that the generation with the CMS generation expression given Fby the gen-expr parameter be deleted. If you specify 5this qualifier, do not specify the /STREAM qualifier./LOG (default)
/NOLOG
@Controls whether log messages are printed after generations are Cdeleted. The /LOG qualifier causes such messages to be printed and H/NOLOG suppresses them. The messages indicate that the generations have @been deleted from the specified development stream and that the 0database transaction has successfully committed./REMARK="string"
HSpecifies a remark string that explains why you deleted the generation. :The quoted remark string can be up to 132 characters long./STREAM=stream-name
HSpecifies that the latest generation in the development stream given by Dthe stream-name parameter be deleted. If both this 9qualifier and the /GENERATION qualifier are omitted, VDE prompts you for the stream name.
6
| #1 |
|---|
3VDEä DELETE GENERATION [FACIL]MODNAM.C /STREAM=V2.0G%VDE-I-GENDEL, generation [FACIL]MODNAM.C;5(5) deleted from stream V2.0>%VDE-I-COMMIT, database transaction has successfully committedVDEä$VDEä SHOW GENERATION [FACIL]MODNAM.COGeneration [FACIL]MODNAM.C;4(4) by user SMITH on 9-MAY-1990 19:43VDEä |
EThis example deletes the latest generation of module [FACIL]MODNAM.C Gfrom stream V2.0. The log message shows that generation 5 was deleted. FThe subsequent SHOW GENERATION command shows that generation 4 is now 2the latest generation of the module in the stream.
| PreviousX | Next[ | Contents] | Index |