HP OpenVMS Systems Documentation

HP OpenVMS Alpha Version 7.3--2 Release Notes

This chapter contains information about OpenVMS associated products. Notes specifically related to installation or upgrade issues related to associated products are in subsections to Section 2.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 HP 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 ACMS: Changes in Error Reporting

V7.3-2

When the Application Control and Management System (ACMS) is run on OpenVMS Alpha Version 7.3-2, there are changes in error reporting under the following conditions:

• The account specified in ACMSGEN for ACC_USERNAME has expired.
  Messages reported in prior versions:

  $ ACMS/START SYSTEM/NOTERM %ACMSOPR-E-STRTSYSERR, Error while attempting to START SYSTEM -ACMSOPS-E-ACCDIED, ACC died unexpectedly. -LOGIN-F-ACNTEXPIR, your account has expired; contact your system manager %ACMSOPR-E-ERROR, Some operations may not have been performed

  
  Messages reported in OpenVMS Version 7.3-2:

  $ ACMS/START SYSTEM/NOTERM %ACMSOPR-E-STRTSYSERR, Error while attempting to START SYSTEM -ACMSOPS-E-ACCDIED, ACC died unexpectedly. %ACMSOPR-E-ERROR, Some operations may not have been performed

  
  The exact error can be seen in the accounting file. No errors are reported in the ACMS audit log or in the software event log (SWL) file.
• The account specified for an application does not exist and the application will not start.
  Messages reported in prior versions:

  $ ACMS/START APPL FOO %ACMSOPR-E-STRTAPLERR, Error while attempting to START APPLICATION FOO -ACMSACC-E-APPLTERM, EXC process for application FOO terminated -LOGIN-F-NOSUCHUSER, no such user %ACMSOPR-E-ERROR, Some operations may not have been performed

  
  Messages reported in OpenVMS Version 7.3-2:

  $ ACMS/START APPL FOO %ACMSOPR-E-STRTAPLERR, Error while attempting to START APPLICATION FOO -ACMSACC-E-APPLTERM, EXC process for application FOO terminated %ACMSOPR-E-ERROR, Some operations may not have been performed

  
  The exact error can be seen in the accounting file. The SWL file also has a log of the failure.

V7.3-2

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

Earlier versions of BASIC can install on OpenVMS Version 7.3-2 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.

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

BASIC V1.5A is available on the latest consolidated layered product CD-ROM.

2.4 COBOL: Changes in I/O Run-Time Diagnostics and RMS Special Registers

V7.3

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

2.5 COM for OpenVMS

V7.3-2

For the latest information about COM for OpenVMS, please refer to the following website:

http://h71000.www7.hp.com/openvms/PRODUCTS/DCOM/INDEX.HTML

V7.3-2

Because of changes to the $ACM system service (see Section 5.20), the NTA$LOGON utility now behaves differently in two ways:

• The NTA$LOGON /TYPE qualifier no longer requires IMPERSONATE privilege.
• BATCH is no longer a valid value for the NTA$LOGON /TYPE qualifier. NTA$LOGON now returns an ACME-E-INVREQUEST error if you explicitly specify /TYPE=BATCH, or if you invoke the NTA$LOGON utility in batch mode without explicitly specifying the /TYPE qualifier with a value other than BATCH.
  To avoid this error, specify the /TYPE=NETWORK qualifier in batch mode. For example:

  $ NTLOG*ON :== "$NTA$LOGON.EXE" $ NTLOGON /TYPE=NETWORK NTUSER1 "password"

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.6 DECdfs Version 2.3-3 Required for OpenVMS Version 7.3-2

V7.3-2

To run DECdfs for OpenVMS on OpenVMS Alpha Version 7.3-2, you must install DECdfs Version 2.3-3, which ships with OpenVMS Version 7.3-2. Earlier versions of DECdfs on OpenVMS Alpha Version 7.3-2 will fail to start, resulting in a system bugcheck.

If you have an old version of DECdfs on your system, comment out the @SYS$STARTUP:DFS$STARTUP command from your system startup procedure (SYS$MANAGER:SYSTARTUP_VMS.COM) before upgrading to OpenVMS Version 7.3-2. After you upgrade to OpenVMS Version 7.3-2 and install DECdfs for OpenVMS Version 2.3-3, you can reinstate (uncomment) the DECdfs startup command.

2.7 DECforms Web Connector Version 3.0

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 higher:

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^tm environment is set up systemwide for all processes. HP recommends adding the Java environment setup to the system's SYLOGIN.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 in question is SYS$LIBRARY:DPLI$RTLSHR.EXE.

OpenVMS distributes the following version of the file, which can be identified by 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 higher and find a newer version of DPLI$RTLSHR.EXE, you can either copy it and restore it after the upgrade or reinstall the PL/I kit afterward.

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

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

V7.3-2

To install FMS on OpenVMS Alpha, use the following FMS ECO kit (or a later one):

DECFMSECO5024

The Graphical Configuration Manager (GCM) is included on the Layered Products CD-ROM that ships with the operating system. However, GCM is frequently updated. Check regularly for new versions of the software on the following web page:

http://h71000.www7.hp.com/openvms/products/gcm/index.html

This section contains release notes pertaining to DECram.

2.11.1 DECram Version 3.2 Required for OpenVMS Version 7.3-2

V7.3-2

DECram Version 3.2 is required for OpenVMS Version 7.3-2. This version of DECram ships on the Layered Products CD-ROM and on the Software Products Library CD-ROM.

2.11.2 DECram Version 2.5

V7.3-2

OpenVMS Alpha Version 7.3-2 is the last version to support DECram Version 2.5. In future releases of OpenVMS Alpha, DECram will be included as a System Integrated Product (SIP), and will continue to require a unique license. DECram Version 2.5 will continue to be supported on VAX systems only.

2.11.3 Maximum Disk Size for DECram Version 3.*

V7.3-2

Contrary to what the DECram documentation cites, theoretically the largest value that you can specify for /SIZE and /CAPACITY for DECram Version 3.* is 4,294,967,295 (or %XFFFFFFFF), depending on your available free memory.

However, the largest value that OpenVMS supports is 2,147,483,647 for ODS-2 and ODS-5 volumes.

2.11.4 Earlier Versions of DECram

V7.3-2

DECram Version 3.2 runs on OpenVMS Alpha systems, including Galaxy configurations, running OpenVMS Alpha Version 7.2-2 or higher. DECram Version 3.2 and supporting documentation are included on the Software Products Library and the Online Documentation Library CD-ROMs.

DECram Version 2.5 runs on all versions of OpenVMS for both VAX and Alpha systems. (However, OpenVMS Version 7.3-2 is the last release to support DECram Version 2.5. See Section 2.11.2.) Version 2.5, like Version 3.2, uses IOPOST_LOCAL postprocessing and allocates memory across resource affinity domains (RADs).

The following table summarizes OpenVMS support for versions of DECram:

V7.3-1

It is important to check for disk errors after issuing any DECram command, because not all errors are returned to the user interface. Errors specific to a device are sent to the system error log. Type SHOW DEVICE MD at the DCL prompt to see if any device errors were generated as a result of a DECram command. You will need to use an error log analyzer tool to recover the error. Errors are logged in ASCII file format; you can search for errors with an MD-E-FAILURE prefix in the SYS$SYSROOT:[SYSERR]ERRLOG.SYS file.

2.11.6 DECram and Volume Shadowing

V7.3-1

Using Volume Shadowing for OpenVMS, DECram Version 3.1 and higher can shadow a DECram disk to a physical disk. However, be aware that in the current implementation of Volume Shadowing for OpenVMS, if the physical disk goes away, you will be writing to a volatile disk. A mechanism that will "freeze writes" if the physical disk goes away is planned for a future release of Volume Shadowing for OpenVMS.

2.12 HP DECwindows Motif for OpenVMS

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

2.12.1 Supported Versions

HP DECwindows Motif for OpenVMS Alpha Version 1.3-1 is the only version of DECwindows Motif supported in the OpenVMS Alpha Version 7.3-2 environment. When you install or upgrade to OpenVMS Alpha Version 7.3-2, the DECwindows Motif Version 1.3-1 software is installed automatically if you answer Yes to the question during installation.

2.12.2 Support for LAT Transport Interface Restored

V7.3-2

With OpenVMS Alpha Version 7.3-2, support for the DECwindows Motif interface to the LAT transport, which was withdrawn with HP DECwindows Motif for OpenVMS Alpha Version 1.3, has been restored. This support enables users of X terminal systems, such as the VXT2000, to start LAT X sessions to communicate with systems running DECwindows Motif Version 1.3-1 or higher. It also allows single- and multithreaded client applications running on these DECwindows Motif systems to use the LAT transport to connect to X terminal systems.

Note that the restored LAT interface included with the OpenVMS Alpha Version 7.3-2 operating system can be used as a valid network transport for communication with the DECwindows Motif Version 1.3 and OpenVMS Alpha Version 7.3-2 display servers. However, use with any other communication protocols in the X11R6.6 environment is not supported. This includes communication by or with the following:

• Inter-Client Exchange (ICE) and Session Manager protocols
• Low-Bandwidth X (LBX) proxy servers
• Proxy manager applications
• Font servers

Additionally, HP does not support the use of token-based authentication protocols (such as MIT-MAGIC-COOKIE-1 or MIT-KERBEROS-5) with the restored LAT transport interface.

2.12.3 User-Written Transports No Longer Supported

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 higher.

All existing transports (DECNET, TCPIP, and LOCAL) remain available and function as expected. However, HP no longer provides support for 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.3-1 or greater environment, contact your HP support representative to develop a migration strategy.

2.12.4 Available Language Variants

V7.3-2

The only language variants offered with DECwindows Motif for OpenVMS Alpha Version 1.3-1 are Hebrew and Japanese.

If you require another language variant for DECwindows Motif, contact your HP support representative either to identify a prior version that offers the variant or to discuss options regarding software translation.

2.12.5 System Parameter Values Required for Installation

V7.3-1

The installation procedure for DECwindows Motif for OpenVMS Version 1.3 or higher can fail if the values for the GBLPAGES, FREE_GBLPAGES, and CLISYMTBL system parameters are set too low.

The installation fails with the following error:

%SYSTEM-W-NOSUCHFILE, no such file
\sys$library:decw$xlibshr.exe\

If the installation fails, set these parameters to the minimum values shown in the following table, then reinstall the product.

V7.3

Users of Process Software MultiNet Version 4.3 (or earlier) who are also using DCE should install the UCXDRIVER-041_a043 (or higher) ECO from Process Software. MultiNet Version 4.4 includes this fix.

Refer to the following web site to obtain the most recent patch and any dependencies for your version and/or contact Process Software Technical Support:

The following release notes pertain to HP Pascal.

2.14.1 V5.8A Required to Create STARLET Library

V7.3-2

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

Earlier versions of Pascal can install on OpenVMS Version 7.3-2 if you answer "NO" to 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.

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

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

2.14.2 Installing HP Pascal After an Upgrade

V7.3

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

After upgrading OpenVMS, you should 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 contain any new or corrected definitions supplied by the OpenVMS upgrade.