| Previous | Contents | Index |
Also see /OTHER and /SCT.
If you omit both qualifiers, VDE's behavior depends on the library attribute that is set with the /ASK_INFO_FILE or cleared with the /NOASK_INFO_FILE qualifier to the CREATE or MODIFY LIBRARY command. If this attribute is set, VDE asks you whether you want to edit an information file. If this attribute is not set, VDE queues the replacement without an information file.
For immediate replacements, VDE ignores both qualifiers and does not create an information file.
To edit an information file through VDE, you should first declare your preferred editor with the SET EDITOR command. If you do not declare an editor, VDE invokes the system default text editor.
VDE can also enter the note into the conference directly, see the /SCT qualifier for information.
Also see /FOLD and /SCT.
When specified, the /PROPAGATE qualifier causes VDE to propagate the changed module(s) only as far as the stream specified by the stream-name parameter, but not to any successors of that stream---change propagation thus stops at the specified stream.
The /NOPROPAGATE qualifier causes VDE to disable all propagate of the change beyond the current stream (the default stream or the stream specified with the /STREAM qualifier).
If you omit both qualifiers, the REPLACE command will propagate the changed modules to all successors of the current stream.
By default, neither /NOPROPOGATE nor /PROPOGATE is specified, and the module changes will propogate to all subsequent streams. The behaviour is affected by the specification of the propogation qualifier on the RESERVE command.
Of /QUEUE and /IMMEDIATE, /IMMEDIATE is the default.
This qualifier is part of the statistics collection component of VDE. Statistics collection is enabled or disabled on a library basis, using the MODIFY LIBRARY/STATISTICS command. If statistics collection is disabled, the statistics qualifiers are ignored and have no adverse effects. Certain keywords on this command require the specification of the /DEFECTS_CORRECTED or /NODEFECTS_CORRECTED qualifier.
| Change Code | Defect Count Collection | Reason For Replacement |
|---|---|---|
| BF | Yes | The replacement is a Bug Fix |
| NF | No | New Feature or Enhancement |
| PI | No | Performance Improvement |
| CS | No | Common Sources |
| CU | Yes | Code Cleanup, Retrofit, or a fix for a Regression |
| NH | No | New Hardware Support |
| FE | No | Functional Equivalence |
| OT | No | Other |
The reason-code is listed in Table 3-2, as is a brief explaination of the code, and an indication as to whether or not the number of defects is collected (see /DEFECTS_CORRECTED) for the particular reason code.
This qualifier is part of the statistics collection component of VDE. Statistics collection is enabled or disabled on a library basis, using the MODIFY LIBRARY/STATISTICS command. If statistics collection is disabled, the statistics qualifiers are ignored and have no adverse effects. Certain keywords on this command require the specification of the /DEFECTS_CORRECTED or /NODEFECTS_CORRECTED qualifier.
If statistics collection is enabled on the current library and you do not specify this qualifier, you will be prompted for the information.
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.
Queued replacements are implicitly and automatically created whenever a REPLACE is performed on a stream marked for queued replacements. For further information on explicitly creating a queued replacement, see the CREATE REPLACEMENT command.
If you specify only one username parameter, you may omit the surrounding parentheses.
If this qualifier is used, the default notes conference for the stream---SCT-stream-name---is assumed.
If this qualifier is specified, the /REMARK string is used as the title of the SCT note.
For information on the proper creation and protection of an SCT notes conference, see the Guide to Using VDE.
Also see /FOLD and /OTHER.
If you use the /SESSION qualifier, those reservations that are members of the specified reservation session are replaced. In this case, you must omit the mod-name parameters from the command.
Sessions can be manipulated via the REPLACE, RESERVE, UNRESERVE, MODIFY SESSION, MODIFY RESERVATION, CREATE MODULE, and CANCEL SESSION commands. And modules created by CREATE MODULE (on a queued-replacement stream) and reserved via RESERVE can be combined into the same session.
| #1 |
|---|
VDE„ REPLACE MOD1 /REMARK="Fixed list-update bug"
%VDE-I-FILCOPLIB, file DEV$:[MYDIR]MOD1.PAS;2 copied to library
%VDE-I-REPLACED, generation [FACIL]MOD1.PAS;8(7A1) replaced into stream V2.0
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
This example replaces the module MOD1.PAS into the current VDE library. Because no facility is specified with the command, the module is assumed to exist in the default facility, FACIL. Because no type name is specified, all source modules with name MOD1 are replaced; in this case there is only one such module, MOD1.PAS. The log messages show that the module was successfully replaced into stream V2.0.
| #2 |
|---|
VDE„ REPLACE [COPY]COPYMAIN.B32
Please supply required information for module [COPY]COPYMAIN.B32:
Enter the replacement remark: ADD THE /FUMBLE QUALIFIER
%VDE-I-FILCOPLIB, file DEV$:[MYDIR]COPYMAIN.B32;3 copied to library
%VDE-I-REPLACED, generation [COPY]COPYMAIN.B32;23(23) replaced into stream V3.0
%VDE-I-REPLACED, generation [COPY]COPYMAIN.B32;23(23) replaced into stream V3.1
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
This command replaces module COPYMAIN.B32 in facility COPY into the current library. Because the /REMARK qualifier is not specified with the command, VDE prompts for the remark before replacing the module. The log messages shows that the REPLACE command replaced the module into stream V3.0 and then propagated the new generation into stream V3.1.
| #3 |
|---|
VDE„ REPLACE/QUEUE FEE.MAR, FOO.MAR "Remark string"
%VDE-I-FILCOPSTAG, file DEV$:[MYDIR]FEE.MAR;3 copied to staging area
%VDE-I-FILCOPSTAG, file DEV$:[MYDIR]FOO.MAR;3 copied to staging area
%VDE-I-REPLQUE, module [FACIL]FEE.MAR queued for replacement SMITH-1
%VDE-I-REPLQUE, module [FACIL]FOO.MAR queued for replacement SMITH-1
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
In this example, the REPLACE command queues the replacement of modules FEE.MAR and FOO.MAR in facility FACIL. The modules are copied to a staging area that VDE manages, but they are not replaced into the VDE library and they remain reserved. The REPLACE command gives the queued replacement the generated name SMITH--1. To actually replaces the two modules, an authorized user must enter a PERFORM REPLACEMENT command for replacement SMITH--1.
Retrieves the latest generation of one or more source modules from a given development stream and marks those modules as reserved by the current user. Related reservations can be grouped and manipulated together using sessions.
RESERVE mod-name [, mod-name...] ["remark"]
mod-name
Specifies a source module in the default stream or the stream specified with the /STREAM qualifier to be reserved from the library. The module name consists of an optional facility name enclosed in square brackets, a module name, and an optional type name preceded by a period (such as [FACIL]MOD1.MAR). If you omit the facility name, source modules from the default facility are reserved. If you omit the type name, all source modules with the given module name in the given facility are reserved.You can reserve more than one module by using wildcard characters in any of the three components of the module name. The percent sign (%) in a name matches any single character in the position it occupies and the asterisk (*) matches zero or more characters in the position it occupies. VDE reserves the source modules whose names match the wildcard pattern.
You can also reserve multiple modules by specifying the name of a source group instead of a module name. Source groups are created with the CREATE GROUP command. If you specify a group name, each module that is a member of the group is reserved from the library.
"remark"
Specifies a remark string for the reservation. Specifying the remark parameter is equivalent to specifying the /REMARK qualifier after the RESERVE keyword.
The RESERVE command copies the latest generation of a module in a specified stream to your default directory (or to another location if you specified the /OUTPUT qualifier) and marks the module as "reserved" in that stream.After you have modified the module, you can return your changes to the library with the REPLACE command. Alternatively, you can cancel the reservation with the UNRESERVE command; no module modifications will be entered into the library.
Note
The module reservation will be released with the UNRESERVE command, by the REPLACE command (when queued-replacement are not enabled on the stream), or by the PERFORM REPLACE command (when queued-replacement is enabled on the stream). See the REPLACE, UNRESERVE, SHOW REPLACEMENT, and SHOW RESERVATION commands.By default, VDE does not allow you to reserve a module that is already reserved by another user (or yourself) for the same development stream. However, you can reserve an already reserved module if you specify the /OVERRIDE=CONCURRENT qualifier and the already existing reservations all allow concurrent reservations. If you do not wish to override a reservation, you can use the /QUEUE qualifier to request notification when the module becomes available for reservation.
When you reserve a generation of a module from a VDE library, the file that is placed in your directory has the same creation and revision times, record format, and record attributes as the file that was used to create the generation that you are reserving.
To reserve modules on behalf of another user, use the /USERNAME qualifier to specify the OpenVMS username of that other user. The modules are then reserved in the specified user's name. You must have the USERNAME privilege to use the /USERNAME qualifier.
For information on creating a new module, see CREATE MODULE. Depending on the queued-replacement setting of the target stream, you may need to issue a REPLACE command after CREATE MODULE; see REPLACE. The behaviour of the CREATE MODULE and the RESERVE commands are identical, save for the initial absence of the module in the library for the CREATE MODULE, and the initial presence of the module in the library for the RESERVE.
On queued-replacement streams, modules created via a CREATE MODULE and modules reserved via a RESERVE can be combined into a single replacement, and can be combined into a single reservation /SESSION.
/CONFIRM
/NOCONFIRM (default)
Controls whether VDE asks you to confirm that you want each module reserved. The /CONFIRM qualifier causes VDE to print a message for each module that you have specified asking whether you want to reserve the corresponding module generation. If you answer YES (or Y), it is reserved. If you answer NO (or N), it is not reserved. The /NOCONFIRM qualifier causes VDE to reserve each specified module without asking for confirmation./FOLD[=fold-ident]
Specifies a fold record to be cancelled when this module reservation is eventually replaced into the library. The fold-ident parameter gives the fold identifier of a fold record for the module being reserved and for the stream in which the reservation is done. When you later replace the module and VDE performs the replacement, VDE will cancel this fold record from the VDE database. You can omit the fold-ident parameter if there is only one fold record for the specified module and stream. You can use the /FOLD qualifier if you are modifying the module to satisfy an existing fold record. You can also specify the /FOLD qualifier with the REPLACE command to achieve the same effect./HISTORY[="string"]
/NOHISTORY
The /HISTORY qualifier specifies that CMS history information is to be included in the file placed in your directory. The history of the module lists the generations that preceded the current generation of the module. Each generation produces one line of history information in the output file. This line gives the CMS generation number, user name, date, time, and remark associated with the generation.The quoted string specifies the format of the history line. The quoted string must contain the characters #H or #B (lower case is allowed) and can contain other printing characters (such as comment delimiters). Each history line is formed by inserting the history information where you specify #H or #B in the history string. If you specify #H, the history information is inserted at the end of the file and if you specify #B it is inserted at the beginning of the file. To include a quotation mark in the output history string, type it twice (""). To include a number sign (#) in the output history string, type it twice (##). If the string parameter is omitted, VDE uses the module's default history string.
The /NOHISTORY qualifier specifies that history information is not to be appended to the output file placed in your directory.
If the /HISTORY and /NOHISTORY qualifiers are both omitted, the RESERVE command generates history information only if the history attribute is enabled for the module. This attribute is set with the CREATE MODULE or MODIFY MODULE command.
If the history-notes attribute for the VDE library is disabled, the RESERVE command will not generate CMS history information into the output file and will not accept the /HISTORY qualifier. See the description of the /HISTORY_NOTES qualifier to CREATE LIBRARY for more information.
/IDENTIFICATION=res-ident
Specifies a reservation identifier for the new reservation. Each reservation has a unique reservation identifier so that you can distinguish between multiple concurrent reservations of the same module by the same user. By default, the RESERVE command assigns a unique numeric identifier to each reservation, such as "1", "2", and so on. The /IDENTIFICATION qualifier overrides this default and allows you to select a reservation identifier of your choice, such as a mnemonic name. The res-ident parameter specifies the reservation identifier. It can be up to 39 characters long and must follow VDE name syntax./LOG (default)
/NOLOG
Controls whether log messages are printed after each module generation is reserved. The /LOG qualifier causes such messages to be printed and /NOLOG suppresses them. The messages indicate that the modules have been reserved and that the database transaction has successfully committed./MERGE=stream-name
/MERGE=(gen-expr)
Controls whether another generation of the module (called the merge generation) is to be merged with the generation that is being reserved (called the retrieved generation). If you specify the /MERGE qualifier with the stream-name parameter, the merge generation is the latest generation of the module in the specified stream. If you specify the /MERGE qualifier with the gen-expr parameter enclosed in parentheses, the merge generation is the generation with the specified generation expression (for example, "2A3").When you specify the /MERGE qualifier, VDE merges the lines of the retrieved generation with the lines of the merge generation and delivers the merged text as a single file to your output directory. The file that is placed in your directory has the current creation and revision times. The merge generation cannot be on the same line of descent as the retrieved generation. When there is a conflict between blocks of one or more lines, VDE includes the conflicting lines and flags the conflict.
VDE uses the callable interface to CMS to provide the merge capability. For a detailed explanation of how two generations are merged and how CMS (and therefore VDE) treats conflicts between the generations, see the CMS documentation.
/NOCONCURRENT
Specifies that the module cannot be reserved by another user while you have it reserved. You must replace or unreserve the module before others can reserve it. By default, VDE allows concurrent reservations if the module has the concurrent attribute set./NOTES[="string"]
/NONOTES
The /NOTES qualifier specifies that CMS notes are to be appended to the lines of the output file. CMS notes indicate in what module generation each source line was created.The quoted string specifies the format of the note. The quoted string can contain text (including the appropriate comment delimiter) and the characters #G or #g. The CMS generation expression of the generation in which the line first appeared in inserted where you specify #G or #g. The resulting string is appended to the end of the output line. To include a quotation mark in the output notes string, type it twice (""). To include a number sign (#) in the output notes string, type it twice (##). If the string parameter is omitted, VDE uses the module's default notes string. (You set the default notes string with the CREATE MODULE or MODIFY MODULE command.)
Previous Next Contents Index