VSI ACMS Version T5.3-7 for OpenVMS (Field Test)

Release Notes


1. Introduction

VSI is pleased to introduce the field test of Application Control and Management System (ACMS) T5.3-7 for VSI OpenVMS.

2. What's New In This Release?

VSI ACMS T5.3-7 for OpenVMS introduces an updated and improved installation procedure. It also includes several bug fixes detailed below.

The installation procedure has been updated to handle the existence of both CDD and VDD on the target system.

  • If the system has both VDD and CDD installed, the ACMS-required definitions will be updated in both VDD and CDD.

  • If the system has VDD installed, the ACMS Installation Verification Procedure (IVP) will use VDD.

For details on ACMS and VDD, refer to their respective documentation sets available at https://docs.vmssoftware.com/.

3. Software Requirements

VSI ACMS T5.3-7 for OpenVMS requires the following software:

  • One of the following versions of VSI OpenVMS:

    • VSI OpenVMS x86-64 Version 9.2-3 + Update V3 or higher

    • VSI OpenVMS IA-64 Version 8.4-2L1 or higher

  • VDD X1.2-03 or higher (ACMS DEV kit only)

  • The ACMS DEV kit on OpenVMS IA-64 requires either VDD or CDD.

  • The ACMS DEV kit on OpenVMS x86-64 requires VDD.

4. Known Issues and Limitations

The following issues have been discovered/reported at the time of this field test:

  • On OpenVMS x86-64, the main application images of all ACMS server and agent applications must be loaded in the P0 memory region. To achieve this, link your ACMS applications via the following command:

    $ LINK/SEGMENT_ATTRIBUTE=CODE=P0

    Warning

    ACMS will crash if you do not perform this action.

    This restriction is expected to be permanent for ACMS on OpenVMS x86-64 systems.

  • If the DECC$FILE_SHARING logical name is defined on your system, the ACMSADU BUILD GROUP command will create an empty object file due to a crash in the MACRO compiler.

  • The AVERTZ sample application currently cannot be built due to dependencies on Oracle CDD and Oracle Rdb.

  • Installing ACMS images as resident (by running the ACMS startup script using the RESIDENT parameter) has no effect on OpenVMS on x86-64. The RESIDENT parameter is ignored, and the following message is displayed:

    $ @SYS$STARTUP:ACMSTART RESIDENT
    ACMSTART-I-NOTSUPPORTED, RESIDENT is not supported on OpenVMS x86-64
    systems

    This restriction is expected to be permanent for ACMS on OpenVMS x86-64 systems.

  • SWL logging sometimes fails to log a message due to exceptions when formatting the messages. Several instances of this issue have been fixed with ACMS T5.3-7.

5. Bug Fixes and Enhancements

In ACMS T5.3-7

  • Previously, the Installation Verification Procedure (IVP) could fail due to incorrect terminal settings. This problem has been fixed.

  • The explanatory text displayed during an installation failure has been improved.

  • Previously, in extremely rare situations, an exception during ACMS rundown could cause a system crash on IA-64. This issue has been resolved.

In ACMS T5.3-6A

  • When running ACMS applications with multiple agents, ACMSEXC would sometimes crash under load. This issue has been fixed.

  • Several performance improvements have been made to ACMS on OpenVMS x86-64.

  • ACMSEXC would sometimes crash in rare situations if an agent program got interrupted or crashed. This issue has been fixed.

  • If ACMS was installed on a system with VDD, installation-related logical names would be left behind. This issue has been fixed.

In ACMS V5.3-5

Issues with STDL generation. Some of the changes made in ACMS V5.3-2 to fix a reported problem with STDL generation for certain data types (as noted here) turned out to be breaking the data types for the right and left separate numeric. To fix this, the STDL files generation for those data types has been restored to the pre-V5.3-2 behaviour.

This issue was reported and fixed in VSI NetSuite NS4661/Jira ACMS-24.

In ACMS V5.3-4

The ACMS tracing mechanism that uses Oracle Trace has been updated and now functions correctly.

This issue was reported and fixed in VSI NetSuite NS2321/Jira ACMS-16.

In ACMS V5.3-3

  • Introduced support for VSI TCP/IP V10.6. The ACMS Remote Management components have been built against both HPE TCP/IP and VSI TCP/IP. During ACMS installation, images for both implementations of TCP/IP are installed. At run time, the implementation of TCP/IP will be determined, and the correct images will be used.

  • The calculated value for the ACMS parameter MSS_POOLSIZE would not allow the IVP to run under the following conditions:

    1. A new ACMS installation

    2. A system with a very high MAXPROCESSCNT

    This bug was originally reported and fixed in ACMS V5.3-2 (as noted here) but was revisited in ACMS V5.3-3 because the fix introduced in ACMS V5.3-2 did not work in the situations listed above.

In ACMS V5.3-2

  • The ACMS IVP would fail if certain ACMSGEN parameters were calculated improperly based on the corresponding VMS SYSGEN parameters. Specifically, MSS_POOLSIZE is based on MAXPROCESSCNT and on systems with a large MAXPROCESSCNT, MSSPOOLSIZE is too low. The problem is that the ACMSIVP does not use site-specific ACMSGEN parameters, and instead uses the default ACMSGEN values. The fix is to always use the site-specific ACMSGEN parameters for the ACMS IVP.

    This issue was reported and fixed in VSI external Bugzilla #1236.

  • STDL generation for certain data types was not consistent with what was generated in previous versions of ACMS. See below for the fix for QuiX QXCM1001162971. That fix happened after HPE ACMS V5.1B was released, and was not released to all ACMS customers by HPE. That fix broke STDL generation for scaled integer data types. This VSI fix preserves the packed decimal fix and restores the prior, correct behaviour of STDL generation for scaled integers.

    This issue was reported and fixed in VSI external Bugzilla #1324.

  • Non-privileged users were unable to debug ACMS tasks, getting the following error:

    $ ACMS/DEBUG VR_TASK_GROUP
    ACMSDBG> START VR_UPDATE_SERVER
    Terminal is in SERVER VR_UPDATE_SERVER
    %ACMSDBG-I-SPDIED, Server VR_UPDATE_SERVER stopped unexpectedly
    -LOGIN-F-FILEACC, error accessing system authorization file

    This issue was reported and fixed in VSI external Bugzilla #1398.

In ACMS V5.3-1

In the ACM$TASK_INFORMATION data structure, the device name field was inadvertently increased by one byte. This caused the applications built on ACMS versions prior to VSI ACMS V5.3 to fail due to a misalignment in ACM$TASK_INFORMATION. Applications that were built or rebuilt on VSI ACMS V5.3 would work properly.

This issue was reported and fixed in VSI external Bugzillas #1161 and #1148.

In ACMS V5.3

These fixes were released as patches for HPE ACMS V5.1B but were not included in VSI ACMS V5.2, as VSI ACMS V5.2 was based on HPE ACMS V5.1B.

  • The ACMSATR LIST command generates a large number of alignment faults.

    This issue was reported and fixed in QXCM1001296226.

  • ACMS generates incorrect STDL for Packed Decimal data type. With this fix, ACMS will now generate the correct STDL for packed decimal data.

    This issue was reported and fixed in QXCM1001162971.

  • Alignment faults in ACMSEXC process. With this fix, the ACMSEXC process no longer produces alignment faults.

    This issue was reported and fixed in QXCM1001189746.

  • ACMS process crashes with NATFAULT in TIE$SHARE. With this fix, processes should no longer crash with a foot NATFAULT in TIE$SHARE

    This issue was reported and fixed in QXCM1001339184.