| Previous[ | Contents] | Index |
;Modifies the attributes of one or more contexts in the VDE Fdatabase. The attributes of a context that you can modify include its Dname, remark, default development stream, and default facility. One Fcontext can be used to set the default stream and facility when first connecting to a VDE database.
1MODIFY CONTEXT ctx-name [, ctx-name...]
ctx-name
EThe name of an existing context whose attributes are to be modified. AYou can modify more than one context at a time by using wildcard Gcharacters in the context name. The percent sign (%) in a context 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 modified.
;A "context" specifies defaults for VDE sessions. GWhen you modify a context using the MODFY CONTEXT command, you specify Dthe name of the context, the associated development stream, and the associated facility.ETo apply the defaults associated with a context, specify the context Dname as a parameter to the SET CONTEXT command. To set a particular Fcontext as the default context for use when you issue the SET LIBRARY Bcommand, use the SET CONTEXT/DEFAULT command to mark a particular context as the default context.
*There are two kinds of contexts available:
D
=You do not need special VDE privileges to create or modify a <private context, but you must have the VDE CRECTX privilege +to create or modify a public context. WhileFa private context can have the same name as a public context, neither Etwo private contexts nor two public contexts can share the same name.- the private context is available to and only % visible to the user who created it.G
- the public context is available to all users of the current VDE library.
/ARCHITECTURE
&Under Construction.../CONFIRM
/NOCONFIRM (default)
<Controls whether VDE asks you to confirm that you want each ;context definition modified. The /CONFIRM qualifier causes <VDE to print a message for the specified context giving the Hname of the context and asking whether you want to modify that context. HIf you answer YES (or Y), the attributes are modified. If you answer NO B(or N), the attributes are not modified. The /NOCONFIRM qualifier ;causes VDE to modify the attributes of the context without asking for confirmation./FACILITY=facil-name
/NOFACILITY
FThe /FACILITY qualifier specifies that the indicated facility becomes Bthe default facility when the context is established with the SET FCONTEXT command. The default facility is the facility that is assumed Fwhen the facility name is omitted from a module name. The /NOFACILITY Aqualifier specifies that the default facility established by the context is null./LOG (default)
/NOLOG
HControls whether log messages are printed after the context definitions Hare modified. The /LOG qualifier causes such messages to be printed and ?/NOLOG suppresses them. The messages indicate that the context Edefinitions have been modified and that the database transaction has successfully committed./NAME=ctx-name
HSpecifies a new name for the context. The new context name can be up to :39 characters long and must follow VDE name syntax. After Fthe context name is changed, you must refer to the context by its new :name in all subsequent VDE commands. The old name is lost from the database./PRIVATE (default)
/PUBLIC
ESpecifies whether the context that is modified is private or public. 9The /PRIVATE qualifier causes VDE to modify your private :context by that name. The /PUBLIC qualifier causes VDE to @modify the public context by that name. You must have the CRECTX'privilege to use the /PUBLIC qualifier.1Of /PRIVATE and /PUBLIC, /PRIVATE is the default.
/REMARK="string"
DSpecifies a remark string for the context. This string replaces the Cremark string from the original CREATE CONTEXT command or from any Hprevious MODIFY CONTEXT command. The quoted remark string, which can be Hup to 132 characters long, may contain any explanatory remark about the <context that you want stored in the VDE database. Typically <the remark describes the function or purpose of the context./STREAM=stream-name
/NOSTREAM
FThe /STREAM qualifier specifies that the indicated development stream Hbecomes the default stream when the context is established with the SET DCONTEXT command. The /NOSTREAM qualifier specifies that the default *stream established by the context is null.
6
| #1 |
|---|
9VDEä MODIFY CONTEXT DEFAULT/STREAM=V2.2-BL1/FACILITY=COPYG%VDE-I-CTXMOD, information for context DEFAULT modified in the database>%VDE-I-COMMIT, database transaction has successfully committed5VDEä DEFINE/KEY KP6 "SET CONTEXT DEFAULTS" /TERMINATEVDEä [KP6]VDEä SHOW DEFAULTS0Library LIBNAME in root directory DEV$:[PROJDIR]!Default directory is DEV$:[SMITH]'Context DEFAULT (private to user SMITH) Default stream is V2.2-BL1 Default facility is COPY VDEä |
6DThe MODIFY CONTEXT command specifies stream V2.2-BL1 as the default Estream and facility COPY as the default facility for private context :DEFAULT. This context is the default at the start of each 7VDE session. The SET CONTEXT command establishes these ;defaults for the current VDE session, as the SHOW DEFAULTS command confirms.
| #2 |
|---|
/VDEä MODIFY CONTEXT/PUBLIC/FACILITY=EXEC PUBCTXF%VDE-I-CTXMOD, information for context PUBCTX modified in the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä SHOW CONTEXT PUBCTX$Context PUBCTX (public to all users) Default stream is V2.0 Default facility is EXEC VDEä |
DThe MODIFY CONTEXT command establishes facility EXEC as the default Hfacility for public context PUBCTX. The SHOW CONTEXT command shows that the change has taken effect.
=Modifies the attributes of one or more facilities in the VDE Gdatabase. The attributes of a facility you can modify are its name and remark string.
6MODIFY FACILITY facil-name [, facil-name...]
facil-name
8The name of a facility in the current VDE library whose Hattributes are to be modified. You can modify more than one facility at Fa time by using wildcard characters in the facility name. The percent @sign (%) in a facility name matches any single character in the ?position it occupies and the asterisk (*) matches zero or more 9characters in the position it occupies. VDE modifies the Fattributes of those facilities whose names match the wildcard pattern.
/CONFIRM
/NOCONFIRM (default)
<Controls whether VDE asks you to confirm that you want each 8facility modified. The /CONFIRM qualifier causes VDE to Bprint a message for the specified facility giving the name of the Bfacility and ask whether you want to modify that facility. If you Eanswer YES (or Y), the attributes are modified. If you answer NO (or EN), the attributes are not modified. The /NOCONFIRM qualifier causes <VDE to modify the attributes of the facility without asking for confirmation./DELETE
/NODELETE (default)
GSets or clears the delete attribute for the facility. AThis attribute allows the facility to be deleted with the DELETE EFACILITY command. The /DELETE qualifier sets the delete attribute so Ethat the facility can be deleted. The /NODELETE qualifier clears the Fdelete attribute so that the facility cannot be deleted without first resetting the attribute./LOG (default)
/NOLOG
=Controls whether log messages are printed after the facility Hdefinitions are modified. The /LOG qualifier causes such messages to be Cprinted and /NOLOG suppresses them. The messages indicate that the >facility definitions have been modified and that the database 'transaction has successfully committed./NAME=facil-name
GSpecifies a new name for the facility. The new facility name can be up 6to 39 characters long and must follow normal VDE name Hsyntax. After the facility name has been changed, you must refer to the =facility by its new name in all subsequent VDE commands. The #old name is lost from the database./PROPAGATE
/NOPROPAGATE
ESpecifies whether automatic change propagation is allowed by default Hfor new modules created in this facility. /PROPAGATE causes new modules @added to the facility to be marked as allowing automatic change Hpropagation when reserved and replaced. /NOPROPAGATE marks such modules Eas not allowing change propagation. When you create new modules, you Acan override these defaults with qualifiers to the CREATE MODULE command./REMARK="string"
ESpecifies a remark string for the facility. This string replaces the Dremark string from the original CREATE FACILITY command or from any Fprevious MODIFY FACILITY command. The quoted remark string, which can Gbe up to 132 characters long, may contain any explanatory remark about 7the facility that you want stored in the VDE database. HTypically the remark describes the function or contents of the facility.
6
| #1 |
|---|
7VDEä MODIFY FACILITY ACCTNG /REMARK="New remark string"G%VDE-I-FACMOD, information for facility ACCTNG modified in the database>%VDE-I-COMMIT, database transaction has successfully committed |
6EIn this example, the user specifies a new remark string for facility CACCTNG. This remark string can be retrieved with a subsequent SHOW FACILITY command.
| #2 |
|---|
+VDEä MODIFY FACILITY/NAME=ACCOUNTING ACCTNGK%VDE-I-FACMOD, information for facility ACCOUNTING modified in the database>%VDE-I-COMMIT, database transaction has successfully committed |
6GIn this example, the name of facility ACCTNG is changed to ACCOUNTING. BYou must refer to the facility by this new name in all subsequent VDE commands.
| #3 |
|---|
AVDEä MODIFY FACILITY/CONFIRM ACCTNG/REMARK="New remark string", -C_VDEä FUMBLE/REMARK="New remark string" Modify facility ACCTNG ? [No]: Y7%VDE-I-FACMOD, facility ACCTNG modified in the database Modify facility FUMBLE ? [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 facility should Gbe modified. For facility ACCTNG, the user answers Y (for YES) and the Hremark string for that facility is modified in the database, as the log Dmessage shows. For facility FUMBLE, the user answers N (for NO) and Fthat facility is not modified. Hence there is no log message for that Hfacility. The final log message indicates that the database transaction 1for the whole command has successfully committed.
>Modifies the remark string of one or more fold records in the VDE database.
.MODIFY FOLD mod-name [, mod-name...]
mod-name
BSpecifies a module for which a fold record is to be modified. The Emodule name consists of an optional facility name enclosed in square Hbrackets, a module name, and an optional type name preceded by a period G(such as [FACIL]MOD1.MAR). If the facility name is omitted, the module Bis assumed to belong to the default facility. If the type name is :omitted, VDE modifies fold records for all source modules 5with the specified module name in the given facility.GYou can modify 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 8position it occupies. VDE modifies fold records for all 6source modules whose names match the wildcard pattern.
EThe MODIFY FOLD command modifies the remark string of each specified fold record in the VDE database.
/CONFIRM
/NOCONFIRM (default)
<Controls whether VDE asks you to confirm that you want each ;fold record modified. The /CONFIRM qualifier causes VDE to Bprint a message for each fold record asking whether you want that Hrecord modified. If you answer YES (or Y), that fold record is modified Ain the database. If you answer NO (or N), the fold record is not Dmodified. If you enter a module name with a wildcard specification, =VDE asks you to confirm the modification of fold records for ?each module whose name matches the wildcard specification. The =/NOCONFIRM qualifier causes VDE to modify the specified fold (records without asking for confirmation.#/IDENTIFICATION=fold-ident
ESpecifies the fold record to be modified. 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 Eidentifier of the fold record to be modified. The fold identifier is 6the identifier you specified or VDE assigned when you Ecreated the fold record, usually a small integer value. Use the SHOW BFOLD command to determine the fold identifier of each fold record./LOG (default)
/NOLOG
EControls whether log messages are printed after each fold record has Ebeen modified. The /LOG qualifier causes such messages to be printed Gand the /NOLOG qualifier suppresses them. These messages indicate that Hthe fold record has been modified and that the database transaction has successfully committed./REMARK="string"
HSpecifies a new remark string for the fold record. This string replaces Fthe remark string from the original REPLACE or CREATE FOLD command or Gfrom any previous MODIFY FOLD command. The quoted remark string, which Ecan be up to 132 characters long, may contain any explanatory remark 6about the fold record that you want stored in the VDE Fdatabase. Typically the remark describes the purpose or contents of a 5source change to be folded into a development stream./STREAM=stream-name
BSpecifies the development stream for which fold records should be Gmodified. The stream-name parameter gives the name of <the stream. If this qualifier is omitted, VDE modifies fold 0records for the default development stream only./USERNAME=username
DSpecifies that fold records are to be modified 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ä MODIFY FOLD [CODE]X.FOR/IDENT=1/REMARK="New remark string"I%VDE-I-FOLDMOD, fold record 1 for module [CODE]X.FOR modified in database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
HThis example specifies a new remark string for fold record 1 for module <[CODE]X.FOR. The log messages show that the fold record was successfully modified.
GModifies the attributes associated with specific module generations in the VDE database.
4MODIFY GENERATION gen-spec [, gen-spec...]
gen-spec
>Specifies a module generation in a specified (or the default) Edevelopment stream whose attributes are to be modified. A 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 name1
- an optional type name preceded by a period<
- an optional generation number preceded by a semicolon
CIf you omit the facility name, module generations from the default Ffacility are modified. If you omit the type name, generations for all Emodules with the specified module name in the specified facility are Hmodified. If you omit the generation number, the most recent generation 2of the module in the specified stream is modified.
DIf you specify a zero or negative generation number, that number is Crelative to the most recent generation of the module in the stream Dspecified with 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 modifies the Dgeneration with the given CMS generation expression and ignores the =generation number on the gen-spec parameter.
HYou can modify more than one generation by using wildcard characters in Hthe facility name, module name, or type 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 Hoccupies. An asterisk (*) in place of the generation number matches all Hgenerations of a module. Those module generations whose names match the wildcard pattern are modified.
BThe MODIFY GENERATION command allows you to modify the attributes 8associated with a specific module generation in the VDE library.AAttributes that can be altered via the MODIFY GENERATION command include:
H
- The generation's remark string. This string is originally created * by the CREATE MODULE or REPLACE command.D
- The module's status in the specified development stream. This H command can be used to mark a specific generation of the module as as C obsolete in the specified development stream. An obsolete module ? remains in the VDE database since it may not be obsolete for J old streams, only for new ones. Once a module is marked as obsolete for G a given stream, that module is not carried over to any future stream * that has the given stream as its parent.A
- The module's status as the main line of descent in the the specified development stream.
/CONFIRM
/NOCONFIRM (default)
;Controls whether VDE asks you to confirm that you want the Fattributes of each generation modified. The /CONFIRM qualifier causes ;VDE to print a message for each generation giving the name Hof the generation and asking whether you want to modify the generation. GIf you answer YES (or Y), the generation's attributes are modified. If Fyou answer NO (or N), the attributes are not modified. The /NOCONFIRM 6qualifier causes VDE to modify the attributes of each +generation without asking for confirmation./GENERATION=gen-expr
GSpecifies that the generation with the CMS generation expression given Bby the gen-expr parameter be modified. When this ?qualifier is specified, the generation number specified on the /gen-spec parameter is ignored./LOG (default)
/NOLOG
BControls whether log messages are printed after the attributes of Hgenerations are modified. The /LOG qualifier causes such messages to be Cprinted and /NOLOG suppresses them. The messages indicate that the Egenerations have been modified and that the database transaction has successfully committed.!/MAIN_STREAM=stream-name
GSpecifies the stream that "owns" the main development thread Ffor the specified generation. If the generation is later reserved and 7its successor is replaced into the stream given by the Cstream-name parameter (directly or through change 2propagation), the successor generation will get a C"whole-number" CMS generation expression. If the current Egeneration has generation expression 10, for example, the generation ?created by replacing into the specified stream gets generation Eexpression 11. A replacement into any other stream gets a generation Fexpression such as 10A1 or 10B1. Similarly, if the current generation =has generation expression 5A2, the specified stream gets the ?"whole-number" successor 5A3 instead of a generation expression such as 5A2A1.:VDE automatically maintains information about what stream Downs the whole-number successor for each generation in the library. EThis information is determined by your use of the /MAIN qualifier to Ethe CREATE STREAM command. For this reason, you will seldom need the H/MAIN_STREAM qualifier to the MODIFY GENERATION command. However, there Hare exceptional cases where you may need to change what stream owns the Gwhole-number successor for a given generation, and then this qualifier lets you set that attribute.
/NOTE=note-number
EThe note-number parameter specifies the note number Gfor the (previously-entered) SCT note associated with this replacement.:VDE can also enter the note into the conference directly, 'see the /SCT qualifier for information.
/OBSOLETE
/NOOBSOLETE
DSpecifies whether the module is marked as obsolete in the specified Fdevelopment stream. The /OBSOLETE qualifier specifies that the module Dis obsolete in that stream. An obsolete module is not propagated to Cfuture streams created from that stream. The /NOOBSOLETE qualifier Cspecifies that the module is not obsolete. If neither qualifier is ;specified, the current status of the module is not changed./REMARK="string"
DSpecifies a new remark string to be stored for the generation. This Cstring replaces the generation's current remark string. The quoted Gremark string, which can be up to 132 characters long, may contain any Dexplanatory remark about the generation that you want stored in the VDE database.;The remark string is used as the title of the SCT note, if <VDE was asked to enter the SCT note by the specification of the /SCT qualifier.
/SCT=filename
HThe filename parameter specifies the name of a file to @be loaded into the SCT notes conference. This file contains the Hpreviously-edited text of an SCT entry for the SCT note associated with this replacement.@If this qualifier is used, the default notes conference for the /stream---SCT-stream-name---is assumed.
HIf this qualifier is specified, the /REMARK string is used as the title of the SCT note.
FFor information on the proper creation and protection of an SCT notes 0conference, see the Guide to Using VDE.
Also see /FOLD and /OTHER.
/STREAM=stream-name
CSpecifies that generations for the development stream given by the Hstream-name parameter be modified. This qualifier thus Baffects the interpretation of generation numbers on the command's Cgen-spec parameter. If this qualifier is omitted, <VDE modifies generations for the default development stream.
6
| #1 |
|---|
CVDEä MODIFY GENERATION [FACIL]MODNAM.C;5/REMARK="New remark string"K%VDE-I-GENMOD, information for generation [FACIL]MODNAM.C;5 modified in the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
6GThis example changes the remark string associated with generation 5 of Emodule MODNAM.C in facility FACIL. The log messages confirm that the =attributes of the module were modified and that the database #transaction successfully completed.
| #2 |
|---|
+VDEä MODIFY GENERATION MODNAM.MAR /OBSOLETEK%VDE-I-GENMOD, information for generation [RMS]MODNAM.MAR;6 modified in the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
AThis example illustrates how to mark a module as obsolete in the Cdefault stream. The module will be dropped from all future streams Edescended from the default stream, but will remain accessible in the default stream.
| PreviousX | Next[ | Contents] | Index |