This chapter describes creating an application enviroment manually.

When installed at the System or Turnkey level, SysWorks is normally used to create application environments using the Application Management Menu. This chapter also provides a guide to the actions which SysWorks takes when performing such tasks.

11.1 Directories

To set up an application environments directory structure library manually, the following steps should be used. If SysWorks is installed at the Turnkey level or at the System level where it is used to manage the system, all these steps are executed as part of the Add an application or the Create an application's environment task.

1. Ensure that the SysWorks root logical names have been defined. This normally done in the site specific startup procedure SWRK_LCL_DIR:site_PRE_STARTUP.COM. Each root logical name should be defined using a command such as:

   $ DEFINE/SYSTEM/EXECUTIVE_MODE DISK_envnn device:[env_nn.] - _$ /TRANSLATION=(CONCEALED,TERMINAL)

2. If the application common structures have not yet been defined, create them as follows:

   $ CREATE/DIRECTORY DISK_APPLnn:[appl] $ CREATE/DIRECTORY DISK_APPLnn:[appl.SRC]

3. Create the application environment structures as follows:

   $ CREATE/DIRECTORY DISK_envnn:[appl] $ CREATE/DIRECTORY DISK_envnn:[appl.DAT] $ CREATE/DIRECTORY DISK_envnn:[appl.DOC] $ CREATE/DIRECTORY DISK_envnn:[appl.RUN] $ CREATE/DIRECTORY DISK_envnn:[appl.SFT]

4. If the application environment is used to build software (eg. development, maintenence and testing environments) create the construction directories as follows:

   $ CREATE/DIRECTORY DISK_envnn:[appl.LIB] $ CREATE/DIRECTORY DISK_envnn:[appl.WRK]

5. If the application environment is used to construct a kit (eg. testing environments) create the kit directory as follows:

   $ CREATE/DIRECTORY DISK_envnn:[appl.KIT]

6. Create other site specific directories as appropriate.

To set up a CMS library manually, the following steps should be used. If SysWorks is installed at the Turnkey level or at the System level where it is used to manage the system, steps 1 through 6 are executed as part of application environment setup.

1. Create the OpenVMS directory for the common CMS library using a command such as:

   $ CREATE/DIRECTORY DISK_APPLn:[appl.SRC.CMSLIB]

2. Create the CMS library using a command such as:

   $ CMS CREATE LIBRARY DISK_APPLn:[appl.SRC.CMSLIB]/NOREFERENCE - _$ "Appl common CMS library"

3. Create the initial CMS classes for each environment using commands such as:

   $ cms CMS> CREATE CLASS appl_DEV "Development class" CMS> CREATE CLASS appl_DTST "Development testing class" CMS> CREATE CLASS appl_MNT "Maintenance class" CMS> CREATE CLASS appl_MTST "Maintenance testing class"

4. Create the initial elements using a command such as:

   $ CMS CREATE ELEMENT *.*/INPUT=DISK_DEV:[appl.WRK] "Initial version"

   
   This should create a set of initial generations.

5. If they weren't created with the initial elements above, insert template DCL command procedures using commands such as:

   $ CMS CREATE ELEMENT ENTER.COM_SRC- _$ /INPUT=SWRK_SFT_DIR:ENTER_APPL_ENV.TEMPLATE "Base procedure" $ CMS CREATE ELEMENT EXIT.COM_SRC- _$ /INPUT=SWRK_SFT_DIR:EXIT_APPL_ENV.TEMPLATE "Base procedure" $ CMS CREATE ELEMENT LOGICALS.COM_SRC- _$ /INPUT=SWRK_SFT_DIR:LOGICALS_APPL_ENV.TEMPLATE "Base procedure"

6. Copy the above template files into the application development environment software directory using commands such as:

   $ COPY SWRK_SFT_DIR:ENTER_APPL_ENV.TEMPLATE appl_SFT_DIR:ENTER.COM $ COPY SWRK_SFT_DIR:EXIT_APPL_ENV.TEMPLATE appl_SFT_DIR:EXIT.COM $ COPY SWRK_SFT_DIR:LOGICALS_APPL_ENV.TEMPLATE appl_SFT_DIR:LOGICALS.COM

7. Move to the applications development environment using a command such as:

   $ CONTEXT APPLICATION appl DEV

   
   This should result in the new application development environment's LOGICALS.COM and ENTER.COM command procedures being executed. The template LOGICALS.COM should define the appl_CMS_PATH logical name to have a value of appl_DEV+.

8. Insert all the initial generations into the development class using a command such as:

   $ CMS INSERT GENERATION *.*/GENERATION=1 appl_DEV "Initial version"

9. Build the initial version using a command such as:

   $ BUILD/BATCH/FROM_SOURCES

10. Copy the minimum required DCL command procedures into the development testing directory using a command such as:

    $ COPY appl_SFT_DIR:ENTER.COM,EXIT.COM,LOGICALS.COM - _$ DISK_DTST:[appl.SFT]

    
    This is so that the following TRIAL will work when it uses the CONTEXT command to moe to the development testing environment.

11. Move the initial version into development testing using a command such as:

    $ vsnctl trial Target environment [DTST]: Override CMS reservations (Yes/No) [No]: Build (Yes/No) [Yes]: From sources or work area (Source/Work) [Work]: Execution (Batch/Detached/Online/Subprocess) [Batch]: Batch queue [SYS$BATCH]: Execute after [NOW]:

    
    This should cause the same generations as are in the development class to be placed into the development testing class.

12. Move to the applications development testing environment using a command such as:

    $ CONTEXT ENVIRONMENT DTST

13. Release the initial version of the application using a command such as:

    $ vsnctl release Test environment [DTST]: Version [V1.0]: Execution (Batch/Detached/Online/Subprocess) [Batch]: Batch queue [SYS$BATCH]: Execute after [NOW]:

    
    This should cause the same generations as are in the development and devlopment testing class to be placed into the release class.

14. Split the release into its continued development and maintenance streams using a command such as:

    $ vsnctl split Version: V1.0 Development environment [DEV]: Build (Yes/No) [Yes]: Development testing environment [DTST]: Maintenance environment [MNT]: Build (Yes/No) [Yes]: Maintenance testing environment [MTST]: Keep existing maintenance version (Yes/No) [Yes]: Execution (Batch/Detached/Online/Subprocess) [Batch]: Batch queue [SYS$BATCH]: Execute after [NOW]:

    
    This should result in the release class retaining its existing generation 1 members, the development and development testing classes having generation 2 members and the maintenance and maintenance testing classes having generation 1A1 members. All the generations of an element should have the same contents and modification date. The development and maintenance streams are now in separate brances of the generation tree so they can be merged in the future.

To grant access to a developer manually, the following steps should be used. If SysWorks is installed at the Turnkey level or at the System level where it is used to manage the system, all these steps are executed as part of the Grant a user access to an application task.

1. Create the OpenVMS directories for the developer using commands such as:

   $ CREATE/DIRECTORY DISK_envnn:[appl.RUN.username] $ CREATE/DIRECTORY DISK_envnn:[appl.WRK.username]