| Previous | Contents | Index |
This example cancels the directory template for the root directory for facility RMS. The log messages show that the template was successfully deleted from the database.
| #2 |
|---|
VDE„ CANCEL DIRECTORY/SUBDIRECTORY=ANASYM
%VDE-I-DIRDEL, directory specification [.ANA] deleted from database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
This example cancels the directory template for the subdirectory with directory symbol ANASYM. VDE deletes the subdirectory template that is used for all facilities that do not have explicit subdirectory templates.
Deletes one or more fold records from the VDE database. A fold record is a reminder that a source change should be manually "folded" into a given development stream in order to propagate the change.
CANCEL FOLD mod-name [, mod-name...]
mod-name
Specifies a module for which a fold record is to be deleted. 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 the facility name is omitted, the module is assumed to belong to the default facility. If the type name is omitted, VDE deletes fold records for all source modules with the specified module name in the given facility.You can delete fold records for 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 deletes fold records for all source modules whose names match the wildcard pattern.
A fold record is a reminder that a source change should be manually folded into a given development stream in order to propagate the change into that stream. The CANCEL FOLD command deletes each specified fold record from the VDE database. This command is a synonym for the DELETE FOLD command.
/CONFIRM
/NOCONFIRM (default)
Controls whether VDE asks you to confirm that you want each fold record deleted. The /CONFIRM qualifier causes VDE to print a message for each fold record asking whether you want that record deleted. If you answer YES (or Y), that fold record is deleted from the database. If you answer NO (or N), the fold record is not deleted. If you enter a module name with a wildcard specification, VDE asks you to confirm the deletion of fold records for each module whose name matches the wildcard specification. The /NOCONFIRM qualifier causes VDE to delete the specified fold records without asking for confirmation./IDENTIFICATION=fold-ident
Specifies the fold record to be deleted. This qualifier is required when you have multiple fold records for the same module in the same stream. The fold-ident parameter is the fold identifier of the fold record to be deleted. The fold identifier is the identifier you specified or VDE assigned when you created the fold record, usually a small integer value. Use the SHOW FOLD command to determine the fold identifier of each fold record./LOG (default)
/NOLOG
Controls whether log messages are printed after each fold record has been deleted. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate that the fold record has been deleted and that the database transaction has successfully committed./STREAM=stream-name
Specifies the development stream for which fold records should be deleted. The stream-name parameter gives the name of the stream. If this qualifier is omitted, VDE deletes fold records for the default development stream only./USERNAME=username
Specifies that fold records are to be deleted 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.
| #1 |
|---|
VDE„ CANCEL FOLD [CODE]X.FOR/IDENT=1
%VDE-I-FOLDDEL, fold record 1 for module [CODE]X.FOR has been deleted
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
This example deletes fold record 1 for module [CODE]X.FOR. The log messages confirm that the fold record has been successfully deleted.
Disables the recording of VDE input and output in a log file. Input and output logging is enabled using the SET LOG command.
CANCEL LOG
None.
None.
| #1 |
|---|
VDE„ CANCEL LOG
VDE„ SHOW LOG
No output logging
VDE„
|
The CANCEL LOG command disables input and output logging. The SHOW LOG command confirms that logging is disabled.
Disables VDE privileges for the current VDE session.
CANCEL PRIVILEGES priv [, priv...]
priv
The name of a VDE privilege to disable for the current VDE session.For a list of privileges, see Table 3-5 in SET PRIVILEGES.
The VDE privileges enabled for your current VDE session determine the VDE commands (and in some cases command qualifiers) you are allowed to use. Use the CANCEL PRIVILEGES command to disable privileges for the current VDE session. You may want to use the command to prevent accidental changes to the library database, for example.You can reestablish privileges using the SET PRIVILEGES command and you can display your current privileges using the SHOW PRIVILEGES command.
None.
| #1 |
|---|
VDE„ CANCEL PRIVILEGES FROZEN, USERNAME
VDE„ SHOW PRIVILEGES
Currently set privileges:
BUILD CREFAC CREGRP CREMOD CRESTEP RESREP
VDE„
|
The CANCEL PRIVILEGES command disables the FROZEN and USERNAME privileges. THE SHOW PRIVILEGES command confirms that those privileges are no longer set.
This command is the negation of the PERFORM REPLACEMENT command. This command allows a project leader or other reviewer to cancel one or more accepted, queued replacements, and thus prevent these modules from being relocated into the VDE library via a PERFORM REPLACEMENT command.Requires RESREP privilege to cancel your own queued replacement. Requires PERFREP privilege to cancel another user's queued replacement.
CANCEL REPLACEMENT rep-name [, rep-name...]
rep-name
The name of a queued replacement to be cancelled. You can cancel more than one replacement at a time by using wildcard characters in the replacement 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. Those queued replacements whose names match the wildcard pattern are cancelled.
The CANCEL REPLACEMENT command is used after the module(s) in the replacement have been replaced by a user and have been accepted through the (optional) code review process supported by VDE. Cancellation prevents these modules from being moved into the VDE library. This operation is the negation of the PERFORM REPLACEMENT command.The CANCEL REPLACEMENT command cancels each specified queued replacement so that the replacement is deleted from the VDE library and is no longer eligible to be performed by the PERFORM REPLACEMENT command.
The modules belonging to the cancelled replacement will remain reserved to the user that originally reserved and replaced them, and that user can later REPLACE updated modules, or can UNRESERVE the modules to entirely cancel the outstanding reservation(s). If subsequently replaced, the modules will again have to be accepted (or rejected) by the reviewers.
For information on how a queued replacement is accepted or rejected, see the ACCEPT REPLACEMENT and REJECT REPLACEMENT commands.
/CONFIRM
/NOCONFIRM (default)
Controls whether VDE asks you to confirm that you want each replacement cancelled. The /CONFIRM qualifier causes VDE to print a message for each replacement asking whether you want that replacement cancelled. If you answer YES (or Y), that replacement is cancelled. If you answer NO (or N), the replacement is not cancelled. If you enter a replacement name with a wildcard specification, VDE asks you to confirm the cancellation of each replacement whose name matches the wildcard specification. The /NOCONFIRM qualifier causes VDE to cancel the specified replacements without asking for confirmation./LOG (default)
/NOLOG
Controls whether log messages are printed after each replacement has been cancelled. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate that the replacement has been cancelled and that the database transaction has successfully committed.
| #1 |
|---|
VDE„ CANCEL REPLACEMENT SMITH-2
%VDE-I-REPCAN, replacement SMITH-2 cancelled
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
This example cancels replacement SMITH--2 so that this replacement is no longer queued in the VDE database. The modules associated with the replacement are still reserved after the replacement is cancelled.
Cancels one or more reservation sessions by deleting them from the VDE database.Requires RESREP privilege to cancel your own session. Requires PERFREP privilege to cancel another user's session.
CANCEL SESSION session-name [, session-name...]
session-name
The name of a reservation session to be cancelled. You can cancel more than one session at a time by using wildcard characters in the session 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. Those reservation sessions whose names match the wildcard pattern are cancelled.
The CANCEL SESSION command cancels each specified reservation session so that the session is deleted from the VDE database. The reservations that belonged to the session remain in the database, but no longer belong to the cancelled session.If you want to both delete a session and unreserve all modules associated with the session, use the UNRESERVE command with the /SESSION qualifier.
/CONFIRM
/NOCONFIRM (default)
Controls whether VDE asks you to confirm that you want each session cancelled. The /CONFIRM qualifier causes VDE to print a message for each session asking whether you want that session cancelled. If you answer YES (or Y), that session is cancelled. If you answer NO (or N), the session is not cancelled. If you enter a session name with a wildcard specification, VDE asks you to confirm the cancellation of each session whose name matches the wildcard specification. The /NOCONFIRM qualifier causes VDE to cancel the specified sessions without asking for confirmation./LOG (default)
/NOLOG
Controls whether log messages are printed after each session has been cancelled. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate that the session has been cancelled and that the database transaction has successfully committed.
| #1 |
|---|
VDE„ CANCEL SESSION SMITH-3
%VDE-I-SESCAN, session SMITH-3 cancelled
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
This example cancels reservation session SMITH--3 so that this session is no longer recorded in the VDE database. The modules associated with the session are still reserved after the session is cancelled.
Cancels display of command input to the terminal.
CANCEL VERIFY
None.
The CANCEL VERIFY command disables the echoing of command input to the terminal. It cancels the effect of the SET VERIFY command. The CANCEL VERIFY command normally is used to disable the echoing of input commands from command procedures.The CANCEL VERIFY and SET NOVERIFY commands are equivalent.
None.
| #1 |
|---|
VDE„ SET VERIFY
VDE„ SHOW MODULE MOD1.FOR
SHOW MODULE MOD1.FOR
Module [FACIL]MOD1.FOR
VDE„ CANCEL VERIFY
CANCEL VERIFY
VDE„ SHOW FACILITY FACIL
Facility FACIL
VDE„
|
The SET VERIFY command allows the terminal to display (echo) the command line it receives. The SHOW MODULE command is therefore echoed on the terminal before the output of the command is displayed. The CANCEL VERIFY command is also echoed but it disables the display of subsequent commands. The SHOW FACILITY command that follows is not displayed on the terminal but the output of the command is.
Compiles the specified modules using the appropriate scripts from the database.
COMPILE mod-name [, mod-name...]
mod-name
Specifies a module to be compiled. 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 no facility name is specified, the default facility is assumed. If no type name is specified, all source modules of the specified module name in the given facility are compiled.You can compile 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 compiles those modules whose names match the wildcard pattern.
The COMPILE command compiles a module the same way it is compiled in a build job. The COMPILE command retrieves the compile script for each specified module and generates a DCL command file from the script. The command then executes the command file in a subprocess. If the module compiles successfully, VDE updates the build dependency information for the compile step in the database.The COMPILE command can be used to compile a module without starting a build job. It is often used to test compile scripts. It can also be used to collect the initial dependency information for a compile step that does not yet have dependency information in the database.
The COMPILE command only operates on modules that have a generation in the current stream (the default stream or the stream specified with the /STREAM qualifier). In addition, it only operates on source modules unless you specify the type name in the mod-name parameter without wildcard characters. In other words, unless you explicitly specify a derived-module file extension, the command assumes that you only want to compile source modules.
/LOG (default)
/NOLOG
Controls whether log messages are printed after the compile step executes. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate that the compile step has completed, either successfully or with errors, and that the dependency information for the step has been updated in the VDE database./STREAM=stream-name
Specifies that the modules be compiled for the stream given by the stream-name parameter. If this qualifier is omitted, the modules are compiled for the default stream.
| #1 |
|---|
VDE„ COMPILE B.C
$ DEFINE/NOLOG SRC$ DEV$:[PROJDIR.MAIN.CODE.SRC]
$ DEFINE/NOLOG OBJ$ DEV$:[PROJDIR.MAIN.CODE.OBJ]
$ VDE FETCH [CODE]B.C/OUTPUT=SRC$:
%VDE-I-FETCHED, module generation [CODE]B.C;1(1) fetched from library
%VDE-I-OUTFILE, output file is DEV$:[PROJDIR.MAIN.CODE.SRC]B.C;
$ CC/ANA=OBJ$:/OBJECT=OBJ$: SRC$:B.C
$ VDE/DEPEND C OBJ$:B.ANA
$ !
$ SET NOVERIFY ! Successful script completion
%VDE-I-COMPSUCC, compilation of [CODE]B.C completed successfully
%VDE-I-DEPUPDATE, dependency information updated for build step
VDE„
|
This example compiles module B.C in the default facility, facility CODE. The output from the execution of the compile script is displayed on the terminal. The final log messages show that the compile step completed successfully and that its dependency information was updated in the database.
| #2 |
|---|
VDE„ COMPILE [RMS]E.B32
$ VDE FETCH [RMS]E.B32/OUTPUT=DEV$:[PROJDIR.MAIN.RMS.SRC]
%VDE-I-FETCHED, module generation [RMS]E.B32;3(2A1) fetched from library
%VDE-I-OUTFILE, output file is DEV$:[PROJDIR.MAIN.RMS.SRC]E.B32;
$ DEFINE/NOLOG SRC$ DEV$:[PROJDIR.MAIN.RMS.SRC]
$ DEFINE/NOLOG OBJ$ DEV$:[PROJDIR.MAIN.RMS.OBJ]
$ BLISS/OBJECT=OBJ$:/ANA=OBJ$: SRC$:E.B32
; 0067 2 RETRUN;
% WARN#000 ....1 L1:0067
Undeclared name: RETRUN
%BLS32-W-ENDDIAGS, Compilation completed with 1 diagnostic
$VDE$ERROR:
$ SET NOVERIFY ! Script completed with errors
%VDE-I-COMPFAIL, compilation of [RMS]E.B32 completed with errors
VDE„
|
This example compiles module [RMS]E.B32 but the compilation terminates with errors. The output of the compile step includes error messages from the compiler, and the final log message shows that the step failed. In this case, VDE does not update the database dependency information.
Converts the current VDE library to the format required by the current version of VDE.Requires MODLIB privilege if automatic conversion is disabled.
CONVERT LIBRARY
None.
When a new version of VDE is installed on your system, that new version frequently requires a different library format than the previous version. The new version may require a different database schema or new library subdirectories, for example. Because your existing VDE libraries are in the old library format, you must convert them to the new format. The CONVERT LIBRARY command performs this conversion.The VDE database in your library contains a "format version number" that tells VDE what format your library has. If the current version of VDE requires a more recent library format, the CONVERT LIBRARY command converts the library and its database to that more recent format. It then updates the format version number in the database.
Once you have converted a VDE library to a more recent format, you can no longer use older versions of VDE on that library. If you want to retain the option of going back to an older version of VDE, you should back up your library and its database before your convert them.
If you have specified the /AUTO_CONVERT qualifier with the CREATE or MODIFY LIBRARY command, VDE will automatically convert your library to the new format the first time a user accesses the library database using the new version of VDE. Automatic conversion is more convenient than using the CONVERT LIBRARY command, but does not give you the option of backing up the library before converting it. If you have specified the /NOAUTO_CONVERT qualifier with the CREATE or MODIFY LIBRARY command, you must convert the library with an explicit CONVERT LIBRARY command. See the descriptions of the CREATE LIBRARY and CONVERT LIBRARY commands for a full explanation.
None.
| #1 |
|---|
VDE„ CONVERT LIBRARY
%VDE-I-LIBCONV, library format converted for new version of VDE
VDE„
|
This command converts the current library to the format required for the new version of VDE. The log message shows that the conversion successfully completed.
| Previous | Next | Contents | Index |