| Previous | Contents | Index |
Copies the specified modules using the appropriate scripts from the database.
COPY mod-name [, mod-name...]
mod-name
Specifies a module to be copied using a copy script. The module name consist of an optional facility name enclosed in square brackets, a module name, and an optional type name preceded by a period, such as [FACIL]MOD2.H. If no facility name is specified, the default facility is assumed. If no type name is specified, all modules of the specified module name in the given facility are copied.You can copy 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 copies those modules whose names match the wildcard pattern.
The COPY command copies a module the same way it is copied in a build job. The COPY command retrieves the copy script for each specified module and generates a DCL command file from the script. The command then executes the command file in a subprocess.A copy step moves a module into the directory or other location where other build steps later expect to find it. For example, copy steps move INCLUDE files from delta files into clear-copy files in the subdirectories where other build steps will later access them. Unlike a compile or link step, a copy step does not transform one set of modules into a different set of modules; it only copies a single module from one form or location to another.
The COPY command can be used to perform a copy step without starting a build job. It is often used to test copy scripts.
The COPY 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 copy source modules.
/LOG (default)
/NOLOG
Controls whether log messages are printed after the copy step executes. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate that the copy step has completed, either successfully or with errors, and that the dependency information for the step has not been updated in the VDE database. (Copy steps do not normally update dependency information since the only input and output to the step is the module being copied.)/STREAM=stream-name
Specifies that the modules be copied for the stream given by the stream-name parameter. If this qualifier is omitted, the modules are copied for the default stream.
| #1 |
|---|
VDE„ COPY [CODE]A.REQ
$ VDE FETCH [CODE]A.REQ/OUTPUT=DEV$:[PROJDIR.MAIN.CODE.SRC]
%VDE-I-FETCHED, module generation [CODE]A.REQ;1(1) fetched from library
%VDE-I-OUTFILE, output file is DEV$:[PROJDIR.MAIN.CODE.SRC]A.REQ;
$ !
$ SET NOVERIFY ! Successful script completion
%VDE-I-COPYSUCC, copy of [CODE]A.REQ completed successfully
%VDE-I-DEPNOTUPDATE, dependency information not updated for build step
VDE„
|
This example performs the copy action for module [CODE]A.REQ. The copy script fetches the latest generation for module A.REQ from its delta file and leaves it in clear-copy form in the [.SRC] subdirectory for facility CODE and the default development stream. There it is available to future compile steps. The output from the copy script is displayed on the terminal as shown. The final log messages show that the copy step completed successfully and that its dependency information was not updated in the database.
Defines one or more architecture table entries in the VDE database. Each architecture table entry...Requires the CREARCH privilege.
ARCHITECTURE support is not fully implemented.
An architecture is a construct that encompasses one or more facilities, and allows modules to exist in a "common" or "default" facility, and zero or more architecture specific facilities. In must the same fashion as the SYS$SYSROOT: logical name allows one to support both system-specific and cluster-common files, an architecture allows one to support architecture-specific and architecture-common modules.
CREATE ARCHITECTURE arch-name [, arch-name...]
arch-name
The name of the architecture to be created. This name may be up to 39 characters long and must follow VDE name syntax.
Under Construction...
/DEFER (default)
/NODEFER
Under Construction.../DELETE (default)
/NODELETE
Under Construction.../LOG (default)
/NOLOG
Under Construction.../PRIVATE (default)
/PUBLIC
Under Construction.../REMARK="string"
Specifies a remark string to be stored for the new architecture. The quoted remark string, which can be up to 132 characters long, may contain any explanatory remark about the architecture. that you want stored in the VDE database. Typically the remark describes the function or purpose of the architecture.
| #1 |
|---|
VDE„ CREATE ARCHITECTURE VAXPDP/REMARK="Version n"
VDE„
|
Under Construction...
Defines one or more contexts in the VDE database. Each context can be used to specify the default development stream, default architecture and default facility for a VDE session, and one context can be used to set the default stream and facility when first connecting to a VDE database.
CREATE CONTEXT ctx-name [, ctx-name...]
ctx-name
The name of the context to be created. This name may be up to 39 characters long and must follow VDE name syntax.
A "context" specifies defaults for VDE sessions. When you create a context using the CREATE CONTEXT command, you specify the name of the context, the associated development stream, and the associated facility.To apply the defaults associated with a context, specify the context name as a parameter to the SET CONTEXT command. To set a particular context as the default context for use when you issue the SET LIBRARY command, use the SET CONTEXT/DEFAULT command to mark a particular context as the default context.
There are two kinds of contexts available:
You do not need special VDE privileges to create a private context, but you must have the VDE CRECTX privilege to create a public context. While a private context can have the same name as a public context, neither two 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.
- the public context is available to all users of the current VDE library.
/ARCHITECTURE
Under Construction.../FACILITY=facil-name
/NOFACILITY
The /FACILITY qualifier specifies the default facility for a context established with the SET CONTEXT command. The default facility is the facility that is assumed when the facility name is omitted from a module name. The /NOFACILITY qualifier specifies that the default facility established by the context is null. If you omit both qualifiers, the current default facility becomes the facility associated with the new context./LOG (default)
/NOLOG
Controls whether log messages are printed after a new context is created. The /LOG qualifier causes the messages to be printed and the /NOLOG qualifier suppresses them. The messages indicate that each new context has been created and that the database transaction has successfully committed./PRIVATE (default)
/PUBLIC
Specifies whether a private or a public context is created. The /PRIVATE qualifier causes VDE to create a context that is private to you. The /PUBLIC qualifier causes VDE to create a context that is available to all users of the library. You must have the CRECTX privilege to use the /PUBLIC qualifier.Of /PRIVATE and /PUBLIC, the former is the default.
/REMARK="string"
Specifies a remark string to be stored for the new context. The quoted remark string, which can be up to 132 characters long, may contain any explanatory remark about the new context that you want stored in the VDE database. Typically the remark describes the function or purpose of the context./STREAM=stream-name
/NOSTREAM
The /STREAM qualifier specifies that the indicated development stream becomes the default stream when the context is established with the SET CONTEXT command. The /NOSTREAM qualifier specifies that the default stream established by the context is null. If you omit both qualifiers, the current default stream becomes the stream associated with the new context.
| #1 |
|---|
VDE„ CREATE CONTEXT NEWCTX/STREAM=V2.0/FACILITY=RMS/REMARK="Version 2"
%VDE-I-CTXADDED, context NEWCTX added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„ SHOW CONTEXT NEWCTX
Context NEWCTX (private to user SMITH)
Default stream is V2.0
Default facility is RMS
VDE„
|
This example creates a private context NEWCTX in which the default stream is V2.0 and the default facility is RMS. The SHOW CONTEXT command displays the context settings associated with the new context.
| #2 |
|---|
VDE„ CREATE CONTEXT PUBCTX/PUBLIC/STREAM=V3.3-2FT/FACILITY=RMS
%VDE-I-CTXADDED, context PUBCTX added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
In this example, the CREATE CONTEXT command creates a public context PUBCTX available to all users. When this context is specified on a SET CONTEXT command, the default stream is set to V3.3-2FT and the default facility is set to RMS.
Creates the disk directory tree for the VDE library's delta files, for the default development stream, or for a specified facility.
CREATE DIRECTORY_TREE
The CREATE DIRECTORY_TREE command creates the directory tree on disk for a VDE library's delta files, for a development stream, or for a facility. You use the CREATE DIRECTORY_TREE command only if you deferred directory creation by using the /DEFER qualifier on a CREATE LIBRARY, CREATE STREAM, or CREATE FACILITY command. The /DEFER qualifier prevents these three commands from creating the disk directories they normally would create. You then have the opportunity to override the normal directory-creation rules within the SET DIRECTORY commands. After entering your SET DIRECTORY commands, you enter the CREATE DIRECTORY_TREE command to create disk directories according to the rules you specified with your SET DIRECTORY commands.Directories are created using the protection setting of the parent directory for the UIC group and world access, any applicable ACE entries from the parent directory, and allowing full system and owner access.
/BRIEF (default)
/FULL
Determines how many log messages are displayed when VDE creates new disk directories. The /BRIEF qualifier only displays log messages for the stream or delta-file root directory and for each facility root directory. The /FULL qualifier displays a log message for every directory VDE creates, including all facility subdirectories. (The facility subdirectories are the most numerous directories.) These qualifiers have no effect if you use the /NOLOG qualifier.Of /BRIEF and /FULL, the former is the default.
/DELTA_FILES
/STAGING
/STREAM (default)
Determines whether directories are created for the VDE library's delta files, for its staging areas, or for the default development stream. The /DELTA_FILES qualifier specifies that disk directories be created for the VDE library's delta files. These are the directories that hold CMS libraries. The /STAGING qualifier specifies that the root directory be created for the library's staging directories. Staging directories are temporary holding areas for files that are replaced into the library with queued replacements. The /STREAM qualifier specifies that disk directories be created for the default development stream.If you specify the /DELTA_FILES qualifier but not the /FROM_CMS_LIBRARY qualifier, VDE creates the CMS library for each facility affected by this command. If you specify the /STREAM qualifier, VDE runs the default stream's new-stream script for each facility affected by this command, provided such a script is defined. Depending on how it is defined, this script may populate the stream's facility-specific directories with source modules and other files.
Of /DELTA_FILES, /STAGING and /STREAM, the latter is the default.
/FACILITY=fac-name
Specifies that disk directories be created only for the facility specified by the fac-name parameter. If this qualifier is omitted, directories are created for all facilities, either for delta files or for the default stream.You can create directory trees for multiple facilities by using wildcard characters in the fac-name parameter. 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 creates directory trees for those facilities whose names match the wildcard pattern.
/FROM_CMS_LIBRARY[=date-time]
Specifies that the delta-file root directory for each facility covered by the current CREATE DIRECTORY_TREE command already contains a CMS library and that VDE should enter all modules and module generations present in that CMS library into the current VDE database. This qualifier, which VDE also accepts on the CREATE FACILITY command, gives you a way to automatically populate a VDE library with modules from an existing CMS library.If you specify the optional date-time parameter, VDE additionally retrieves all reservations from the CMS library that were created since the date and time given by that parameter. VDE prints warning messages for any reservations created earlier than this time and for any reservations whose stream (CMS class) cannot be ascertained. If you omit the date-time parameter, VDE does not retrieve reservations from the CMS library, only modules and generations.
If this qualifier is omitted, VDE creates a new CMS library in each delta-file facility root directory it creates. This qualifier has no effect unless you also use the /DELTA_FILES qualifier.
If this qualifer is specified, all VDE streams must be created prior to issuing this command, and these stream names must match (a subset of) the CMS class names in use in the CMS libraries; these stream names must match the CMS classes to be uploaded from within the CMS library. In order to correctly establish the main and variant lines of descent and the correct CMS generation number sequence, all streams involved must be created with the appropriate /MAIN, /NOMAIN, /PARENT and /SUCCESSOR settings.
/LOG (default)
/NOLOG
Controls whether log messages are printed when disk directories are created. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate the names of the disk directories that VDE creates. The /BRIEF and /FULL qualifiers control how many log messages are printed.
| #1 |
|---|
VDE„ CREATE LIBRARY/DEFER
Enter the name you want for the new library: LIBNAME
Enter directory specification for the new library: [PROJDIR]
Enter your full name (first and last names): Zrebhasha Fulkutznodoy
Enter the remark for new library: Library for the mumble project
Library LIBNAME to be created in root directory [PROJDIR]
Library root directory DEV$:[PROJDIR] has been created.
Logical name VDE$LIBRARY now points to the new library.
Creating library database; please wait...
Library database has been created.
Library creation completed.
VDE„ SHOW LOCATION
Directory locations for stream MAIN:
Stream root directory is not recorded in database
VDE„ SHOW LOCATION/DELTA_FILES
Directory locations for delta files:
Delta-file root directory is not recorded in database
|
In this example, the /DEFER qualifier to the CREATE LIBRARY command prevents disk directories from being created for the library's delta files and its default stream MAIN. The CREATE LIBRARY command only creates the library root directory DEV$:[PROJDIR], where it also creates the VDE database. The SHOW LOCATION commands confirm that no other directories are recorded in the VDE database.
| #2 |
|---|
VDE„ SET DIRECTORY/DELTA_FILES [PROJDIR]
%VDE-I-DIRADDED, directory specification [PROJDIR] added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„ SET DIRECTORY/STREAM DISK2:[MAIN_DIR]
%VDE-I-DIRADDED, directory specification DISK2:[MAIN_DIR] added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
A SET DIRECTORY command then specifies that the root directory for the library's delta files (its CMS libraries) should be directory [PROJDIR]. The normal rule used within VDE is to make directory DEV$:[PROJDIR.VDE$CMS] the delta-file root directory and to make subdirectories within that directory contain the CMS libraries for individual facilities. A second SET DIRECTORY command specifies that the root directory for stream MAIN is directory DISK2:[MAIN_DIR]. VDE typically makes the directory DEV$:[PROJDIR.MAIN] the root directory for stream MAIN. In this case, the user wants stream MAIN's whole directory tree on a separate disk.
This sequence sets up the library for the following commands:
| #3 |
|---|
VDE„ CREATE DIRECTORY_TREE/DELTA_FILES
Creating directory tree for delta files:
Root directory WORK4:[PROJDIR] already exists
Facility CODE root directory DEV$:[PROJDIR.CODE] has been created
CMS library for facility CODE has been created
All directories for delta files now exist
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
VDE„ CREATE DIRECTORY_TREE/STREAM
Creating directory tree for stream MAIN:
Root directory DISK2:[MAIN_DIR] has been created
Facility CODE root directory DISK2:[MAIN_DIR.CODE] has been created
All directories for stream MAIN now exist
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
VDE„ SHOW LOCATION/DELTA_FILES
Directory locations for delta files:
Delta-file root directory: DEV$:[PROJDIR]
Directory locations for facility CODE:
Root directory: DEV$:[PROJDIR.CODE]
VDE„ SHOW LOCATION/STREAM
Directory locations for stream MAIN:
Stream root directory: DISK2:[MAIN_DIR]
Subdirectory: DISK2:[MAIN_DIR.VDE$BLD] (symbol VDE$BLD)
Directory locations for facility CODE:
Root directory: DISK2:[MAIN_DIR.CODE]
Subdirectory: DISK2:[MAIN_DIR.CODE.OBJ] (symbol OBJ)
Subdirectory: DISK2:[MAIN_DIR.CODE.SRC] (symbol SRC)
Subdirectory: DISK2:[MAIN_DIR.CODE.VDE$COM] (symbol VDE$COM)
Subdirectory: DISK2:[MAIN_DIR.CODE.VDE$LOG] (symbol VDE$LOG)
VDE„
|
This section shows the results of two CREATE DIRECTORY_TREE commands. The first one creates the directory tree for the library's delta files and create the CMS library for facility CODE in that directory tree. The second command creates the directory tree for stream MAIN. As the log messages show, the directory tree begins with root directory DISK2:[MAIN_DIR] as requested. The subsequent SHOW LOCATION commands confirm that all disk directories have been created in the desired locations.
| #4 |
|---|
VDE„ CREATE FACILITY/DEFER NEWFACIL
Please supply required information for facility NEWFACIL:
Enter a remark for the new facility: New facility
%VDE-I-FACADDED, facility NEWFACIL added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
VDE„ SET DIRECTORY/FACILITY=NEWFACIL [PROJDIR.NEW]
%VDE-I-DIRADDED, directory specification [PROJDIR.NEW] added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
VDE„ CREATE DIRECTORY_TREE/FULL/FACILITY=NEWFACIL/DELTA_FILES
Creating directory tree for delta files:
Facility NEWFACIL root directory DEV$:[PROJDIR.NEWFACIL] has been created
CMS library for facility NEWFACIL has been created
All directories for delta files now exist
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
VDE„ CREATE DIRECTORY_TREE/FULL/FACILITY=NEWFACIL
Creating directory tree for stream MAIN:
Facility NEWFACIL root directory DEV$:[PROJDIR.NEW] has been created
Subdirectory DEV$:[PROJDIR.NEW.OBJ] has been created
Subdirectory DEV$:[PROJDIR.NEW.SRC] has been created
Subdirectory DEV$:[PROJDIR.NEW.VDE$COM] has been created
Subdirectory DEV$:[PROJDIR.NEW.VDE$LOG] has been created
All directories for stream MAIN now exist
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
In this example, the CREATE FACILITY command creates a new facility NEWFACIL, but defers the creation of disk directories for that facility. A SET DIRECTORY command then specifies that directory [PROJDIR.NEW] should be the facility root directory for the default stream MAIN. Two CREATE DIRECTORY_TREE commands follow. The first one creates the delta-file root directory and CMS library for the facility. The second one creates the default stream's directory tree for the facility. This directory tree consists of a facility root directory and four facility subdirectories. The /FULL qualifier causes VDE to prints log messages for all directories it creates for the facility; without this qualifier, VDE omits the subdirectory log messages.
| #5 |
|---|
VDE„ CREATE STREAM V2.0/DEFER
Please supply required information for stream V2.0:
Enter a remark for the new stream: Version 2.0
%VDE-I-STRMADDED, stream V2.0 added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
VDE„ SET STREAM V2.0
VDE„ SHOW LOCATION/STREAM
Directory locations for stream V2.0:
Stream root directory is not recorded in database
VDE„ SET DIRECTORY/STREAM [PROJDIR.VER_2]
%VDE-I-DIRADDED, directory specification [PROJDIR.VER_2] added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
VDE„ CREATE DIRECTORY_TREE/STREAM
Creating directory tree for stream V2.0:
Root directory DEV$:[PROJDIR.VER_2] has been created
Facility CODE root directory DEV$:[PROJDIR.VER_2.CODE] has been created
Facility SPEC root directory DEV$:[PROJDIR.VER_2.SPEC] has been created
Facility TOOL root directory DEV$:[PROJDIR.VER_2.TOOL] has been created
All directories for stream V2.0 now exist
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
|
The CREATE STREAM command creates a new stream called V2.0, but defers creating the disk directory tree for that stream. The SET STREAM command makes V2.0 the default stream, and the SHOW LOCATION command shows that no directories are recorded in the VDE database for that stream. The SET DIRECTORY command specifies that directory [PROJDIR.VER_2] should be the root directory for the stream. The CREATE DIRECTORY_TREE command creates the full directory tree for stream V2.0. This directory tree includes the stream root directory specified by the SET DIRECTORY command, a facility root directory for each facility in the system, and several facility subdirectories for each facility. Because the /FULL qualifier is not specified, VDE only prints log messages for the stream and facility root directories, and not for the facility subdirectories.
| Previous | Next | Contents | Index |