| Previous | Contents | Index |
Establishes the context of the current VDE session or the default context for future VDE sessions. A context can be used to specify the default development stream, default architecture and default facility for a VDE session.
SET CONTEXT ctx-name
ctx-name
Specifies the context for the current VDE session or the default context for future VDE sessions. The parameter must be the name of an existing public or private context in the VDE database.
This command establishes a context for the current VDE session or establishes the default context for future sessions. A context sets the following two defaults:Using a SET CONTEXT command is equivalent to using individual SET STREAM and SET FACILITY commands to establish the same settings.
- the default development stream for the VDE session
- the default facility for the session
If you specify the /DEFAULT qualifier, the context becomes the default for future VDE sessions and VDE records that setting in the database. The context of the current session does not change. If you do not specify the /DEFAULT qualifier, the command establishes the context for the current VDE session.
To display contexts, use the SHOW CONTEXT command.
/DEFAULT
Establishes the specified context as the default context for future VDE sessions. The context of the current session is not changed.If you do not use this qualifier, the specified context becomes the context for your current session.
/PRIVATE (default)
/PUBLIC
Specifies whether the context to set is a private or public context. The /PRIVATE qualifier specifies that the context is an existing private context. The /PUBLIC qualifier specifies that the context is an existing public context. If neither qualifier is not used, VDE assumes that the specified context is private to you.Of /PRIVATE and /PUBLIC, /PRIVATE is the default.
| #1 |
|---|
VDE„ SET CONTEXT BUGFIXES
VDE„ SHOW DEFAULTS
Library LIBNAME in root directory DEV$:[PROJDIR]
Default directory is DEV$:[SMITH]
Context BUGFIXES (private to user SMITH)
Default stream is V2.2-BL1
Default facility is RMS
VDE„
|
The SET CONTEXT command takes the defaults for the current VDE session from context BUGFIXES. The SHOW DEFAULTS command confirms that those defaults have been established for the session.
| #2 |
|---|
VDE„ SET CONTEXT/DEFAULT FOO
VDE„
|
This command makes context FOO the default context for the current user's future VDE sessions.
Sets or modifies the current settings of the developer flags.Use this command only under the explicit direction of, and with the assistance of, a VDE developer.
SET DEVELOPER dev-flags
Under Construction... Table 3-4 contains various parameters.
Table 3-4 Parameters Parameter Description LOCK NOMAIL SHOW SYNCH NONOTES
| #1 |
|---|
VDE„ SET DEVELOPER
Under Construction...
VDE„ SET DEVELOPER SCRIPT
VDE„
|
Creates a directory template in the VDE database. Directory templates determine what disk directories VDE creates when creating new streams and facilities and various disk storage areas.
SET DIRECTORY dir-spec
dir-spec
Specifies a OpenVMS directory specification for the new directory template. This parameter may specify an absolute or a relative directory specification. An absolute directory specification is a fully specified OpenVMS directory name and follows the normal syntax for such names. You use an absolute directory specification when you want to decide the exact disk location for a directory in the VDE library. For example, you may want to locate a new stream's root directory on a specific disk before VDE creates the stream's directory tree. The parameter DEV:[DIRNAM.FOO] is an example of an absolute directory specification.A relative directory specification begins with a left bracket and a period ([.), then contains one or more subdirectory names separated by periods, and ends with a right bracket (]). This directory specification is concatenated to the name of the appropriate root directory to form a full directory specification. You use a relative directory specification to specify a subdirectory name that VDE should use relative to some root directory. The directory specification [.SRC], for example, can be used to specify that a facility subdirectory named SRC should be created within each facility's root directory.
The SET DIRECTORY command creates a new "directory template" in the VDE database. A directory template specifies the name that VDE should assign to each disk directory of a certain kind when creating directories for new streams or facilities. You can create directory templates for stream root directories, facility root directories, facility subdirectories, the library's delta-file root directory, and the library's staging-area root directory for queued replacements. (The library root directory is created when you create the library and cannot be changed thereafter.)The SET DIRECTORY command does not itself create new directories; it only stores the new directory template in the VDE database. VDE does not use the template to create new disk directories until a subsequent CREATE STREAM or CREATE FACILITY command creates the directory tree for a new stream or facility. The CREATE DIRECTORY_TREE command uses directory templates to create directories for an existing stream or facility.
Unless the new template is for the library's delta files or its staging area, it is only defined for the default development stream. However, directory templates are inherited by the stream's future descendants and are used to create the disk directories for those descendants. They are also used to create directory trees for new facilities in the default stream.
If you want to create directory templates for a new stream, you can specify the templates for the parent stream, in which case they are automatically applied to all child streams. You must then enter the SET DIRECTORY command before you enter the CREATE STREAM command for the new stream. Alternatively, you can create the new stream with the /DEFER qualifier on the CREATE STREAM command. This qualifier suppresses directory-tree creation for the new stream. You can then use the SET STREAM command to make the new stream the default stream and use the SET DIRECTORY command to create the directory templates you want. A subsequent CREATE DIRECTORY_TREE command uses the new templates (and any applicable default rules) to create the directory tree for the new stream. The /DEFER qualifier thus defers directory-tree creation so that you can enter SET DIRECTORY commands before creating the new directory tree.
You may also want to create directory templates for a new facility. If the templates should apply to that facility only, you must create the new facility with the /DEFER qualifier on the CREATE FACILITY command. This qualifier suppresses directory-tree creation for the new facility. You then use the SET DIRECTORY command with the /FACILITY qualifier to create the directory templates you want for that facility. A subsequent CREATE DIRECTORY_TREE command uses the new templates to create the directory tree for the facility.
For additional information on directory creation, and on directory symbols (dir-symbol) and directory symbol processing, see CANCEL DIRECTORY, SHOW DIRECTORY, and Script Functions.
/DEFER
/NODEFER (default)
The /DEFER qualifier specifies that directory tree creation for new streams be deferred when those streams are created. This action only applies to new streams for which the default stream is the parent. This qualifier should be used when you always want an opportunity to alter a new stream's directory templates before you actually create its directory tree. The /NODEFER qualifier specifies that directory tree creation not be deferred for new streams unless the user explicitly uses the /DEFER qualifier with the CREATE STREAM command./DELTA_FILES
/STAGING
/STREAM (default)
Specifies whether the new directory template is for the VDE library's delta files, for its staging area, or for the default stream. The /DELTA_FILES qualifier specifies that the new directory template is for directories that store the library's delta files (CMS libraries). The /STAGING qualifier specifies that the new directory template is for the library's staging-area root directory. (Staging areas hold files for queued replacements.) The /STREAM qualifier specifies that the new directory template is for directories that store files for the current default stream. Because streams inherit directory templates from their parents, the /STREAM qualifier causes the new directory template to apply to all of the default stream's future descendants.Of /DELTA_FILES, /STAGING and /STREAM, /STREAM is the default.
/FACILITY=fac-name
Specifies that the new directory template only applies to the facility given by the fac-name parameter. This parameter may not contain wildcard characters. If both this qualifier and the /SUBDIRECTORY qualifier are specified, VDE creates a directory template for the specified facility subdirectory. If the /FACILITY qualifier is specified and the /SUBDIRECTORY qualifier is omitted, VDE creates a template for the specified facility's root directory.If the /FACILITY qualifier is omitted and the /SUBDIRECTORY qualifier is specified, VDE creates a directory template for the facility subdirectory for all facilities that are not explicitly specified in other templates. If both the /FACILITY qualifier and the /SUBDIRECTORY qualifier are omitted, VDE creates a template for the stream or delta-file root directory.
/LOG (default)
/NOLOG
Controls whether log messages are printed after the directory template is created. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages indicate that the directory template has been added to the database and that the database transaction has completed successfully./PROMPT
/NOPROMPT (default)
The /PROMPT qualifier specifies that users who create new streams for which the default stream is the parent be prompted for the name of the new stream's root directory. This qualifier should be used when you do not want to use the default root directory name for new streams, but want the user to explicitly select the location of the new stream's directory tree each time (perhaps to select a different disk each time). The /NOPROMPT qualifier specifies that a new stream should get the root directory determined by VDE's default rules unless the user explicitly specifies otherwise on the CREATE STREAM command./REMARK="string"
Specifies a remark string to be stored for the new directory template. The quoted remark string, which can be up to 132 characters long, may contain any explanatory remark about the new directory template that you want stored in the VDE database./SUBDIRECTORY=dir-symbol
Specifies that the new directory template is for a facility subdirectory. The dir-symbol parameter specifies the directory symbol that you want to associate with the subdirectory. The directory symbol must follow normal VDE name syntax. You use the directory symbol in VDE scripts to reference the subdirectory; see the description of the CREATE SCRIPT command for an explanation of VDE scripts. If the /SUBDIRECTORY qualifier is omitted, VDE creates a directory template for a facility, stream, or delta-file root directory. (The description of the /FACILITY qualifier explains how the qualifiers interact to select the template to create.)When you specify facility subdirectories for delta-files, the directory symbol may have a special meaning to VDE. If you specify a delta-file subdirectory with the symbol VDE$CMS, VDE puts the CMS library for the facility in that subdirectory instead of in the facility root directory. If you specify a delta-file subdirectory with the symbol VDE$MARKER, VDE puts the actual source files for modules that use "marker files" in that subdirectory. If you use marker files, you must have both a marker-file subdirectory and a CMS-library subdirectory. (The description of the /MARKER qualifier to the CREATE MODULE command discusses marker files in more detail.)
| #1 |
|---|
VDE„ SET DIRECTORY/STREAM/SUBDIRECTORY=ANASYM [.ANA]
%VDE-I-DIRADDED, directory specification [.ANA] added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„ SHOW DIRECTORY
Directory-creation templates for stream V2.1-1:
Directory creation flags:
Do not defer creation of directory tree for substreams
Do not prompt for root directory for substreams
Stream root directory is [.V2_1-1] by default
Subdirectory: [.VDE$BLD] (symbol VDE$BLD)
Directory templates for unspecified facilities:
Subdirectory: [.ANA] (symbol ANASYM)
Subdirectory: [.OBJ] (symbol OBJ)
Subdirectory: [.SRC] (symbol SRC)
Subdirectory: [.VDE$COM] (symbol VDE$COM)
Subdirectory: [.VDE$LOG] (symbol VDE$LOG)
All other directories created using default rules
VDE„
|
This example creates a directory template for a new facility subdirectory. The directory specification is [.ANA], which says that a subdirectory called ANA should be created within each facility's root directory. The directory symbol associated with that subdirectory is ANASYM. This symbol is used in VDE scripts to reference the subdirectory. The SHOW DIRECTORY command shows that the new directory template is stored in the database.
| #2 |
|---|
VDE„ SET DIRECTORY/FACILITY=RMS [MYDIR.RMS]
%VDE-I-DIRADDED, directory specification [MYDIR.RMS] added to the database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„ SHOW DIRECTORY
Directory-creation templates for stream V2.1-1:
Directory creation flags:
Do not defer creation of directory tree for substreams
Do not prompt for root directory for substreams
Stream root directory is [.V2_1-1] by default
Subdirectory: [.VDE$BLD] (symbol VDE$BLD)
Directory templates for unspecified facilities:
Subdirectory: [.OBJ] (symbol OBJ)
Subdirectory: [.SRC] (symbol SRC)
Subdirectory: [.VDE$COM] (symbol VDE$COM)
Subdirectory: [.VDE$LOG] (symbol VDE$LOG)
Directory templates for facility RMS:
Root directory: [MYDIR.RMS]
All other directories created using default rules
VDE„
|
This example creates a directory template for the root directory of facility RMS. The directory specification is [MYDIR.RMS], an absolute directory specification for the root directory. VDE will create this directory for facility RMS when a subsequent CREATE DIRECTORY_TREE command is entered for that facility or a new stream is created from the default stream. The SHOW DIRECTORY command shows that the new directory template is stored in the database.
The following example shows an example of a VDE library creation, including a number of directory-related commands.
$ $! Locate and delete previous incarnations of the test facility files, $! then unpack the saveset containing the test files... $ $ if f$search("sys$scratch:A.REQ") .nes. "" Then Delete sys$scratch:A.REQ;*/log $ if f$search("sys$scratch:B.REQ") .nes. "" Then Delete sys$scratch:B.REQ;*/log $ if f$search("sys$scratch:C.B32") .nes. "" Then Delete sys$scratch:C.B32;*/log $ if f$search("sys$scratch:D.B32") .nes. "" Then Delete sys$scratch:D.B32;*/log $ if f$search("sys$scratch:E.B32") .nes. "" Then Delete sys$scratch:E.B32;*/log $ if f$search("sys$scratch:F.B32") .nes. "" Then Delete sys$scratch:F.B32;*/log $ $ Backup VDE$CREATE.BCK/SAVE Sys$Scratch: $ $! Create the core directory -- this must be present... $ $ 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]. ! create librar STAR$DATA:[QTV.WWW.VDE$DATABASE] /DEFER - /NAME=WWW - /REMARK="QTV WWW Source Library" - /NOAUTO_CONVERT /AUTO_ADD_USER=VMS_SOURCE /AUTO_MAIL - /ASK_INFO_FILE /ASK_REPL_CAUSE /SHOW_GEN_EXPR /NOSTATISTI - /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 MODIFY CONTEXT/PUBLIC DEFAULT/NOSTREAM/NOFACILITY ! CREATE USER SYSTEM /NAME="System Manager" - /DEF_P=ALL/AUTH_P=ALL/REMARK="System Manager" ! ! Create the CMS ("delta") library directory structure. ! Configure the CMS libraries to use the directory structure: ! STAR$DATA:[QTV.WWW.CMS$DATABASE.'facility'.CMS]. ! Configure the "marker" files to use the directory structure: ! STAR$DATA:[QTV.WWW.CMS$DATABASE.'facility'.SRC]... ! SET DIRECTORY/DELTA_FILES STAR$DATA:[QTV.WWW.CMS$DATABASE] SET DIRECTORY/DELTA_FILES/SUBDIRECTORY=VDE$CMS [.CMS] SET DIRECTORY/DELTA_FILES/SUBDIRECTORY=VDE$MARKER [.SRC] CREATE DIRECTORY_TREE/DELTA_FILES SHOW DIRECTORY/DELTA_FILES ! ! Create the staging area... ! SET DIRECTORY/STAGING STAR$DATA:[QTV.WWW.VDE$STAGING] CREATE DIRECTORY_TREE/STAGING ! ! Create the stream/build directories ! SET DIRECTORY/STAGING 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" CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: A.REQ CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: B.REQ CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: C.B32 CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: D.B32 CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: E.B32 CREATE MODULE/NODELETE/REMARK="VDE self-test module" - /INPUT=SYS$SCRATCH: F.B32 ! EXIT $ $ Exit
Specifies the editor that VDE should use for those VDE commands that invoke an editor.
SET EDITOR "editor-string"
editor-string
The DCL command that VDE should spawn to invoke the desired editor. This string should include the editor name and any desired qualifiers. VDE will append the name of the file to edit to this string when invoking the editor.
The SET EDITOR command specifies the editor that VDE should use when a subsequent VDE command must invoke an editor for you. VDE can invoke an editor for you when you review queued replacements, for example, or when you create a comment file with the ACCEPT or REJECT REPLACEMENT command. In such cases, VDE spawns a DCL command to place you in an editing session. The spawned DCL command is formed by concatenating your editor string, a space, and the name of the file to edit. The editor string that you specify with the SET EDITOR command should thus give the DCL command that invokes your preferred editor, along with any qualifiers that you want for that command.VDE maintains two editor strings in memory for the current VDE session. One string is used for read-write editing and the other for read-only editing. Use the /READ_ONLY qualifier to specify the read-only editor string. If you do not specify a read-only editor string (or if you specify the null string for this case), VDE assumes that the editor you specified with the read-write editor string will accept the /READ_ONLY qualifier (most Digital editors do). In this case, VDE appends the /READ_ONLY qualifier to your read-write editor string to form the read-only editor string. For example, if you specify TPU as the read-write editor string but no read-only editor, then VDE uses the string TPU/READ_ONLY for read-only editing.
The SET EDITOR command always modifies the read-write or read-only editor string for the current VDE session. If you specify the /DEFAULT qualifier, the command in addition writes your current editor settings to the VDE database to establish your default editor strings for future VDE sessions. VDE retrieves these editor strings each time you connect to the VDE database.
If you do not use the SET EDITOR command to declare your preferred editor, VDE uses the system default text editor.
/DEFAULT
Specifies that VDE should write the editor strings for your current session to the VDE database and that those strings should be your default editor strings for future VDE sessions./LOG (default)
/NOLOG
Controls whether log messages are printed after your editor strings are written to the VDE database. The /LOG qualifier causes such messages to be printed and the /NOLOG qualifier suppresses them. These messages, which only appear if you specify the /DEFAULT qualifier, indicate that the editor strings have been updated in the database and that the database transaction has successfully committed./READ_ONLY
Specifies that you are establishing the editor string to use for read-only editing. If this qualifier is omitted, VDE establishes the editor string to use for read-write editing.
| #1 |
|---|
VDE„ SET EDITOR "LSEDIT"
VDE„ SHOW EDITOR
Current editor strings:
Read-write editor string: LSEDIT
Read-only editor string: LSEDIT/READ_ONLY
VDE„
|
This example establishes LSEDIT (which invokes the Language-Sensitive Editor) as your read-write editor string. The SHOW EDITOR command confirms that this is now your current read-write editor string, and it shows that VDE will append the /READ_ONLY qualifier to this string for read-only editing.
| #2 |
|---|
VDE„ SET EDITOR/READ_ONLY "EDIT/EDT/READ"
VDE„ SHOW EDITOR
Current editor strings:
Read-write editor string: LSEDIT
Read-only editor string: EDIT/EDT/READ
VDE„
|
This example defines the editor string to use for read-only editing.
| #3 |
|---|
VDE„ SET EDITOR/DEFAULT "TPU"
%VDE-I-EDITUPDATE, default editor definition updated in the VDE database
%VDE-I-COMMIT, database transaction has successfully committed
VDE„
VDE„ SHOW EDITOR/FULL
Current editor strings:
Read-write editor string: TPU
Read-only editor string: TPU/READ_ONLY
Default editor strings:
Read-write editor string: TPU
Read-only editor string: TPU/READ_ONLY
VDE„
|
This example establishes TPU as your editor. Because the /DEFAULT qualifier is specified, VDE then writes your current editor strings to the VDE database to be used in future VDE sessions. The SHOW EDITOR command shows that these settings have been established both for the current session and as the default for future sessions.
| Previous | Next | Contents | Index |