| Previous | Contents | Index |
All-In-1 directories are normally used only in the USER environment. The standard directory code is A1.
A typical All-In-1 directory would be of the form:
DISK_USER:[JONES_FW.A1]
|
If SysWorks is installed at the system or turnkey level and a user is
registered using SysWorks, this directory will be created for the user
if they are placed in the ALLIN1 system user class, and the users
All-In-1 profile will be set to use this as the All-In-1 directory.
8.5 CDD/Repository
CDD/Repository directories are used as the CDD/Repository anchor directory for an environment.
Typically these directories are used with application environments, although the may be used with the USER or GROUP environments. The standard directory code is CDD.
A typical CDD/Repository directory would be of the form:
DISK_DEV:[FIN.CDD
|
The SDC_CDD
symbol may be used to force another code to be used in place of CDD in
the directory name and any associated logical names.
8.6 Data
Data directories are used to store runtime data for an environment.
They are used to to store data including RMS files and Rdb/OpenVMS database and snapshot files. Applicable to all environment types. This directory is often split across multiple disk volume sets. It is mandatory for dats directories to be located on different volumes to the journal directory, at least in production environments. It is preferable for application environments data directories to be located on different disk volumes to all other directories of the application environment.
Typically these directories are used with application environments, although the may be used with the USER or GROUP environments. The standard directory code is DAT.
A typical data directory would be of the form:
DISK_DEV:[FIN.DAT]
|
The SDC_DAT
symbol may be used to force another code to be used in place of DAT in
the directory name and any associated logical names.
8.7 DECwindows
DECwindows directories are normally used only in the USER environment. The standard directory code is DECW.
A typical DECwindows directory would be of the form:
DISK_USER:[JONES_FW.DECW]
|
The logical name DECW$USER_DEFAULTS points to this directory. If the
directory is not present for a user, the logical name points to
SYS$LOGIN, the users default login directory.
8.8 Dictionary
Dictionary directories are used as the anchor for a CDD/Plus dictionary or CDD/Repository repository.
Typically these directories are used with application environments, although they may be used with the USER or GROUP environments. The standard directory code is CDD.
A typical dictionary directory would be of the form:
DISK_DEV:[FIN.CDD]
|
The SDC_CDD
symbol may be used to force another code to be used in place of CDD in
the directory name and any associated logical names.
8.9 Documentation
Documentation directories are used to store the final target documentation for an application environment such as bookreader and PostScript files and help libraries.
Typically these directories are used with application environments, although they may be used with the USER or GROUP environments. The standard directory code is DOC.
A typical documentation directory would be of the form:
DISK_DEV:[FIN.DOC]
|
The SDC_DOC symbol may be used to force another code to be used in place of DOC in the directory name and any associated logical names.
For each development or maintenance application environment, the documentation directory also contains a sub-directory for each developer who is registered to work on that application environment.
A typical developer specific documentation directory would be of the form:
DISK_DEV:[FIN.DOC.JONES_AB]
|
Journal directories are used to store runtime journaling for an environment such as after and before image journal files for RMS and after image journal files for Rdb/OpenVMS. This directory is applicable to all environment types. It must be placed on a disk different to the data directory in production environments. It is preferable to place it on a different disk in other environments.
Typically these directories are used with application environments, although the may be used with the USER or GROUP environments. The standard directory code is JNL.
A typical journal directory would be of the form:
DISK_DEV:[FIN.JNL]
|
Note thate where journal directories are used, they should not normally be placed on the same disk volume(s) (and hence logical sub-disk(s)) as the data directories.
The SDC_JNL
symbol may be used to force another code to be used in place of JNL in
the directory name and any associated logical names.
8.11 Architecture independent library
Architecture independent library directories are used to contain all the intermediate files which are not architecture dependent i.e. not sources, objects or software. This includes such files as documentation intermediate files and CDD/Repository tag files for an environment.
This directory and its sub-directories are only applicable to development, maintenance and their associated testing environments
Typically these directories are used with application environments, although the may be used with the USER or GROUP environments. The standard directory code is AIL.
A typical library directory would be of the form:
DISK_DEV:[FIN.AIL]
|
The SDC_AIL symbol may be used to force another code to be used in place of AIL in the directory name and any associated logical names.
For each development or maintenance application environment, the architecture independent library directory also contains a sub-directory for each developer who is registered to work on that application environment.
A typical developer specific architecture independent library directory would be of the form:
DISK_DEV:[FIN.AIL.JONES_AB]
|
Library directories are used to contain all the intermediate files which are architecure dependent i.e. not sources or software. This includes such files as object files, object libraries, entry point tag files, test or copy libraries, listing, maps etc.for an environment.
This directory and its sub-directories are only applicable to development, maintenance and their associated testing environments
Typically these directories are used with application environments, although the may be used with the USER or GROUP environments. The standard directory code is LIB.
A typical library directory would be of the form:
DISK_DEV:[FIN.LIB]
|
The SDC_LIB symbol may be used to force another code to be used in place of LIB in the directory name and any associated logical names.
For each development or maintenance application environment, the library directory also contains a sub-directory for each developer who is registered to work on that application environment.
A typical developer specific library directory would be of the form:
DISK_DEV:[FIN.LIB.JONES_AB]
|
The application library directory may have a sub-directory for SCA the Source Code Analyzer.
A typical SCA library directory would be of the form:
DISK_MNT:[FIN.LIB.SCALIB]
|
The application envoronment or group logical SCA$LIBRARY is defined as
this directory. Typically MMS would drive SCA to populate the files in
this direcctory.
8.13 Mail
Mail directories are normally used only in the USER environment. The standard directory code is MAIL.
A typical mail directory would be of the form:
DISK_USER:[JONES_FW.MAIL]
|
If SysWorks is installed at the system or turnkey level and a user is
registered using SysWorks, this directory will be created for the user,
and the users mail profile will be set to use this as the mail
directory.
8.14 Runtime
Runtime directories are used to store runtime logs and reports for an environment. When SysWorks is installed at the system or turnkey levels, it is also the application environment username default directory.
Typically these directories are used with application environments, although the may be used with the USER or GROUP environments. The standard directory code is RUN.
A typical runtime directory would be of the form:
DISK_DEV:[FIN.RUN]
|
For each group or application environment, the runtime directory also contains a sub-directory for each user or developer who is registered to use that group or application environment.
A typical runtime directory would be of the form:
DISK_DEV:[FIN.RUN.JONES_AB]
|
This sub-directory contains user specific log files and reports. This is the default directory after the CONTEXT APPLICATION command is used by a non developer or a developer in a non development or maintenance environment.
For a user, their runtime directory may contain a sub-directories for each group or application environment for which they are registered. When present, these user runtime sub-directories are used in preference to the group or application envirnment sub-directories.
A typical user runtime sub-directory would be of the form:
DISK_USER:[JONES_AB.RUN.FIN_DEV]
|
Note the with application environments, the sub-directory has a name of the form appl_envr.
The SDC_RUN
symbol may be used to force another code to be used in place of RUN in
the directory name and any associated logical names.
8.15 Scratch
Scratch directories are used to provide runtime scartch areas for an environment. The application or group logical name SYS$SCRATCH is defined as this directory. It is preferable for the scratch directory to be on a different disk volume to all other directories. Furthermore, the disk volume should not have disk quotas enabled, so that temporary files (which are created under the UIC of the creating process) may be created.
Typically these directories are used with application environments, although the may be used with the USER or GROUP environments. The standard directory code is SCR.
A typical scratch directory would be of the form:
DISK_DEV:[FIN.SCR]
|
Note that it is common to place all the scratch directories for all application environments on a separate disk volume with no disk quotas. In such a model, applications should handle errors resulting from lack of disk space. Logical names such as SORTWORK0 through SORTWORK9 would point to this directory.
The SDC_SCR
symbol may be used to force another code to be used in place of SCR in
the directory name and any associated logical names.
8.16 Software
Software directories are used to store the final target software for an environment such as DCL command procedures, images, ACMS database files (menu, application and task group) and TDMS request libraries.
This software should be placed in this directory by the build procedure or by MMS. The command procedures that are used with the application standard job must reside in this directory. Typical file types include .ADB, .COM, .EXE, .FORM, .MDB, .RLB and .TDB.
Typically these directories are used with application environments, although they may be used with the USER or GROUP environments. The standard directory code is SFT.
A typical software directory would be of the form:
DISK_DEV:[FIN.SFT]
|
The SDC_SFT symbol may be used to force another code to be used in place of SFT in the directory name and any associated logical names.
For each development or maintenance application environment, the software directory also contains a sub-directory for each developer who is registered to work on that application environment.
A typical developer specific software directory would be of the form:
DISK_DEV:[FIN.SFT.JONES_AB]
|
Source directories are used to store CMS and DTM libraries. This directory and its sub-directories are only applicable to the application common and future development environments and optionally the development environment.
Typically these directories are used with application common environments, although the may be used with other application environments and the USER or GROUP environments. The standard directory code is SRC.
A typical source directory would be of the form:
DISK_APPL:[FIN.SRC]
|
Unlike most other directories, this directory is normally used as a root for other directories such as the CMS library.
The SDC_SRC symbol may be used to force another code to be used in place of SRC in the directory name and any associated logical names.
The application source directory usually has a CMS library subdirectory.
A typical CMS library directory would be of the form:
DISK_APPL:[FIN.SRC.CMSLIB]
|
The application or group logical name CMS$LIB is defined as this directory.
The application source directory may also have a DEC/Test Manager (DTM) library directory. The benchmark and template directories are set to the DTM CMS library.
A typical DTM library directory would be of the form:
DISK_APPL:[FIN.SRC.DTMLIB]
|
The application or group logical name DTM$LIB is defined as this directory.
A typical DTM CMS library directory would be of the form:
DISK_APPL:[FIN.SRC.DTMCMS]
|
Third party software directories are used by an application environment to hold all third party software. The contents of this diectory tree are moved without any change control between different environments of an application.
Typically these directories are used with application common environments, although the may be used with other application environments and the USER or GROUP environments. The standard directory code is TPS.
A typical third party software directory would be of the form:
DISK_DEV:[FIN.TPS]
|
Unlike most other directories, this directory is normally used as a root for other directories such as the CMS library.
The SDC_TPS
symbol may be used to force another code to be used in place of TPS in
the directory name and any associated logical names.
8.19 Test
Test directories are used by an application environment to store test targets such as DCL command procedures and images which are used only for testing, not for normal runtime activities.
Typically these directories are used with application common environments, although the may be used with other application environments and the USER or GROUP environments. The standard directory code is TST.
A typical test directory would be of the form:
DISK_DEV:[FIN.TST]
|
Unlike most other directories, this directory is normally used as a root for other directories such as the CMS library.
The SDC_TST
symbol may be used to force another code to be used in place of TST in
the directory name and any associated logical names.
8.20 Work
Work directories are used by an application environment to store the sources used to build the software. This copy of the source is required by MMS and the compilers as they cannot compile directly from a CMS library. It also makes a reference directory for the CMS library unnecessary - the work directory effectively has a reference copy for the apecific application environment. The sources are fetched from the CMS library into this directory in order for MMS to compile or build them. This directory is only applicable to development, maintenance and and their associated testing environments.
Typically these directories are used with application environments, although the may be used with the USER or GROUP environments. The standard directory code is WRK.
A typical work directory would be of the form:
DISK_DEV:[FIN.WRK]
|
For each group or application environment, the work directory also contains a sub-directory for each user or developer who is registered to use that group or application environment.
A typical developer work directory would be of the form:
DISK_DEV:[FIN.WRK.JONES_AB]
|
These sub-directories are only applicable in development and maintenance environments. This is the default directory after the CONTEXT APPLICATION command is used by a developer.
For a developer, their work directory may contain a sub-directories for each group or application environment for which they are registered. When present, these user work sub-directories are used in preference to the group or application envirnment sub-directories.
A typical developer work sub-directory would be of the form:
DISK_USER:[JONES_AB.WRK.FIN_DEV]
|
Note the with application environments, the sub-directory has a name of the form appl_envr.
The SDC_WRK symbol may be used to force another code to be used in place of WRK in the directory name and any associated logical names.
| Previous | Next | Contents | Index |