| Previous[ | Contents] | Index |
=Deletes one or more development streams from the current VDE library.
6DELETE STREAM stream-name [, stream-name...]
stream-name
8The name of a stream to be deleted from the current VDE @library. You can delete more than one stream at a time by using Gwildcard characters. The percent sign (%) in a name matches any single Hcharacter in the position it occupies and the asterisk (*) matches zero Dor more characters in the position it occupies. Those streams whose -names match the wildcard pattern are deleted.
DThe DELETE STREAM command deletes each specified development stream <from the current VDE library. When a stream is deleted, all Hdatabase information associated with the stream is deleted. The deleted Gdatabase information includes the stream's group definitions, scripts, Gand build dependency graph. The stream is also removed from any stream Esuccessor chains it belongs to. The stream's disk directories remain )unchanged, however; they are not deleted.FYou can only delete a stream if the delete attribute Eis set for the stream. If this attribute is not set, you must set it Awith the MODIFY STREAM /DELETE command before you can delete the Bstream. Unless the library's allow-deletion attribute is set, the Hstream must also be closed before it can be deleted. (Use MODIFY STREAM /CLOSED to close a stream.)
/CONFIRM
/NOCONFIRM (default)
<Controls whether VDE asks you to confirm that you want each =stream deleted. The /CONFIRM qualifier causes VDE to print a Hmessage for each stream asking whether you want that stream deleted. If Gyou answer YES (or Y), that stream is deleted from the library. If you Hanswer NO (or N), the stream is not deleted. If you enter a stream name ;with a wildcard specification, VDE asks you to confirm the Gdeletion of each stream whose name matches the wildcard specification. <The /NOCONFIRM qualifier causes VDE to delete the specified (streams without asking for confirmation./LOG (default)
/NOLOG
EControls whether log messages are printed after each stream has been Gdeleted. The /LOG qualifier causes such messages to be printed and the C/NOLOG qualifier suppresses them. These messages indicate that the ?stream 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 Dstream. 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 STREAM V3.1-17%VDE-I-STRMDEL, stream V3.1-1 deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
6GIn this example, development stream V3.1-1 is deleted from the current :VDE library. The log messages confirm that the stream was Adeleted and that the database transaction successfully completed.
| #2 |
|---|
/VDEä DELETE STREAM V2.0-BL1, V2.0-BL2, V2.0-BL39%VDE-I-STRMDEL, stream V2.0-BL1 deleted from the database9%VDE-I-STRMDEL, stream V2.0-BL2 deleted from the database9%VDE-I-STRMDEL, stream V2.0-BL3 deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
CThis example shows how to specify a list of stream names to delete Emultiple streams from the library. The log messages list the deleted streams.
:Deletes user records from the database in the current VDE Flibrary. This command deletes the database record for each user whose ?OpenVMS username is listed as a parameter and denies that user "access to the current VDE library.
.DELETE USER username [, username...]
username
5The OpenVMS username of the VDE user whose record is :deleted from the database of the current VDE library. You >can delete more than one username at a time by using wildcard Bcharacters. The percent sign (%) in a username matches any single Hcharacter in the position it occupies and the asterisk (*) matches zero Bor more characters in the position it occupies. Those users whose 1usernames match the wildcard pattern are deleted.
FThe DELETE USER command disables access by, and disallows any command Especification of, the specified user. It also cancels all review and ,notification entries for the specified user.@The command marks the specified user records in the database as Edeleted, though the user records are not physically deleted from the <database. As a result of this behaviour, records in the VDE Fdatabase can continue to refer to the user records marked as deleted. BFor example, the record for each module indicates who created the Emodule, and the SHOW MODULE command shows the creator's username and Bfull name string. That information is found in the creator's user Drecord, even if the creator has since left the project and a DELETE >USER command has marked the associated user record as deleted.
FA user that lacks a matching user entry, or has a deleted user entry, 5will be unable to access the VDE utility1 HFurther, usernames that have been deleted will not be accepted :on VDE commands. However, the username record does remain Hwithin the database, should manual recovery be required at a later date.
3Lists of valid VDE users can also be automatically *maintained using the VDE/READ_UAF command.>VDE/READ_UAF compares the current list of users stored in the 5VDE database with those stored in the OpenVMS system authorization= database (SYSUAF). The VDE/READ_UAF command is described in = VDE/READ_UAF.
GAs an alternative to the DELETE USER command, one could clear all bits Bin the associated privilege mask, and/or one could use the MODIFY %USER/USER command to rename the user.?These steps prevent the user from performing operations on the 8VDE database, but these options preserve the ability to %specify the username in VDE commands.
/CONFIRM
/NOCONFIRM (default)
<Controls whether VDE asks you to confirm that you want each Euser record deleted from the database. The /CONFIRM qualifier causes 7VDE to print a message for each user record giving the Husername and asking whether you want that record deleted. If you answer BYES (or Y), that user record is deleted from the database. If you Aanswer NO (or N), the user record is not deleted. If you enter a 8username with a wildcard specification, VDE asks you to @confirm the deletion of each username that matches the wildcard =specification. The /NOCONFIRM qualifier causes VDE to delete Fthe specified users from the database without asking for confirmation./LOG (default)
/NOLOG
EControls whether log messages are printed after each user record has Ebeen deleted. These messages indicate that the user has been deleted Efrom the database and that the database transaction has successfully Ecommitted. The /LOG qualifier causes such messages to be printed and %the /NOLOG qualifier suppresses them./REMARK="string"
GSpecifies a remark string to be stored in the database for the deleted >user record. 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 USER SMITH4%VDE-I-USERDEL, user SMITH deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
6HIn this example, the record for user SMITH is deleted from the database :of the current VDE library. The log messages confirm that >the user record was deleted and that the database transaction successfully completed.
| #2 |
|---|
"VDEä DELETE USER SMITH, DOE, JONES4%VDE-I-USERDEL, user SMITH deleted from the database2%VDE-I-USERDEL, user DOE deleted from the database4%VDE-I-USERDEL, user JONES deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
6GThis example shows how to delete multiple users from the database. The 2log messages list the users who have been deleted.
| #3 |
|---|
#VDEä DELETE USER/CONFIRM SMITH, DOEDelete user SMITH ? [No]: Y4%VDE-I-USERDEL, user SMITH deleted from the databaseDelete user DOE ? [No]: N>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
6GThis example illustrates the /CONFIRM qualifier. This qualifier causes 7VDE to ask the user whether each specified user record Eshould be deleted from the database. For user SMITH, the answer is Y F(for YES) and that user record is deleted from the database. For user CDOE, the answer is N (for NO) and that user record is not deleted. BHence there is no log message for user DOE. The final log message Bindicates that the database transaction for the whole command has successfully committed.
| #4 |
|---|
VDEä DELETE USER %O*2%VDE-I-USERDEL, user DOE deleted from the database4%VDE-I-USERDEL, user JONES deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
DIn this example, the username specification (%O*) contains wildcard Gcharacters. All usernames with an "O" in the second position Hmatch the specification. Hence users DOE and JONES are deleted from the database.
| N E 1 This assumes that the VDE N library option that allows automatic addition of new users upon first access is disabled. |
<Displays the differences between any two module generations.
-DIFFERENCES gen-spec-1 [gen-spec-2]
gen-spec-1
ESpecifies the first module generation to be compared. The generation 1specification consists of the following in order:<
<An example of a generation specification is [RMS]MOD1.MAR;5.- an optional facility name enclosed in square brackets
- a module name
- a type name<
- an optional generation number preceded by a semicolon
DIf you omit the facility name, a module generation from the default Bfacility is compared. If you omit the generation number, the most Hrecent generation of the module in the specified (or default) stream is compared.
DIf you specify a zero or negative generation number, that number is Crelative to the most recent generation of the module in the stream Bspecified by the /STREAM qualifier (or the default stream if that Equalifier is omitted). For example, if the most recent generation is @generation 5, then generation 0 is the same as generation 5 and +generation --1 is the same as generation 4.
;If you specify the /GENERATION qualifier, VDE compares the Dgeneration with the given CMS generation expression and ignores the ?generation number on the gen-spec-1 parameter.
gen-spec-2
FSpecifies the second module generation to be compared. This parameter .can have the same form as the first parameter 5(gen-spec-1) to fully specify a VDE Hgeneration. If the facility, module, and type names are the same as for Fthe first parameter, this second parameter can be abbreviated to just Hthe generation number, optionally preceded by a semicolon. For example, G";5" or just "5" is enough to specify generation 5 Aof the module given by the gen-spec-1 parameter.=If the gen-spec-2 parameter is omitted, VDE Acompares the generation given by the gen-spec-1 Fparameter with the immediately preceding generation. You can also use Gthe /GENERATION and /STREAM qualifiers to compare other generations of the same module.
CThe DIFFERENCES command determines the differences between any two :module generations in the VDE library. It fetches the two @specified generations into a scratch directory and runs the DCL DIFFERENCESHcommand in a subprocess to compare the texts of the two generations and 9to display the differences between them on your terminal.GThe command fetches the specified generations into a scratch directory ?determined as follows. If logical name VDE$SCRATCH is defined, VDEEfetches the files into the directory that this logical name is bound 9to. If this logical name is not defined, VDE fetches the ;files into a VDE-created subdirectory [.VDE$SCRATCH] under Gthe current SYS$SCRATCH directory. (By default, SYS$SCRATCH is defined as yourHSYS$LOGIN login directory. This logical name can be redefined by a user Hto reference a user-created subdirectory; all scratch files can thus be 8corraled in a particular subdirectory.) VDE creates the F[.VDE$SCRATCH] subdirectory if it does not already exist, and defines 7the logical name VDE$SCRATCH to reference it. VDE then Gspawns a subprocess to run the DCL DIFFERENCES command and display the =differences. VDE deletes the fetched files at the end of the Fcommand unless you specify the /KEEP qualifier. The difference output Hgoes to your terminal by default, but you can direct it to a file using the /OUTPUT qualifier.
EAlthough the DIFFERENCES command can compute the differences between <any two generations in the VDE library, it is almost always Eused to compare two generations of the same module. For this reason, Cyou can reduce the second generation specification parameter so it Econsists of only a generation number. The following example compares Egenerations 5 and 2 of module [FACIL]MOD.TYP for your default stream:
"$VDEä DIFFERENCES [FACIL]MOD.TYP;5 ;2@You can also omit the second generation specification parameter Dentirely. In this case, the specified generation is compared to its Himmediate predecessor. The following command thus compares generation 5 with generation 4:
"!VDEä DIFFERENCES [FACIL]MOD.TYP;5@When you omit the second parameter, you can use the /GENERATION ?qualifier to specify the CMS generation expressions of the two Hgenerations to compare. For example, the following command compares the :generations with CMS generation expressions 10A2 and 11B1:
"6VDEä DIFFERENCES [FACIL]MOD.TYP/GENERATION=(10A2,11B1)BYou can also use the /STREAM qualifier to specify that the latest @generations from two streams be compared. The following example .illustrates this use of the /STREAM qualifier:
DThis example compares the latest generations of the given module in streams V2.0 and V2.2.
"2VDEä DIFFERENCES [FACIL]MOD.TYP/STREAM=(V2.0,V2.2):In addition to accepting certain VDE-specific qualifiers, Hthe DIFFERENCES command accepts all qualifiers that the DCL DIFFERENCES Ccommand accepts. These qualifiers are simply passed through to the 5subprocess that runs the OpenVMS DIFFERENCES program.
/GENERATION=gen-expr
ASpecifies that the module generation that has the CMS generation ?expression given by the gen-expr parameter be 5compared. If this qualifier is omitted, VDE uses the Hgeneration given by the generation number on the module-name parameter. BIf both this qualifier and the generation number are omitted, the Ccommand uses the latest generation of the module for the specified development stream./KEEP
>Specifies that one or both of the fetched and compared module Cgenerations be retained in the scratch directory after the command completes. If thisAqualifier is omitted, the files containing those generations are Edeleted after the differences are computed. If you specify the /KEEP Dqualifier after the gen-spec-1 parameter, the file Gcontaining that generation is kept. Likewise, if you specify the /KEEP Dqualifier after the gen-spec-2 parameter, the file Gcontaining that generation is kept. If you specify the qualifier after Gthe DIFFERENCES keyword or after both parameters, the files containing both generations are kept./STREAM=stream-name
FSpecifies that the generation to be compared should be taken from the Hdevelopment stream given by the stream-name parameter. HIf this qualifier is omitted, the generation is taken from your default 0stream unless you use the /GENERATION qualifier.-/CHANGE_BAR
+
/COMMENT_DELIMITER/IGNORE
/MAXIMUM_DIFFERENCES/MATCH
/MERGED/MODE
/NUMBER/NONUMBER
#
/OUTPUT/PARALLEL
"
/SEPARATED/SLP
CThese qualifiers are passed through to the spawned DCL DIFFERENCES Gcommand without change. See the description of the DIFFERENCES command @in the OpenVMS DCL Dictionary manual for a description )of these qualifiers and their parameters.
/WIDTH /WINDOW
#
VDEä DIFFERENCES [FACIL]A.B32 ************%File DEVD$:[SMITH.VDE$SCRATCH]A.REQ;2= 9 ! declarations. Here is an additional comment. 10 !******%File DEVD$:[SMITH.VDE$SCRATCH]A.REQ;1 9 ! declarations. 10 ! ************ &Number of difference sections found: 1%Number of difference records found: 1 DIFFERENCES /IGNORE=()/MERGED=1-% DEVD$:[SMITH.VDE$SCRATCH]A.REQ;2-$ DEVD$:[SMITH.VDE$SCRATCH]A.REQ;1VDEä |
GThis example compares the default stream's two most recent generations Fof module [FACIL]A.B32 and displays their differences on the terminal.
8Ends the VDE session or ends execution of commands in a command procedure.
EXIT
None.
EWhen you enter the EXIT command at the terminal, you end the current .VDE session. (Pressing Ctrl/Z also ends a VDE 9session.) When VDE executes an EXIT command in a command Eprocedure, it returns control to the command stream that invoked the Fcommand procedure. That command stream may be the terminal or another command procedure.
/KEPT_PROCESS
EIf you enter the EXIT/KEPT_PROCESS command at the terminal (not in a .VDE command procedure) and the VDE utility is ;running in a kept subprocess, this qualifier causes VDE to Bterminate that subprocess before it returns you to DCL level. The Badvantage of terminating the kept subprocess is that it no longer ;consumes resources. The disadvantage is that your next VDE ;command will require more time to reactivate the VDE image "and reconnect to the VDE database.
6
| #1 |
|---|
VDEä EXIT$ |
?This example shows how the EXIT command returns control to DCL.
0Extracts a VDE script from the VDE database and writes it to a file.
"EXTRACT SCRIPT file-spec
file-spec
=Specifies the OpenVMS file specification for the output file Ethat will contains the text of the extracted script. If you omit the Gdirectory specification from the file-spec parameter, @your current default directory is assumed. If you omit the file Hextension from the file-spec parameter, file extension VDESCRIPT is assumed.
=The EXTRACT SCRIPT command reads a specified VDE script from 6the VDE database and writes it to an ASCII text file. 7VDE only extracts the script of the specified type and Gsegment number that belongs to the default development stream. You can Duse the EXTRACT SCRIPT command when you want to get a script into a Dfile so that you can edit it and then reinsert it into the database (with a subsequent CREATE SCRIPT command.GYou must specify a script-type qualifier to select the script you want Cextracted. See the description of the CREATE SCRIPT command for an Fexplanation of the format of scripts, the different types of scripts, Dand how scripts are selected using script-type qualifiers. You must Halso specify the script segment number unless the default value applies.
|Keywords used within scripts are documented in Script Keywords, while yscript functions are in Script Functions, and script types are in mScript Types. For other script-related commands, also see CREATE SCRIPT, DELETE SCRIPT, INVOKE SCRIPT, MODIFY SCRIPT, and @SHOW SCRIPT.
/BUILD
>Specifies that the default stream's BUILD script be extracted./COMPILE=mod-name
FSpecifies that the default stream's COMPILE script with the specified 5mod-name specification be extracted./COPY=mod-name
CSpecifies that the default stream's COPY script with the specified 5mod-name specification be extracted./CREATE_FACILITY
6Specifies that the script that VDE invokes when a new (facility is created should be extracted.$/DELETE_GENERATION=mod-name
FSpecifies that the default stream's DELETE_GENERATION script with the ?specified mod-name specification be extracted./DIFFERENCES=mod-name
@Specifies that the default stream's DIFFERENCES script with the ?specified mod-name specification be extracted./FETCH=mod-name
DSpecifies that the default stream's FETCH script with the specified 5mod-name specification be extracted.$/INSERT_GENERATION=mod-name
FSpecifies that the default stream's INSERT_GENERATION script with the ?specified mod-name specification be extracted./LINK=mod-name
CSpecifies that the default stream's LINK script with the specified 5mod-name specification be extracted./LOG (default)
/NOLOG
>Controls whether log messages are printed after the script is Eextracted. The /LOG qualifier causes such messages to be printed and Gthe /NOLOG qualifier suppresses them. These messages indicate that the 7script has been extracted and identify the output file./NEW_STREAM=fac-name
?Specifies that the default stream's NEW_STREAM script with the ?specified fac-name specification be extracted./NOKEEP=mod-name
ESpecifies that the default stream's NOKEEP script with the specified 5mod-name specification be extracted./REPLACE=mod-name
FSpecifies that the default stream's REPLACE script with the specified 5mod-name specification be extracted./RESERVE=mod-name
FSpecifies that the default stream's RESERVE script with the specified 5mod-name specification be extracted./SEGMENT=seg-num
;Specifies the segment number of the script to extract. The Aseg-num parameter specifies the integer segment <number. If you omit this qualifier, VDE extracts the script with segment number 10./SET_FACILITY=fac-name
ASpecifies that the default stream's SET_FACILITY script with the ?specified fac-name specification be extracted./SET_STREAM
CSpecifies that the default stream's SET_STREAM script be extracted./STAGING=mod-name
FSpecifies that the default stream's STAGING script with the specified 5mod-name specification be extracted./UNRESERVE=mod-name
HSpecifies that the default stream's UNRESERVE script with the specified 5mod-name specification be extracted.
6
| #1 |
|---|
5VDEä EXTRACT SCRIPT/COMPILE=[CODE]*.C [MYDIR]SCRIPT_CJ%VDE-I-SCRPEXTR, script extracted to file DEV$:[MYDIR]SCRIPT_C.VDESCRIPT;10 script to compile module [CODE]*.C (segment 10) VDEä EXIT $ TYPE [MYDIR]SCRIPT_C.VDESCRIPT ! Script to compile a C module.!EMIT "$ SET VERIFY"&EMIT "$ DEFINE/NOLOG SRC$ ", $DIR(SRC)&EMIT "$ DEFINE/NOLOG OBJ$ ", $DIR(OBJ)3EMIT "$ CC/DEBUG/OBJ=OBJ$:/ANA=OBJ$: SRC$:",$MODTYP'EMIT "$ VDE/DEPEND C OBJ$:",$MOD,".ANA"EXIT$ |
HThis example extracts the script to compile C modules in facility CODE. VDE writes the script into file GDEV$:[MYDIR]SCRIPT_C.VDESCRIPT. The subsequent TYPE command shows that )the file contains the text of the script.
| PreviousX | Next[ | Contents] | Index |