| Previous[ | Contents] | Index |
FCreates a new facility definition and its associated disk directories in the current VDE library.
6CREATE FACILITY facil-name [, facil-name...]
facil-name
FThe name of the new facility to be created. This name can be up to 39 0characters long and must follow VDE name syntax.=VDE prohibits the creation of any facilities with names that Gbegin with the character sequences "VDE$", "VSC$", =and "VTSC$", as these prefixes are used within VDE.
9A facility is the highest level of organization in a VDE Flibrary and identifies a set of related modules. For example, the RMS Cfacility is composed of all the modules needed to build the Record <Management Services portion of the OpenVMS operating system.CAll modules within a given facility must have unique names; no two Fmodules in the same facility can have the same module name and module Htype. If, however, two modules belong to different facilities, they can #have the same module name and type.
;The VDE library stores modules from separate facilities in Hseparate disk directories. Therefore, you may want to create a separate Ffacility for each component of your software system that is developed independently.
FWhen you create a facility, the CREATE FACILITY command first creates ;an entry for the new facility in the VDE database. It then Ccreates a disk directory to hold the delta files of the facility's %source modules. VDE uses callable CMS9to create a CMS library in that directory. When you later=create source modules in the facility, VDE uses callable CMS @to create delta files for those modules. A delta file (which is Fidentical to a CMS "element") contains all past and present 2versions of your source file in a compressed form.
DThe CREATE FACILITY command also creates a disk directory structure C(directory tree) for the new facility for the default stream. This Gdirectory structure is repeated for all streams that are successors of Ethe default stream. These directories will hold all files associated ?with the facility that are stream-specific. Such files include Dclear-copy source files, object files, object libraries, executable 6images, and other derived files. For each stream, this0structure consists of the following directories:
H
- a facility root directory, which is a subdirectory of the stream root directoryG
- several facility subdirectories that will contain source files, H derived files, build log files, and certain other kinds of files. The G subdirectories that are created depend on the SET DIRECTORY commands ( you have used as well as VDE defaults.
DIf the default disk directory structure is not suitable for the new @facility, you can defer its creation until you have defined the Fstructure you want. To defer creation of the directory structure, use Gthe /DEFER qualifier. Then use the SET DIRECTORY command to define the Edirectory structure you want. Finally, use the CREATE DIRECTORY_TREE 2command to create the desired directory structure.
/DEFER
/NODEFER (default)
GSpecifies whether the creation of the disk directory structure for the Anew facility should be postponed. The /DEFER qualifier postpones Dcreation of the disk directory structure and the /NODEFER qualifier Bcauses the directory structure to be created immediately. Use the G/DEFER qualifier when the default directory structure is inappropriate for the new facility.CIf the /NODEFER qualifier is specified (or /DEFER is omitted), the GCREATE FACILITY command first creates the delta-file directory for the <facility and creates a CMS library within that directory. ItFthen creates the facility root directory for the default stream. Next Git creates the facility subdirectories within that root directory. The Dsubdirectories that are created are determined by the SET DIRECTORY @commands entered for the stream and by the default rules of the 9VDE utility. Once the directory structure exists, source >modules and other files can be added to the new facility. The Bdirectory-creation sequence is repeated for all successors of the default stream.
GIf the /DEFER qualifier is specified, the CREATE FACILITY command does Bnot create the delta-file directory, nor the stream-specific root Hdirectories, nor the associated subdirectories. You can therefore enter HSET DIRECTORY commands to specify the disk directories you want created Dfor the facility. You then use the CREATE DIRECTORY_TREE command to Hcreate the directory structure on disk according to the rules specified /by the SET DIRECTORY commands and VDE defaults.
/DELETE
/NODELETE
FControls whether the delete attribute is set for the Hnew facility. This attribute allows the facility to be deleted with the ?DELETE FACILITY command. The /DELETE qualifier sets the delete Aattribute so that the new facility can be deleted. The /NODELETE Fqualifier clears the delete attribute so that the new facility cannot Hbe deleted unless you first reset this attribute with a MODIFY FACILITY <command. Marking a facility as /NODELETE makes it harder to !accidentally delete the facility.>If this qualifier is not specified, VDE uses the value of the Eallow-deletion library attribute. The library allow-deletion default Fattribute can be set or reset by using the /ALLOW_DELETE qualifier on 4the CREATE LIBRARY or on the MODIFY LIBRARY command.&
/FROM_CMS_LIBRARY[=date-time]
BSpecifies that the delta-file root directory for the new facility =already contains a CMS library and that VDE should enter all modules and module=generations present in that CMS library into the current VDE Edatabase. This qualifier gives you a way to automatically populate a :VDE library with modules from an existing CMS library. If <this qualifier is omitted, VDE creates a new CMS library in )the facility's delta-file root directory.BIf you specify the optional date-time parameter, 9VDE 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 Ecreated earlier than this time and for any reservations whose stream 3(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.
GThis qualifier has no effect if you also specify the /DEFER qualifier. DIf you defer directory creation, you must use the /FROM_CMS_LIBRARY Equalifier on the CREATE DIRECTORY_TREE command that actually creates 0the delta-file directories for the new facility.
=If this qualifer is specified, all VDE streams must Dbe created prior to issuing this command, and these stream Enames must match (a subset of) the CMS class names in use in the CMS Hlibraries; these stream names must match the CMS classes to be uploaded Ffrom within the CMS library. In order to correctly establish the main Cand variant lines of descent and the correct CMS generation number Dsequence, all streams involved must be created with the appropriate 0/MAIN, /NOMAIN, /PARENT and /SUCCESSOR settings.
/LOG (default)
/NOLOG
GControls whether log messages are printed after the new facilities are Fcreated. The /LOG qualifier causes the messages to be printed and the F/NOLOG qualifier suppresses them. The messages indicate that each new Gfacility has been created, that its CMS library has been created, that >its disk directories have been created, and that the database 'transaction has successfully committed./PROPAGATE (default)
/NOPROPAGATE
ESpecifies whether automatic change propagation is allowed by default Hfor new modules created in this facility. /PROPAGATE causes new modules @added to the facility to be marked as allowing automatic change Hpropagation when reserved and replaced. /NOPROPAGATE marks such modules Eas not allowing change propagation. When you create new modules, you Acan override these defaults with qualifiers to the CREATE MODULE command./REMARK="string"
HSpecifies a remark string to be stored for the new facility. The quoted Gremark string, which can be up to 132 characters long, may contain any Fexplanatory remark about the new facility that you want stored in the =VDE database. Typically the remark describes the function or contents of the facility.EAlthough this qualifier is required, you can specify an empty remark 9string. If you do not specify the /REMARK qualifier, VDE prompts you for a remark string.
6
| #1 |
|---|
9VDEä CREATE FACILITY ACCTNG /REMARK="Accounting function"(Creating directory tree for delta files:P Facility ACCTNG root directory DEV$:[PROJDIR.VDE$CMS.ACCTNG] has been created6 CMS library for facility ACCTNG has been created, All directories for delta files now exist (Creating directory tree for stream MAIN:M Facility ACCTNG root directory DEV$:[PROJDIR.MAIN.ACCTNG] has been createdB Subdirectory DEV$:[PROJDIR.MAIN.ACCTNG.OBJ] has been createdB Subdirectory DEV$:[PROJDIR.MAIN.ACCTNG.SRC] has been createdF Subdirectory DEV$:[PROJDIR.MAIN.ACCTNG.VDE$COM] has been createdF Subdirectory DEV$:[PROJDIR.MAIN.ACCTNG.VDE$LOG] has been created, All directories for stream MAIN now exist 6%VDE-I-FACADDED, facility ACCTNG added to the database>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
EThis example creates a new facility called ACCTNG. The remark string Dindicates that this facility performs an accounting function in the Fuser's software system. The log messages indicate that the delta-file =disk directory has been created, that a CMS library has been Bestablished in that directory, that a facility root directory and Gvarious facility subdirectories have been created for stream MAIN, and 9that the facility was successfully added to the database.
=Creates a new fold record in the VDE database. A fold record 6is a reminder that a source change should be manually ?"folded" into a given development stream in order to propagate the change.
.CREATE FOLD mod-name [, mod-name...]
mod-name
HSpecifies a module for which a fold record is to be created. The module Hname consists of an optional facility name enclosed in square brackets, Ga module name, and an optional type name preceded by a period (such as A[FACIL]MOD1.MAR). If the facility name is omitted, the module is Hassumed to belong to the default facility. If the type name is omitted, 9VDE creates fold records for all source modules with the ,specified module name in the given facility.GYou can create fold records for more than one module by using wildcard Bcharacters in any of the three components of the module name. The Hpercent sign (%) in a name matches any single character in the position Hit occupies and the asterisk (*) matches zero or more characters in the >position it occupies. VDE creates fold records for the source /modules whose names match the wildcard pattern.
=A fold record is a record in the VDE database that reminds a Guser to manually "fold" a source change from one development Bstream into another. A fold record is created when the REPLACE or GPERFORM REPLACEMENT command attempts to propagate a source change from Ga given development stream to one of its successors, but finds that it Hcannot automatically propagate the change because the source module has Ealready diverged between the two streams. The user must then reserve Gthe module in the successor stream, manually edit the change into that Ggeneration of the module, and then replace it. This operation is known Fas "folding" the change into the successor stream. Once the Efold operation has been performed, its fold record should be deleted >from the VDE database with the /FOLD qualifier to the REPLACE (command or with the CANCEL FOLD command.GThe CREATE FOLD command lets you manually enter a fold record into the 9VDE database. This fold record and its remark string can Fserve as a reminder to perform some action on a specified module in a Fspecified stream. Once you have performed this action, you can delete Bthe fold record with the CANCEL FOLD command. The new fold record >records that some change should be propagated from the latest Egeneration of the specified module in the default development stream 1into another development stream that you specify.
/CONFIRM
/NOCONFIRM (default)
>Controls whether VDE asks you to confirm that you want a fold >record created for each module. The /CONFIRM qualifier causes :VDE to print a message for each module asking whether you Hwant to create a fold record for that module. If you answer YES (or Y), ;VDE creates a fold record for it. If you answer NO (or N), 9VDE does not create a fold record for it. If you enter a ;module name with a wildcard specification, VDE asks you to Aconfirm the creation of a fold record for each module whose name Dmatches the wildcard specification. The /NOCONFIRM qualifier causes 2VDE to create the fold records without asking for confirmation.!/FROM_STREAM=stream-name
HSpecifies the development stream from which the source change should be Efolded. The stream-name parameter gives the name of <the stream. If you omit this qualifier, VDE determines what Hgeneration you want to fold by looking up the latest generation for the :current default stream. VDE then records that you want to Efold the change from the stream in which that generation was created.#/IDENTIFICATION=fold-ident
FSpecifies a fold identifier for the new fold record. Each fold record Ahas a unique fold identifier so that you can distinguish between Gmultiple fold records for the same module and user in the same stream. HBy default, the CREATE FOLD command assigns a unique numeric identifier Fto each fold record, such as "1", "2", and so on. GThe /IDENTIFICATION qualifier overrides this default and allows you to Fselect a fold identifier of your choice, such as a mnemonic name. The Hfold-ident parameter specifies the fold identifier. It 9can be up to 39 characters long and must follow VDE name syntax./LOG (default)
/NOLOG
HControls whether log messages are printed when the new fold records are Fcreated. The /LOG qualifier causes the messages to be printed and the D/NOLOG qualifier suppresses them. The messages indicate that a fold Hrecord has been created for each specified module and that the database 'transaction has successfully committed./REMARK="string"
ESpecifies a remark string to be stored for each new fold record. The Bquoted remark string, which can be up to 132 characters long, may Gcontain any explanatory remark about the fold to be performed that you 6want stored in the VDE database. Typically the remark Edescribes the function or contents of the source change to be folded into the new stream.EAlthough this qualifier is required, you can specify an empty remark 9string. If you do not specify the /REMARK qualifier, VDE prompts you for a remark string.
/STREAM=stream-name
HSpecifies the development stream into which the source change should be Efolded. The stream-name parameter gives the name of Bthe stream. This qualifier is required; if you do not specify it, $VDE prompts you for the stream name./USERNAME=username
ESpecifies that the fold record be created on behalf of another user. >The username parameter specifies the OpenVMS Husername of the other user. You must have the USERNAME privilege to use this qualifier.
6
| #1 |
|---|
PVDEä CREATE FOLD X.FOR/STREAM=V1.0/REMARK="Fix access violation in sort routine"H%VDE-I-FOLDADDED, fold record 1 for module [CODE]X.FOR added to database>%VDE-I-COMMIT, database transaction has successfully committedVDEäVDEä SHOW FOLDHFold 1 of [CODE]X.FOR;2(2) into stream V1.0 26-JUN-1990 JONESVDEä |
CThis example creates a new fold record for module [CODE]X.FOR. The Fremark indicates that a sort routine access violation should be fixed Bin that module. The change should be made in stream V1.0. The log =message shows that VDE assigned the unique fold identifier 1 Bto the new fold record. The SHOW FOLD command shows that the fold "record is now in the VDE database.
<Creates a new group definition in the VDE database. A group His either a source group or a build group. A source group consists of a Hset of source modules to be acted upon when the group name is specified Fwith various source control commands. A build group consists of a set Eof modules to be built when the group name is specified with a BUILD command.
<CREATE GROUP group-name = mod-name [, mod-name...]
group-name
CThe name of the new group to be created. This name may be up to 39 0characters long and must follow VDE name syntax.mod-name
BThe name of a module to be included in the group. The module name Econsists of an optional facility name enclosed in square brackets, a Hmodule name, and an optional type name preceded by a period. An example Bis [FACIL]MOD1.PAS. If no facility name is specified, the current Fdefault facility is assumed. If no type name is specified, all source Hmodules (for a source group) or all module (for a build group) with the Bgiven module name in the given facility are included in the group./You can add many modules to the group with one Fmod-name parameter by specifying wildcard characters Hin any of the three components of the module name. 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 Foccupies. Those source modules (for a source group) or modules (for a Fbuild group) whose names match the wildcard pattern become members of the new group.
HA group consists of the set of modules that are members of the group. A Hsource group only consists of source modules. When the name of a source Hgroup is specified with the RESERVE, REPLACE, FETCH, UNRESERVE, or SHOW GRESERVATION command, that command acts on all modules that are members Dof the group. A build group can consists of both source modules and Aderived modules, although it normally only consists of executableEimages and other derived modules that can be the outputs of a system Bbuild. When the name of a build group is specified with the BUILD Gcommand, that command builds all modules that are members of the group.?When a new group is created, it is only defined in the default Hdevelopment stream. You can refer to the new group only from within the stream to which it belongs.
EWhen you want to create the same group for more than one development Hstream, you must use the CREATE GROUP command for each stream. For each Bstream, first enter the SET STREAM command to set the development Hstream, then enter the CREATE GROUP command to create the desired group within the stream.
EWhen a new development stream is created, all group definitions from Cthe parent stream are copied to the child stream. If modified, the Cgroup definitions then evolve independently in the two development streams.
/BUILD
/SOURCE (default)
HSpecifies whether a source group or build group is created. The /SOURCE =qualifier causes VDE to create a source group and the /BUILD 9qualifier causes VDE to create a build group. If neither 3qualifier is specified, VDE creates a source group..Of /BUILD and /SOURCE, /SOURCE is the default.
/CONFIRM
/NOCONFIRM (default)
<Controls whether VDE asks you to confirm that you want each Fmodule matching the mod-name parameters added to the <group. The /CONFIRM qualifier causes VDE to print a message Gfor each matching module asking whether you want that module added. If Gyou answer YES (or Y), the module is added to the group. If you answer @NO (or N), the module is not added to the group. The /NOCONFIRM 5qualifier causes VDE to add all modules matching the Emod-name parameters to the group without asking for confirmation./LOG (default)
/NOLOG
GControls whether log messages are printed after the new group has been Fcreated. The /LOG qualifier causes the messages to be printed and the E/NOLOG qualifier suppresses them. The messages indicate that the new Fgroup has been created, that the requested modules are members of the Dgroup, and that the database transaction has committed successfully./REMARK="string"
ESpecifies a remark string to be stored for the new group. The quoted Gremark string, which can be up to 132 characters long, may contain any Cexplanatory remark about the new group that you want stored in the <VDE database. Typically the remark describes the purpose or contents of the group.
6
| #1 |
|---|
:VDEä CREATE GROUP/REMARK="Two modules" GRP1 = A.PAS, B.MAR1%VDE-I-GRPADDED, group GRP1 added to the database8%VDE-I-GRPADD, module [CODE]A.PAS is added to group GRP18%VDE-I-GRPADD, module [CODE]B.MAR is added to group GRP1>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
6CThis command creates a new source group called GRP1. The new group Hcontains two members, source modules A.PAS and B.MAR. These modules are Freserved if the group name is specified with the RESERVE command, for Cexample. Both modules are assumed to belong to the current default Efacility, facility CODE in this example. The remark string "Two Cmodules" is stored in the database with the rest of the group Gdefinition and can be retrieved later with the SHOW GROUP command. The Hexample shows the informational messages created by the /LOG qualifier, %specified by default in this example.
| #2 |
|---|
4VDEä CREATE GROUP/BUILD SYSGRP = X.EXE, Y.EXE, Z.HLB3%VDE-I-GRPADDED, group SYSGRP added to the database@%VDE-I-GRPADD, module [BUILD_TEST]X.EXE is added to group SYSGRP@%VDE-I-GRPADD, module [BUILD_TEST]Y.EXE is added to group SYSGRP@%VDE-I-GRPADD, module [BUILD_TEST]Z.HLB is added to group SYSGRP>%VDE-I-COMMIT, database transaction has successfully committedVDEä |
FThis command creates a new build group called SYSGRP. The build group Gcontains three members, executable images X.EXE and Y.EXE and the help Elibrary Z.HLB. If group name SYSGRP is specified as a parameter to a 2BUILD command, VDE will build these three modules.
| PreviousX | Next[ | Contents] | Index |