HP OpenVMS Systems Documentation

LSE is an optional layered product for all ACMS kits. If the minimum version (or a higher, allowed version) of LSE as identified in the ACMS SPD is not available when you install ACMS, LSE templates for ACMS Version 4.4 are not provided on your system. If you subsequently install LSE, you can make the ACMS Version 4.4 LSE templates available by reinstalling the ACMS Version 4.4 kit and choosing the LSE update option at the beginning of the installation.

1.4.4 Requirements for TP Desktop Connector

Compaq TP Desktop Connector for OpenVMS is an optional layered product for ACMS. If you are installing TP Desktop Connector on a system with ACMS Version 4.0 or higher, you must have at least the minimum version of the TP Desktop Connector as identified in the ACMS SPD.

If the ACMS installation runs while TP Desktop Connector is running, the results are unpredictable. Use the following command to shut down TP Desktop Connector before you begin an installation of ACMS:

$ @SYS$STARTUP:ACMSDI$SHUTDOWN.COM

To ensure problem-free installation of software on your system, install the OpenVMS operating system and layered products in the following order:

1. OpenVMS
2. LSE
3. Oracle Rdb
4. Oracle Trace
5. Oracle CDD
6. Oracle CODASYL DBMS
7. TDMS (VAX only)
8. DECforms
9. ACMS
10. TP Desktop Connector

Upgrading software in a distributed transaction processing system is complex because of the dependencies among the software products. The process becomes even more complex when you take into account the dependencies that are created from multiple versions that exist for each of the individual software products.

Because you cannot upgrade all nodes in a distributed environment simultaneously, and because the upgrade process might last several days, a clear methodology is required to ensure smooth and timely introduction of new software versions.

1.5.1 Configuration Issues

A simple, distributed configuration in a TP system consists of an ACMS front-end node and an ACMS back-end node. You can configure ACMS on each node for the processing of specific tasks. Likewise, the roles of the layered products on each node are distinct. For simple configurations, the upgrade process is straightforward:

1. Upgrade the software on the front-end nodes.
2. Upgrade the software on the back-end nodes.

Upgrading in this order ensures that the system delivers the same version of software to the front-end node and the back-end node.

However, this simple rule cannot be applied to a configuration in which a node is both a front end and a back end. To successfully upgrade a more complex configuration, apply these two key points:

• A component built by a previous software version is compatible with the upgraded version of the software.
  For example, DECforms Version 1.4 can execute a form created by DECforms Version 1.3, without any modification. You can also copy this component from a node on which DECforms Version 1.3 is installed to a node with DECforms Version 1.4. The DECforms Version 1.3 form executes correctly, as long as you do not rebuild the form using Version 1.4.
• Do not rebuild a component under the new software version until you upgrade all nodes to which it may possibly be shipped.

To upgrade software in a distributed system, follow these steps:

1. Upgrade all software on the front-end-only nodes.
2. Upgrade all software on nodes that are both front-end and back-end nodes.
3. Upgrade all software on back-end-only nodes.

Keep in mind the following dependencies when upgrading software, especially in a distributed environment:

• ACMS
  ACMS copies DECforms forms (.FORM) and shareable images (.EXE), TDMS request library files (.RLB), and ACMS application database files (.ADB) from back-end to front-end nodes, if the versions or dates of the files on the back end are more recent.
• Oracle CDD
  CDD versions are interoperable in a distributed environment as long as features of the new version are not requested when using the previous version. CDD is not referenced in the run-time system by the layered products (except possibly by Rdb and DBMS, although this is not advised) except in the case of module recompilation. However, do not recompile or add features until the upgrade is complete.
• DECforms
  See the DECforms SPD for DECforms dependencies.
• OpenVMS Alpha operating system
  When upgrading major versions of the OpenVMS Alpha operating system, you must reinstall ACMS. This applies when upgrading the OpenVMS Alpha operating system from Version 6.x to Version 7.x.
  It is not necessary to reinstall ACMS on OpenVMS VAX systems that have been upgraded from OpenVMS VAX Version 6.x to Version 7.x.
• Oracle CODASYL DBMS
  Remote access between different versions of Oracle CODASYL DBMS is possible as long as features unique to the newer version are not requested of a previous version.
• Oracle Rdb
  Rdb modules are upwardly compatible; for example, modules compiled under Rdb Version 6.0 execute correctly if Rdb is upgraded to Version 7.0 on the system. Remote access between different versions of Rdb is possible as long as features unique to the newer version are not requested of the previous version.
  Because Rdb is the base data repository for many products, particularly CDD and Oracle Trace in a transaction processing system, you must convert all databases (RMU/CONVERT) used by these products after you upgrade Rdb. Refer to the product-specific information for more details.

• Oracle Trace
  Oracle Trace depends on Oracle Rdb since it provides the base data repository, as mentioned above. Refer to the product-specific information for more details.
• Pascal and PL/I (VAX only)
  Changes were made to the Pascal and PL/I include files after ACMS Version 3.1. Some changes may not be compatible with existing programs. If you are upgrading from ACMS Version 3.1, save a copy of the ACMS Version 3.1 definition files, SYS$LIBRARY:ACMSPLI.TLB and SYS$LIBRARY:ACMSPAS.PAS, before installing ACMS Version 4.4, and use these files until you make the necessary modifications to use the correct definitions.
• TDMS (VAX only)
  TDMS request libraries generated since the release of TDMS Version 1.7 are compatible with all later versions of TDMS.

This chapter discusses the preparations and requirements necessary for installing ACMS Version 4.4.

ACMS provides online release notes and gives you the option of printing or displaying the release notes during the installation procedure. Compaq strongly recommends that you read the release notes before proceeding with the installation in case they contain some important information regarding the installation procedure.

The sections in this chapter describe requirements that are checked by the ACMS installation procedure. With the exception of optional layered products, your system must meet these requirements before you can install ACMS successfully.

2.1 Backing Up Your System Disk

At the beginning of the installation, VMSINSTAL asks whether you have backed up your system disk. Compaq recommends that you back up your system disk before installing any software.

Use the backup procedures that have been established at your site to do this backup. For details about performing a system disk backup, see the section on the Backup Utility in the OpenVMS documentation set.

2.2 Software Versions

As discussed in Section 1.4, ACMS Version 4.4 requires minimum versions of a number of layered products. The installation procedure lists all layered products that do not meet or exceed the required minimum version. The ACMS Software Product Description (SPD) identifies the minimum software versions of required and optional products. If any required products are below minimum version, the installation fails.

2.2.1 Installed Images

In order to use other layered products during the installation of ACMS, certain executable images related to those products must be installed using the DCL command INSTALL. These images are normally installed by executing the startup procedure for the product. These startup procedures should be executed automatically when the system is started. Startup procedures are found in SYS$STARTUP.

To determine whether an image is installed, execute the following DCL command:

$ INSTALL LIST file-specification

If an image is not installed, you must execute the related product startup procedure; also ensure that this startup procedure is executed automatically during system startup.

If you are installing the ACMS development kit, the CDD image SYS$LIBRARY:CDDSHR.EXE must be installed. If you are installing the ACMS run-time kit, this is optional; however, if the image is not installed, CDD-related files will not be made available. The CDD startup procedure is CDDSTRTUP.COM.

To use CDD, Rdb must also be available. Therefore, if you are installing the ACMS development kit, or if you plan to use the CDD-related function of the ACMS run-time kit, the Rdb image SYS$LIBRARY:RDBSHR.EXE must be installed. The Rdb startup procedure is RMONSTART.COM.

If you have Oracle Trace installed on your system and you want the ACMS facility definition updated during the installation, the Oracle Trace image SYS$LIBRARY:EPC$FUNCSHRP.EXE must be installed. The Oracle Trace startup procedure is EPC$STARTUP.COM.

2.3 Privileges

To install ACMS, you must be logged in to the SYSTEM account, or any account with similar privileges. The SYSTEM account has all the privileges required for the installation.

Table 2-1 lists the privileges required to execute various steps of the installation.

The following sections describe the approximate disk space requirements for a normal installation, and an option for installing ACMS on a system disk with limited space available.

2.4.1 Disk Space for a Normal Installation

Installing ACMS requires a certain amount of free storage space during the installation. Once ACMS is installed, less storage space is required. Table 2-2 and Table 2-3 summarize the approximate storage requirements for ACMS during and after installation. These tables reflect the installation of full kits, with all options selected.

If you are installing only some parts of the ACMS kits, you need less disk space for the installation. Table 2-4 and Table 2-5 list the approximate amount of space required for each optional component of the ACMS kits.

To determine the number of free disk blocks on your system disk, enter the following command:

$ SHOW DEVICE SYS$SYSDEVICE

If your system disk has less space than indicated in Section 2.4.1, and if you have previously installed ACMS on your system disk, you may be able to install ACMS Version 4.4 by using the VMSINSTAL Alternate Working Device (AWD) option.

The AWD option allows you to specify another disk device on which VMSINSTAL creates its temporary working directory.

For a normal Compaq ACMS for OpenVMS, Version 4.4 development kit installation, VMSINSTAL creates the following temporary working directory:

SYS$SPECIFIC:[SYSUPD.ACMSDEVA_044]

For an AWD installation of the same kit, the VMSINSTAL temporary working directory is:

alternate-working-device:[000000.ACMSDEVA_044]

The space required during installation indicated in Section 2.4.1 must be available on the alternate working device; this space will be available again after the installation is complete. You must still have at least 5000 blocks available on the system disk to use the AWD option.

To determine the number of free disk blocks on your system disk and alternate working device, execute the following commands:

$ SHOW DEVICE SYS$SYSDEVICE
$ SHOW DEVICE alternate-working-device

If disk quotas are enabled on the system disk, the ACMS Installation Verification Procedure (IVP) fails. The ACMS installation procedure normally schedules the IVP to execute automatically after the installation is completed. However, if disk quotas are enabled, the installation procedure cancels the IVP and notifies you. You can choose to stop the installation and address the issue, or continue the installation and execute the IVP manually at a later time.

To determine whether disk quotas are enabled, execute the following DCL command:

$ SHOW QUOTA/DISK=SYS$SYSDEVICE

Table 2-6 and Table 2-7 list the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings.

The following sections describe how to check system parameter values, calculate values for the GBLPAGES and GBLSECTIONS system parameters, change parameter values with the OpenVMS AUTOGEN command procedure, and set the CLISYMTBL dynamic system parameter with the OpenVMS System Generation Utility (SYSGEN).