| Previous [ | Contents ] | Index |
; Creates a new VDE library, including its database and disk directory structure.
!CREATE LIBRARY dir-spec
dir-spec
B Specifies the name of the root directory of the library. The root B directory is the disk directory that contains the database of the @ library. It normally also contains subdirectories that hold the A contents of the library. Use the OpenVMS directory specification : format to specify the dir-spec parameter.> This parameter is required. If not specified, VDE prompts you # for the name of the root directory.
< A VDE library is the repository for all the modules in your B software system. A library consists of a top-level disk directory E called the root directory, an Rdb database which resides in the root A directory, and a number of directories (or subdirectories) which F contain all the source modules, derived modules, and other components of your software system.F The CREATE LIBRARY command first creates a root directory for the new ; library and defines logical name VDE$LIBRARY to contain the > name of this directory. It then creates and initializes a VDE D database in the root directory. The CREATE LIBRARY command normally E also creates the disk directory structure that will hold all sources C and other files that make up your software system. However, if the H default directory structure is not appropriate for you, you can use the ? /DEFER qualifier to postpone directory creation until you have 0 specified the directory structure that you want.
< The VDE database is a multifile Rdb database. This database F consists of three separate files: an Rdb root file (the .RDB file), a H storage area file (the .RDA file), and a snapshot file (the .SNP file). The 5 .RDB file is always stored in the VDE library's root H directory. This file is relatively small. The .RDA file stores the bulk H of the database contents and the .SNP file allows multiple users to use E the database concurrently. The .RDA and .SNP files are stored in the VDE library's C root directory by default, but you can specify different directory G locations for these files with the /DATABASE and /SNAPSHOT qualifiers, > or by defining the logical names VDE$DB_AREA and VDE$SNAPSHOT. C By placing these files on different disks, you can distribute your 9 VDE library's space and I/O requirements across multiple disks.
G You may also want to establish an Rdb after-image journal file for the = VDE database. If used with the RMU database backup facility, F such a journal file allows Rdb to recover all database data as of the > last completed transaction after a disk failure. To establish A journalling, use the /JOURNAL qualifier to specify the directory C location of the journal file. This directory should always be on a ; different physical disk than the rest of your VDE database.
> Once you have created a new VDE library, that library becomes 9 the current VDE library for your present process so that = subsequent VDE commands act upon that library. To change the = current VDE library, you must use the SET LIBRARY command or redefine logical name > VDE$LIBRARY to point to the root directory of the VDE library you want to work with.
> Most steps in creating a new VDE library are reasonably fast. H For example, each directory in your directory structure is created in a D fraction of a second unless your system is heavily loaded. However, : VDE requires several minutes to create and initialize the F library database. The database can usually be created in about six to H eight minutes but more time may be required on a heavily loaded system. 6 A log message tells you when database creation starts.
/ALLOW_DELETE (default)
/NOALLOW_DELETE
F Specifies the default value for the delete attribute F for new modules, facilities, and streams. The /ALLOW_DELETE qualifier ; causes VDE to set the delete attribute by D default when users create new such entities. As a result, users can 6 delete these entities without first having to set the F delete attribute with a separate MODIFY command. The 2 /NOALLOW_DELETE qualifier causes VDE to clear the > delete attribute by default for new modules, H facilities, and streams. As a result, it is harder for a user to delete E an entity by mistake; the entity's delete attribute D must be set with a separate MODIFY command before the entity can be F deleted with a DELETE command. When creating new modules, facilities, D and streams, you can override this default setting with an explicit 5 /DELETE or /NODELETE qualifier to the CREATE command.G Use the /ALLOW_DELETE qualifier if you expect to make frequent changes F to your library, often deleting modules, facilities, and streams. Use > the /NOALLOW_DELETE qualifier if you are more concerned about 0 preventing accidental deletion of such entities.
/ASK_INFO_FILE
#/NOASK_INFO_FILE (default)
E Specifies whether the REPLACE command should by default ask the user C whether he or she wants to edit an information file when creating a @ queued replacement. The /ASK_INFO_FILE qualifier sets a library D attribute that causes the REPLACE command to ask for an information D file by default. The /NOASK_INFO_FILE qualifier clears this library F attribute so that the REPLACE command does not ask for an information < file by default. This library attribute only affects queued C replacements (not immediate replacements), and it only affects the G REPLACE command's default behavior; users can always use the command's F /INFORMATION or /NOINFORMATION qualifier to explicitly request either behavior./ASK_REPL_CAUSE
$/NOASK_REPL_CAUSE (default)
E Specifies whether the REPLACE command should by default ask the user F for the "cause" of the replacement. The cause may be a fold G operation, a Source Control Tracking (SCT) entry in a Notes conference, B or some other cause. The /ASK_REPL_CAUSE qualifier sets a library D attribute that causes the REPLACE command to query the user for the F cause of the replacement. The /NOASK_REPL_CAUSE qualifier clears this D library attribute so that the REPLACE command does not ask for this information.+/AUTH_PRIVILEGES=(priv [,priv...])
H Specifies the standard authorized privileges for the library. These are A the authorized privileges that a new user gets when added to the F library unless a different set of authorized privileges is explicitly = specified for that user. Authorized privileges are those VDE E privileges the user is allowed to set with the SET PRIVILEGE command.G If only one privilege is specified, the parentheses may be omitted. If 9 this qualifier is omitted entirely, VDE provides default = values for the standard authorized privileges of the library.
? Each priv parameter specifies the name of one © privilege. For a list of privileges, see Table 3-5 in SET PRIVILEGES. &
/AUTO_ADD_USER[=rights-ident]
#/NOAUTO_ADD_USER (default)
D Specifies whether new users should be added to the library database E automatically when they first access the library. The /AUTO_ADD_USER B qualifier specifies that new users should be added to the library B database automatically when they first access the library. If the D rights-ident parameter is specified, new users are : only added to the library if they hold the OpenVMS rights F identifier specified by the parameter. The /NOAUTO_ADD_USER qualifier > specifies that new users not be added to the library database G automatically. In this case, new users can only be added with explicit CREATE USER commands.5 The owner information specified in the OpenVMS SYSUAF < database will be used as the owner of any new VDE username 8 created. VDE will ignore any leading numerics, leading I hyphens, leading space characters, and leading tilde characters, listed in the SYSUAF owner field.
/AUTO_CONVERT
"/NOAUTO_CONVERT (default)
A Specifies whether the library and its database are automatically > converted to the new library format when a new version of VDE = is used on the library. A new version of VDE will frequently D require a different database schema and possibly other changes to a ; library than the previous version. Each new version of VDE > can convert a VDE library from an older format to the current A format. This is either done automatically the first time someone G accesses the library database, or it is done with an explicity CONVERT : LIBRARY command. These qualifiers determine the behaviour.A The /AUTO_CONVERT qualifier specifies that the library should be D converted automatically the first time a user uses a new version of = VDE on the present library and its database. /NOAUTO_CONVERT B specifies that the library should not be converted automatically; G instead a privileged user must explicitly convert the library with the CONVERT LIBRARY command.
B The advantage of automatic conversion is that it is automatic and C requires no special steps on the part of the user. However, once a G library has been converted, it is not possible to use an older version of VDE on that library.
B The advantage of disabling automatic conversion is that you get a A chance to back up the database (or the whole library) before you F explicitly convert the library. You then have the option of restoring F the backed up copy of the library if you need to go back to using the < old version of VDE. However, once you install a new version 8 of VDE, nobody can use the existing library until it is A converted. Also, all accessors must use the same or a compatible version of VDE.
7 In general, automatic conversion is best for small VDE G libraries whose databases are relatively easy to rebuild if necessary. G Explicit conversion may be more suitable for large libraries where the E difficulty of rebuilding the library justifies more stringent backup and recovery procedures.
/NOAUTO_CONVERT is the default.
/AUTO_MAIL (default)
/NOAUTO_MAIL
5 Specifies whether VDE should automatically send mail @ notification to the user who has queued a replacement when that H replacement is later performed. The /AUTO_MAIL qualifier sets a library H attribute that causes the PERFORM REPLACEMENT command to send such mail G notification. The /NOAUTO_MAIL qualifier clears this library attribute H so that the PERFORM REPLACEMENT command does not send such notification.!/CMS_ELEM_HIST (default)
/NOCMS_ELEM_HIST
7 Specifies whether VDE creates the CMS elements for new G modules with default CMS history and notes strings. The /CMS_ELEM_HIST qualifier causes VDE to G create the CMS elements for new modules with default history and notes 9 strings and the /NOCMS_ELEM_HIST qualifier causes VDE to > create CMS elements with no default history or notes strings. > /NOCMS_ELEM_HIST is normally only used if you regularly fetch = VDE modules using the CMS FETCH command and you want to make C sure you do not get CMS history or notes by default. If you always 8 fetch through VDE, use /CMS_ELEM_HIST because it allows < VDE to avoid a deficiency in CMS and always give and remove history information correctly./CREATOR_NAME="string"
H Specifies the full name of the user who created the library. The quoted H name string, which may be up to 40 characters long, should contain your F first name, middle initial, and last name. The CREATE LIBRARY command ? automatically creates a user record in the new library for the E library's creator. This name string becomes part of that user record.F This qualifier is required. An empty name string may be specified but F this is not recommended. If the /CREATOR_NAME qualifier for a library 6 is not specified, VDE prompts you for the name string.
/DATABASE=dir-spec
F Specifies that the database storage area (.RDA) file and the snapshot > (.SNP) file be created in the directory location given by the E dir-spec parameter. This qualifier lets you put the > largest part of the VDE database on a different disk than the 5 rest of the VDE library. If you omit this qualifier, / VDE creates the .RDA and .SNP files in the VDE library's root directory./DEFER
/NODEFER (default)
F Specifies whether the creation of the directory structure for the new H library should be postponed. The /DEFER qualifier postpones creation of H the disk directory structure for the library and the /NODEFER qualifier B causes the directory structure to be created immediately. Use the G /DEFER qualifier when the default directory structure is inappropriate for the new library.C If the /NODEFER qualifier is specified (or /DEFER is omitted), the @ CREATE LIBRARY command first creates the root directory and the < VDE database for the library. Then it creates the remaining @ disk directory structure for the library. This structure, which > includes directories to hold delta-files for one facility and G directories to hold files for one development stream, is determined by G the default rules of the utility. Once the directory structure exists, ? source modules and other files can be added to the new library.
A If the /DEFER qualifier is specified, the CREATE LIBRARY command H creates only the library's root directory and its database; it does not E create the remaining directory structure for the new library. If you B use the /DEFER qualifier, you can enter SET DIRECTORY commands to D specify the disk directories you want for the library. Then use the D CREATE DIRECTORY_TREE command to create that directory structure on : disk. The CREATE DIRECTORY_TREE command uses VDE defaults E combined with the rules you specified with SET DIRECTORY commands to # create the new directory structure. *
/DEF_PRIVILEGES=(priv [,priv...])
E Specifies the standard default privileges for the library. These are F the default privileges that a new user gets when added to the library E unless a different set of default privileges is explicitly specified ; for that user. Default privileges are those VDE privileges 9 that are enabled each time the user starts a VDE session.G If only one privilege is specified, the parentheses may be omitted. If 9 this qualifier is omitted entirely, VDE provides default : values for the standard default privileges of the library.
? Each priv parameter specifies the name of one © privilege. For a list of privileges, see Table 3-5 in SET PRIVILEGES.
D Each privilege specified becomes a standard authorized privilege as G well as a standard default privilege. This rule ensures that users are 0 authorized to have all their default privileges.!
/HISTORY_NOTES (default)
/NOHISTORY_NOTES
8 Specifies whether VDE's RESERVE command can produce CMS history or notes E information in its output files. The /HISTORY_NOTES qualifier allows D the RESERVE command to produce history and notes information and to ; accept the /HISTORY, /NOTES, and /POSITION qualifiers. The G /NOHISTORY_NOTES qualifier causes the RESERVE command to never produce A history and notes information (even when such information is the E default for a module being reserved) and to not accept the /HISTORY, A /NOTES, and /POSITION qualifiers. In this case, you must use the ' VDE FETCH command to get CMS history or H notes information for a module. Disabling history and notes information @ in reserved files makes certain mistakes less likely where such > information gets replaced into the VDE library as part of the module text./JOURNAL=dir-spec
> Enables after-image journalling and specifies that a database E after-image journal (.AIJ) file be created in the directory location E given by the dir-spec parameter. When used with the F RMU backup and restore facilities, after-image journalling allows you A to recover the up-to-date contents of your database after a disk E failure. The specified directory should always reside on a different H physical disk than any of your other database files so that the journal H file cannot be damaged by the same disk failure as the database itself. 5 If you omit this qualifier, VDE disables after-image @ journalling. Digital recommends that you always use journalling./LOG (default)
/NOLOG
B Controls whether log messages are printed when the new library is B created. The /LOG qualifier causes messages to be printed and the A /NOLOG qualifier suppresses them. The messages indicate that the 2 library and its many components have been created./NAME=lib-name
H Specifies a name for the new library to be created. This name may be up 7 to 39 characters long and must follow VDE name syntax. = VDE stores this name in the database and displays it back to C you when you enter the SHOW LIBRARY or SHOW DEFAULTS command. This = qualifier is required; if you do not specify it, VDE prompts you for the library name./REMARK="string"
H Specifies a remark string. The quoted remark string, which can be up to F 132 characters long, may contain any explanatory remark about the new F library that you want stored in the library's database. Typically the < remark describes the purpose or contents of the new library.E Although this qualifier is required, you can specify an empty remark 9 string. If you do not specify the /REMARK qualifier, VDE prompts you for a remark string.
/REPL_HISTORY (default)
/NOREPL_HISTORY
< Specifies whether VDE should maintain a history of all past 3 source code replacements into the VDE library. The C /REPL_HISTORY qualifier specifies that such history information be > maintained in the VDE database. The /NOREPL_HISTORY qualifier E specifies that such information not be maintained. When you maintain A replacement history, you can display past replacements using the 3 /HISTORY qualifier to the SHOW REPLACEMENT command.z For documentation on the SHOW REPLACEMENT command in SHOW REPLACEMENT.
/SEND_MAIL (default)
/NOSEND_MAIL
= Specifies whether VDE should send mail notification messages ; for those VDE operations that normally send such messages. 7 The /SEND_MAIL qualifier enables VDE to send such mail ; messages and the /NOSEND_MAIL qualifier suppresses all VDE E mail messages. The /NOSEND_MAIL qualifier is useful when you want to 8 test or play with a private VDE library without sending F notification messages to other people. However, for normal production H use, you should always leave the mail notification feature enabled. The < CREATE LIBRARY command enables mail notification by default./SHOW_ARCH_NAME
$/NOSHOW_ARCH_NAME (default)
F Specifies whether the architecture name is displayed as part of every > module name in VDE output. The /SHOW_ARCH_NAME qualifier sets : a library attribute that causes VDE to always include the H architecture name in every module name it displays. This attribute also F causes the SHOW DEFAULTS command to display the default architecture. F The /NOSHOW_ARCH_NAME qualifier clears this library attribute so that 8 VDE omits the architecture names when displaying module G names. You normally only want to see the architecture name if you have 4 defined multiple architectures for your VDE library./ This qualifier is not yet implemented.
/SHOW_GEN_EXPR
#/NOSHOW_GEN_EXPR (default)
F Specifies whether the expected replace-time CMS generation expression H for each module is displayed by the RESERVE command. The /SHOW_GEN_EXPR F qualifier sets a library attribute that causes the RESERVE command to ; compute and display the CMS generation expression that the G corresponding REPLACE command is most likely to use for the new module ; generation. You can use this value as an "audit trail D identifier" in your code if your project uses this convention. C This library attribute also causes the SHOW RESERVATION command to A display the expected CMS generation expression and it causes the A REPLACE or PERFORM REPLACEMENT command to print an informational A message if the actual CMS generation expression for the replaced @ generation turns out to be different than the expected one. The ; /NOSHOW_GEN_EXPR qualifier disables this library attribute.< Please note that VDE cannot guarantee that the expected CMS C generation expression will actually be used. It is not possible to F determine at RESERVE time whether a CMS variant letter should be used G when the module is eventually replaced; that decision can only be made @ at REPLACE time and depends on propagation decisions and stream @ successor relationships at that time. However, the expected CMS A generation expression is generally the one that is actually used.
/SNAPSHOT=dir-spec
C Specifies that the database snapshot (.SNP) file be created in the E directory location given by the dir-spec parameter. D This qualifier lets you put the snapshot file on a separate disk to F better use disk space or to improve database performance. If you omit ; this qualifier, VDE creates the .SNP file in the directory D given by the /DATABASE qualifier if that qualifier is specified. If > neither qualifier is specified, VDE creates the snapshot file $ in the VDE library's root directory./LOCK
/UNLOCK
D The /LOCK and /UNLOCK qualifiers provide a method by which RESERVE, D REPLACE, UNRESERVE, and other similar commands can be disabled on a 9 copy of a VDE library. This mechanism is not intended to 0 completely lock-out all access to a VDE library.F Specification of /LOCK write-locks the library, and the corresponding H /UNLOCK qualifier reverses the lock. The write-lock status is read only ? when the user initially accesses the library---once a user has B connected to the library, the lock status is not updated.
; A write-locked library can be used to prevent various user < modifications to the contents of the library during library 7 maintenance, or to maintain a shadow copy of a library.
G Users holding the MODLIB privilege are allowed to override the library write-lock. I An informational message will be displayed when the lock is overridden.
/STATISTICS
H Enables statistics collection on the specified library. This will cause C various extra questions to be asked during replacement and related F operations. This includes the addition of questions around the reason H for the change, the number of defects fixed, and the particular project a change is associated with./WILD_INS_GEN
"/NOWILD_INS_GEN (default)
G Specifies whether wildcard characters are allowed in the parameters to @ the INSERT GENERATION command when the /GENERATION qualifier is ; specified. The /WILD_INS_GEN qualifier causes VDE to allow A wildcard characters in such parameters while the /NOWILD_INS_GEN < qualifier causes VDE to not allow such wildcard characters. @ When the /GENERATION qualifier to INSERT GENERATION specifies a H specific CMS generation expression, it is unlikely that this generation C expression could apply to more than one module. As a result, it is @ unlikely that the use of wildcard characters in the module-name H parameters will give the result the user intended. To prevent mistakes, = VDE therefore does not allow such wildcard usage by default. D However, there are some situations when such usage might be correct D (for example, if the specified CMS generation expression is 1). For H such situations, you can enable the use of wildcard characters with the /WILD_INS_GEN qualifier.
| #1 |
|---|
, VDE„ CREATE LIBRARY [PROJDIR] /NAME=NEWLIB -8 _VDE„ /CREATOR_NAME="John Doe" -< _VDE„ /REMARK="Main project library"8 Library NEWLIB to be created in root directory [PROJDIR]8 Library root directory DEV$:[PROJDIR] already exists.: Logical name VDE$LIBRARY now points to the new library., Creating library database; please wait...% Library database has been created. E Staging area root directory DEV$:[PROJDIR.VDE$STAGE] has been created ( Creating directory tree for delta files:9 Root directory DEV$:[PROJDIR.VDE$CMS] has been created L Facility CODE root directory DEV$:[PROJDIR.VDE$CMS.CODE] has been created4 CMS library for facility CODE has been created, All directories for delta files now exist( Creating directory tree for stream MAIN:6 Root directory DEV$:[PROJDIR.MAIN] has been created? Subdirectory DEV$:[PROJDIR.MAIN.VDE$BLD] has been created I Facility CODE root directory DEV$:[PROJDIR.MAIN.CODE] has been created @ Subdirectory DEV$:[PROJDIR.MAIN.CODE.SRC] has been created@ Subdirectory DEV$:[PROJDIR.MAIN.CODE.OBJ] has been createdD Subdirectory DEV$:[PROJDIR.MAIN.CODE.VDE$COM] has been createdD Subdirectory DEV$:[PROJDIR.MAIN.CODE.VDE$LOG] has been created, All directories for stream MAIN now exist Library creation completed. VDE„ |
E This command creates a new library called NEWLIB. The root directory E for the new library is DEV$:[PROJDIR] and the name of the creator is ? John Doe. The log messages indicate when the various steps are 9 completed. First VDE indicates the root directory of the G library currently exists and binds the logical name VDE$LIBRARY to that 9 directory. Then VDE creates the database of the library, 6 which may take several minutes. Next, VDE creates the D directory structure for the delta files of the project. Finally, it H creates the directory structure for stream MAIN, the only stream in the library.
| #2 |
|---|
VDE„ CREATE LIBRARY < Enter directory specification for the new library: [PROJDIR]3 Enter the name you want for the new library: NEWLIB 5 Enter your full name (first and last names): John Doe 6 Enter the remark for new library: Main project library8 Library NEWLIB to be created in root directory [PROJDIR]8 Library root directory DEV$:[PROJDIR] already exists.: Logical name VDE$LIBRARY now points to the new library., Creating library database; please wait...% Library database has been created. ( Creating directory tree for delta files:9 Root directory DEV$:[PROJDIR.VDE$CMS] has been created L Facility CODE root directory DEV$:[PROJDIR.VDE$CMS.CODE] has been created4 CMS library for facility CODE has been created, All directories for delta files now exist( Creating directory tree for stream MAIN:6 Root directory DEV$:[PROJDIR.MAIN] has been createdI Facility CODE root directory DEV$:[PROJDIR.MAIN.CODE] has been created @ Subdirectory DEV$:[PROJDIR.MAIN.CODE.SRC] has been created@ Subdirectory DEV$:[PROJDIR.MAIN.CODE.OBJ] has been createdD Subdirectory DEV$:[PROJDIR.MAIN.CODE.VDE$COM] has been createdD Subdirectory DEV$:[PROJDIR.MAIN.CODE.VDE$LOG] has been created, All directories for stream MAIN now exist Library creation completed. VDE„ |
A In this example, the user enters the keywords CREATE LIBRARY and > VDE prompts for all other needed information. The new library . is created exactly as in the previous example.
"$ G $! Locate and delete previous incarnations of the test facility files, 8 $! then unpack the saveset containing the test files... $ P $ if f$search("sys$scratch:A.REQ") .nes. "" Then Delete sys$scratch:A.REQ;*/log P $ if f$search("sys$scratch:B.REQ") .nes. "" Then Delete sys$scratch:B.REQ;*/log P $ if f$search("sys$scratch:C.B32") .nes. "" Then Delete sys$scratch:C.B32;*/log P $ if f$search("sys$scratch:D.B32") .nes. "" Then Delete sys$scratch:D.B32;*/log P $ if f$search("sys$scratch:E.B32") .nes. "" Then Delete sys$scratch:E.B32;*/log P $ if f$search("sys$scratch:F.B32") .nes. "" Then Delete sys$scratch:F.B32;*/log $ * $ Backup VDE$CREATE.BCK/SAVE Sys$Scratch: $ 8 $! Create the core directory -- this must be present... $ 4 $ Create/Directory STAR$DATA:[QTV.WWW.VDE$DATABASE] $ VDE ! > ! create the WWW library in STAR$DATA:[QTV.WWW...], using the > ! mnemonic WWW, placing all Rdb-related library components in $ ! STAR$DATA:[QTV.WWW.VDE$DATABASE]. ! 9 create librar STAR$DATA:[QTV.WWW.VDE$DATABASE] /DEFER - /NAME=WWW - $ /REMARK="QTV WWW Source Library" - 8 /NOAUTO_CONVERT /AUTO_ADD_USER=VMS_SOURCE /AUTO_MAIL - = /ASK_INFO_FILE /ASK_REPL_CAUSE /SHOW_GEN_EXPR /NOSTATISTI - 4 /NOHISTORY_NOTES /NOALLOW_DELETE /NOWILD_INS_GEN - / /NOCMS_ELEM_HIST /CREATOR="Stephen Hoffman" - * /DEF_PRIVILEGES=(CREMOD,RESREP,CREFAC) - + /AUTH_PRIVILEGES=(CREMOD,RESREP,CREFAC) - * /data=STAR$DATA:[QTV.WWW.VDE$DATABASE] - + /journ=STAR$DATA:[QTV.WWW.VDE$DATABASE] - ( /snap=STAR$DATA:[QTV.WWW.VDE$DATABASE] ! SHOW DEFAULTS SHOW LIBRARY/FULL 2 MODIFY CONTEXT/PUBLIC DEFAULT/NOSTREAM/NOFACILITY ! , CREATE USER SYSTEM /NAME="System Manager" - 2 /DEF_P=ALL/AUTH_P=ALL/REMARK="System Manager" ! 8 ! Create the CMS ("delta") library directory structure. > ! Configure the CMS libraries to use the directory structure: 5 ! STAR$DATA:[QTV.WWW.CMS$DATABASE.'facility'.CMS]. ? ! Configure the "marker" files to use the directory structure: 7 ! STAR$DATA:[QTV.WWW.CMS$DATABASE.'facility'.SRC]... ! ; SET DIRECTORY/DELTA_FILES STAR$DATA:[QTV.WWW.CMS$DATABASE] 6 SET DIRECTORY/DELTA_FILES/SUBDIRECTORY=VDE$CMS [.CMS] 9 SET DIRECTORY/DELTA_FILES/SUBDIRECTORY=VDE$MARKER [.SRC] " CREATE DIRECTORY_TREE/DELTA_FILES SHOW DIRECTORY/DELTA_FILES ! ! Create the staging area... ! 6 SET DIRECTORY/STAGING STAR$DATA:[QTV.WWW.VDE$STAGING] CREATE DIRECTORY_TREE/STAGING ! & ! Create the stream/build directories ! 4 SET DIRECTORY/STREAM STAR$DATA:[QTV.WWW.VDE$STREAM] CREATE DIRECTORY_TREE/STREAM ! ) ! create and load the VDE test facility. ! CREATE FACILITY AAA_VDE_TEST - / /REMARK="Test facility for VDE developers" SET FACILITY AAA_VDE_TEST" 7 CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: A.REQ 7 CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: B.REQ 7 CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: C.B32 7 CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: D.B32 7 CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: E.B32 7 CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: F.B32 ! EXIT $ $ Exit
| Previous X | Next[ | Contents ] | Index |