| PreviousZ | Contents\ | Index |
m Use the SHOW REPLACEMENT command (see Section 2.9) to display the C status of a replacement being reviewed. For each replacement, this G command can list the reviewers and whether each reviewer has accepted, * rejected, or not reviewed the replacement.
E This chapter explains how to perform those source control operations H normally performed by release project leaders and by maintainers of the ; various VDE libraries. These operations include performing E queued replacements, inserting generations into development streams, D removing generations from streams, deleting generations, specifying > reviewers for streams and modules, and creating build streams.
E These operations are typically not performed by most developers. All 6 commands here require VSC privileges. Many of the H commands documented in this section can have serious adverse effects on a VDE library. a 5.1 Performing Queued Replacements
F If you are the project leader for a given development stream, you are G responsible for performing all replacements queued for that stream. To ? see what replacements are queued for your stream, use the SHOW q REPLACEMENT command (see Section 2.9) with the /STREAM qualifier. The G /STREAM qualifier selects those replacements that are for your stream. F You might also want to use the /FULL qualifier to display the list of G reviewers for each replacement and their votes to accept or reject it. F However, even the brief SHOW REPLACEMENT output summarizes the review D status of a replacement. You should also use the REVIEW REPLACEMENT D command to read the queuing user's information file since that file % might have information meant for you.
F Based on the advice of the reviewers and your own judgement, you must G decide whether to perform each such replacement. Once you have decided B to perform a given replacement, you do so by entering the PERFORM ! REPLACEMENT command. For example:
|
" . VSC„ PERFORM REPLACEMENT SMITH-1 /STREAM=BIRCH |
D The PERFORM REPLACEMENT command accepts a list of replacement names G separated by commas, and you can use the asterisk (*) and percent sign F (%) wildcard characters in the names. The command performs all queued @ replacements that match the wildcard patterns and belong to the specified stream or streams.
E The /STREAM qualifier specifies that replacement should be performed G only if they belong to a specified stream. The stream name can contain 4 wildcard characters, in which case VSC performs all E replacements that match both the specified replacement names and the > specified stream name. If you omit the /STREAM qualifier, VSC G performs only those specified replacements that belong to your default stream.
G Since the PERFORM REPLACEMENT command can be time-consuming, you might E want to include it in a DCL command file that you run as a batch job.
G The log messages that the command prints indicate that each module has D been replaced into the appropriate streams. If a module is replaced B into multiple streams due to change propagation, you will see one ; message per stream. Other messages tell you if VSC created ; fold records. VSC also prints an informational message for E each replacement that matches the specified replacement names but is ? not performed because it does not belong to a requested stream.
G In some unusual circumstances, you might also see a message that tells H you that a module generation did not get the same generation expression < (such as 5A1) as VSC expected when the module was reserved. D In this case, you should notify the developer since he or she might ? have used the expected generation expression as an audit trail identifier in code comments.
= VSC also includes all log messages in a mail message that it F sends to the developer who queued the reservation. The developer will H therefore see what happened during the replacement and will be aware of D any errors that arose. If errors occurred, you should work with the E developer to resolve the errors so that replacement can be performed again.
; The PERFORM REPLACEMENT requires the VSC privilege PERFREP.
t Table 5-1 lists the qualifiers for the PERFORM REPLACEMENT command " and describes their functions.
| /CONFIRM
! /NOCONFIRM | |
| N /CONFIRM asks you to confirm that you want each replacement performed. O This qualifier is particularly useful if you use wildcard characters in J the replacement name. /NOCONFIRM performs each replacement without : asking for confirmation. /NOCONFIRM is the default. | |
| /LOG
/NOLOG | |
| H Specify whether informational log messages are printed after the M replacement is performed. /LOG causes such messages to be printed and 3 /NOLOG suppresses them. /LOG is the default. | |
| * /STREAM=stream-name | |
| M Specifies that only those replacements that belong to certain streams be performed. TheF stream-name parameter specifies a stream name, I possibly containing the asterisk (*) and percent sign (%) wildcard > characters. VSC performs a given replacement only if it 0 belongs to a stream whose name matches theJ stream-name parameter. If you omit this qualifier, ? VSC performs only those replacements that belong to your default stream. L For each replacement that matches a replacement name parameter but . does not belong to a stream matching the< stream-name parameter, VSC prints an J informational message saying that the replacement was not performed. | |
> Examples
F This is an example of the output from the PERFORM REPLACEMENT command:
|
" VSC„ SET STREAM PHONEIX VSC„ PERFORM REPLACEMENT SMITH-1L %VDE-I-REPLACED, generation [FACIL]FOO.MAR;6(6) replaced into stream PHOENIXM %VDE-I-REPLACED, generation [RMS]FUMBLE.B32;2(2) replaced into stream PHOENIX - %VDE-I-REPPERF, replacement SMITH-1 performed > %VDE-I-COMMIT, database transaction has successfully committed VSC„ |
B In addition to providing automatic change propagation, the source F control system gives you a manual way to insert a change already made E to one development stream into another stream. The INSERT GENERATION A command makes an existing generation of a module into the latest F generation for a specified development stream. This command is mainly @ used to take bug fixes and other changes that have already been H replaced into some development stream and insert them into a base level D or variant stream that needs those changes to build correctly. This : command requires the VSC privilege PERFREP. The following 7 example shows how to use the INSERT GENERATION command:
|
" E VSC„ INSERT GENERATION [FACIL]MOD.TYP/STREAM=PHOENIX P-BUILD "remark" |
F You can specify a generation number for the source stream if you want D to select a generation other than the latest one. Zero and negative @ generation numbers are allowed; they specify generation numbers F relative to the latest generation for the source stream. You can also @ use the qualifier /GENERATION=gen-expr to identify the , generation by its CMS generation expression.
F If you omit both the /STREAM qualifier and the /GENERATION qualifier, & VSC prompts you for the source stream.
H The inserted generation's position in the source stream is not affected G by this command. In the previous example, the selected generation thus H winds up being the latest generation for both stream PHOENIX and stream P--BUILD.
q Table 5-2 lists the qualifiers for the INSERT GENERATION command " and describes their functions.
| /CONFIRM
! /NOCONFIRM | |
| K /CONFIRM asks you to confirm that you want each generation inserted M into the specified destination stream. This qualifier is particularly L useful if you use wildcard characters in the module name. /NOCONFIRM N inserts each generation without asking for confirmation. /NOCONFIRM is the default. | |
| + /GENERATION=gen-expr | |
| H Specifies that the module generation that has the CMS generation expression given by theI gen-expr parameter be inserted into the specified L destination stream. If this qualifier is omitted, the command selects I for insertion the generation given by the generation number on the N module-name parameter. If both this qualifier and the generation number N are omitted, the command selects the latest generation of the module in : the stream you specified with the /STREAM qualifier. | |
| /LOG
/NOLOG | |
| H Specify whether informational log messages are printed after the M generations are inserted. /LOG causes such messages to be printed and 3 /NOLOG suppresses them. /LOG is the default. | |
| * /STREAM=stream-name | |
| O Specifies that the generation should be selected from the source stream given by the M stream-name parameter. This qualifier thus determines E the interpretation of the generation number on the module-name F parameter. This qualifier is ignored if you use the /GENERATION N qualifier to select the module generation. If you omit both the /STREAM C qualifier and the /GENERATION qualifier, VSC prompts you for the source stream. | |
> Sometimes it is necessary to remove a generation from a given H development stream so that the module no longer has a latest generation C in that stream. For example, sometimes one needs to undo an INSERT H GENERATION command directed to the wrong stream. After you have removed 8 a module generation from a stream, the module no longer A "belongs" to that stream and can no longer be fetched, A reserved, or built for the stream. The REMOVE GENERATION command 0 removes a generation from a stream. For example:
|
" 0 VSC„ REMOVE GENERATION [FACIL]MOD.TYP/STREAM=FOO |
> The removed generation remains in the VDE library, and it can H still be the latest generation of the module for some other stream. The B REMOVE GENERATION command thus breaks the association between the C module generation and the specified stream but does not delete the generation.
G The REMOVE GENERATION command accepts a list of module names separated A by commas, and you can use the asterisk (*) and percent sign (%) C wildcard characters in the module names. The latest generations of D those modules that match the wildcard patterns are removed from the specified stream.
G Keep in mind that the REMOVE GENERATION command may not be the command G you actually want to use. It is not very common that you want a module H to not belong to a given stream at all; it is much more common that you E want some other generation of the module to be the latest generation B for the stream. Before you use the REMOVE GENERATION command, you E should thus make sure that INSERT GENERATION or DELETE GENERATION is not the appropriate command.
9 The REMOVE GENERATION command requires the VSC privilege PERFREP.
q Table 5-3 lists the qualifiers for the REMOVE GENERATION command " and describes their functions.
| /CONFIRM
! /NOCONFIRM | |
| O /CONFIRM asks you to confirm that you want each generation removed from N the specified stream. This qualifier is particularly useful if you use H wildcard characters in the module names. /NOCONFIRM removes each M generation without asking for confirmation. /NOCONFIRM is the default. | |
| /LOG
/NOLOG | |
| H Specify whether informational log messages are printed after the L generations are removed. /LOG causes such messages to be printed and 3 /NOLOG suppresses them. /LOG is the default. | |
| * /STREAM=stream-name | |
| M Specifies that the latest generations of the specified modules should . be removed from the stream given by theL stream-name parameter. If this qualifier is omitted, * VSC prompts you for the stream name. | |
F When it is necessary to undo a change to a module, you can delete the F latest generation of the module in a specified stream with the DELETE < GENERATION command. This command requires the VSC privilege F PERFREP. The following example shows how to use the DELETE GENERATION command:
|
" 0 VSC„ DELETE GENERATION [FACIL]MOD.TYP/STREAM=FOO |
G The DELETE GENERATION command can only delete the latest generation in C a stream; it cannot delete generations in the middle of a stream's G generation chain. The purpose of the command is only to allow a recent G bad replacement to be undone when that is necessary. Usually, however, G developers should fix bad replacements by reserving the module, fixing it, and replacing it again.
G The DELETE GENERATION command accepts a list of module names separated A by commas, and you can use the asterisk (*) and percent sign (%) C wildcard characters in the module names. The latest generations of D those modules that match the wildcard patterns are deleted from the VDE library.
q Table 5-4 lists the qualifiers for the DELETE GENERATION command " and describes their functions.
| /CONFIRM
! /NOCONFIRM | |
| O /CONFIRM asks you to confirm that you want each generation deleted from N the specified stream. This qualifier is particularly useful if you use H wildcard characters in the module names. /NOCONFIRM deletes each M generation without asking for confirmation. /NOCONFIRM is the default. | |
| /LOG
/NOLOG | |
| H Specify whether informational log messages are printed after the L generations are deleted. /LOG causes such messages to be printed and 3 /NOLOG suppresses them. /LOG is the default. | |
| * /STREAM=stream-name | |
| M Specifies that the latest generations of the specified modules should . be deleted from the stream given by theL stream-name parameter. If this qualifier is omitted, * VSC prompts you for the stream name. | |
C When a module has become obsolete, it can be marked as such in the ; VSC database using the MODIFY GENERATION/OBSOLETE command. F This command will prevent further propogation of the specified module F into any successor streams. The following sequence shows the commands 7 typically used to mark a module generation as obsolete:
|
" + VSC„ MODIFY MODULE/NOLOG [TAPE]DEVDRV.MAR - ' _VSC„ /REMARK="Old tape device driver" ) VSC„ MODIFY GENERATION [TAPE]DEVDRV.MAR - _VSC„ /NOLOG /OBSOLETE |
9 VSC allows you to specify that certain developers should G review or be notified of all changes to certain streams or modules. To D specify that a certain developer should review all changes replaced C into a certain stream, use the /REVIEWER qualifier with the MODIFY STREAM command. For example:
|
" 0 VSC„ MODIFY STREAM BIRCH /REVIEWER=(SMITH,SNURD) |
F To remove reviewers from a stream's reviewer list, you should use the @ /NOREVIEWER qualifier to the MODIFY STREAM command. For example:
|
" * VSC„ MODIFY STREAM BIRCH /NOREVIEWER=SNURD |
> VSC also allows you to specify that certain developers should E review all changes to a given module. The /REVIEWER qualifier to the A MODIFY MODULE command attaches reviewers to modules. For example:
|
" 3 VSC„ MODIFY MODULE [BAD]BADMAIN.B32 /REVIEWER=BROWN |
E In addition to specifying reviewers for streams and modules, you can E specify that certain developers be notified of all replacements to a 9 certain stream or of a certain module. VSC automatically G notifies such developers of replacements for the stream or module, but G does not add them to the reviewer lists. They can therefore not accept H or reject the replacements. This example shows how to add user BROWN to ; the list of users to notify of all changes to stream BIRCH:
|
" & VSC„ MODIFY STREAM BIRCH /NOTIFY=BROWN |
G Each parameter to the /NOTIFY qualifier can specify the user name of a 8 OpenVMS developer already recorded in the VSC database, @ an OpenVMS mail address containing one or more node names (such G as NODE::SMITH), or a logical name bound to a list of users to notify. G If you specify a logical name, keep in mind that the logical name must F be defined both when you specify it and when it is later used to send H the notification messages. The logical should thus be a group or system 8 logical name, or a mail forwarding alias in the OpenVMS VMSMAIL.DATA database.
G Similarly, the following example shows how to specify that users SMITH @ and SNURD be notified of all changes to module [BAD]BADMAIN.B32:
|
" 9 VSC„ MODIFY MODULE [BAD]BADMAIN.B32 /NOTIFY=(SMITH,SNURD) |
B To remove users from a stream's reviewer list, you should use the > /NONOTIFY qualifier to the MODIFY STREAM command. For example:
|
" ( VSC„ MODIFY STREAM BIRCH /NONOTIFY=BROWN |
> The MODIFY STREAM command requires the VSC privilege CRESTRM; MODIFY MODULE requires CREMOD.
| PreviousW | Next Z | Contents\ | Index |