VSI OpenVMS ECO Kit

Release Notes


Issues on Systems That Use Multinet

VSI and Process Software have recently identified some issues with the CRTL when using Multinet. These issues may manifest in layered software when using Multinet, such as Samba.

At this time we do not have solutions for these issues. This kit does not address them.

If you are successfully using Multinet for your network stack, VSI strongly recommends you continue with the RTL patch kit version you are currently using and do not update the CRTL via this patch kit or other previous RTL patch kits.

We will address these issues in a future patch kit.

1. Kit Name

VMS842L3I_RTL-V0900

2. Kit Description

2.1. Installation Rating

INSTALL_1: To be installed by all customers.

This installation rating serves as a guide to which customers should apply this remedial kit.

Reference the Disclaimer of Warranty and Limitation of Liability Statement.

2.2. Reboot Requirement

No reboot is necessary after installation of this kit.

However there are additional steps that must be performed to use the images provided by this kit on all nodes of a VMSCluster using a common system disk. Refer to Special Installation Instructions for required post-installation actions.

2.3. Version(s) of VSI OpenVMS to Which This Kit May Be Applied

VSI OpenVMS for Integrity Servers V8.4-2L3

3. Kits Superseded by This Kit

This kit is a superset of all previously released kits for RTL defect repair and the new functionality of the CRTL. These specific kits are superseded:

  • VMS842L3I_RTL-V0800
  • VMS842L3I_RTL-V0600
  • VMS842L3I_RTL-V0500
  • VMS842L3I_RTL-V0400

Note

There was no RTL V7.0 kit.

This kit includes updates for CRTL ECO 9.0.

CRTL ECO 9.0 functionality was previously included in OpenVMS x86_64 V9.2-3 and is now available for other architectures.

This RTL kit version number is V9.0 to keep in sync with the CRTL ECO level of included bugfixes and new functionality.

4. Kit Dependencies

VMS842L3I_DPML-V0200

This provides math library updates needed by the CRTL functionality included in this kit.

Note

The DPML kit must be installed with a separate PRODUCT INSTALL command prior to installing this kit. Do not use the same PRODUCT INSTALL command to install both kits simultaneously.

VMS842L1I_UPDATE-V0100

All new patch kits for VSI OpenVMS for Integrity Servers V8.4-2L1 require the VMS842L1I_UPDATE-V0100 kit.

5. Problems Addressed in This Kit

5.1. CRTL ECO 9.0 Updates to the C Run Time Library

5.1.1. Problem Description

This patch kit provides updated support for the C Run Time Library.

CRTL ECO V9.0 provides various bug fixes and new functions. It is a superset of all previous CRTL ECO updates.

For a complete description of the changes, refer to the additional release notes in:

  • SYS$HELP:VSI_OPENVMS_CRTL_ECO9_RELEASE_NOTES.TXT
  • SYS$HELP:VSI_OPENVMS_CRTL_ECO9_RELEASE_NOTES.PDF

5.1.2. Images and/or Files Affected

  • [SYSLIB]DECC$SHR.EXE
  • [SYSLIB]DECC$SHRP.EXE
  • [SYSLIB]DECC$RTLDEF.TLB

5.1.3. VSI Case Identifiers

  • Jira DEV-1855
  • Jira JDK-204
  • Jiras RTLS-149, 312, 406, 411, 414, 419, 420, 421, 433, 438, 446, 447, 450, 454, 455, 457, 473
  • Bugzilla 4476

5.1.4. Release Version of VSI OpenVMS That Will Contain This Change

Next VSI OpenVMS for Integrity Servers release after V8.4-2L3.

5.2. Correct Regression in malloc() Behavior from RTL V8.0 Patch Kit

5.2.1. Problem Description

A change made to add additional POSIX support in the RTL V8.0 patch kit had unexpected side effects for certain applications.

When support for posix_memalign was added to the VSI OpenVMS malloc code, checks were added for the correctness of pointers passed to the free function. The unintended consequence of this occurred when both malloc and lib$vm_malloc functions were used in the same program. Incorrect behavior when freeing memory could range from spurious errors to access violations, many of which could cause an application failure.

The behavior is corrected with this patch kit, allowing legacy applications to operate as before while continuing to provide better POSIX support for porting to VSI OpenVMS x86-64.

5.2.2. Images and/or Files Affected

  • [SYSLIB]DECC$SHR.EXE

5.2.3. VSI Case Identifiers

  • Jiras RTLS-418, 450
  • Jira SSH-1099
  • Netsuite 6013, 7191

5.2.4. Release Version of VSI OpenVMS That Will Contain This Change

Next VSI OpenVMS for Integrity Servers release after V8.4-2L3.

6. Problems Addressed From Previous Kits

6.1. CRTL ECO V4.0 updates to the C Run Time Library

6.1.1. Problem Description

This patch kit provides updated support for the C Run Time Library.

CRTL ECO V4.0 provides various bug fixes and new functions.

6.1.2. Images and/or Files Affected

  • [SYSLIB]DECC$SHR.EXE
  • [SYSLIB]DECC$SHRP.EXE
  • [SYSLIB]DECC$RTLDEF.TLB
  • [SYSMSG]DECC$MSG.EXE
  • [SYSEXE]GENCAT.EXE

6.1.3. VSI Case Identifiers

  • Various Jira items
  • VSI Bugzilla 4584

6.1.4. Release Version of VSI OpenVMS That Will Contain This Change

Next VSI OpenVMS for Integrity Servers release after V8.4-2L3.

6.2. Spurious Warning Message When Compiling C++ Programs

6.2.1. Problem Description

Depending on the options in use, compiling a C++ program could produce the error message:

%CXX-W-NESTCOMMENT, (1) nested comment is not allowed

The error is from a typo in the closing comment syntax of a math.h definition statement.

The problem is corrected with this patch kit.

6.2.2. Images and/or Files Affected

  • [SYSLIB]DECC$RTLDEF.TLB

6.2.3. VSI Case Identifiers

  • Netsuite 3875
  • Jira RTLS-296

6.2.4. Release Version of VSI OpenVMS That Will Contain This Change

Next VSI OpenVMS for Integrity Servers release after V8.4-2L3.

6.3. CRTL ECO V6.0 Updates to the C Run Time Library

6.3.1. Problem Description

This patch kit provides updated support for the C Run Time Library.

CRTL ECO V6.0 provides various bug fixes and new functions.

6.3.2. Images and/or Files Affected

  • [SYSLIB]DECC$SHR.EXE
  • [SYSLIB]DECC$RTLDEF.TLB

6.3.3. VSI Case Identifiers

  • Various Jira items

6.3.4. Release Version of VSI OpenVMS That Will Contain This Change

Next VSI OpenVMS for Integrity Servers release after V8.4-2L3.

6.4. Various Performance Issues With the C Run Time Library

6.4.1. Problem Description

Recent enhancements to the C Run Time Library exposed some performance issues with products and applications:

  • Samba processes that should have been idle were constantly doing 1000 buffered I/O (BUFIO) operations per second when not handling actual tasks.

  • Oracle and TCPIP$NTP processes get into a compute intensive state when using poll() as a high precision sleep function.

  • Samba reports a network error when transferring large files.

6.4.2. Images and/or Files Affected

  • [SYSLIB]DECC$SHR.EXE

6.4.3. VSI Case Identifiers

  • Jiras RTLS-318, RTLS-319, RTLS-320, RTLS-321
  • Netsuite 4186, 4187, 4207, 4227

6.4.4. Release Version of VSI OpenVMS That Will Contain This Change

Next VSI OpenVMS for Integrity Servers release after V8.4-2L3.

6.5. CRTL ECO V8.0 and V7.0 Updates to the C Run Time Library

6.5.1. Problem Description

This patch kit provides updated support for the C Run Time Library.

CRTL ECO V8.0 provides various bug fixes and new functions. It is a superset of all previous CRTL ECO updates, including ECO V7.0, which was only supplied previously on OpenVMS x86-64 and is now available for other architectures.

6.5.2. Images and/or Files Affected

  • [SYSLIB]DECC$SHR.EXE
  • [SYSLIB]DECC$SHRP.EXE
  • [SYSLIB]DECC$RTLDEF.TLB

6.5.3. VSI Case Identifiers

  • Jiras RTLS-47, 54, 66, 289, 311, 316, 329, 333, 336, 363, 381, 386-389, 391, 392, 395, 396, 398

6.5.4. Release Version of VSI OpenVMS That Will Contain This Change

Next VSI OpenVMS for Integrity Servers release after V8.4-2L3.

6.6. Correct Potential Issues With the LIB$CVT_DX_DX Routine

6.6.1. Problem Description

The run-time library routine LIB$CVT_DX_DX could potentially return an incorrect result or provoke an access violation. This behavior occurred on OpenVMS x86-64 systems due to memory layout changes in the generated code.

The same issue is present for other architectures, although much less likely to occur due to the memory layout differences.

The issue is corrected with this patch kit.

6.6.2. Images and/or Files Affected

  • [SYSLIB]LIBRTL.EXE
  • [SYSLIB]LIBRTL.STB
  • [SYSLIB]LIBRTL.DSF

6.6.3. VSI Case Identifier

  • Jira RTLS-381

6.6.4. Release Version of VSI OpenVMS That Will Contain This Change

Next VSI OpenVMS for Integrity Servers release after V8.4-2L3.

7. Images or Files Replaced

[SYSLIB]DECC$SHR.EXE
Image name:"DECC$SHR"
Image file identification:"V8.4-00"
Image build identification:"XFWL-C6E-000159"
Link identification:"Linker I02-37"
Link Date/Time:22-DEC-2024 14:00:04.78
Image Checksum (MD5):390A77444931AFFD2195ECE16E972412
[SYSLIB]DECC$SHRP.EXE
Image name:"DECC$SHRP"
Image file identification:"V8.4-00"
Image build identification:"XFWL-C6E-000159"
Link identification:"Linker I02-37"
Link Date/Time:22-DEC-2024 14:00:03.75
Image Checksum (MD5):9EA2C3898B11C230866E2C0AADFF1E4B
[SYSLIB]DECC$RTLDEF.TLB
File creation date and time:22-DEC-2024 13:46:16.32
Checksum (MD5):F93C48B2B746AAFA4C73C7188ADE7FDE
[SYSLIB]LIBRTL.EXE
Image name:"LIBRTL"
Image file identification:"X01-001"
Image build identification:"XFWL-C6E-000159"
Link identification:"Linker I02-37"
Link Date/Time:22-DEC-2024 13:59:57.38
Image Checksum (MD5):1715B3126B30BD169BFBDED1AAA35E6C
[SYSLIB]LIBRTL.STB
File creation date and time:22-DEC-2024 13:59:57.45
Checksum (MD5):9DFF7DD0A8000B019F29FF72294A0789
[SYSLIB]LIBRTL.DSF
File creation date and time:22-DEC-2024 13:59:57.42
Checksum (MD5):7710DB755071BDB0FBDB7CB21C65DD32
[SYSMSG]DECC$MSG.EXE
Image name:"DECC$MSG"
Image file identification:"V8.4-00"
Image build identification:"XFWL-C6E-000159"
Link identification:"Linker I02-37"
Link Date/Time:22-DEC-2024 14:00:51.85
Image Checksum (MD5):EC506741BA16E4AC86901C76EC2C9FC2
[SYSEXE]GENCAT.EXE
Image name:"GENCAT"
Image file identification:"V8.4"
Image build identification:"XFWL-C6E-000159"
Link identification:"Linker I02-37"
Link Date/Time:22-DEC-2024 14:00:31.01
Image Checksum (MD5):4A99854845EB71B2EB01DEAAF0A98933

Note

VMS Software, Inc. will only distribute kits in signed form. There is no need for most customers to compare file checksums for security or kit integrity reasons.

However, some sites may require such checking even when using signed kits. The image or file checksums are supplied (in MD5 format) to provide comparisons to the extracted final kit files. To find a file checksum, use:

$ CHECKSUM/ALGORITHM=MD5 filename
$ SHOW SYMBOL CHECKSUM$CHECKSUM

Note

Because a file or image may be replaced by multiple patch kits over time, a PCSI generation number is used to ensure that the latest version of the file or image is preserved on your system during PRODUCT INSTALL of a patch kit. Should a particular kit installation discover a newer version of a file or image in place on the system disk, the following message will be displayed:

%PCSI-I-RETAIN, file <filename> will not be replaced because file from kit has lower generation number

This is a normal occurrence depending on the order of kit installation. The correct version of the file or image will remain on the system after the current kit installation. The %PCSI-I-RETAIN message is informational only and does not indicate a problem.

8. Installation Instructions

8.1. Compressed File

This kit is provided for download within a ZIP archive container file.

The kit files may be extracted on any system with UNZIP and copied to your OpenVMS system, or extracted on your OpenVMS system directly.

Assuming you have created an UNZIP symbol to invoke the UNZIP image, you can invoke UNZIP to unpack the kit on OpenVMS using the command:

$ UNZIP VMS842L3I_RTL-V0900

This will extract the installable PCSI product kit file and its associated signed manifest (_VNC file), used for kit validation during PRODUCT commands.

VSI strongly recommends always using the manifest to validate the kit content during any PRODUCT commands. This will occur automatically if the files are both contained in the same directory.

UNZIP Tool Availability

Most customers likely have already installed a set of ZIP and UNZIP tools on their VSI OpenVMS systems. Should you need these tools, a set of the Info-ZIP freeware ZIP and UNZIP tools for VSI OpenVMS is available for download on the web at this address: https://vmssoftware.com/products/zip-tools/.

8.2. Installation Command

Install this kit with the POLYCENTER Software Installation Utility by logging into the SYSTEM account, and typing the following at the DCL prompt:

$ PRODUCT INSTALL VMS842L3I_RTL [/SOURCE=location_of_kit]

The kit location may be a tape drive, CD/DVD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location.

This kit requires the use of /RECOVERY_MODE and /SAVE_RECOVERY_DATA and will automatically set them; they do not need to be present on the command line.

The release notes for any kit may be extracted prior to kit installation using the PRODUCT EXTRACT RELEASE_NOTES command.

User-selectable options for installation behavior and scripting are available in this kit, refer to Appendix A, User-Selectable Control Options and Scripting Considerations for further details.

Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt.

8.3. Special Installation Instructions

If this kit is being installed in a non-clustered environment, the following steps may be ignored. In a VMScluster with a shared system disk, additional steps must be taken so that the other nodes that share the system disk will use the new images.

Execute the following commands on each node that is sharing the system disk that has been updated:

$ INSTALL REPLACE SYS$LIBRARY:DECC$SHR.EXE
$ INSTALL REPLACE SYS$LIBRARY:DECC$SHRP.EXE
$ INSTALL REPLACE SYS$MESSAGE:DECC$MSG.EXE
$ INSTALL REPLACE SYS$LIBRARY:LIBRTL.EXE

These same commands should be repeated for other systems sharing the system disk if this patch kit is removed via a PRODUCT UNDO PATCH operation.

8.4. Documentation for CRTL ECO 9.0 functionality

Additional documentation for CRTL ECO V9.0 functionality included in this kit is copied to the system disk during kit installation. This documentation is provided both in text format (.TXT) for immediate reference and convenience of using the OpenVMS SEARCH command, and in PDF format for more legible output and convenience for formatted printing or viewing from a browser:

SYS$HELP:VSI_OPENVMS_CRTL_ECO9_RELEASE_NOTES.TXT
SYS$HELP:VSI_OPENVMS_CRTL_ECO9_RELEASE_NOTES.PDF

The release notes for this kit and the above files containing additional documentation may be extracted from the PCSI kit before kit installation for reference and planning purposes. The PCSI kit files are present after extraction from the ZIP archive as described above in Section 8.1, “Compressed File”.

To extract the VSI_OPENVMS_CRTL_ECO9_RELEASE_NOTES.TXT file and the standard kit release notes, use the command:

$ PRODUCT EXTRACT RELEASE_NOTES VMS842L*_RTL /VERSION=V9.0

To extract the PDF format additional documentation, use the command:

$ PRODUCT EXTRACT FILE VMS842L*_RTL /VERSION=V9.0 /SELECT=*.PDF

Either of these commands will create a local copy of the desired file(s) in the current default directory.

An update for the HELP CRTL online help that corresponds to these changes will be contained in a future patch update kit.

9. Copyright

VMS SOFTWARE, INC. CONFIDENTIAL. This software is confidential proprietary software licensed by VMS Software, Inc., and is not authorized to be used, duplicated or disclosed to anyone without the prior written permission of VMS Software, Inc.

Copyright 2024 VMS Software, Inc.

10. Disclaimer of Warranty and Limitation of Liability

This patch is provided as is, without warranty of any kind. All express or implied conditions, representations and warranties, including any implied warranty of merchantability, fitness for particular purpose, or non-infringement, are hereby excluded to the extent permitted by applicable law. In no event will VMS Software, Inc. be liable for any lost revenue or profit, or for special, indirect, consequential, incidental or punitive damages, however caused and regardless of the theory of liability, with respect to any patch made available here or to the use of such patch.

11. Patch ID

I64VMS-VMS842L3I_RTL-V0900--4

A. User-Selectable Control Options and Scripting Considerations

A.1. Controlling Kit Behavior for Introductory Questions

This kit provides user-selectable control options for kit dialogue interaction and automated scripting capability as described here in this appendix.

The general form of a VSI ECO patch kit, when using PRODUCT INSTALL, consists of three initial questions regarding these topics:

  1. System disk backup: A reminder that VSI recommends backing up the system disk before installing patches, followed by a Do you want to continue? yes/no question, default is YES.

  2. Reboot requirement: A summary of whether the kit being installed requires a system reboot, followed by a Do you want to continue? yes/no question, default YES.

  3. Archival of updated files: A description of saving an "_OLD" copy of each image or file updated by the kit, followed by a Do you want to save "_OLD" copies of replaced files? yes/no question, default is NO.

Other questions may be asked later, depending on the target disk or system environment or other kit-specific requirements.

Note

An initial Do you want to continue? question may be asked directly by the PCSI utility during any PRODUCT command – this has nothing to do with the kit being used. To avoid that question, you must supply sufficient detail to uniquely identify the product you wish to use and specify /OPTIONS=NOCONFIRM on the PRODUCT command.

Control options are available to customize the dialogue for the initial three kit questions. The controls are logical names, which may be defined in the process logical name table with a value of YES or NO.

To modify the behavior of the VSI ECO patch kit regarding the initial questions, define one or more of the following logical names before issuing the PRODUCT INSTALL command.

  • To skip one or more of the questions, define the corresponding logical name shown here to YES:

    SKIP$BACKUPSkips system backup awareness question.
    SKIP$REBOOTSkips system reboot awareness question.
    SKIP$ARCHIVE_OLDSkips question about saving "_OLD" files. This will take the default, which is NO.
    SKIP$INTROSkips all three of the above questions.
  • To specifically override the default for saving "_OLD" files, define this logical name to YES or NO:

    VSIKIT$ARCHIVE_OLDSets an answer for saving "_OLD" files behavior. This will skip the archive "_OLD" files question regardless of the above SKIP$* logical names.
  • Two additional logical names may be defined as YES to modify the amount of explanatory text displayed for each question:

    VSIKIT$VERBOSEShows all explanatory text for questions.
    VSIKIT$BRIEFSkips some general details in the explanations.

    The default if neither name is defined is VERBOSE. If both names are defined to YES, VERBOSE overrides BRIEF. The BRIEF form is displayed for any questions that are skipped.

For example, to skip all three questions but save an archive "_OLD" copy of each replaced file:

$ DEFINE VSIKIT$ARCHIVE_OLD YES
$ DEFINE SKIP$INTRO YES
$ PRODUCT INSTALL kitname

A.2. Standard Behavior for YES/NO Questions Asked During Kit Installation

Any YES/NO questions asked during kit installation now follow these rules:

  1. Ctrl/Y issued while a question is being asked will force the current PRODUCT operation to terminate. This is completely safe to do while the initial three questions are being asked during PRODUCT INSTALL as no changes have yet been made to the target disk.

  2. Some questions may ignore Ctrl/Y and ask for a specific answer, if aborting the current operation may have side effects. PCSI may trap Ctrl/Y directly for some PRODUCT operations. Ctrl/Y may be disabled during some sensitive kit processing.

  3. The default YES/NO answer is automatically chosen if a kit is installed from a batch job, unless explicitly overridden by a logical name that provides the particular value, such as VSIKIT$ARCHIVE_OLD.

A.3. Installing a Kit From a Batch Job

To install a kit from a batch job, you will need to fully qualify the kit name so PCSI will have enough information to select the kit without asking for confirmation. For example, to install this kit:

$ PRODUCT INSTALL VMS842L3I_RTL/VERSION=V9.0/OPTIONS=NOCONFIRM
If the kit is located in a directory other than the current default directory, you will also need to add the qualifier:
/SOURCE=location_of_the_kit

For a batch job, any YES/NO question will automatically select the default answer. Use the control logical names explained above to modify the behavior if necessary. For the system disk backup and reboot questions, the batch behavior is identical to the default. For the save "_OLD" files question, define the VSIKIT$ARCHIVE_OLD logical name to YES if you want to save copies of the files, since the batch default is NO.

A.4. Deprecated Logical Names From HPE Patch Kits

The three names listed below were used by older VSI OpenVMS patch kits for compatibility with HPE patch kit behavior. These old names continue to function, but VSI encourages you to modify any scripts you may have to use the new names shown instead:

Old NameNew Name
NO_ASK$BACKUPSKIP$BACKUP
NO_ASK$REBOOTSKIP$REBOOT
ARCHIVE_OLDVSIKIT$ARCHIVE_OLD