Document revision date: 19 July 1999

This chapter contains installation and support information about OpenVMS layered products. Notes about using compilers, linkers, and run-time library routines are included in Chapter 5.

2.1 Layered Product Support

Information about layered product support is available in the Software Public Rollout Reports for OpenVMS. The Software Public Rollout Reports for OpenVMS list the availability of Compaq's software products shipping on the Software Products Library kits (CD-ROM consolidations) for OpenVMS Alpha and OpenVMS VAX.

The reports contain the product name and version, the operating system version required to support the product, and the volume ship date for the product. The information in these tables is continually evolving and is subject to change. The reports are intended for public distribution and are updated monthly. The information is not provided in these release notes because of the changing nature of the information.

2.2 Advanced Server V7.2 for OpenVMS (Alpha Only)

V7.2

Advanced Server V7.2 for OpenVMS and PATHWORKS V6.0B for OpenVMS are the only OpenVMS file server products supported on OpenVMS Version 7.2. These products supersede PATHWORKS for OpenVMS (Advanced Server) Version 6.0 and 6.0A, which are not supported on OpenVMS Version 7.2. PATHWORKS V6.0B for OpenVMS (Advanced Server) ships on both VAX and Alpha Version 7.2 systems.

Advanced Server V7.2 for OpenVMS ships with the OpenVMS Alpha Version 7.2 kit. (It is not supported on OpenVMS VAX.) If you are upgrading to Advanced Server V7.2 for OpenVMS from an earlier version of PATHWORKS for OpenVMS, you must first upgrade to PATHWORKS V6.0B.

For information about upgrading from PATHWORKS for OpenVMS and about installing Advanced Server for OpenVMS, refer to the Advanced Server for OpenVMS Server Installation and Configuration Guide provided with the kit documentation.

Features

Advanced Server for OpenVMS includes the following features:

• OpenVMS Registry support
  The Advanced Server provides network users with access to the OpenVMS Registry. The Advanced Server also stores its own configuration data in the OpenVMS Registry.
  When you upgrade from PATHWORKS for OpenVMS to Advanced Server for OpenVMS, the server configuration parameters are automatically migrated from the LANMAN.INI file to the OpenVMS Registry. The Advanced Server provides the PWRK$REGUTL utility to manage server configuration parameters in the OpenVMS Registry.
  The server parameters in the OpenVMS Registry can also be viewed and managed from a Windows NT-based registry editor.
  See Section 5.17 for more information about the OpenVMS Registry.
• Extended File Specifications support
  Advanced Server disk shares can be stored and managed on ODS-5 devices, providing better integration with Windows 98, Windows 95, and Windows NT file systems.

Requirements

To access Advanced Server for OpenVMS on OpenVMS Version 7.2, clients must be licensed using the new Advanced Server V7.2 license PAK: PWLMXXXCA07.02. Refer to the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses for more information.

The Advanced Server requires that the OpenVMS Registry be available when the server is started. The server startup procedure starts the registry server if it is not available. Compaq recommends that the OpenVMS Registry be configured and started before you install and configure the Advanced Server for OpenVMS software.

2.3 DEC BASIC

This section contains release notes pertaining to DEC BASIC.

2.3.1 Problems and Restrictions

The following note describes a build restriction for DEC BASIC Version 1.2.

2.3.1.1 BASIC$STARLET.TLB Build Restriction (Alpha Only)

V7.0

The restriction described in this release note applies to using DEC BASIC Version 1.2 on OpenVMS Alpha Version 7.0 or later. The restriction does not apply to DEC BASIC Version 1.3. The introduction of 64-bit support for system services prevents the proper construction and use of BASIC$STARLET.TLB on OpenVMS Alpha systems.

If you do not need any of the system definitions from STARLET, take the default for the following question when installing DEC BASIC:

Do you want to install the OpenVMS AXP system definitions (10 min.) [NO]?

If you do need system definitions from STARLET, there are two possible workarounds:

• If you need only a few definitions, you can construct your own include library using the STARLET definitions as a guide.
• If you require a number of system definitions, you must construct your own copy of BASIC$STARLET.TLB, as follows:
  1. Before installing DEC BASIC, make a copy of STARLETSD.TLB in SYS$LIBRARY. Be sure no one uses STARLETSD.TLB until you have completed building BASIC$STARLET.TLB.
  2. Edit your copy of SYS$LIBRARY:STARLETSD.TLB to remove any system definitions that refer to 64-bit integers by value. (DEC BASIC does not support these, so you will not need them.)
  3. Install DEC BASIC and request that the system definitions be installed.
  4. When the DEC BASIC installation is complete, delete your copy of SYS$LIBRARY:STARLETSD.TLB. A usable copy of BASIC$STARLET.TLB will be in SYS$LIBRARY.
     It is now safe for other users to access STARLETSD.TLB.

This section contains release notes pertaining to DEC C and DEC C++.

2.4.1 Changes and Enhancements

The following note describes a change in how STARLET header files now ship on OpenVMS VAX.

2.4.1.1 STARLET Header Files Now Ship with OpenVMS VAX

V7.1

Starting with Version 7.1, OpenVMS VAX directly supplies the STARLET header files for DEC C and DEC C++ in SYS$LIBRARY:SYS$STARLET_C.TLB, as has always been done on OpenVMS Alpha systems. DEC C and DEC C++ compiler Versions 5.2 or later are required to access the STARLET headers. See a warning about installing earlier DEC C and DEC C++ compiler versions on OpenVMS VAX Version 7.1 or later in Section 2.4.2.1.

The content of the STARLET headers has also been edited to correct deficiencies in versions supplied by the DEC C and DEC C++ compilers in releases prior to Version 7.1.

2.4.2 Problems and Restrictions

The following notes describe problems associated with DEC C and DEC C++.

2.4.2.1 Pre-Version 5.2 Kits May Delete SYS$STARLET_C.TLB (VAX Only)

V7.1

Installing a version of the DEC C or DEC C++ compiler older than Version 5.2 on OpenVMS VAX Version 7.1 or later may damage or delete SYS$LIBRARY:SYS$STARLET_C.TLB. (See Section 2.4.2.2 for another warning about installing DEC C++ Version 5.3 on OpenVMS VAX Version 7.1 and later.)

2.4.2.2 DEC C++ Version 5.3 Installation Fails (VAX Only)

V7.1

When you attempt to install DEC C++ Version 5.3 on VAX systems running OpenVMS Version 7.1 or later, the installation fails because the Version 5.3 kit fails to install the system headers on OpenVMS Version 7.1 and later.

DEC C++ Version 5.4 fixes these problems.

2.5 DEC Pascal

This section contains release notes pertaining to DEC Pascal.

2.5.1 Problems and Restrictions

The following note describes a potential problem with an older version of DEC Pascal.

2.5.1.1 Installing DEC Pascal Version 5.5 After an Upgrade (Alpha Only)

V7.1

After upgrading to OpenVMS Alpha Version 7.1 or later, you should reinstall DEC Pascal to produce new versions of STARLET.PAS and other definition files to match the upgraded system.

If you do not reinstall DEC Pascal after upgrading to OpenVMS Alpha Version 7.1 or later, the compiler on your system will still work correctly. However, STARLET.PAS and the other definition files will not contain any of the new definitions added in Version 7.1 and later.

Note that because of changes in OpenVMS, the DEC Pascal Version 5.5 kit can sometimes go into an infinite loop when it is installed on OpenVMS Alpha Version 7.1 or later. This problem is solved in DEC Pascal Version 5.6.

2.6 DEC PL/I

This section contains release notes pertaining to DEC PL/I for OpenVMS.

2.6.1 Problems and Restrictions

The following note describes a DEC PL/I restriction.

2.6.1.1 RTL Support for OpenVMS

V7.2

The RTL that ships with OpenVMS Version 7.2 has not been tested with OpenVMS Version 7.1 or 7.2, and therefore is not supported.

However, the RTL that ships with DEC PL/I Version 4.2 and later is supported on OpenVMS Versions 7.1 and 7.2.

2.7 DECdfs for OpenVMS

This section contains release notes pertaining to DECdfs.

2.7.1 Problems and Restrictions

The following note cites the consequences of using an old version of DECdfs for OpenVMS.

2.7.1.1 Version 2.3 Required for OpenVMS Alpha

V7.2

If you want to run DECdfs for OpenVMS on OpenVMS Alpha Version 7.2, you must install Version 2.3. Do not install earlier versions of DECdfs on OpenVMS Alpha Version 7.2; your system will crash. DECdfs for OpenVMS Version 2.3 ships with OpenVMS Version 7.2.

DECdfs for OpenVMS Version 2.3 is also recommended for OpenVMS VAX Version 7.2 systems. Earlier versions of DECdfs for OpenVMS may not cause your OpenVMS VAX system to crash, but DECdfs will function with limited capacity.

2.8 DECforms

This section contains release notes pertaining to DECforms.

2.8.1 Problems and Restrictions

The following note describes a DECforms support issue.

2.8.1.1 Support on OpenVMS Version 7.0 and Later (Alpha Only)

V7.0

Because of changes in DECthreads, DECforms Version 2.1 does not work with OpenVMS Alpha Version 7.0 and later. Installing OpenVMS Alpha Version 7.0 or later causes existing applications based on DECforms Version 2.1 to fail; installing DECforms Version 2.1 on OpenVMS Alpha Version 7.0 or later also fails. In both cases, you get the following error message:

%CMA-F-USE_ERROR, requested operation is inappropriate for the specified object

For DECforms based applications to operate correctly on OpenVMS Alpha Version 7.0 and later, you must run DECforms Version 2.1A or later.

2.9 DECnet Layered Products

This section contains release notes pertaining to the DECnet layered products.

2.9.1 Problems and Restrictions

Several restrictions for DECnet layered products are covered elsewhere in this manual, as follows:

• External authentication requirements:
  • For DECnet Phase IV (See Section 4.8.2.3.)
  • For DECnet Phase V (See Section 4.8.2.8.)
• DECnet-Plus MOP satellite boot service restriction (See Section 4.14.2.2.)

The following release note documents a correction to the DECnet-Plus for OpenVMS Network Management manual.

2.9.2.1 DECnet-Plus for OpenVMS Network Management

V7.2

Section 8.4.2.1 of the DECnet-Plus for OpenVMS Network Management manual incorrectly states that DECnet-Plus for OpenVMS supports up to 16 circuits. In fact, the maximum number of circuits that can be created really is 4, as stated in the Software Product Description. The configuration utility (NET$CONFIGURE.COM) now imposes a limit of 4 circuits.

2.10 DECpresent

This section contains a release note pertaining to installing DECpresent.

2.10.1 Problems and Restrictions

The following note describes a dependence for installing DECpresent.

2.10.1.1 Installation Dependency on OpenVMS VAX Version 6.1 or Later

V6.1

To run DECpresent Version 1.0A on OpenVMS VAX Version 6.1 or later, you must upgrade the CDA Converter Library from Version 1.1 to Version 2.0.

When installing DECpresent Version 1.0A on OpenVMS VAX Version 6.1 or later, system managers can safely ignore the IVP failure for the CDA Converter Library Version 1.1 because that version of the product is bundled with DECpresent, but does not work on OpenVMS VAX Version 6.1 and later.

After installing DECpresent Version 1.0A on OpenVMS VAX Version 6.1 or later, or upgrading from VMS Version 5.5--2 to Version 6.1 or later with DECpresent Version 1.0A already installed on the system, system managers should install CDA Converter Library Version 2.0.

2.11 DECram

This section contains a release note about DECram support.

2.11.1 Problems and Restrictions

The following note describes a DECram support limitation.

2.11.1.1 DECram Version 2.3 Is Required (Alpha Only)

V7.2

OpenVMS Alpha Version 7.2 requires DECram Version 2.3. Do not install earlier versions of DECram on OpenVMS Alpha Version 7.2.

Table 2-1 summarizes DECram support on OpenVMS.

Table 2-1 DECram Support on OpenVMS

OpenVMS Platform/Version	Minimum Version	Recommended Version
Alpha Version 7.2	Version 2.3	Same
Alpha Version 6.2 through 7.1--1H x	Version 2.2F	Version 2.3
VAX Version 6.2 through 7.2	Version 2.2C	Version 2.2F

Furthermore, do not try to upgrade from OpenVMS Alpha Version 6.2 to Version 7.0 or later if you have DECram Version 2.2C or earlier installed. Attempting to do so prevents the system from booting. To avoid this problem, follow these steps:

1. Rename the DECram executable image, using the DCL command RENAME, as shown in the following example:

   $ RENAME SYS$SPECIFIC:[SYS$LDR]DECRAM$EXECLET.EXE - _$ SYS$SPECIFIC:[SYS$LDR]OLD_DECRAM$EXECLET.EXE

2. Upgrade OpenVMS Alpha.
3. Install DECram Version 2.3.

DECram Version 2.3 and supporting documentation are included in the OpenVMS Version 7.2 kit, on an OpenVMS Version 7.2 CD-ROM, in the following directory:

[.DECRAM_023]

This version of DECram is not architecture-specific. It can be used on systems running either OpenVMS Alpha or OpenVMS VAX.

For more information about the contents of the DECram directory, refer to the Guide to OpenVMS Version 7.2 CD--ROMs.

	privacy and legal statement
6534PRO_004.HTML