9Deletes one or more groups from the current VDE database.

+Requires CREGRP privilege.

Format

2

DELETE GROUP group-name [,group-name...]

Parameter



group-name

AThe name of a source group or build group defined in the default ;development stream that is to be deleted from the database.

?You can delete more than one group at a time by using wildcard Ccharacters in the group name. The percent sign (%) in a group name Amatches any single character in the position it occupies and the @asterisk (*) matches zero or more characters in the position it Boccupies. Those groups whose names match the wildcard pattern are deleted.

Description

EThis command deletes the database definition of each source group or Cbuild group listed as a parameter. The /SOURCE or /BUILD qualifier Ddetermines whether source groups or build groups are deleted. Group Edefinitions are deleted only in the default development stream. This Dcommand does not affect the modules that are members of the deleted +groups, only the definitions of the groups.

Qualifiers



/BUILD



/SOURCE (default)

ASpecifies whether source groups or build groups are deleted. The 9/SOURCE qualifier causes VDE to delete the source groups =with the specified names. The /BUILD qualifier causes VDE to Gdelete the build groups with the specified names. If neither qualifier (is specified, VDE deletes source groups.

.Of /BUILD and /SOURCE, /SOURCE is the default.

/CONFIRM



/NOCONFIRM (default)

<Controls whether VDE asks you to confirm that you want each <group deleted. The /CONFIRM qualifier causes VDE to print a Hmessage giving the name of the group and asking if you want it deleted. CIf you answer YES (or Y), the group definition is deleted from the Hdatabase. If you answer NO (or N), the group is not deleted. If you use =a group specification that contains wildcard characters, VDE @asks you to confirm the deletion of each group that matches the <wildcard specification. The /NOCONFIRM qualifier causes VDE ?to delete all specified groups without asking for confirmation.

/LOG (default)



/NOLOG

DControls whether log messages are printed after each group has been Gdeleted. The /LOG qualifier causes such messages to be printed and the C/NOLOG qualifier suppresses them. These messages indicate that the =group has been deleted and that the database transaction has successfully committed.

/REMARK="string"

GSpecifies a remark string to be stored in the database for the deleted Cgroup. The quoted remark string, which can be up to 132 characters @long, may contain any explanatory remark about the group or its 0deletion that you want to store in the database.

Examples

VDEä DELETE GROUP GRPNAM5%VDE-I-GRPDEL, group GRPNAM deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



DIn this example, the source group called GRPNAM is deleted from the =VDE database in the default stream. The log messages confirm ?that the group was deleted and that the corresponding database #transaction completed successfully.

)VDEä DELETE GROUP/BUILD GRP1, GRP2, GRP333%VDE-I-GRPDEL, group GRP1 deleted from the database3%VDE-I-GRPDEL, group GRP2 deleted from the database4%VDE-I-GRPDEL, group GRP33 deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



HThis example shows how to specify a list of group names with the DELETE CGROUP command. The log messages list the groups that were deleted. EBecause the /BUILD qualifier is specified, this command only deletes build groups.

*VDEä DELETE GROUP/CONFIRM GROUP_1, GROUP_2Delete group GROUP_1 ? [No]: Y6%VDE-I-GRPDEL, group GROUP_1 deleted from the databaseDelete group GROUP_2 ? [No]: N>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



GThis example illustrates the /CONFIRM qualifier. This qualifier causes ;VDE to ask the user whether each specified group should be Hdeleted. For group GROUP_1, the user answers Y (for YES) and that group Bis deleted from the database, as the log message shows. For group HGROUP_2, the user answers N (for NO), that group is not deleted, and no Clog message is displayed. The final log message indicates that the Fdatabase transaction for the whole command has successfully committed.

VDEä DELETE GROUP GRP*3%VDE-I-GRPDEL, group GRP1 deleted from the database3%VDE-I-GRPDEL, group GRP2 deleted from the database4%VDE-I-GRPDEL, group GRP22 deleted from the database4%VDE-I-GRPDEL, group GRP33 deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



DIn this example, the group specification (GRP*) contains a wildcard Gcharacter. The asterisk matches zero or more characters. Source groups CGRP1, GRP2, GRP22, and GRP33 match the group specification and are !deleted as the log messages show.

VDEä DELETE GROUP GRP%3%VDE-I-GRPDEL, group GRP1 deleted from the database3%VDE-I-GRPDEL, group GRP2 deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



BThis example is identical to the previous example except that the Gpercent sign is used as a wildcard character. The percent sign matches Eexactly one character. As a result, source groups GRP1 and GRP2 (but Anot GRP22 or GRP33) match the group specification (GRP%) and are deleted.

9Deletes one or more modules from the current VDE library.

<Requires DELMOD privilege or, in some cases, CREMOD privilege.

Format

0

DELETE MODULE mod-name [, mod-name...]

Parameter



mod-name

8The name of a module to be deleted from the current VDE Glibrary. This name consists of a module name and a type name separated Bby a period (such as MOD1.PAS) and can be preceded by an optional Ffacility name enclosed in square brackets (as in [FACIL]MOD1.PAS). If Gno facility name is specified, the current default facility is assumed.

@You can delete more than one module at a time 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 Cposition it occupies. Those modules whose names match the wildcard pattern are deleted.

Description

AThe DELETE MODULE command deletes each specified module from the /current VDE library. When a module is deleted, <VDE deletes its database record and removes the module from Athe build dependency graph and from any group definitions. After ;committing the database transaction, VDE also deletes each :specified module's delta file (CMS element). However, VDE Edoes not remove the module from any stream-specific disk directories /such as clear-copy areas or object directories.

@Normally, you must have the DELMOD privilege to delete a module.FHowever, if you have created a particular module and you have not yet Gcreated the first generation of the module (normally done by replacing <the first generation into the VDE library), you are allowed Fto delete the module without the DELMOD privilege. In this particular case, you must have theG CREMOD privilege, which was required for the initial module creation. C The creator of a module can thus correct simple mistakes, such as H misnaming the module, by simply deleting the module before the initial H replacement is performed. The outstanding reservation on the module is F canceled, the module is removed from any reservation session that it ; might be included in, and the module never appears in the ; VDE library. For further information on the CREATE MODULE N command, see CREATE MODULE.

GIf you are not the creator of a module or if the module already has at Eleast one generation, you must have the DELMOD privilege to delete it@and you can only delete a module if the delete Hattribute is set for the module. If this attribute is not set, you must Hset it with the MODIFY MODULE /DELETE command before you can delete the module.

Qualifiers



/CONFIRM



/NOCONFIRM (default)

<Controls whether VDE asks you to confirm that you want each =module deleted. The /CONFIRM qualifier causes VDE to print a Hmessage for each module asking whether you want that module deleted. If Gyou answer YES (or Y), that module is deleted from the library. If you Hanswer NO (or N), the module is not deleted. If you enter a module name ;with a wildcard specification, VDE asks you to confirm the Edeletion of each module that matches the wildcard specification. The 8/NOCONFIRM qualifier causes VDE to delete the specified (modules without asking for confirmation.

/LOG (default)



/NOLOG

EControls whether log messages are printed after each module has been Gdeleted. The /LOG qualifier causes such messages to be printed and the C/NOLOG qualifier suppresses them. These messages indicate that the ?module 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 Dmodule. 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.

Examples

VDEä DELETE MODULE MOD1.PAS>%VDE-I-MODDEL, module [CODE]MOD1.PAS deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



=In this example, module MOD1.PAS is deleted from the current =VDE library. Since no facility name is specified, the module Eis assumed to belong to the current default facility, facility CODE. BThe log messages confirm that the module was deleted and that the ,database transaction successfully completed.

9VDEä DELETE MODULE [FACIL]FOO.MAR, FOO.OBJ, [RMS]MOD2.FOR>%VDE-I-MODDEL, module [FACIL]FOO.MAR deleted from the database>%VDE-I-MODDEL, module [FACIL]FOO.OBJ deleted from the database=%VDE-I-MODDEL, module [RMS]MOD2.FOR deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



HThis example shows how to delete multiple modules from the library. The &log messages list the deleted modules.

5Deletes one or more queued replacements from the VDE Adatabase to free up database space. Most users should use CANCEL REPLACEMENT instead.

+Requires DELREP privilege.

Format

5

DELETE REPLACEMENT rep-name [, rep-name...]

Parameter



rep-name

@The name of a queued replacement to be deleted from the current ;VDE library. You can delete more than one replacement at a Gtime by using wildcard characters in the replacement name. The percent Csign (%) in a name matches any single character in the position it Eoccupies and the asterisk (*) matches zero or more characters in the Fposition it occupies. Those queued replacements whose names match the wildcard pattern are deleted.

FDo not specify the rep-name parameter if you use the /IDENTIFICATION qualifier.

Description

HThe DELETE REPLACEMENT command deletes each specified queued replacement7from the current VDE database. This command is used to Hremove replacement records from the database to free up database space. >It can be used to delete both current replacement records and Ehistorical replacement data. For this reason, it requires the DELREP privilege.

EUsers who simply want to cancel a current replacement should use the GCANCEL REPLACEMENT command. This command requires the RESREP privilege to cancelFyour own replacement or the PERFREP privilege to cancel another user'sreplacement.

Qualifiers



/CONFIRM



/NOCONFIRM (default)

<Controls whether VDE asks you to confirm that you want each :replacement deleted. The /CONFIRM qualifier causes VDE to Bprint a message for each replacement asking whether you want that Creplacement deleted. If you answer YES (or Y), that replacement is Gdeleted from the database. If you answer NO (or N), the replacement is =not deleted. If you enter a replacement name with a wildcard <specification, VDE asks you to confirm the deletion of each ?replacement whose name matches the wildcard specification. The 8/NOCONFIRM qualifier causes VDE to delete the specified -replacements without asking for confirmation.

/HISTORY

CSpecifies that replacement history be deleted. Replacement history Econsists of database records for past replacements that have already Bbeen performed; it does not include currently queued replacements.EWhen used with the /IDENTIFICATION qualifier, the /HISTORY qualifier Bdeletes information for chronological ranges of past replacements.

:If you omit the /HISTORY qualifier, VDE deletes currently queued replacements only.!

/IDENTIFICATION=id-range

FSpecifies that the replacements with the unique Replacement Ids given Fby the id-range parameter be deleted. Do not specify Dthe rep-name parameter when you use this qualifier.

9VDE assigns a unique Replacement Id to each immediate or queued replacement into the VDE<library. VDE assigns Replacement Ids in chronological order Hso that the first replacement into the library has Id value 1, the next <has Id value 2, and so on. When you use this qualifier, all ;replacements that have Id values in the range given by the 0id-range parameter are deleted.

GThe id-range parameter can be a single integer value, Da range of integers, or a wildcard character. If the parameter is a 8single integer (for example, /IDENT=5), VDE deletes the Ereplacement with that Replacement Id. If the parameter is a range of ?integers (specified as two integers separated by a colon as in ;/IDENT=3:5), VDE deletes the replacements with Ids in that Brange. Finally, if the id-range parameter is the :asterisk wildcard character (as in /IDENT=*), VDE deletes all replacements.

0If you specify a zero or negative number in the Did-range parameter, that number is relative to the =largest Replacement Id value for the VDE library (the latest Hreplacement). For example, if the latest replacement has Replacement Id A250, then /IDENT=0 is equivalent to /IDENT=250 and /IDENT=--1 is equivalent to /IDENT=249.

FThe /IDENTIFICATION qualifier can be used with the /HISTORY qualifier :to delete historical replacement information from the VDE Gdatabase. Deleting such information allows database space to be reused.

/LOG (default)



/NOLOG

EControls whether log messages are printed after each replacement has Hbeen deleted. The /LOG qualifier causes such messages to be printed and Gthe /NOLOG qualifier suppresses them. These messages indicate that the Ereplacement has been deleted from the database and that the database 'transaction has successfully committed.

Examples

"VDEä DELETE REPLACEMENT ANDERSON-1?%VDE-I-REPDEL, replacement ANDERSON-1 deleted from the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



=In this example, replacement ANDERSON--1 is deleted from the <VDE database. The log messages confirm that the replacement Ewas deleted and that the database transaction successfully completed.

+Deletes a VDE script from the VDE database.

,Requires CRESCRP privilege.

Format



DELETE SCRIPT

Description

9The DELETE SCRIPT command deletes a specified VDE script ,from the VDE database. VDE only deletes the Dscript of the specified type and segment number that belongs to the default development stream.

GYou must specify a script-type qualifier to select the script you want Adeleted. See the description of the CREATE SCRIPT command for an Bexplanation of the different types of scripts and how scripts are Hselected using script-type qualifiers. You must also specify the script 0segment 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, EXTRACT SCRIPT, INVOKE SCRIPT, MODIFY SCRIPT, and @SHOW SCRIPT.

Qualifiers



/BUILD

<Specifies that the default stream's BUILD script be deleted.

/COMPILE=mod-name

FSpecifies that the default stream's COMPILE script with the specified 3mod-name specification be deleted.

/CONFIRM



/NOCONFIRM (default)

<Controls whether VDE asks you to confirm that you want each =script deleted. The /CONFIRM qualifier causes VDE to print a Hmessage for each script asking whether you want that script deleted. If Gyou answer YES (or Y), the script is deleted from the database. If you Fanswer NO (or N), the script is not deleted. The /NOCONFIRM qualifier :causes VDE to delete the specified scripts without asking for confirmation.

/COPY=mod-name

CSpecifies that the default stream's COPY script with the specified 3mod-name specification be deleted.

/CREATE_FACILITY

6Specifies that the script that VDE invokes when a new &facility is created should be deleted.$

/DELETE_GENERATION=mod-name

FSpecifies that the default stream's DELETE_GENERATION script with the =specified mod-name specification be deleted.

/DIFFERENCES=mod-name

@Specifies that the default stream's DIFFERENCES script with the =specified mod-name specification be deleted.

/FETCH=mod-name

DSpecifies that the default stream's FETCH script with the specified 3mod-name specification be deleted.$

/INSERT_GENERATION=mod-name

FSpecifies that the default stream's INSERT_GENERATION script with the =specified mod-name specification be deleted.

/LINK=mod-name

CSpecifies that the default stream's LINK script with the specified 3mod-name specification be deleted.

/LOG (default)



/NOLOG

GControls whether log messages are printed after the script is deleted. EThe /LOG qualifier causes such messages to be printed and the /NOLOG Gqualifier suppresses them. These messages indicate that the script has =been deleted and that the database transaction has committed successfully.

/NEW_STREAM=fac-name

?Specifies that the default stream's NEW_STREAM script with the =specified fac-name specification be deleted.

/NOKEEP=mod-name

ESpecifies that the default stream's NOKEEP script with the specified 3mod-name specification be deleted.

/REPLACE=mod-name

FSpecifies that the default stream's REPLACE script with the specified 3mod-name specification be deleted.

/RESERVE=mod-name

FSpecifies that the default stream's RESERVE script with the specified 3mod-name specification be deleted.

/SEGMENT=seg-num

:Specifies the segment number of the script to delete. The Aseg-num parameter specifies the integer segment ;number. If you omit this qualifier, VDE deletes 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 deleted.

/SET_STREAM

ASpecifies that the default stream's SET_STREAM script be deleted.

/STAGING=mod-name

FSpecifies that the default stream's STAGING script with the specified 3mod-name specification be deleted.

/UNRESERVE=mod-name

HSpecifies that the default stream's UNRESERVE script with the specified 3mod-name specification be deleted.

Examples

$VDEä DELETE SCRIPT/COMPILE=[CODE]*.C0%VDE-I-SCRPDEL, script deleted from the database0 script to compile module [CODE]*.C (segment 10)>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



EThis example deletes the script to compile all C modules in facility @CODE. The log messages identify the script and show that it was Asuccessfully deleted. The script is only deleted for the default development stream.

7Deletes build-step dependency information from the VDE Gdatabase. This information specifies the input and output modules of a "given compile, copy, or link step.

,Requires CRESTEP privilege.

Format

.

DELETE STEP mod-name [, mod-name...]

Parameter



mod-name

HThe name of the module that is compiled, copied, or linked by the build Hstep to be deleted from the database. This name consists of an optional Afacility name enclosed in square brackets, a module name, and an 6optional type name preceded by a period (for example, A[FACNAM]MOD1.PAS). If no facility name is specified, the current Edefault facility is assumed. If no type name is specified, all build Csteps for modules with the given facility name and module name are deleted.

DYou can delete more than one build step at a time 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 Eposition it occupies. Those build steps whose module names match the wildcard pattern are deleted.

Description

GThe DELETE STEP command deletes all dependency information for a given Gbuild step so that the database no longer records the input and output Emodules for the step. The modules themselves remain in the database; 4only their relationships to the build step are lost.

DThe command deletes build-step dependency information from only the Cdefault development stream. To delete build steps in more than one Estream, you must repeat the DELETE STEP command for each stream. For Geach stream, first enter the SET STREAM command to set the development Astream, then enter the DELETE STEP command to delete the desired *build-step dependencies from the database.

Qualifiers



/COMPILE (default)



/COPY



/LINK

ESpecifies the kind of build step to be deleted. /COMPILE deletes the Fcompile step, /COPY deletes the copy step, and /LINK deletes the link step for the specified module.

6Of /COMPILE, /COPY and /LINK, /COMPILE is the default.

/CONFIRM (default)



/NOCONFIRM

;Controls whether VDE asks you to confirm that you want the =build-step definition deleted. The /CONFIRM qualifier causes :VDE to print a message for each build step asking whether Eyou want that step deleted. If you answer YES (or Y), the build-step ?definition is deleted. If you answer NO (or N), the build-step ;definition is not deleted. The /NOCONFIRM qualifier causes ;VDE to delete all specified build-step definitions without asking for confirmation.

/LOG (default)



/NOLOG

FControls whether log messages are printed when build-step definitions Fare deleted from the database. The /LOG qualifier causes the messages Eto be printed and the /NOLOG qualifier suppresses them. The messages Eindicate that each build step has been deleted and that the database 'transaction has committed successfully.

Examples

VDEä DELETE STEP [RMS]FOO.MARM%VDE-I-COMSTEPDEL, compile step for module [RMS]FOO.MAR deleted from database>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



>This example deletes all build dependency information for the .compilation of module FOO.MAR in facility RMS.

'VDEä DELETE STEP/LINK FOO.EXE, MOD1.EXEK%VDE-I-LNKSTEPDEL, link step for module [CODE]FOO.EXE deleted from databaseL%VDE-I-LNKSTEPDEL, link step for module [CODE]MOD1.EXE deleted from database>%VDE-I-COMMIT, database transaction has successfully committedVDEä      



GThis command deletes the dependency information for the link steps for Gmodules FOO.EXE and MOD1.EXE in the current default facility, facility CODE.