HP OpenVMS Systems Documentation

This chapter contains information about the OpenVMS associated products. Notes specifically related to installation or upgrade issues of associated products are in Chapter 1.

For notes about using compilers, linkers, and run-time library routines, see Chapter 5.

2.1 Associated Product Support

Information about associated product support is available in the Software Public Rollout Reports for OpenVMS.

The Software Public Rollout Reports for OpenVMS list the availability of the HP software products shipped with the Software Products Library kits (CD-ROM consolidations) for OpenVMS Alpha and OpenVMS VAX and on the Layered Product Library kits (DVD consolidation) for OpenVMS Integrity servers.

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.1.1 HP BASIC for OpenVMS

Because of a change in OpenVMS Version 7.3-2 and later, BASIC versions before V1.5A cannot create the BASIC$STARLET library file during installation.

Earlier versions of BASIC can install on OpenVMS Version 7.3-2 and later, provided you do not request the option to build the STARLET library file. Also, previously installed BASIC compilers and previously created STARLET library files will continue to function after upgrading an older OpenVMS system to Version 7.3-2 and later.

Only the BASIC$STARLET library file creation does not work on OpenVMS Version 7.3-2 and later. The BASIC V1.5A kit contains an enhanced installation procedure that correctly builds the STARLET library file on OpenVMS Version 7.3-2 and later.

BASIC V1.6 is available on the latest consolidated layered product CD.

2.2 HP TCP/IP Services for OpenVMS

V8.4

You must use HP TCP/IP Services for OpenVMS Version 5.7 after upgrading to OpenVMS Version 8.4. For more information, see the HP TCP/IP Services for OpenVMS Version 5.7 Release Notes.

2.3 NetBeans Version 5.5.1 Requires Latest JDK

V8.4

NetBeans Version 5.5.1 for OpenVMS Alpha and OpenVMS Integrity servers is supported only on Java Platform, Standard Edition, Development Kit (JDK) v 1.4.2-7 or higher.

V8.4

When accessing an ODS-5 disk over DFS, if the path specification from the client includes the MFD, the access fails with the error message as shown in the example. If the path specification does not include the MFD, the access succeeds. For example:

Let us assume the access point be DKA100:[USERS] and the client DFS disk be DFSC1001.

$ DIR DFSC1001:[000000]  ! fails with the error message 
 
%DIRECT-E-OPENIN, error opening DFSC1001:[000000]*.*;* 
as input -RMS-E-DNF, directory not found 
-SYSTEM-W-NOSUCHFILE, no such file 
 
$ TYPE DFSC1001:[000000]file.dat  ! fails with the error message  (1) 
 
%TYPE-W-SEARCHFAIL, error searching for DFSC1001:[000000]file.dat 
-RMS-E-DNF, directory not found 
-SYSTEM-W-NOSUCHFILE, no such file 
 
$ DIR DFSC1001:[SUBDIR]  ! works as expected    (2) 

1. file.dat is a file under USERS.DIR.
2. SUBDIR is a subdirectory under USERS.DIR.

This problem is fixed in DECdfs Version 2.4B.

2.5 HP DCE for OpenVMS Restriction (Integrity servers Only)

V8.4

On OpenVMS Version 8.4, installing HP DCE for OpenVMS Version 3.2 by selecting Install or Upgrade Layered Products from the Install menu fails with the following error message:

%PCSI-E-ERROWNER, error in owner specification 'DCE$SERVER' 
-SYSTEM-E-NORIGHTSDB, rights database file not found %PCSI-E-OPFAILED, 
operation failed 

Workaround

To install DCE, mount the OE DVD installation disk on the OpenVMS system and execute the DCE$INSTALL.COM procedure, located in the DCE_I64032 folder.

2.6 XML-C Product Zip File

V8.3-1H1

The XML-C product for OpenVMS for Integrity servers is delivered as a ZIP file that contains a self-extracting executable file. The XML-C installation documentation describes the installation procedure using the executable file. To obtain the executable file, extract it from the ZIP file.

2.7 CMAP Files Added

V8.2

The following new CMAP files are provided in the OpenVMS Version 8.2 internationalization data kit.

DECKANJI2000
GB18030
ISO8859-1-EURO
UTF8-20
UTF8-30

V7.3

Because of the addition of Extended File Support in OpenVMS Alpha Version 7.2, you might notice changes in the handling of the I/O run-time diagnostics and RMS special registers on OpenVMS Alpha Version 7.2 and later. In particular, a long file name that produced RMS$_FNM under versions of OpenVMS Alpha before Version 7.2 now produces RMS$_CRE on OpenVMS Alpha Version 7.2 and later. You need not use the new ODS-5 support to notice the RMS differences.

2.9 COM for HP OpenVMS (Alpha Only)

V8.4

HP COM Version 1.4 for OpenVMS is currently supported on OpenVMS Alpha Version 7.3-2 and later. For information about COM for OpenVMS, see the following website:

V7.3-2

You might get an "Error accessing registry database, contact system manager (0x000025fc)" message if you run a heavy load of COM for OpenVMS applications with the CTLPAGES value set to 256 or less. Set the CTLPAGES value to 512 to avoid this problem.

2.10 Supported Versions of DECdfs

V8.4

DECdfs for OpenVMS Version 2.4B is required for OpenVMS Version 8.4 and later.

V8.3

DECdfs for OpenVMS Version 2.4A is required for OpenVMS Versions 8.3 and 8.3-1H1. If you use an older version of DECdfs, an error message appears.

2.11 DECforms Web Connector Version 3.0 (Alpha Only)

V7.3-1

If you already have DECforms installed, perform the following tasks to enable DECforms Web Connector V3.0 to run on OpenVMS Version 7.3-1 and later:

1. Remove or comment out the following line:

   $ @SYS$COMMON:[JAVA$122.COM]JAVA$122_SETUP.COM

   
   from these command procedures in the FORMS$INSTALL_AREA directory:
   • FORMS_SMGR_STARTUP.COM
   • FORMS_WEB$STARTUP.COM
   • FORMS_WEB_CONFIG.COM
2. Ensure that the Java environment is set systemwide for all processes. HP recommends adding the Java environment setup to the system's SYSLOGIN.COM file.
3. Ensure that the browser clients use the Sun Java Plugin Version 1.2.2, as stated in the SPD and the Administrative guide.

V7.3

There is a known incompatibility between the PL/I RTL distributed with the OpenVMS operating system and the more recent PL/I RTL owned and distributed by Kednos Corporation. The older version shipped with the OpenVMS operating system may overwrite a newer version. The image effected is SYS$LIBRARY:DPLI$RTLSHR.EXE.

OpenVMS distributes the following version of the file, which can be identified using the DCL command ANALYZE/IMAGE:

Image Identification Information 
 
        image name: "DPLI$RTLSHR" 
        image file identification: "V4.0-6" 

If you execute an ANALYZE/IMAGE command before upgrading to OpenVMS Version 7.3 or later and find a newer version of DPLI$RTLSHR.EXE, you can either copy it and restore it after upgrading, or reinstall the PL/I kit.

Any questions about DEC PL/I and VAX PL/I should be directed to Kednos Corporation:

Phone: (831) 373-7003
Email: tom@kednos.com

See a related note in Section 5.35.

2.13 FMS Kits

V8.3

You can install either of the following FMS kits (or later versions) on both the OpenVMS Alpha and OpenVMS Integrity servers:

Full kit: HPFMS025

Run-time kit: HPFMSRT025

FMS V2.5 is supported on OpenVMS V8.2 and later systems (Alpha and Integrity servers).

2.14 HP DECram

This section contains release notes pertaining to DECram.

V8.2

Starting with OpenVMS Alpha and Integrity servers Version 8.2, DECram ships with the OpenVMS operating system as a System Integrated Product (SIP). You must have a DECram license. The DECram driver is located in SYS$COMMON:[SYS$LDR]. Alpha users must remove any remaining SYS$MDDRIVER images in the system-specific directories ([SYSx.SYS$LDR]). For information about removing old versions of DECram before you upgrade to Version 8.2, see the HP OpenVMS Version 8.2 Upgrade and Installation Manual.

If you load any old versions of DECram, the following error message appears:

SYSTEM-W-SYSVERDIF, system version mismatch; please relink 
No older versions of DECram are supported on OpenVMS Version 8.2. 
DECram Version 2.5 will continue to be supported on VAX systems only.  

V8.2

The Encryption for OpenVMS Alpha layered product creates its own DCL command DECRYPT during installation. DECRYPT then overwrites the default definition of DECR, which you might have been using to invoke DECram.

If both products are installed, you can access the DECram interface by defining a DCL foreign command symbol such as:

$ DECRAM == "$MDMANAGER" 

This section contains release notes pertaining to the HP DECwindows Motif for OpenVMS product.

2.15.1 New Locales Added

V8.2

The following new locales, which are used by localized DECwindows Motif software, have been added to the OpenVMS Version 8.2 internationalization data kit.

iw_IL.utf-8 (Hebrew, Israel, UTF-8)
ko_KR.utf-8 (Korean, UTF-8)
zh_CN.utf-8 (Chinese, PRC, UTF-8)
zh_HK.utf-8 (Chinese, Hong Kong, UTF-8)
zh_TW.utf-8 (Chinese, Taiwan, UTF-8)

V7.3-2

In DECwindows Motif Version 1.3 for OpenVMS Alpha, significant changes were made to the DECwindows Motif transport library to accommodate multithreading and the communication needs of the Inter-Client Exchange (ICE) protocol, Low-Bandwidth X (LBX) proxy server, and Input Method servers. As a result, HP has discontinued support for user-written network transports on systems running DECwindows Motif Version 1.3 or later.

All existing transports (DECnet, TCP/IP, LAT, and LOCAL) remain available and function as expected. However, HP no longer supports designing and implementing user-written transports based on the updated transport interface. The VMS DECwindows Transport Manual has been archived, and the new libraries are not publicly available.

If you have implemented a custom transport and want to migrate that transport to the DECwindows Motif Version 1.5 or greater environment, contact your HP support representative to develop a migration strategy.

2.16 HP Secure Web Server Version Support

V8.2

OpenVMS Alpha Version 7.3-2 and OpenVMS Version 8.2 (Alpha and Integrity servers) are the last releases on which the Secure Web Server (SWS) Version 1.3-* is supported. OpenVMS Alpha Version 7.3-2 is the last release on which SWS Version 2.0 is supported.

The functional replacement for SWS Version 1.3-* and SWS Version 2.0 is SWS Version 2.1. All future new features and enhancements to SWS will be provided beginning with SWS Version 2.1, which is based on the Apache 2.0.* open source code base.

SWS Version 1.3-* and SWS Version 2.0 will be supported while OpenVMS Alpha Version 7.3-2 is in Prior Version Support (PVS) status, and SWS Version 1.3-* will be supported as long as OpenVMS Version 8.2 is supported. Support for these SWS versions will include remedial fixes and security fixes as deemed appropriate.

2.17 HP Pascal for OpenVMS Alpha Systems

The following release notes pertain to HP Pascal for OpenVMS Alpha systems.

2.17.1 HP Pascal: Version 5.8A (or later) Required to Create STARLET Library (Alpha Only)

V7.3-2

Because of a change in OpenVMS Version 7.3-2, Pascal versions before V5.8A cannot create the STARLET library files during installation.

Earlier versions of Pascal can install on OpenVMS Version 7.3-2 or later, if you answer "NO" when prompted with the option to create and install the STARLET library files. Also, previously installed Pascal compilers and previously created STARLET library files will continue to function after upgrading an older OpenVMS system to Version 7.3-2 or later.

It is only the STARLET library creation portion of the Pascal installation that does not work on OpenVMS Version 7.3-2 or later. The Pascal V5.8A kit contains an enhanced installation procedure to correctly build the STARLET library files on OpenVMS Version 7.3-2 or later.

Pascal V5.8A is available on the latest consolidated layered product CD.

2.17.2 Installing HP Pascal After an Upgrade (Alpha Only)

V7.3

This note applies to any version of HP Pascal and any version of the OpenVMS Alpha operating system.

After upgrading OpenVMS, reinstall HP Pascal to produce new versions of STARLET.PAS and other definition files to match the upgraded system.

If you do not reinstall HP Pascal after upgrading OpenVMS, the compiler on your system will still work correctly. However, STARLET.PAS and the other definition files will not include any new or corrected definitions supplied by the OpenVMS upgrade.

2.18 WEBES and SEA Support on Integrity servers

V8.3

The latest version of WEBased Enterprise Services (WEBES) is available at the WEBES website: