RVDE7

VDE
VDE
Reference Manual


 q
Previous[ Contents] Index



:You must have the CRESTRM privilege to use this qualifier.*

/NOTIFY=(username [,username...])

/

/NONOTIFY[=(username [,username...])]

AThe /NOTIFY qualifier specifies a list of users to notify of all Ereplacements into the specified stream, and of all facility creation =operations. VDE appends these users to the stream's existing Fnotification list. Each username parameter gives the 9OpenVMS username or mail address of a user who should be Hnotified by mail message each time a module is replaced into the stream.

GEach username parameter can specify the username of a 5user already recorded in the VDE database, a OpenVMS Gmail address with one or more node names (such as NODE::SMITH), a mail Hforwarding alias, or a defined logical name bound to a list of users to Enotify. If you specify a logical name, keep in mind that the logical @name must be defined when it is later used to send notification Hmessages. It should thus be a group or system logical name or a logical <name that is in some other way defined for all users of the VDE library.

FThe /NONOTIFY qualifier specifies that a list of users already on the Hstream's notification list be removed from that notification list. Each ?username parameter gives the OpenVMS username Gor mail address of a user to remove from the notification list. If you ;omit the username parameters, VDE removes ,the entire notification list for the stream.

6If you specify both qualifiers, VDE removes the users Bspecified with the /NONOTIFY qualifier from the notification list =before adding the users specified with the /NOTIFY qualifier.

HIf you specify only one username parameter with either 4qualifier, you may omit the surrounding parentheses.

/OPEN



/FROZEN



/CLOSED

FSets the status of the stream to open, frozen, or permanently closed. FIf you specify the /OPEN qualifier, all users can reserve and replace Fsource modules from the stream and thereby modify the contents of the stream.

DIf you specify the /FROZEN qualifier, all users may reserve modules Bfrom the stream. However, a user must have the FROZEN privilege toHreplace modules into the stream; non-privileged users cannot change the Econtents of the stream. You can later change the status to open with Ganother MODIFY STREAM command, so the stream is not permanently frozen.

FIf you specify the /CLOSED qualifier, modules cannot be reserved from Bor replaced into the stream. This status cannot be changed with a Gsubsequent MODIFY STREAM command unless you have the UNCLOSE privilege.BUse the /CLOSED qualifier when you never want the contents of the Dstream to change again, for example, when capturing a base-level of Eyour software system or when capturing the final state of a released version of your software.

?You must have the UNCLOSE privilege to use the /OPEN or /FROZENqualifier for a closed stream.

/OWNER=username



/NOOWNER

FThe /OWNER qualifier specifies the owner of the specified stream. The ?username parameter gives the OpenVMS username Aof a user who should be recorded as the "owner" of the 9stream. VDE assigns no special meaning to the owner of a Hstream, but the SHOW STREAM command displays the owner. The owner could >thus be the person to contact with questions about the stream.

DThe /NOOWNER qualifier specifies that the stream has no owner. Both ?qualifiers remove the previous owner's ownership of the stream.

/POPULATE



/NOPOPULATE

=Specifies whether the stream is allowed to be populated with Cgenerations from another stream using the POPULATE STREAM command. B/POPULATE allows subsequent use of the POPULATE STREAM command to Fpopulate the stream and /NOPOPULATE disallows such use. You must have .the CRESTRM privilege to use these qualifiers."

/PROCESS_COUNT=proc-count

HSpecifies the default number of processes to execute build jobs for the Dstream. This parameter determines the degree of parallelism for the Dstream's build jobs. See the description of the BUILD command for a 'detailed description of this qualifier.-

/QUEUE=(queue-name [,queue-name...])

FSpecifies the default batch queues to which build jobs for the stream Gare submitted. See the description of the BUILD command for a detailed Gdescription of this qualifier and for a description of its interaction "with the /PROCESS_COUNT qualifier.

/REMARK="string"

DSpecifies a remark string for the stream. The quoted remark string, Dwhich can be up to 132 characters long, may contain any explanatory 8remark about the stream that you want stored in the VDE Gdatabase. Typically the remark describes what version or base-level of Cyour system the stream represents. This string replaces the remark Dstring from the original CREATE STREAM command or from any previous MODIFY STREAM command.

/REPLACEMENT=keyword

ESets or clears the queued-replacement attribute for Hthe stream. This attribute controls whether the REPLACE command permits Gimmediate replacements into the stream or requires queued replacements.DIf the keyword parameter is IMMEDIATE, the REPLACE Hcommand will immediately replace modules into the stream by default. If >the parameter is QUEUE, the REPLACE command will always queue Freplacements for the stream so that modules are not replaced into the Dstream until a privileged user enters a PERFORM REPLACEMENT command.,

/REVIEWER=(username [,username...])

1

/NOREVIEWER[=(username [,username...])]

EThe /REVIEWER qualifier specifies a list of reviewers for all module :replacements into the specified stream. VDE appends these 7reviewers to the stream's existing reviewer list. Each ?username parameter gives the OpenVMS username Gof a user who should review all replacements into the stream. The user <must already be recorded in the VDE database. When a module :is replaced into the stream, VDE notifies the user of the 2replacement by mail message. If the replacement isHqueued, the user should then review the queued replacement before it is =performed. If the replacement is immediate, VDE notifies the Euser of the new module generation that was created, and the user may then inspect that generation.

FThe /NOREVIEWER qualifier specifies that a list of existing reviewers Afor the specified stream be removed from the reviewer list. Each ?username parameter gives the OpenVMS username Hof a user who should be removed from the reviewer list. If you omit the =username parameters, VDE removes the entire reviewer list for the stream.

6If you specify both qualifiers, VDE removes the users Gspecified with the /NOREVIEWER qualifier from the reviewer list before 8adding the users specified with the /REVIEWER qualifier.

HIf you specify only one username parameter with either 4qualifier, you may omit the surrounding parentheses."

/STEP_DELAY=time-interval

FSpecifies the default step-delay time interval used by build jobs for :the stream. See the description of the BUILD command for a'detailed description of this qualifier.0

/SUCCESSOR=(succ-name [, succ-name...])

HSpecifies new successors to the stream being modified. A successor to a Gstream is another stream to which source changes are propagated by the EREPLACE command. Each succ-name parameter specifies Ethe name of a stream that becomes a successor to the stream given by Ethe stream-name parameter. The specified successors Hare added to the list of successors already stored in the database. You 6must have the CRESTRM privilege to use this qualifier.

/TIMEOUT=time-interval

BSpecifies the default timeout interval used by build jobs for the @stream. See the description of the BUILD command for a detailed description of this qualifier. 


Examples

 6    
#1

 
7VDEä MODIFY STREAM V3.3-FT1 /REMARK="New remark string"H%VDE-I-STRMMOD, information for stream V3.3-FT1 modified in the database>%VDE-I-COMMIT, database transaction has successfully committed


CIn this example, the user specifies a new remark string for stream EV3.3-FT1. This remark string can be retrieved with a subsequent SHOW STREAM command.

 6    
#2

 
$VDEä MODIFY STREAM/NAME=V5.3 HICKORYD%VDE-I-STRMMOD, information for stream V5.3 modified in the database>%VDE-I-COMMIT, database transaction has successfully committed


DIn this example, the name of stream HICKORY is changed to V5.3. You <must refer to the stream by this new name in all subsequent VDE commands.

 6    
#3

 
?VDEä MODIFY STREAM/CONFIRM BLVL-7/REMARK="New remark string", -=_VDEä                       BLVL-9/REMARK="New remark string"Modify stream BLVL-7 ? [No]: Y6%VDE-I-STRMMOD, stream BLVL-7 modified in the databaseModify stream BLVL-9 ? [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 stream should be Bmodified. For stream BLVL-7, the user answers Y (for YES) and the Fremark string for that stream is modified in the database, as the log Gmessage shows. For stream BLVL-9, the user answers N (for NO) and that Gstream is not modified. Hence there is no log message for that stream. FThe final log message indicates that the database transaction for the )whole command has successfully committed.


M

MODIFY USER



FModifies one or more attributes of the database record of one or more users.

+Requires CREUSR privilege.




Format

.

MODIFY USER username [, username...]




Parameter



username

@The OpenVMS username of the user whose record is to be modified 9in the current VDE library. You can modify more than one Fuser record by using wildcard characters in the username. The percent Gsign (%) in a username matches any single character in the position it Eoccupies and the asterisk (*) matches zero or more characters in the Aposition it occupies. The attributes of those user records whose 2usernames match the wildcard pattern are modified.



Qualifiers

+

/AUTH_PRIVILEGES=(priv [,priv...])

FSpecifies a new set of authorized privileges that the user is allowed Eto set with the SET PRIVILEGE command. The privilege list you create Hreplaces the user's current privilege list. Therefore, you must specify 4all authorized privileges you want the user to have.

GEach parameter to this qualifier names a single privilege. If only one 7privilege is specified, the parentheses may be omitted.

₧For a list of privileges, see Table 3-5 in SET PRIVILEGES.

/CONFIRM



/NOCONFIRM (default)

<Controls whether VDE asks you to confirm that you want each ;user record modified. The /CONFIRM qualifier causes VDE to Eprint a message for each user giving the username and asking whether Gyou want to modify the user record. If you answer YES (or Y), the user Drecord is modified. If you answer NO (or N), the user record is not <modified. The /NOCONFIRM qualifier causes VDE to modify the ,user record without asking for confirmation.*

/DEF_PRIVILEGES=(priv [,priv...])

FSpecifies the default privileges which are enabled each time the user ;starts a new VDE session. Each default privilege specified Falso becomes an authorized privilege for the user. The privilege list Fyou create replaces the user's current privilege list. Therefore, you >must specify all default privileges you want the user to have.

GEach parameter to this qualifier names a single privilege. If only one Fprivilege is specified, the parentheses may be omitted. For a list of Dthe privilege names you can specify, see the SET PRIVILEGES command.

/LOG (default)



/NOLOG

EControls whether log messages are printed after the user records are Dmodified. The /LOG qualifier causes such messages to be printed and D/NOLOG suppresses them. The messages indicate that the user records Fhave been modified and that the database transaction has successfully committed.

/NAME="string"

FSpecifies a full name for the user. The quoted name string, which can Cbe up to 40 characters long, should contain a new full name string 9(first name, middle initial, and last name) for the user.*

/NOTIFY=(username [,username...])

/

/NONOTIFY[=(username [,username...])]

HThe /NOTIFY qualifier specifies a list of users to notify each time the 7specified user replaces a module into the VDE library. 9VDE appends these users to the specified user's existing Fnotification list. Each username parameter gives the 9OpenVMS username or mail address of a user who should be Hnotified by mail message each time the specified user replaces a module into the library.

GEach username parameter can specify the username of a 5user already recorded in the VDE database, a OpenVMS Gmail address with one or more node names (such as NODE::SMITH), a mail Hforwarding alias, or a defined logical name bound to a list of users to Enotify. If you specify a logical name, keep in mind that the logical @name must be defined when it is later used to send notification Hmessages. It should thus be a group or system logical name or a logical <name that is in some other way defined for all users of the VDE library.

FThe /NONOTIFY qualifier specifies that a list of users already on the Especified user's notification list be removed from that notification Alist. Each username parameter gives the OpenVMS Cusername or mail address of a user to remove from the notification <list. If you omit the username parameters, )VDE removes the entire notification list.

6If you specify both qualifiers, VDE removes the users Bspecified with the /NONOTIFY qualifier from the notification list =before adding the users specified with the /NOTIFY qualifier.

HIf you specify only one username parameter with either 4qualifier, you may omit the surrounding parentheses.

/REMARK="string"

GSpecifies a remark string to be stored for the user. The quoted remark @string, which can be up to 132 characters long, may contain any >explanatory remark about the user that you want stored in the :VDE database. This string replaces the remark string from Bthe original CREATE USER command or from any previous MODIFY USER Bcommand. Typically the remark describes the user's affiliation or !function within the organization.,

/REVIEWER=(username [,username...])

1

/NOREVIEWER[=(username [,username...])]

FThe /REVIEWER qualifier specifies a list of reviewers for all changes 5replaced into the VDE library by the specified user. <VDE appends these reviewers to the user's existing reviewer Alist. Each username parameter gives the OpenVMS @username of a user who should review all changes created by the Aspecified user. The new reviewer must already be recorded in the =VDE database. When the specified user replaces a module into 2the VDE library, VDE notifies the reviewer of the Cchange by mail message. If the replacement is queued, the reviewer 6should then review the queued replacement before it is=performed. If the replacement is immediate, VDE notifies the Freviewer of the new module generation that was created, and he or she Gmay then inspect that generation. This qualifier can be used to set up E"buddy systems" where two users always review each other's code.

FThe /NOREVIEWER qualifier specifies that a list of existing reviewers ?for the specified user be removed from the reviewer list. Each ?username parameter gives the OpenVMS username Hof a user who should be removed from the reviewer list. If you omit the =username parameters, VDE removes the entire reviewer list for the user.

6If you specify both qualifiers, VDE removes the users Gspecified with the /NOREVIEWER qualifier from the reviewer list before 8adding the users specified with the /REVIEWER qualifier.

HIf you specify only one username parameter with either 4qualifier, you may omit the surrounding parentheses.

/USERNAME=username

@Specifies a new OpenVMS username for the user. The new username ;can be up to 12 characters long and must follow normal VDE :name syntax. If you change a username in the VDE database Fyou should also remember to have your system manager change it in the Hsystem User Authorization File. After the username is changed, you must 8refer to the user by the new name in all subsequent VDE Ecommands and the user must access the database with the new username.



Examples

 6    
#1

 
<VDEä MODIFY USER SMITH /USERNAME=BROWN /NAME="Jane S. Brown"C%VDE-I-USERMOD, information for user BROWN modified in the database>%VDE-I-COMMIT, database transaction has successfully committed


BIn this example, Jane Smith has changed her name. The MODIFY USER @command is used to enter her new OpenVMS username and full name ;string into the VDE database. Thereafter, Jane must access =the VDE library as user BROWN and she must be referred to as ;BROWN on subsequent VDE commands. The log messages confirm Dthat her user record was modified and that the database transaction successfully completed.

 6    
#2

 
AVDEä MODIFY USER DOE /REMARK="OpenVMS Documentation Supervisor" -(_VDEä       /DEF_PRIVILEGES=BUILD /NOLOGVDEä


HHere John Doe has been promoted to Documentation Supervisor. The MODIFY DUSER command changes his remark string to indicate his new role and Dreduces his default privileges to only the BUILD privilege. In this :example, the /NOLOG qualifier suppresses the log messages.


V

PERFORM REPLACEMENT



CPerforms one or more queued replacements so that the corresponding *modules are replaced into the VDE library.

,Requires PERFREP privilege.




Format

6

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




Parameter



rep-name

FThe name of a queued replacement to be performed. You can perform moreCthan one replacement at a time by using wildcard characters in the Dreplacement name. The percent sign (%) in a name matches any single Hcharacter in the position it occupies and the asterisk (*) matches zero =or more characters in the position it occupies. Those queued Breplacements whose names match the wildcard pattern are performed.



Description

FThe PERFORM REPLACEMENT command replaces the modules that are members =of a specified queued replacement into the VDE library. Once Gthis command has completed, each member module has a new generation in @the library and is no longer marked as reserved in the affected Astreams. In addition, the replacement is no longer queued in the VDE database.

FThe PERFORM REPLACEMENT command only performs those replacements that Gmatch the rep-name parameters and that belong to your ?default stream or to another stream specified with the /STREAM Fqualifier. To perform replacements belonging to more than one stream, Hyou can use wildcard characters in the stream name you specify with the /STREAM qualifier.

BThe PERFORM REPLACEMENT command is normally used by a user who is Eauthorized to determine when changed modules should be replaced into :the VDE library. Other developers reserve source modules, Fmake changes to them, and queue them for replacement with the REPLACE Hcommand. The REPLACE command queues modules for replacement (as opposed Ato replacing them immediately), if the user specifies the /QUEUE 8qualifier or if any affected development stream has the Cqueued-replacement attribute. Once a replacement is queued, it can Doptionally be reviewed using the REVIEW REPLACEMENT command and its Hsubcommands. When the authorized user decides that the modules that are %members of the queued replacement are;ready to be replaced into the VDE library, the user enters Ethe PERFORM REPLACEMENT command to actually perform the replacement. DWhen replacements are queued, it is the PERFORM REPLACEMENT command ?that actually creates new generations for the modules and that #terminates the module reservations.

FWhether you should use queued replacements or not is a policy decision9that may be different for different VDE libraries or for Fdifferent development stream within a given library. If you decide to Halways use immediate replacements, the REPLACE command will perform the Factual replacement and you do not use the PERFORM REPLACEMENT command.




Qualifiers



/CONFIRM



/NOCONFIRM (default)

<Controls whether VDE asks you to confirm that you want each <replacement performed. The /CONFIRM qualifier causes VDE to Bprint a message for each replacement asking whether you want that Ereplacement performed. If you answer YES (or Y), that replacement is Fperformed. If you answer NO (or N), the replacement is not performed. ?If you enter a replacement name with a wildcard specification, 0VDE asks you to confirm that VDE should perform Deach replacement whose name matches the wildcard specification. The 9/NOCONFIRM qualifier causes VDE to perform the specified -replacements without asking for confirmation.

/LOG (default)



/NOLOG

EControls whether log messages are printed after each replacement has Fbeen performed. The /LOG qualifier causes such messages to be printed Gand the /NOLOG qualifier suppresses them. These messages indicate that Dthe associated modules have been replaced, that the replacement has Cbeen performed, and that the database transaction has successfully committed.

/STREAM=stream-name

FSpecifies that only those replacements that belong to certain streams Ebe performed. The stream-name parameter specifies a Fstream name and can contain wildcard characters. The percent sign (%) Gin a name matches any single character in the position it occupies and Dthe asterisk (*) matches zero or more characters in the position it 6occupies. VDE performs a given replacement only if it Hbelongs to a stream whose name matches the stream-name 9parameter. If you omit this qualifier, VDE performs only 6those replacements that belong to your default stream.

HFor each replacement that matches a rep-name parameter -but does not belong to a stream matching the 6stream-name parameter, VDE prints an Cinformational message saying that the replacement is not performed.




Examples

 6    
#1

 
 VDEä PERFORM REPLACEMENT SMITH-2H%VDE-I-REPLACED, generation [FACNAM]A.REQ;9(9) replaced into stream V2.0H%VDE-I-REPLACED, generation [FACNAM]B.REQ;6(6) replaced into stream V2.0-%VDE-I-REPPERF, replacement SMITH-2 performed>%VDE-I-COMMIT, database transaction has successfully committedVDEä


CThis example performs the queued replacement SMITH--2. The PERFORM EREPLACEMENT command replaces the two modules that are members of the :replacement, A.REQ and B.REQ in facility FACNAM, into the 9VDE library. Thereafter, these two modules are no longer Areserved. The command also deletes replacement SMITH--2 from the VDE database.





 q
PreviousX Next[ Contents] Index