======================================================================= VMS Software, Inc. OpenVMS ECO Kit Release Notes ======================================================================= 1 KIT NAME: VMS923X_UPDATE-V0300 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 attached Disclaimer of Warranty and Limitation of Liability Statement. 2.2 Reboot Requirement: A reboot is mandated as part of installing this kit, performed automatically following the kit installation. VSI OpenVMS for the x86-64 architecture uses a memory disk image, stored on the system disk, when booting the system. The content of the memory disk must remain consistent with the system disk content. This kit updates the memory disk image and invokes a system reboot sequence (shutdown with reboot) directly as part of the kit installation. You must be prepared to allow the system reboot when installing the kit. After all other kit actions are complete, the system will automatically shutdown and reboot. If you allow the reboot, you will have the choice of whether to invoke the site-specific shutdown procedure, SYS$MANAGER:SYSHUTDWN.COM, during the shutdown portion of the reboot. By default, after installation completes, the minutes until shutdown is zero. If you wish to leave additional time before the shutdown begins, define the system logical name SHUTDOWN$MINIMUM_MINUTES as the integer value of the wait time in minutes. For example: $ DEFINE/SYSTEM SHUTDOWN$MINIMUM_MINUTES 10 No other options for the shutdown may be specified. The shutdown will commence directly after the memory disk update as the final portion of the kit installation. 2.3 Version(s) of VSI OpenVMS to which this kit may be applied: VSI OpenVMS x86-64 V9.2-3 2.4 Target disk requirements This kit will create a new memory disk image file during PRODUCT INSTALL or PRODUCT UNDO PATCH operations. This file is required for x86-64 systems bootstrap. If this file cannot be correctly created, the target disk will not be bootable and you will need to restore from backup. During PRODUCT INSTALL, the kit will check for sufficient space on the target disk. The minimum free space is 600,000 blocks to ensure that the memory disk image file and kit files can safely fit on the disk. Additionally, a check is made to determine if the disk is too fragmented to correctly create the memory disk file. If either check fails, the installation will be aborted before making any changes. After you take any necessary corrective actions to free up disk space or defragment the volume, the PRODUCT INSTALL operation can be re-attempted. These same checks are not automatically handled by the kit before a PRODUCT UNDO PATCH operation. This is not a frequent operation for customer systems. If you need to remove this kit, you should ensure sufficient disk space before you start. The same total 600,000 block minimum applies. To check fragmentation requirements, you can use the following commands: $ ANALYZE/DISK/EXTENTS/REQUIRED=200000/NOOUTPUT $ SHOW SYMBOL ANALYZE$REQUIRED_EXTENTS If the symbol value is 25 or more, the disk is too fragmented. You should defragment the disk before using PRODUCT UNDO PATCH, by using a defragmentation tool or restoring an image backup. 3 KITS SUPERSEDED BY THIS KIT: VMS923X_UPDATE-V0100 VMS923X_UPDATE-V0200 4 KIT DEPENDENCIES: VMS923X_PCSI-V0100 Note: The VMS923X_PCSI-V0100 kit must be installed prior to installing this kit, using a separate PRODUCT INSTALL command. The kits may not be jointly installed with a single PRODUCT INSTALL operation. 5 PROBLEMS AND CHANGES ADDRESSED IN THIS KIT New problem and change notes table of contents for Update V3.0 kit ================================================================== SYS changes -- Notes 5.1 to 5.8 ------------------------------- 5.1 Problems with reserving large amounts of memory 5.2 Flood of Math Fault exceptions may affect system performance or crash 5.3 MTXCNTNONZ bugcheck when using SYSMAN CLASS_SCHEDULE ADD 5.4 OPCOM process goes compute-bound until system reboot 5.5 Enabling audit alarms for privilege failure impacts system performance 5.6 Performance improvement for message handling routines 5.7 Cannot boot x86-64 system with over 2 TB physical memory 5.8 Various issues with writing system crash dump files RTL changes -- Notes 5.9 to 5.10 -------------------------------- 5.9 Various corrections for the C++ Run-Time Library 5.10 Internal LIBOTS memory routines performance enhancements DEBUG changes -- Note 5.11 -------------------------- 5.11 Various corrections to OpenVMS Debugger behavior Security changes -- Notes 5.12 to 5.14 -------------------------------------- 5.12 Changes to SET PASSWORD/GENERATE 5.13 Corrections to proxy account creation, modification, or removal 5.14 SHOW AUDIT command displays multiple "Process:" prefixes ACME changes -- Notes 5.15 to 5.16 ---------------------------------- 5.15 Changes to OpenVMS ACME support 5.16 Output from $ SHOW SERVER ACME may contain null characters I/O device support changes -- Notes 5.17 to 5.25 ------------------------------------------------ 5.17 MOUNT/MEDIA_FORMAT=FILES11 on a DVD may hang or get read errors 5.18 VirtIO-SCSI devices on Oracle OCI are offline and cannot be used 5.19 Data corruption might occur with files on a VirtIO-SCSI disk 5.20 System may hang during boot if many VirtIO devices are configured 5.21 Cannot mount or use a physical LDDRIVER device 5.22 Systems with very large physical memory may not boot 5.23 Some SATA devices may not be recognized or configured 5.24 Various errors on QLogic Fibre Channel card during startup or shutdown 5.25 32Gb Fibre Channel HBA requires V9.2-3 UPDATE V2.0 or later LAN changes -- Notes 5.26 to 5.28 --------------------------------- 5.26 LAN Bandwidth Monitoring issues with system time adjustments 5.27 LANCP commands to enable or disable jumbo frames are confusing 5.28 Various LANCP tracing improvements MACRO programming support -- Note 5.29 -------------------------------------- 5.29 Updates to the MACRO compiler Cluster changes -- Notes 5.30 to 5.31 ------------------------------------- 5.30 Provide diagnosis hints for lost connection cluster messages 5.31 Use better default PEDRIVER Load Class for newly discovered devices RMS changes -- Note 5.32 ------------------------ 5.32 Spurious process terminations from RMS exception XQP changes -- Note 5.33 ------------------------- 5.33 System may crash with rare spurious XQPERR bugcheck Miscellaneous changes -- Notes 5.34 to 5.36 ------------------------------------------- 5.34 $ SHOW PATH/DEVICE may encounter spurious access violation 5.35 JBC$COMMAND works correctly, but returns spurious error 5.36 VMSINSTAL procedure may not accept passwords 5.37 Allow terminals connected via OpenSSH to run SHUTDOWN.COM ----- SYS changes ----- 5.1 Problems with reserving large amounts of memory 5.1.1 Problem Description The SYSMAN RESERVED_MEMORY mechanism may be used to reserve memory sections for specific application use. The following issues are corrected with this ECO kit: - SYSMAN RESERVED_MEMORY ADD may erroneously report that insufficient memory is available. - After adding a large reserved memory section, the system may hang or crash with an INCONSTATE bugcheck after rebooting. - The SHOW MEMORY/RESERVED command might display incorrect totals for reserved memory or exit with an ACCVIO status. This behavior could occur with this command from DCL or from within SDA when using ANALYZE/SYSTEM. 5.1.2 Images and/or Files Affected: [SYS$LDR]EXEC_INIT.EXE [SYS$LDR]EXEC_INIT.STB [SYS$LDR]SYSTEM_PRIMITIVES.EXE [SYS$LDR]SYSTEM_PRIMITIVES.STB [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB [SYSEXE]SHOW.EXE [SYSLIB]SDA$SHARE.EXE [SYSMSG]CLIUTLMSG.EXE 5.1.3 VSI case identifier Jira BO-2131, BO-2132, BO-2169 Netsuite NS8441 5.1.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.2 Flood of Math Fault exceptions may affect system performance or crash 5.2.1 Problem Description On x86-64, the system might trigger a "math fault" exception if a floating-point exception occurs. Many of these are masked or handled by compiler-generated code, but those which are not handled may wreak havoc on the system if the offending code continuously encounters the floating-point exceptions. Should a system encounter such a flood of exceptions, they will be reported as non-fatal INCONSTATE bugchecks. If the system parameter BUGCHECKFATAL is set to 1, the system will crash with an INCONSTATE bugcheck. If BUGCHECKFATAL is set to 0, the ERRFMT process will become very busy and the error log file will grow rapidly. This behavior has been mitigated by establishing a default math fault exception handler. Should there be no application handler set up to trap these types of exceptions, they will be turned into the appropriate SS$_FLTxxx_F status and signaled to the caller. 5.2.2 Images and/or Files Affected: [SYS$LDR]EXCEPTION.EXE [SYS$LDR]EXCEPTION.STB [SYS$LDR]EXCEPTION_MON.EXE [SYS$LDR]EXCEPTION_MON.STB 5.2.3 VSI case identifier Jira BO-2243, BO-2244 Netsuite NS8690 5.2.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.3 MTXCNTNONZ bugcheck when using SYSMAN CLASS_SCHEDULE ADD 5.3.1 Problem Description An error accessing the created schedule array causes the code to unexpectedly exit without releasing the CLASS mutex. A later sanity check then triggers the MTXCNTNONZ bugcheck. This is corrected with this ECO kit. 5.3.2 Images and/or Files Affected: [SYSLIB]SMI$OBJSHR.EXE 5.3.3 VSI case identifier Jira UT-362, UT-363 Netsuite NS8863 5.3.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.4 OPCOM process goes compute-bound until system reboot 5.4.1 Problem Description Under rare circumstances, the OPCOM process might encounter an access violation and end up in a compute-bound infinite loop. The OPCOM mailbox MBA2 might get full when heavy system load generates many OPCOM messages. This can result in a stale timer context that causes an access violation. The OPCOM processing loops on the broken context, sending the process compute-bound. A system reboot is likely the only way to clear the condition. This problem is corrected with this ECO kit. 5.4.2 Images and/or Files Affected: [SYS$LDR]IO_ROUTINES.EXE [SYS$LDR]IO_ROUTINES.STB [SYS$LDR]IO_ROUTINES_MON.EXE [SYS$LDR]IO_ROUTINES_MON.STB 5.4.3 VSI case identifier Netsuite NS8922 5.4.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.5 Enabling audit alarms for privilege failure impacts system performance 5.5.1 Problem Description On all VSI OpenVMS V9.x versions, enabling security audits for privilege failure generates a large number of audits for attempted use of SYS$CMKRNL without the CMKRNL privilege. These alarms are triggered for non-privileged users running certain user-mode programs, including some standard system utilities. The EXCEPTION execlet contains a message display routine used primarily by VSI engineering to debug the exception routines. However, even when the trace code was disabled, a SYS$CMKRNL call was needlessly generated in user and supervisor modes. If the process executing this path lacked the CMKRNL privilege, a security alarm was logged. Systems with audit alarms enabled for privilege failure suffered a significant performance impact for an operation that produced no useful work. This issue is corrected with this ECO kit. 5.5.2 Images and/or Files Affected: [SYS$LDR]EXCEPTION.EXE [SYS$LDR]EXCEPTION.STB [SYS$LDR]EXCEPTION_MON.EXE [SYS$LDR]EXCEPTION_MON.STB 5.5.3 VSI case identifier Jira BO-2340 Netsuite NS8996 5.5.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.6 Performance improvement for message handling routines 5.6.1 Problem Description Message processing to access message vectors that should always be accessible were invoking PROBE instructions to validate access. PROBE instruction emulation is expensive on x86-64. The message processing is now changed to use an exception handler for access violations on disallowed access. Since this would be a very rare circumstance, the PROBE cost can be eliminated for successful access at the expense of an exception when access is not allowed. Overall, this eliminates a performance penalty for correctly behaving code. Because the message services are executed in caller's mode, there is no danger to skipping the PROBEs and allowing the exception to occur for access error handling. 5.6.2 Images and/or Files Affected: [SYS$LDR]MESSAGE_ROUTINES.EXE [SYS$LDR]MESSAGE_ROUTINES.STB 5.6.3 VSI case identifier Jira UT-382 5.6.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.7 Cannot boot x86-64 system with over 2 TB physical memory 5.7.1 Problem Description An incorrect sanity check for memory configuration made it impossible to boot an x86-64 system with more than 2 TB of physical memory. This problem is now corrected. 5.7.2 Images and/or Files Affected: [SYS$LDR]SYSTEM_PRIMITIVES.EXE [SYS$LDR]SYSTEM_PRIMITIVES.STB [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 5.7.3 VSI case identifier Jira DRIV-638 5.7.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.8 Various issues with writing system crash dump files 5.8.1 Problem Description The Dump Kernel writes the dump file after a system crash on an OpenVMS x86-64 system. The following issues have been corrected in the Dump Kernel: - The Dump Kernel crashed if many disk ports were configured. - Fibre Channel devices were not always found. - Very large crash dump files could not be written. - Many spurious "Unexpected unmatched PTE/PFN pair" messages might be displayed during crash processing. 5.8.2 Images and/or Files Affected: [SYSEXE]SYS$DUMP_KERNEL.EXE 5.8.3 VSI case identifier Jira BO-2240, DRIV-638 5.8.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- RTL changes ----- 5.9 Various corrections for the C++ Run-Time Library 5.9.1 Problem Description The following issues are corrected with this ECO kit: - The internal condition handler for the C++ Run-Time Library corrupts the sigargs parameter for non-C++ errors. This could cause an access violation or other incorrect behavior during exception error handling. This issue was previously addressed in the HOTFIX V4.0 kit for the customer reporting the problem. - An incompatibility between standard exceptions and std::string32 is now resolved. - Symbol table names within the LIBCXX.EXE image are now correctly uppercased. 5.9.2 Images and/or Files Affected: [SYSLIB]LIBCXX.EXE [SYSLIB]LIBCXX.OLB [SYSLIB]LIBCXXABI.EXE [SYSLIB]LIBCXXABI.OLB 5.9.3 VSI case identifier Jira DEV-3106, DEV-3165 Netsuite NS8777 5.9.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.10 Internal LIBOTS memory routines performance enhancements 5.10.1 Problem Description Some of the most used Object-Time Library routines in LIBOTS.EXE have been rewritten in native x86-64 assembler to provide better performance. This includes the memory handling routines to move, compare, search, and translate characters. 5.10.2 Images and/or Files Affected: [SYSLIB]LIBOTS.EXE [SYSLIB]LIBOTS.STB 5.10.3 VSI case identifier Jira RTLS-518 5.10.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- DEBUG changes ----- NOTE: Some of the changes in the Debugger may work in conjunction with changes in the most recent version of a corresponding language compiler. VSI recommends using the latest version of the language compilers to provide the best experience when using the Debugger. 5.11 Various corrections to OpenVMS Debugger behavior 5.11.1 Problem Description The following issues in the Debugger are corrected with this ECO kit: - STEP/NOSHARE ignored the /NOSHARE qualifier. - Programs linked with the /BASE=0 parameter could not be debugged. The STEP command worked like GO, and the program output was disrupted. - In 'single step by instruction' mode, the Debugger did not stop after a 'jmpb' instruction. - Debugger might crash on startup. - The Debugger did not display the elements of an array which was passed by descriptor. - The Debugger incorrectly displayed indirect 'jmpq' instructions, truncating the target address. - Debugger EXAMINE of a character array might display irrelevant extra symbols beyond the array bounds. - The Debugger might run past a 'jmpb' instruction that has a negative offset. - When stopping at the start of a routine, the Debugger prints an extra line number after the routine name. - The Debugger does not display the cell type of a Pascal packed array. - DEPOSIT of double-precision floating-point values fails. - A breakpoint at the start of a routine may be ignored. - Local variables are not displayed after a STEP/RETURN command. - The Debugger does not display COBOL packed decimal string type. - When stopping at a label, the label name is not displayed. - The Debugger crashes on start when a variant part in the program has a name. - When examining an array in BASIC, raw addresses are shown rather than symbol names. - EXAMINE of %XMMn registers could be inconsistent or might return an error. - Source lines in C++ programs could not be displayed. - Incorrect values displayed from EXAMINE/TYPE command when the value is an unaligned bitstring. - The Debugger MONITOR command causes an internal memory error. - The Debugger did not understand forward DWARF references from C++ programs. The user-visible symptom for this problem was error messages similar to these: %DEBUG-I-INFODWARF, error reading Dwarf info: forward ref (0000008C) for spec attr not supported -DEBUG-I-DWARFLOC, error occurs 0000002E bytes into .debug_info, in unit TEST - The Debugger was unable to interpret DWARF 4 packed-decimal attributes. 5.11.2 Images and/or Files Affected: [SYSLIB]DEBUG.EXE [SYSLIB]DEBUGSHR.EXE [SYSLIB]DEBUGUISHR.EXE 5.11.3 VSI case identifier Jira DEV-1807,2456,2761,2768,2777,2778,2800,2901,2903,2908,2974 DEV-3012,3015,3023,3024,3036,3058,3066,3078,3079,3088 DEV-3108,3114,3123,3142,3147,3151,3181,3205 5.11.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- Security changes ----- 5.12 Changes to SET PASSWORD/GENERATE 5.12.1 Problem Description The following changes for the SET PASSWORD/GENERATE command are provided in this ECO kit: - Generated passwords may now be up to 64 characters long. The previous limit was 32 characters. - SET PASSWORD/GENERATE did not generate passwords when PWDMINIMUM was 0. This has been corrected. 5.12.2 Images and/or Files Affected: [SYSEXE]AUTHORIZE.EXE [SYSEXE]LOGIN_ACME.EXE [SYSEXE]LOGIN_UAF.EXE [SYSEXE]SETP0_ACME.EXE [SYSEXE]SETP0_UAF.EXE 5.12.3 VSI case identifier Jira UT-352, UT-358 5.12.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.13 Corrections to proxy account creation, modification, or removal 5.13.1 Problem Description The following corrections affect the behavior of the ADD/PROXY, MODIFY/PROXY, and REMOVE/PROXY commands in AUTHORIZE and the resulting security audit messages produced from those commands: - When adding three or more proxy accounts to a proxy record, the data contained in the "New:" line for proxy audits may be incorrect. Additionally, some of the preset string values may have a spurious period character at the end. - Changes to proxy records with multiple local users were not recorded properly. Updating a proxy record to change the default user or one of several local users was not properly recorded in the proxy database or in the corresponding audit. - REMOVE/PROXY would not remove a local user from a proxy record. The command would fail claiming no matching user, with messages similar to: UAF> REMOVE/PROXY TAO::FRED PROX1 %UAF-E-NAFREMERR, error removing proxy from TAO::FRED to PROX1 -SECSRV-E-NOSUCHUSER, no user matches your specification - Proxy commands which modify the Default User in a proxy record triggered an audit always containing "" for the value of the New and Original Default User data. The New or Original proxy account fields in the audit message now have the appropriate corresponding username. 5.13.2 Images and/or Files Affected: [SYSEXE]SECURITY_SERVER.EXE 5.13.3 VSI case identifier Jira BO-1829, BO-2100, BO-2189, BO-2190, BO-2215, BO-2241 5.13.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.14 SHOW AUDIT command displays multiple "Process:" prefixes 5.14.1 Problem Description The SHOW AUDIT command output for process events requiring multiple display lines may include extra "Process:" prefixes. For example, before the correction from this ECO kit: $ SHOW AUDIT /ALARM System security alarms currently enabled for: ACL Authorization Audit: illformed Process: CREPRC,DELPRC,SCHDWK,CANWAK,WAKE,SUSPND,RESUME,GRANTID,REVOKID, Process: FORCEX,SIGPRC,SETPRI,PROCESS_CAPABILITIES,PROCESS_AFFINITY, SET_IMPLICIT_AFFINITY Breakin: dialup,local,remote,network,detached Login: batch,dialup,local,remote,network,detached,server Logfailure: batch,dialup,local,remote,network,subprocess,detached,server After the correction in this kit: $ SHOW AUDIT /ALARM System security alarms currently enabled for: ACL Authorization Audit: illformed Process: CREPRC,DELPRC,SCHDWK,CANWAK,WAKE,SUSPND,RESUME,GRANTID,REVOKID, FORCEX,SIGPRC,SETPRI,PROCESS_CAPABILITIES,PROCESS_AFFINITY, SET_IMPLICIT_AFFINITY Breakin: dialup,local,remote,network,detached Login: batch,dialup,local,remote,network,detached,server Logfailure: batch,dialup,local,remote,network,subprocess,detached,server 5.14.2 Images and/or Files Affected: [SYSEXE]SHOW.EXE 5.14.3 VSI case identifier Jira BO-886 5.14.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- ACME changes ----- NOTE: If you change the login mechanism from ACME to UAF or from UAF to ACME after installing this kit, you will need to take an additional step if you later remove the kit using PRODUCT UNDO PATCH. Refer to the information in Section 8.4 in the installation instructions below. 5.15 Changes to OpenVMS ACME support 5.15.1 Problem Description The following changes or issues in the OpenVMS ACME Agent are addressed in this ECO kit: - The ACME Agent can now use SET PASSWORD/GENERATE to generate passwords of up to 64 characters. The previous limit was 32 characters. - Authentications could fail when the system is configured with the ACME Server and OpenSSH, and passwords exceed 16 characters. - For ACME Server-enabled systems, the SET PASSWORD command would accept passwords with illegal characters and return success for accounts without the PWDMIX flag set. - When the ACME Server is the default login mechanism, the SET PASSWORD command could hang or return an ACME$_TIMEOUT error, even though the password was successfully changed. - For ACME Server-enabled systems, login attempts may spuriously fail or timeout. This might be accompanied by event messages in the ACME Server log file, SYS$MANAGER:ACME$SERVER.LOG, ending with either or both of these error messages: ACME-E-ASTCTXNOTFND, AST context not found LOGIN-F-TEXT, When called by FINISH_PROCESSING Preface found TEMP_CSCHED_CTX not NULL at start In some cases the ACME Server process might exit with an error and restart itself, producing a process crash dump file, SYS$SYSTEM:ACME_SERVER.DMP. 5.15.2 Images and/or Files Affected: [SYSLIB]VMS$VMS_ACMESHR.EXE 5.15.3 VSI case identifier Jira BO-2128, BO-2171, BO-2325, BO-2383, BO-2384 LDAP-185 5.15.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.16 Output from $ SHOW SERVER ACME may contain null characters 5.16.1 Problem Description Output from $ SHOW SERVER ACME can contain null characters as part of the node name string. With the correction in this ECO kit, the null characters are correctly replaced with spaces. 5.16.2 Images and/or Files Affected: [SYSEXE]ACME_SERVER.EXE 5.16.3 VSI case identifier Jira BO-881, BO-2182 Netsuite NS3354 5.16.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- I/O device support changes ----- 5.17 MOUNT/MEDIA_FORMAT=FILES11 on a DVD may hang or get read errors 5.17.1 Problem Description If a DVD is mounted with /MEDIA_FORMAT=FILES11 to use the file system to read OpenVMS content, the process may hang or encounter incorrect data when the device is read. A DVD- or CR-ROM I/O reads in 2K bytes, and there were edge conditions where either insufficient data was read or stale data from a previous read could be returned. These issues are corrected with this ECO kit. Additionally, a sanity check has been added to ensure that only 32-bit values can be used for DVD LBN (logical block number) values in case the device appears to have more blocks due to read errors. 5.17.2 Images and/or Files Affected: [SYS$LDR]SYS$DKDRIVER.EXE 5.17.3 VSI case identifier Jira BO-2133 5.17.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.18 VirtIO-SCSI devices on Oracle OCI are offline and cannot be used 5.18.1 Problem Description VirtIO-SCSI devices on Oracle OCI appear as offline and cannot be used. This was due to missing support for the device type. Support for SCSI-3 SPC-6 versions has been added to DKDRIVER, and these devices can now be used. 5.18.2 Images and/or Files Affected: [SYS$LDR]SYS$DKDRIVER.EXE 5.18.3 VSI case identifier Jira DRIV-566 5.18.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.19 Data corruption might occur with files on a VirtIO-SCSI disk 5.19.1 Problem Description Files on VirtIO-SCSI disks could encounter spurious data corruption. This is highly dependent on data format and usually only occurs on very large files. This problem is corrected with this ECO kit. 5.19.2 Images and/or Files Affected: [SYS$LDR]SYS$VSPDRIVER.EXE [SYS$LDR]SYS$VSPDRIVER.STB 5.19.3 VSI case identifier Jira BO-2147, BO-2148 Netsuite NS8343 5.19.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.20 System may hang during boot if many VirtIO devices are configured 5.20.1 Problem Description The system could hang at boot if a large number of VirtIO-Net and/or VirtIO-SCSI adapters are configured. Some device-specific capability checks were incorrectly using the wrong interrupt mode. The platform bus probing now correctly finds and configures these devices. 5.20.2 Images and/or Files Affected: [SYS$LDR]SYS$PCIE_SUPPORT.EXE [SYS$LDR]SYS$PCI_SUPPORT.EXE 5.20.3 VSI case identifier Jira DRIV-549 5.20.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.21 Cannot mount or use a physical LDDRIVER device 5.21.1 Problem Description If an LD CONNECT command is issued to a physical device instead of the usual container file target, then the created LDxxx device cannot be mounted and the error status SS$_ILLBLKNUM is returned. The issue is corrected with this ECO kit. 5.21.2 Images and/or Files Affected: [SYS$LDR]SYS$LDDRIVER.EXE 5.21.3 VSI case identifier Jira DRIV-559 5.21.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.22 Systems with very large physical memory may not boot 5.22.1 Problem Description A system might fail to boot from an LSI Logic SCSI disk if the physical memory size is greater than roughly 270 GB (the limit might vary depending on SYSGEN parameters). This was due to restrictions in the LSI adapter that required 32-bit physical memory addressing. This issue is corrected with this ECO kit. 5.22.2 Images and/or Files Affected: [SYS$LDR]SYS$PKMDRIVER.EXE 5.22.3 VSI case identifier Jira DRIV-592, BO-2174, BO-2175 Netsuite NS8549 5.22.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.23 Some SATA devices may not be recognized or configured 5.23.1 Problem Description SATA devices like a CD-ROM might not be recognized and configured on an x86-64 system. This was due to a missing entry in the system configuration tables in SYS$CONFIG.DAT for a SATA controller on the PCIe bus. 5.23.2 Images and/or Files Affected: [SYSEXE]SYS$CONFIG.DAT 5.23.3 VSI case identifier Jira BO-2233, BO-2234 Netsuite NS8662 5.23.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.24 Various errors on QLogic Fibre Channel card during startup or shutdown 5.24.1 Problem Description Various intermittent problems have been observed with the QLogic Fibre Channel card during startup or shutdown. It is suspected that these problems are caused when configuring the card from an unknown internal state. Bare metal systems perform a full reset of the PCI bus, which will always bring the Fibre Channel card back to a known state prior to booting. A full PCI bus reset cannot be done on a VM because it could cause problems with other VMs on the same host. PGQDRIVER has been modified to perform a full reset of the QLogic Fibre Channel card during driver initialization and in the controller shutdown routine. This prevents problems attempting to configure the card from an unknown state. 5.24.2 Images and/or Files Affected: [SYS$LDR]SYS$PGQDRIVER.EXE 5.24.3 VSI case identifier Jira DRIV-574, DRIV-611 5.24.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.25 32Gb Fibre Channel HBA requires V9.2-3 UPDATE V2.0 or later 5.25.1 Problem Description Use of the HPE SN1610Q 32Gb Fibre Channel HBA in passthrough mode requires the prior installation of the V9.2-3 UPDATE V2.0 or V3.0 ECO kit as a minimum support level. Booting the V9.2-3 ISO with an SN1610Q HBA configured may cause a hang or crash. To create a new virtual machine with a 32Gb SN1610Q HBA configured, follow these steps: - Define a virtual machine without an SN1610Q HBA. - Boot the VSI OpenVMS V9.2-3 ISO and install it to a local disk. - Update the new local system disk using the V9.2-3 UPDATE V2.0 or UPDATE V3.0 ECO kit. - Power-off the VM and add an SN1610Q HBA to the VM configuration. - Reboot the updated VM. NOTE: VSI OpenVMS V9.2-3 (regardless of any UPDATE ECO kit which may be applied) supports Fibre Channel LUNs only as data disks. Booting from a Fibre Channel LUN is not supported. 5.25.2 Images and/or Files Affected: [SYS$LDR]SYS$PGQDRIVER.EXE 5.25.3 VSI case identifier Jira IN-188 5.25.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- LAN changes ----- 5.26 LAN Bandwidth Monitoring issues with system time adjustments 5.26.1 Problem Description When time goes backwards, the LANCP display of bandwidth data may crash LANCP as it calculates the number of one-second intervals between two bandwidth buckets. Additionally, if the time goes backwards, LANCP may allocate memory uncontrollably, leading to a LANCP crash. 5.26.2 Images and/or Files Affected: [SYS$LDR]SYS$LAN.EXE [SYS$LDR]SYS$LAN_CSMACD.EXE [SYSEXE]LANCP.EXE [SYSHLP]LANCP$HELP.HLB [SYSLIB]LAN$SDA.EXE 5.26.3 VSI case identifier Jira DRIV-549, DRIV-556, DRIV-617 5.26.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.26.5 Workaround Restart bandwidth monitoring after the time change, using the command: $ MCR LANCP SET DEVICE/ALL/BANDWIDTH=RESTART 5.27 LANCP commands to enable or disable jumbo frames are confusing 5.27.1 Problem Description The LANCP commands to enable or disable jumbo frames are inconsistent for LAN Failover devices and other devices. The /STANDARD qualifier was added, and the /JUMBO and /STANDARD qualifiers were made equivalent to the /SIZE=JUMBO|STANDARD qualifier. These sets of commands are now equivalent: LANCP SET DEVICE LLA/JUMBO LANCP SET DEVICE LLA/SIZE=JUMBO LANCP SET DEVICE LLA/STANDARD LANCP SET DEVICE LLA/SIZE=STANDARD 5.27.2 Images and/or Files Affected: [SYSEXE]LANCP.EXE [SYSHLP]LANCP$HELP.HLB 5.27.3 VSI case identifier Jira DRIV-521 5.27.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.27.5 Workaround Use the original commands. 5.28 Various LANCP tracing improvements 5.28.1 Problem Description The following improvements have been made to LANCP tracing: - When decoding trace packets, display IP addresses in correct byte order. - Recognize PTY 80-07 for NISCA packet decode, where the PTY is changed from 60-07 to 80-07 so the packet will be lost. (in support of debug functionality in SYS$EI1000X.EXE). - Adjust trace display to show up to 10 trace mask bits for SHOW DEVICE/TRACE, to reduce the need for doing SHOW DEVICE/TRACE/HEADER. - Fix timestamp in 'special' PCAP entries (non-packet related) to fix the Wireshark display of the PCAP data. 5.28.2 Images and/or Files Affected: [SYSEXE]LANCP.EXE [SYSHLP]LANCP$HELP.HLB 5.28.3 VSI case identifier Jira DRIV-549, DRIV-556 Netsuite NS8314 5.28.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- MACRO programming support ----- 5.29 Updates to the MACRO compiler 5.29.1 Problem Description The following changes were made to the MACRO compiler: - MACRO compiler version is now V6.0-118. - LLVM internal errors now set $STATUS to failure. - Removed LLVM internal failures of "non-zero initializer". - LLVM 10 backend updated from Oct 2024 drop to Jul 2025 drop. 5.29.2 Images and/or Files Affected: [SYSEXE]MACRO.EXE 5.29.3 VSI case identifier Jira DEV-3098, DEV-3112 5.29.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- Cluster changes ---- 5.30 Provide diagnosis hints for lost connection cluster messages 5.30.1 Problem Description "Lost connection" and "Re-established connection" cluster messages lack context, making these events difficult to diagnose. There are multiple reasons why a cluster connection may be closed. Some are visible in the SCACP counters displays for PEDRIVER, for example listen timeouts. But some closures are connection manager initiated, and the reason for them is not recorded. This makes it difficult to diagnose these events and to determine if they are benign or significant. The problem addressed here is the lack of context for these cluster connection closures initiated by the connection manager. Once the cause of a closure is known, it can be dismissed as benign or may need to be investigated further. The closure reason is displayed by new RcvRej fields in the per-node CSB display from the SDA command SHOW CLUSTER. For example: SDA> SHOW CLUSTER --- Cluster System Block (CSB) 82148280 --- State: 0B local Flags: 030A002A member,selected,send_ext_status,local,status_rcvd qf_same,qf_noaccess Cpblty: 00003BF2 vcc,cwcreprc,threads,cwlogicals,ipc_demult_conn rmbxfr,wbm_shadow,sched_class,wbm_amcvp,wbm_type SWVers: XGUT-C6C LNM Seqnum: 000000010000012D HWName: innotek GmbH VirtualBox RcvRej: xxxxxxxx time reason1 reason2 reason3 reason4 reason5 reason6 reason7 reason8 The xxxxxxxx field is 8 4-bit nibbles containing reason codes, filled in from right (newest) to left (oldest). The time is the time of the most recent event. The reason strings are listed for nibbles left (oldest) to right (newest), reason1 to reason8. If nothing has been recorded, the time and reason1..n are omitted. The reason codes that exist are: 1 = msgarray 2 = rcv_nopool 3 = btx_allo_fail 4 = not_in_cluster 5 = deadlock_msg 6 = rcvlck_reject_msg 7 = cdrp_allo_fail The last 8 reasons are saved, and shifted up 4 bits after each event to make room for the new reason code. 5.30.2 Images and/or Files Affected: [SYS$LDR]SYS$CLUSTER.EXE [SYS$LDR]SYS$CLUSTER.STB [SYS$LDR]SYS$CLUSTER_MON.EXE [SYS$LDR]SYS$CLUSTER_MON.STB [SYSEXE]SDA.EXE [SYSLIB]SDA$SHARE.EXE 5.30.3 VSI case identifier Jira DRIV-556, DRIV-557 Netsuite NS8314 5.30.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.31 Use better default PEDRIVER Load Class for newly discovered devices 5.31.1 Problem Description PEDRIVER Load Class may be wrong for devices that see link up later than when PEDRIVER discovers the devices (usually LAN Failover devices where no failset member has link up). LAN devices default the line speed to 10 Mbps if the link is down. PEDRIVER uses this line speed as the BUS and Channel Load Class value. Having a very low value (10) causes PEDRIVER to favor other channels when forming an ECS (Equivalent Channel Set). This favoritism is not justified given the actual speed of the LAN device. The default Load Class has been changed to address this discrepancy. When creating a new channel, the Load Class is filled in with the device speed as reported by the LAN driver. If the LAN driver is reporting a speed of 10 Mbps or less, the Load Class is set to 1000. 5.31.2 Images and/or Files Affected: [SYS$LDR]SYS$PEDRIVER.EXE [SYS$LDR]SYS$PEDRIVER.STB [SYS$LDR]SYS$PEDRIVER_MON.EXE [SYS$LDR]SYS$PEDRIVER_MON.STB 5.31.3 VSI case identifier Jira DRIV-577 Netsuite NS-8314 5.31.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- RMS changes ---- 5.32 Spurious process terminations from RMS exception 5.32.1 Problem Description The UPDATE V1.0 ECO kit contained a change to avoid a system hang due to a process in RWMBX state owning file system locks (described in Section 6.14 below). In a small percentage of cases, the context for the owned lock did not yet include all the structures for the AST delivery. Attempting to read these structures would result in an access violation, leading to a process termination or a SSRVEXCEPT system crash if the SYSGEN parameter BUGCHECKFATAL was set to 1. The triggering issue in the RMS handling of the AST context is corrected with this ECO kit. 5.32.2 Images and/or Files Affected: [SYS$LDR]RMS.EXE [SYS$LDR]RMS.STB 5.32.3 VSI case identifier Jira BO-2042,BO-2043,BO-2176,BO-2177 Netsuite NS7912,NS8558 5.32.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- XQP changes ---- 5.33 System may crash with rare spurious XQPERR bugcheck 5.33.1 Problem Description The system might crash with an XQPERR bugcheck under rare circumstances. The triggering condition involves the inability to acquire a file system access lock for a file which is set to be truncated on close. The specific crash was an incorrect sanity check based on how the affected code returns errors. The situation can safely be resolved by merely returning an SS$_ACCONFLICT (access conflict) status back to the user. 5.33.2 Images and/or Files Affected: [SYS$LDR]F11BXQP.EXE [SYS$LDR]F11BXQP.STB 5.33.3 VSI case identifier Netsuite NS8738 5.33.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- Miscellaneous changes ---- 5.34 $ SHOW PATH/DEVICE may encounter spurious access violation 5.34.1 Problem Description The $ SHOW PATH/DEVICE commnd may exit with an access violation error. This has been corrected with this ECO kit. 5.34.2 Images and/or Files Affected: [SYSEXE]SETSHOWPATH.EXE 5.34.3 VSI case identifier Jira BO-2277 5.34.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.35 JBC$COMMAND works correctly, but returns spurious error 5.35.1 Problem Description The JBC$COMMAND image may be used to perform system management diagnostic or cleanup functions. It now returns a success status when executing correctly. 5.35.2 Images and/or Files Affected: [SYSEXE]JBC$COMMAND.EXE 5.35.3 VSI case identifier Jira UT-284 5.35.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.36 VMSINSTAL procedure may not accept passwords 5.36.1 Problem Description Some legacy software kits still use the VMSINSTAL procedure for kit installation. If the kit must prompt for a new password for a new or modified account, it will typically use the GET_PASSWORD callback. A flaw in this callback will always reject the password if the PWDMIX flag is set for the account. This issue is corrected with this kit. 5.36.2 Images and/or Files Affected: [SYSUPD]VMSINSTAL.COM 5.36.3 VSI case identifier Jira UT-289 5.36.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 5.37 Allow terminals connected via OpenSSH to run SHUTDOWN.COM 5.37.1 Problem Description Beginning with OpenSSH V9.9-2, a process connected to an OpenVMS system via OpenSSH could not successfully shutdown or reboot the system using the SYS$SYSTEM:SHUTDOWN.COM procedure. The associated process running the SSH image was not recognized as required while the shutdown was in progress and would be deleted, which would leave the shutdown in limbo. NOTE: If you plan to allow users with SSH-connected sessions to shutdown the system, do not invoke the SSH$SHUTDOWN.COM procedure from within the site-specific shutdown procedure, SYS$MANAGER:SYSHUTDWN.COM. The SSH shutdown will delete the process executing the shutdown and leave the system in an inconsistent state with logins, SSH, and other system components disabled, but nothing left executing the shutdown or reboot. 5.37.2 Images and/or Files Affected: [SYSEXE]SHUTDOWN.COM 5.37.3 VSI case identifier Jira SSH-1813, SSH-1814 Netsuite NS9031 5.37.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6 PROBLEMS ADDRESSED FROM PREVIOUS KITS Previous release notes table of contents (from UPDATE V1.0 kit) =============================================================== LAN changes -- Notes 6.1 to 6.13 -------------------------------- 6.1 LAN EIx device name corrections 6.2 Statistical and startup corrections for VirtIO and VMXNET3 devices 6.3 LAN Failover Set management interface usability improvements 6.4 VLAN configuration command fails silently on a VirtIO device 6.5 Periodic MOP messages display incorrect SystemID name 6.6 Miscellaneous minor LANCP and LANACP corrections and modifications 6.7 Using jumbo frames could consume excessive non-paged pool 6.8 Miscellaneous LAN driver changes 6.9 Corrections to SCACP SHOW xxx/SDA commands 6.10 Jumbo frames do not work with the VMXNET3 LAN driver 6.11 Potential cluster communications performance limitation 6.12 Certain jumbo receive packets on KVM VMs have incorrect buffer length 6.13 VLAN received bytes counters may be incorrect for jumbo packets RMS changes -- Notes 6.14 to 6.15 --------------------------------- 6.14 File locks owned by process in RWMBX resource wait may cause a hang 6.15 Spurious RMS-E-RLK errors SYS changes -- Notes 6.16 to 6.20 --------------------------------- 6.16 Performance enhancements for PROBE functionality 6.17 MONITOR displays inaccurate data for processor modes and CPU usage 6.18 Dump kernel failure on some configurations if DEVICE_NAMING is enabled 6.19 System may crash with DELCONPFN bugcheck during process deletion 6.20 DCL lexical F$GETDVI(,"MOUNTCNT_CLUSTER") always returns 0 RTL changes -- Notes 6.21 to 6.23 --------------------------------- 6.21 Install the Linker and C++ Run-Time Libraries as known images 6.22 BASIC programs terminate with %BAS-F-NOTIMP error 6.23 PASCAL RTL does not close all local files on routine completion DEBUG changes -- Note 6.24 -------------------------- 6.24 Various corrections to OpenVMS Debugger behavior ACME changes -- Notes 6.25 to 6.28 ---------------------------------- 6.25 Update for the OpenVMS ACME agent 6.26 Enhanced debug tracing for the ACME Server 6.27 Cannot capture SET PASSWORD/GENERATE output from command procedure 6.28 ACME LDAP Agent documentation update Security Server changes -- Notes 6.29 to 6.30 --------------------------------------------- 6.29 Potential cluster node security server failures 6.30 Security server could become non-responsive and require a reboot Miscellaneous changes -- Notes 6.31 to 6.34 ------------------------------------------- 6.31 Changes to the SEARCH/STATISTICS command 6.32 Updates to the MACRO compiler 6.33 The Linker may issue ILINK-W-DRELOSYM messages 6.34 SDA command CLUE XQP/LOCK does not show entire RSB address Previous release notes table of contents (from UPDATE V2.0 kit) =============================================================== SYS changes -- Notes 6.35 to 6.41 --------------------------------- 6.35 Condition handler may not be found for some exceptions 6.36 MONITOR DISK/ITEM=QUEUE_LENGTH issue with bound volume sets 6.37 System may encounter rare KRNLSTAKNV bugcheck 6.38 Rare access violation under unlikely circumstances 6.39 Spurious access violation during exception handling 6.40 System may crash with DELCONPFN bugcheck during process exit 6.41 ACPI interrupt storm may consume CPU time RTL changes -- Notes 6.42 to 6.43 --------------------------------- 6.42 Condition handler stack unwind may fail on certain exceptions 6.43 Debugger STEP/INSTRUCTION may return %DEBUG-W-BADSTACK error DEBUG changes -- Note 6.44 -------------------------- 6.44 Various corrections to OpenVMS Debugger behavior ACME changes -- Notes 6.45 to 6.49 ---------------------------------- 6.45 Generated passwords may be restricted to a maximum of 32 characters 6.46 OpenVMS ACME Agent message improvements 6.47 Batch job with multiple submitted files may fail with access violation 6.48 Malformed domain\username login may trigger ACME Server issues 6.49 Detached process creation failure with ACME-enabled LOGINOUT.EXE Security Server changes -- Note 6.50 ------------------------------------ 6.50 Security Server failure and spurious server restart I/O Device Driver changes -- Notes 6.51 to 6.53 ----------------------------------------------- 6.51 PCI passthrough support for HPE QLogic Fibre Channel cards 6.52 Configuration enhancements for SATA devices 6.53 VirtIO-SCSI device hangs under heavy load LAN changes -- Note 6.54 ------------------------ 6.54 Net applications using VirtIO-Net device may hang on start MACRO programming support -- Note 6.55 -------------------------------------- 6.55 Issues with MACRO programs using floating-point instructions From Update V1.0 kit ==================== ----- LAN changes ----- 6.1 LAN EIx device name corrections 6.1.1 Problem Description The DCL command SHOW DEVICE EIx/FULL or the SDA command SHOW LAN displayed non-specific or confusing device names for EIx devices. Device names for the e1000 and e1000e devices were always set to 82540, the name of the base Intel 82540 chip. In addition to the base 82540 device, the SYS$EI1000X driver supports several variants: the 82543, 82545, and 82574 devices. This update identifies the variant type, if present. When a VM has been configured with multiple types of e1000 and e1000e devices, this change makes it easier to differentiate them. The VirtIO and VMXNET3 devices have also been corrected to display the names EI_VIRTIO and EI_VMXNET3. Previously they contained the prefix EV instead of EI. 6.1.2 Images and/or Files Affected: [SYS$LDR]IO_ROUTINES.EXE [SYS$LDR]IO_ROUTINES.STB [SYS$LDR]IO_ROUTINES_MON.EXE [SYS$LDR]IO_ROUTINES_MON.STB [SYS$LDR]SYS$EVDRIVER.EXE [SYS$LDR]SYS$VMXNET3.EXE [SYSEXE]SDA.EXE [SYSLIB]LAN$SDA.EXE [SYSLIB]SDA$SHARE.EXE 6.1.3 VSI case identifiers Jiras DRIV-464,501 6.1.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.1.5 Workaround Use the LANCP command SHOW DEVICE/INTERNAL_COUNTERS to see the actual device name and description. 6.2 Statistical and startup corrections for VirtIO and VMXNET3 devices 6.2.1 Problem Description Several issues existed with the VirtIO and VMXNET3 NIC drivers. For Virtio, the driver did not tally the number of resets properly as do other network device drivers. For VMXNET3, the driver did not tally link state change interrupts correctly. Also for VMXNET3, when the driver is first started, there was a spurious link bounce. These issues are corrected with this update. 6.2.2 Images and/or Files Affected: [SYS$LDR]SYS$EVDRIVER.EXE [SYS$LDR]SYS$VMXNET3.EXE 6.2.3 VSI case identifier None 6.2.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.3 LAN Failover Set management interface usability improvements 6.3.1 Problem Description Using LANCP commands to manage a LAN Failover Set may have been confusing in some areas. There were no issues with LAN Failover operational behavior, just with the management for setup and configuration. The management usability improvements included: - Clarification of error and status messages when modifying a LAN Failover set. - Modification of status messages to not include a MAC address if the MAC address is not yet known. Previously, the MAC address appeared as either 00-00-00-00-00-00 or FF-FF-FF-FF-FF-FF. - Addition of a 'device removed' message when needed. - Removal of extraneous LAN Failover Event message text. Another improvement was to allow more flexibility in adding devices to and removing devices from a LAN Failover Set. This reduced the need to disable the failover set before making changes. The LANCP SET DEVICE/SWITCH command was modified to round-robin through the members of the failover set rather than selecting the first available started device. This allows you to cycle though all failover set members if there are more than two members. 6.3.2 Images and/or Files Affected: [SYS$LDR]SYS$LLDRIVER.EXE [SYSEXE]LANCP.EXE [SYSEXE]LANACP.EXE [SYSHLP]LANCP$HELP.HLB 6.3.3 VSI case identifiers Jiras DRIV 478-486,507 6.3.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.4 VLAN configuration command fails silently on a VirtIO device 6.4.1 Problem Description VLANs on VirtIO devices were created by associating the VLAN tag with the assigned network. This meant that the VirtIO driver SYS$EVDRIVER would be assigned to the VLAN network directly and never actually see VLAN tags itself. Rather than creating a VLAN device, a VirtIO device (EIF, for example) would embody the VLAN tag by virtue of the assigned network. An attempt to create a VLAN device on a VirtIO device is not supported and should return an error status. The VLAN driver and LANCP were updated to address this issue. LANCP now rejects attempts to create a VLAN device on a NIC that does not support VLANs, such as the VirtIO device. Rather than failing silently, this error message is now issued: Requested VLAN host device not VLAN-capable, VLAN device VLA0 6.4.2 Images and/or Files Affected: [SYS$LDR]SYS$VLANDRIVER.EXE [SYSEXE]LANCP.EXE [SYSEXE]LANACP.EXE [SYSHLP]LANCP$HELP.HLB 6.4.3 VSI case identifier Jira DRIV-463 6.4.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.5 Periodic MOP messages display incorrect SystemID name 6.5.1 Problem Description The MOP messages transmitted every 8-12 minutes include several operating system specific fields. One such field is the O/S name. This field was displayed as AVMS, a remnant from OpenVMS Alpha. The MOP messages now correctly display this field as XVMS for VSI OpenVMS x86-64 systems. 6.5.2 Images and/or Files Affected: [SYS$LDR]SYS$LAN.EXE [SYS$LDR]SYS$LAN_CSMACD.EXE 6.5.3 VSI case identifier Jira DRIV-495 6.5.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.6 Miscellaneous minor LANCP and LANACP corrections and modifications 6.6.1 Problem Description The following changes have been made to LANCP and LANACP: - Consistent error message behavior and display characteristics. - Remove VLAN and LAN Failover devices from LANCP SHOW BANDWIDTH. - LANCP command SHOW DEVICE/REVISION is now SHOW DEVICE/VERSION, which is a more accurate description of the values displayed. - Add the /ZERO qualifier to the LANCP SHOW DEVICE/COUNTERS command. For OpenVMS, some of the counters are always zero and merely clutter the output when displayed. Now by default those fields are not displayed. You can specify the /ZERO qualifier to get the entire set of values displayed as before. This qualifier behavior is the same for LANCP SHOW DEVICE/INTERNAL_COUNTERS. - Simplified applying permanent device database settings to the volatile device database (ie, the actual LAN devices in use). You may now use LANCP DEFINE DEVICE to update the permanent device database settings, then use LANCP SET DEVICE/PERMANENT to apply the settings to the existing devices. For more detail, see the information from LANCP HELP SET DEVICE. - LANCP HELP was updated for accuracy and completeness. - Issuing multiple commands in LANCP could exhaust the process BYTLM quota. This has been corrected. 6.6.2 Images and/or Files Affected: [SYSEXE]LANCP.EXE [SYSEXE]LANACP.EXE [SYSHLP]LANCP$HELP.HLB 6.6.3 VSI case identifiers Jiras DRIV-460,461,465-467,469-475,512 6.6.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.7 Using jumbo frames could consume excessive non-paged pool 6.7.1 Problem Description The LAN drivers did not account for jumbo receive buffers properly, resulting in excessive non-paged pool consumption. This issue has been corrected. 6.7.2 Images and/or Files Affected: [SYSEXE]LANCP.EXE [SYSEXE]LANACP.EXE [SYS$LDR]SYS$LAN.EXE [SYS$LDR]SYS$LAN_CSMACD.EXE 6.7.3 VSI case identifiers Jiras DRIV-487,505 6.7.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.8 Miscellaneous LAN driver changes 6.8.1 Problem Description Treatment of transmit timeout conditions in the SYS$EI1000X driver has been improved. Treatment of the periodic reset function used in driver qualification has been standardized across the three LAN drivers. 6.8.2 Images and/or Files Affected: [SYS$LDR]SYS$EI1000X.EXE [SYS$LDR]SYS$EVDRIVER.EXE [SYS$LDR]SYS$VMXNET3.EXE 6.8.3 VSI case identifiers Jiras DRIV-493,494 6.8.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.9 Corrections to SCACP SHOW xxx/SDA commands 6.9.1 Problem Description SCACP exits with an error when the SCACP SHOW LAN/SDA, SHOW VC/SDA, or SHOW CHANNEL/SDA commands are issued. The /SDA qualifier is intended to produce displays similar to the equivalent SDA> PE commands. This behavior is corrected with this update. Some other SCACP output display spacing has also been corrected. 6.9.2 Images and/or Files Affected: [SYSEXE]SCACP.EXE 6.9.3 VSI case identifiers Jira BO-1924 Netsuite NS7746 6.9.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.10 Jumbo frames do not work with the VMXNET3 LAN driver 6.10.1 Problem Description This affects VMware OpenVMS VMs that have selected the VMXNET3 as the NIC type. Jumbo transmits work, but no jumbo frames are received. This has been corrected in the SYS$VMXNET3 driver. Corresponding changes were made to the LAN SDA extension that supports the VMXNET3 driver. 6.10.2 Images and/or Files Affected: [SYS$LDR]SYS$VMXNET3.EXE [SYSLIB]LAN$SDA.EXE 6.10.3 VSI case identifier Jira DRIV-487 6.10.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.11 Potential cluster communications performance limitation 6.11.1 Problem Description Using a LAN Failover device for cluster communications may limit cluster communication performance. The default receive size is set to 8 for LAN Failover devices, when it should be set to 128. Depending on the load, this may limit performance. PEDRIVER uses this default receive size as the transmit window size, which determines how many transmits PEDRIVER can issue. The default size is corrected to 128 with this update. 6.11.2 Images and/or Files Affected: [SYS$LDR]SYS$LLDRIVER.EXE 6.11.3 VSI case identifiers Jiras BO-1944,DRIV-522 Netsuite NS7748 6.11.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.11.5 Workaround The receive window size for cluster communications can be overridden by issuing this command for Virtual Circuits (VCs) that have the default window size of 8: MCR SCACP SET VC /WINDOW=TRANSMIT=128 However, this command must be repeated when a VC is created. For example, after a system boots. 6.12 Certain jumbo receive packets on KVM VMs have incorrect buffer length 6.12.1 Problem Description KVM VMs using the e1000e NIC (82574) have corrupted jumbo frames if the size is 2049-2053, 4097-4101, 6145-6149, or 8193-8197 bytes. The buffer length reported is 4 bytes shorter than actual. The problem is due to a KVM hypervisor bug with the 82574 device. The issue can be corrected by checking for the condition and adjusting the length of the last two buffer segments. The SYS$EI1000X driver now does this for any e1000 or e1000e (82540, 82545, or 82574) device, although the condition only happens with the 82574 device. The condition is counted in the LANCP SHOW DEVICE/INTERNAL counters as "CRC workarounds applied". 6.12.2 Images and/or Files Affected: [SYS$LDR]SYS$LAN.EXE 6.12.3 VSI case identifier Jira DRIV-517 6.12.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.13 VLAN received bytes counters may be incorrect for jumbo packets 6.13.1 Problem Description For a VLAN device, the "receive bytes" and "multicast receive bytes" counters were counted incorrectly for jumbo packets larger than 2048 bytes. This issue is corrected with this update. 6.13.2 Images and/or Files Affected: [SYS$LDR]SYS$EI1000X.EXE 6.13.3 VSI case identifier None 6.13.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- RMS changes ----- 6.14 File locks owned by process in RWMBX resource wait may cause a hang 6.14.1 Problem Description If a process owns a lock on a file system resource and another process attempts to acquire an incompatible lock on the same resource, then a blocking AST is delivered to the owning process so it may lower the lock mode to allow the new process to continue. Under normal circumstances, this happens automatically and the processes will make progress with the locks and file access as needed. A process in RWMBX resource wait state could own file system locks on files while it is trying to read or write to a mailbox. Should a new process request a lock in this case, the owning process was unable to drop its lock mode since the process could not continue until the resource wait state was satisfied. To prevent a potential hang, the blocking AST routine has been modified to directly lower the lock mode rather than wait until the RWMBX state clears. This behavior was discovered by a customer using PIPE to invoke the AUTHORIZE utility as a step in its piped commands. Since each step in the pipe creates a new sub-process and uses mailboxes for communication, it was possible for the PIPE command to cause the process to block against itself. As this entailed a file lock on the system authorization file (SYSUAF), eventually it would cause a system hang for new processes or any other processes trying to access the file. This behavior is corrected with this ECO kit. 6.14.2 Images and/or Files Affected: [SYS$LDR]RMS.EXE [SYS$LDR]RMS.STB 6.14.3 VSI case identifiers Jiras CLUS-38,BO-1900 Netsuite NS7556 6.14.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.15 Spurious %RMS-E-RLK errors 6.15.1 Problem Description The RMS V5 ECO kits (VMS842L3I_RMS-V0500 for Integrity Servers, VMS842L2A_RMS-V0500 for Alpha systems) contained a comprehensive internal status code reorganization to avoid returning a truncated error status on some RMS operations during heavy load. The equivalent code was updated in VSI OpenVMS x86-64 V9.2. One particular set of status code condition tests was accidentally missed during that update. In trying to determine whether there was a record locked condition during an RMS $DELETE operation, the missed condition test could in some cases mistakenly signal the error: %RMS-E-RLK, target record currently locked by another stream This problem is corrected with this ECO kit. 6.15.2 Images and/or Files Affected: [SYS$LDR]RMS.EXE [SYS$LDR]RMS.STB 6.15.3 VSI case identifiers Jira BO-1945 Netsuite NS7669,NS7935 6.15.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- SYS changes ----- 6.16 Performance enhancements for PROBE functionality 6.16.1 Problem Description The PROBE mechanism is a central piece of the ring protection system that OpenVMS uses for hierarchical access to system memory. PROBE checks the accessibility of a starting and ending address based on caller's mode and the protection mask for read or write access for kernel, executive, supervisor, or user modes. In VAX, Alpha, and Itanium architectures, a PROBE instruction is part of the hardware instruction set, providing an efficient mechanism for these tests. In the x86-64 system architecture, there is no similar instruction, so the behavior is emulated by system software. This is inherently more expensive overhead for the required functionality. The original PROBE emulation in VSI OpenVMS x86-64 has been enhanced for better system performance. This consists of improvements in two areas: 1. Optimization of the emulated PROBE instruction behavior itself. - If the starting address is accessible, skip checking the ending address if they both reside on the same page. - For multiple page address ranges, only traverse the kernel mode page table pages to find the relevant protection data. - Optimizations to the flow and memory usage of the PROBE function routine implementation. 2. Reduction of redundant or unnecessary PROBE operations from the various callers where possible. - Some system services which use IOSB structures to return information to the caller were probing the IOSB structure at both the start of the service and at the end when returning the status to the caller. o If the first probe was successful, there is no need to repeat the probe later as the protection cannot change during the system service call. o However, if the first probe of the IOSB fails, the IOSB cannot be used at service completion since it is not valid. In this case, simply clear the saved IOSB address after the first probe failure, which will prevent the IOSB from being accessed while the error code is returned by the common system service rundown. 6.16.2 Images and/or Files Affected: [SYS$LDR]IO_ROUTINES.EXE [SYS$LDR]IO_ROUTINES.STB [SYS$LDR]IO_ROUTINES_MON.EXE [SYS$LDR]IO_ROUTINES_MON.STB [SYS$LDR]PROCESS_MANAGEMENT.EXE [SYS$LDR]PROCESS_MANAGEMENT.STB [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE [SYS$LDR]PROCESS_MANAGEMENT_MON.STB [SYS$LDR]SYS$VM.EXE [SYS$LDR]SYS$VM.STB [SYS$LDR]SYS$VM_MON.EXE [SYS$LDR]SYS$VM_MON.STB [SYS$LDR]SYSGETSYI.EXE [SYS$LDR]SYSGETSYI.STB [SYS$LDR]SYSTEM_PRIMITIVES.EXE [SYS$LDR]SYSTEM_PRIMITIVES.STB [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB [SYSEXE]SYSBOOT.EXE 6.16.3 VSI case identifiers Jiras BO-1873, BO-1912, BO-1940, QTV-1168 6.16.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.17 MONITOR displays inaccurate data for processor modes and CPU usage 6.17.1 Problem Description On VSI OpenVMS x86-64 virtual machine systems, MONITOR displays inaccurate data on screens which show processor mode or CPU usage. Other utilities which gather similar statistics are also affected. This issue stems from the hard tick rate used by the system for accounting purposes. This is a sampling frequency used to collect the relevant data. VM environments were using a 10 msec rate, which is too coarse to differentiate multiple events which can occur during that interval. The hard tick rate for VMs has been lowered from 10 msec to 1 msec, which is the hard tick rate used on physical machines. Additionally, some hard tick events for x86-64 systems were being incorrectly counted or discarded. This has been corrected with this ECO kit. For VMs, the output for MONITOR and other utilities which display or gather processor mode or CPU usage now have the same behavior as traditional OpenVMS hardware system environments. 6.17.2 Images and/or Files Affected: [SYS$LDR]SYSTEM_PRIMITIVES.EXE [SYS$LDR]SYSTEM_PRIMITIVES.STB [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 6.17.3 VSI case identifier Jira BO-1800 6.17.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.18 Dump kernel failure on some configurations if DEVICE_NAMING is enabled 6.18.1 Problem Description On systems with at least one VirtIO-SCSI adapter configured, if DEVICE_NAMING is enabled, the dump kernel will trigger an access violation and the dump kernel will then crash during reboot. After reboot, the system will be unable to write a crash dump in case of a system crash. This was due to an IOGEN routine being called from executive mode during AUTOCONFIGURE, when it must be called from kernel mode. This issue has been corrected. 6.18.2 Images and/or Files Affected: [SYSLIB]IOGEN$VIRTIO_CONFIG.EXE 6.18.3 VSI case identifier Jira KT-207 6.18.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.19 System may crash with DELCONPFN bugcheck during process deletion 6.19.1 Problem Description When a process is adding address space and the process page tables are being updated, the wrong page table entry could be used when setting the window bit for pages which are doubly-mapped. This incorrect status is ignored until the process address space is torn down during process deletion, either from logging out or being terminated with the $DELPRC system service. When the discrepancy is found during process deletion, the system crashes with a DELCONPFN bugcheck. This issue has been corrected. 6.19.2 Images and/or Files Affected: [SYS$LDR]SYS$VM.EXE [SYS$LDR]SYS$VM.STB [SYS$LDR]SYS$VM_MON.EXE [SYS$LDR]SYS$VM_MON.STB 6.19.3 VSI case identifier Jira SPS-1273 6.19.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.20 DCL lexical F$GETDVI(,"MOUNTCNT_CLUSTER") always returns 0 6.20.1 Problem Description This problem was due to an incorrect buffer length used internally by the $GETDVI system service to retrieve the lock value block which contains the device mount count data. The MOUNTCNT_CLUSTER item returned zero instead of the correct device mount count. This issue only occurred on x86-64 systems. This would also affect calls to the $GETDVI system service or LIB$GETDVI from any programs, in addition to the DCL lexical which was reported by a customer. This issue is corrected with this ECO kit. 6.20.2 Images and/or Files Affected: [SYS$LDR]IO_ROUTINES.EXE [SYS$LDR]IO_ROUTINES.STB [SYS$LDR]IO_ROUTINES_MON.EXE [SYS$LDR]IO_ROUTINES_MON.STB 6.20.3 VSI case identifiers Jira BO-1921 Netsuite NS7715 6.20.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- RTL changes ----- 6.21 Install the Linker and C++ Run-Time Libraries as known images 6.21.1 Problem Description The system startup does not install the Linker (SYS$SYSTEM:LINK.EXE) or the C++ Run-Time Libraries (SYS$SHARE:LIBCXX.EXE and SYS$SHARE:LIBCXXABI.EXE) as known images. Installing the images can help improve performance of the linker and C++ applications. This change adds the relevant entries to the master list used to determine which files to install as known images during system boot. You will need to use AUTOGEN to update the system to actually install the images at boot. The boot time list is generated during the GENPARAMS phase of AUTOGEN. If you wish to install these as known images before the next AUTOGEN and system reboot, you may manually add them yourself for the current incarnation of the system using the commands: $ INSTALL ADD SYS$SHARE:LIBCXXABI /OPEN /HEADER /SHARED=ADDRESS_DATA $ INSTALL ADD SYS$SHARE:LIBCXX /OPEN /HEADER /SHARED=ADDRESS_DATA $ INSTALL ADD SYS$SYSTEM:LINK /OPEN /HEADER /SHARED=ADDRESS_DATA NOTE: The installation order of the two C++ libraries is important. 6.21.2 Images and/or Files Affected: [SYSMGR]VMS$IMAGES_MASTER.DAT 6.21.3 VSI case identifiers Jira BO-1898,BO-1899 6.21.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.22 BASIC programs terminate with %BAS-F-NOTIMP error 6.22.1 Problem Description The NUM and NUM1 functions in the BASIC language convert a number to a text representation. If these functions are called with a quadword integer value to convert, they will signal the error: %BAS-F-NOTIMP, Not implemented For most programs this will terminate the image. The port from I64 to x86-64 for the conversion routine had not yet been completed. The issue is addressed with this ECO kit. 6.22.2 Images and/or Files Affected: [SYSLIB]DEC$BASRTL.EXE 6.22.3 VSI case identifier Jira RTLS-509 6.22.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.23 PASCAL RTL does not close all local files on routine completion 6.23.1 Problem Description For a program written in Pascal, when an open file allocated in a routine is not explicitly closed, the Pascal Run-Time Library routine PAS$CLOSE_LOCAL is called to close those files automatically at the end of the routine, or during an unwind or non-local GOTO operation. The PAS$CLOSE_LOCAL routine needs platform-specific knowledge about the stack layout to find file variables. This code had not been completely ported from I64 to x86-64. The issue is corrected with this ECO kit. 6.23.2 Images and/or Files Affected: [SYSLIB]PAS$RTL.EXE 6.23.3 VSI case identifier Jira RTLS-516 6.23.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- DEBUG changes ----- 6.24 Various corrections to OpenVMS Debugger behavior 6.24.1 Problem Description The following issues in the Debugger are corrected with this ECO kit: - The Heap Analyzer has been ported to VSI OpenVMS x86-64. - STEP/RETURN no longer causes an access violation. - Corrected the source line to PC correlation for C++ programs. - Correctly record the routine prologue end address. - Display the file name during debug line tracing when a file switch is made. - Corrected an issue where the Debugger would encounter an access violation when starting up. - SHOW SYMBOL/TYPE for variant records no longer displays size values, which have no meaning in that context. - Dynamic strings where the string length is in the variable are now correctly displayed. - Set the default lower bound for array elements depending on the language used. For example, FORTRAN arrays now start at 1, not 0. - Class members where the class has multiple inheritances are now displayed correctly. 6.24.2 Images and/or Files Affected: [SYSLIB]DBG$HA_KERNEL.EXE [SYSLIB]DBG$HA_MAIN.EXE [SYSLIB]DEBUG.EXE [SYSLIB]DEBUGSHR.EXE [SYSLIB]DEBUGUISHR.EXE 6.24.3 VSI case identifiers Jira DEV-2492,2631,2674,2737,2752,2828,2837,2846,2856,2876,2881 6.24.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- ACME changes ----- 6.25 Update for the OpenVMS ACME agent 6.25.1 Problem Description Various bug fixes have been made to the OpenVMS ACME agent for ACME logins. The following problems have been corrected: - Access violation when connecting via TELNET when a system password is enabled. - Spurious error when changing an expired password after entering a password contained in the history database. - NULLNETUSER handling for non-interactive network processes like EVL. - Login failures due to using wrong username string for reading UAF records when explicit mapping is used. - Login failures due to missing trailing space character padding for username key string. - SET PASSWORD/GENERATE sometimes refuses to accept an element from the generated list. - SET PASSWORD/GENERATE may suggest passwords of insufficient minimum length. 6.25.2 Images and/or Files Affected: [SYSLIB]VMS$VMS_ACMESHR.EXE 6.25.3 VSI case identifiers Jira BO-1849,1856,1859,1901,1907,1920 6.25.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.26 Enhanced debug tracing for the ACME Server 6.26.1 Problem Description For debugging purposes, the ACME Server has tracing code which can be enabled when needed. This tracing has been modified to set the trace flag for the following control mode phases: - AGENT_INITIALIZE - AGENT_STARTUP - AGENT_SHUTDOWN - AGENT_STANDBY 6.26.2 Images and/or Files Affected: [SYSEXE]ACME_SERVER.EXE 6.26.3 VSI case identifier Jira BO-1737 6.26.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.27 Cannot capture SET PASSWORD/GENERATE output from command procedure 6.27.1 Problem Description When using ACME login on VSI OpenVMS x86-64, attempting to capture the output of a SET PASSWORD/GENERATE command within a DCL command procedure fails with the error: %STR-F-ILLSTRCLA, illegal string class This problem has been corrected. 6.27.2 Images and/or Files Affected: [SYSEXE]SETP0_ACME.EXE 6.27.3 VSI case identifier Jira UT-314 6.27.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.28 ACME LDAP Agent documentation update 6.28.1 Problem Description The installation requirements for the ACME LDAP Agent are different on VSI OpenVMS x86-64 from previous VSI OpenVMS platforms. The ACME LDAP configuration and installation document has been updated to include additional details for x86-64, as well as a general cleanup of content, images, and formatting. The PDF and TXT versions of the document are placed in SYS$HELP. 6.28.2 Images and/or Files Affected: [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.TXT [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.PDF 6.28.3 VSI case identifier Jira BO-1874 6.28.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- Security Server changes ----- 6.29 Potential cluster node security server failures 6.29.1 Problem Description The VSI OpenVMS x86-64 security server could generate improperly formatted suspect records for certain DECnet connections and insert them into the intrusion database. Should this occur in a VMScluster, Alpha or Integrity cluster members could then experience security server failures triggered by the improper records. The security server now correctly formats these suspect records. In addition, the security server now includes a self-healing check that removes any improper records from the intrusion database. 6.29.2 Images and/or Files Affected: [SYSEXE]SECURITY_SERVER.EXE 6.29.3 VSI case identifier Jira BO-1908 6.29.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.30 Security server could become non-responsive and require a reboot 6.30.1 Problem Description The security server includes an exception handler to determine what actions to take if an unexpected error or exception occurs. Usually this will lead to the handler restarting the server. In some cases, the exception handler could terminate before completing the restart process. This will leave the server in a non-responsive "zombie" state that requires a system reboot to clear. The security server has been modified to reorder recovery steps and limit the use of certain services during exception handling to avoid cascading exception failures. This ensures completion of the restart process and proper image cleanup. 6.30.2 Images and/or Files Affected: [SYSEXE]SECURITY_SERVER.EXE 6.30.3 VSI case identifier Jira BO-1998 6.30.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- Miscellaneous changes ----- 6.31 Changes to the SEARCH/STATISTICS command 6.31.1 Problem Description Several items displayed by SEARCH/STATISTICS were tallied in longword (32-bit) counters. The fields would overflow and restart at zero should there be more than 4,294,967,295 records or characters in the file or files being searched, which is easily possible for very large files. Should the field overflow, the output display was incorrect. The following fields are now tallied in quadword (64-bit) counters to prevent overflow: - Records searched - Characters searched - Records matched - Lines printed To accommodate displaying potentially large values for these items, the output format of the statistics summary has changed, with wider field sizes where needed. The same items are displayed in the same order. The displays for Elapsed Time and CPU Time now include the leading digits for the number of days, should the search take that long to complete. Here is an example showing the new format for the output display: Files searched: 9123 Buffered I/O count: 34060 Records searched: 63172133 Direct I/O count: 62142 Characters searched: 2819025795 Page faults: 17 Records matched: 2524 Elapsed CPU time: 0 00:02:56.10 Lines printed: 4180 Elapsed time: 0 00:07:58.89 By default, SEARCH/STATISTICS also creates DCL symbols for some of the metrics calculated. These are defined in the local symbol table as character strings, so they will not overflow for large numeric values. Since DCL only supports 32-bit arithmetic, large values cannot be directly converted to integers for additional processing, but would need to use a program or utility which does provide 64-bit arithmetic. However, DCL procedures may use the character symbols for reporting purposes or to create a comma separated list for input to a spreadsheet program, for example. New symbols are now created for the Elapsed Time and CPU Time values, so this information may also be captured by DCL command procedures without the need to parse the command display output. The two new time symbols are created in DCL Delta Time format, so they may be used directly for DCL time calculations. Here are the DCL symbols generated by the example SEARCH/STATISTICS display output above: SEARCH$CHARACTERS_SEARCHED = "2819025795" SEARCH$CPU_TIME = "0-00:02:56.10" SEARCH$ELAPSED_TIME = "0-00:07:58.89" SEARCH$FILES_SEARCHED = "9123" SEARCH$LINES_PRINTED = "4180" SEARCH$RECORDS_MATCHED = "2524" SEARCH$RECORDS_SEARCHED = "63172133" 6.31.2 Images and/or Files Affected: [SYSEXE]SEARCH.EXE [SYSMSG]CLIUTLMSG.EXE 6.31.3 VSI case identifiers Jiras UT-319,UT-326 6.31.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.32 Updates to the MACRO compiler 6.32.1 Problem Description The following changes were made to the MACRO compiler: - Updated the MACRO compiler to use a newer version of LLVM. - Fixed ACCVIO when using /DEBUG qualifier. - Improved debug information for static data declarations. - The compiler now correctly creates ELF NOBIT sections for PSECTs declared with OVR. - Fixed a regression with 3-operand EVAX builtins using the wrong register The version of the compiler can be shown using MACRO/VERSION: $ MACRO/VERSION XMAC V6.0-117 (GEM 50Y4T) on OpenVMS x86_64 V9.2-3 6.32.2 Images and/or Files Affected: [SYSEXE]MACRO.EXE 6.32.3 VSI case identifiers Jiras DEV-2688,DEV-2703,DEV-2624,DEV-2788 6.32.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.33 The Linker may issue %ILINK-W-DRELOSYM messages 6.33.1 Problem Description On VSI OpenVMS V9.2-3, the linker sometimes reports the warning: %ILINK-W-DRELOSYM, debug relocation for undefined symbol When linking an image with code in P2 space (the default) and using the /DEBUG qualifier, the linker may fail to find a symbol referenced in the debug information. The warning message is displayed along with some additional information. The generated image is not affected in the sense that it can be run and works as expected. If run with the debugger, the debugger may report or display messages if it attempts to access the particular symbol referenced in the DRELOSYM message. This problem has been corrected. 6.33.2 Images and/or Files Affected: [SYSEXE]LINK.EXE 6.33.3 VSI case identifier Jira BO-1895 6.33.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.34 SDA command CLUE XQP/LOCK does not show the entire RSB address 6.34.1 Problem Description The SDA command CLUE XQP/LOCK= displays lock and resource information, but only displays the lower 32 bits of the RSB address. The command now displays the entire 64-bit RSB address. 6.34.2 Images and/or Files Affected: [SYSLIB]CLUE$SDA.EXE 6.34.3 VSI case identifier Jira UT-308 6.34.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 From Update V2.0 kit ==================== ----- SYS changes ----- 6.35 Condition handler may not be found for some exceptions 6.35.1 Problem Description A routine which has 'callq' as the last instruction may not have its associated condition handler invoked if the routine should encounter an exception condition. The common unwind routine in LIBRTL used in condition handler searches is now corrected (see release note 6.42 below). The OpenVMS executive exception handling now correctly l locates the associated condition handler routine for this case. 6.35.2 Images and/or Files Affected: [SYS$LDR]EXCEPTION.EXE [SYS$LDR]EXCEPTION.STB [SYS$LDR]EXCEPTION_MON.EXE [SYS$LDR]EXCEPTION_MON.STB 6.35.3 VSI case identifier Jira BO-1973 6.35.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.36 MONITOR DISK/ITEM=QUEUE_LENGTH issue with bound volume sets 6.36.1 Problem Description MONITOR DISK/ITEM=QUEUE_LENGTH may display a large non-zero queue length for members of bound volume sets, even though the disk may actually be idle. This issue only occurs for bound volume sets consisting of multiple disk devices using the FastIO mechanism. The queue length fields were updated inconsistently between the various volume set members. This problem is corrected with this ECO kit. 6.36.2 Images and/or Files Affected: [SYS$LDR]IO_ROUTINES.EXE [SYS$LDR]IO_ROUTINES.STB [SYS$LDR]IO_ROUTINES_MON.EXE [SYS$LDR]IO_ROUTINES_MON.STB 6.36.3 VSI case identifier Jiras DRIV-553, DRIV-554 Netsuite NS8211 6.36.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.37 System may encounter rare KRNLSTAKNV bugcheck 6.37.1 Problem Description During procedure call handling, a very rare circumstance could cause the system to fail with the crash: KRNLSTAKNV, Kernel stack not valid This crash is unpredictable in nature and very unlikely in production environments. The issue is corrected with this ECO kit. 6.37.2 Images and/or Files Affected: [SYS$LDR]SYSTEM_PRIMITIVES.EXE [SYS$LDR]SYSTEM_PRIMITIVES.STB [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 6.37.3 VSI case identifier Jira BO-2009 6.37.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.38 Rare access violation under unlikely circumstances 6.38.1 Problem Description Access checks against a buffer which has access to the start address but not the end address will correctly signal an access violation. However, an immediate re-check against the same buffer start address where the buffer is now accessible may trigger a spurious access violation. VSI has only encountered this behavior in a regression test which was specifically inducing access failures. To encounter it with production software is extremely unlikely. The issue is corrected with this ECO kit. 6.38.2 Images and/or Files Affected: [SYS$LDR]SYSTEM_PRIMITIVES.EXE [SYS$LDR]SYSTEM_PRIMITIVES.STB [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 6.38.3 VSI case identifier Jiras QTV-1168, BO-2071 6.38.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.39 Spurious access violation during exception handling 6.39.1 Problem Description If a buffer PROBE access check exceeds the end of the current user stack, the stack is automatically extended. An immediate re-PROBE using the same starting address may incorrectly signal an access violation. This issue is corrected with this ECO kit. 6.39.2 Images and/or Files Affected: [SYS$LDR]EXCEPTION.EXE [SYS$LDR]EXCEPTION.STB [SYS$LDR]EXCEPTION_MON.EXE [SYS$LDR]EXCEPTION_MON.STB 6.39.3 VSI case identifier Jira BO-2059 6.39.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.40 System may crash with DELCONPFN bugcheck during process exit 6.40.1 Problem Description When a process is logging out or exiting, the virtual address space for that process is torn down and resources are returned to the system. If a page which is doubly-mapped is encountered during this processing, the system could crash with a DELCONPFN bugcheck. This issue is corrected with this ECO kit. 6.40.2 Images and/or Files Affected: [SYS$LDR]SYS$VM.EXE [SYS$LDR]SYS$VM.STB [SYS$LDR]SYS$VM_MON.EXE [SYS$LDR]SYS$VM_MON.STB 6.40.3 VSI case identifier Jiras SPS-1273, BO-1971 6.40.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.41 ACPI interrupt storm may consume CPU time 6.41.1 Problem Description The ACPI (Advanced Configuration and Power Interface) mechanism on x86-64 systems may interrupt the system to deliver information regarding device configuration or power management. On some x86-64 hosts, an "interrupt storm" from the ACPI subsystem mechanism may occur, delivering on the order of 50,000 interrupts per second for an unknown period of time. This can consume from 30% to 60% of an entire CPU in interrupt context to field and dismiss the interrupts. As far as we can determine, there is no underlying issue of any particular significance to the operating system for these events. The ACPI handling code for OpenVMS has been enhanced to detect this condition. If it occurs, the ACPI interrupts are disabled and the code will switch to a polling mode to learn of any events which are relevant to OpenVMS. 6.41.2 Images and/or Files Affected: [SYS$LDR]SYS$ACPI.EXE [SYS$LDR]SYS$ACPI0006.EXE [SYS$LDR]SYS$SEDRIVER.EXE 6.41.3 VSI case identifier Jira BO-1833 6.41.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- RTL changes ----- 6.42 Condition handler stack unwind may fail on certain exceptions 6.42.1 Problem Description A routine which has 'callq' as the last instruction may not have its associated condition handler invoked if the routine should encounter an exception condition. The common unwind routine in LIBRTL used in condition handler searches is now corrected. The corrected unwind mechanism is built into LIBRTL for run-time use and in the STARLET.OLB object module for programs which must link the code statically. 6.42.2 Images and/or Files Affected: [SYSLIB]LIBRTL.EXE [SYSLIB]LIBRTL.STB LIB$$X86_UNWIND.OBJ, a module in [SYSLIB]STARLET.OLB 6.42.3 VSI case identifier Jira BO-1973 6.42.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.43 Debugger STEP/INSTRUCTION may return %DEBUG-W-BADSTACK error 6.43.1 Problem Description The Debugger may return a BADSTACK error during a STEP/INSTRUCTION. For example: %DEBUG-I-INITIAL, Language: BASIC, Module: ALEXA DBG> step/inst %DEBUG-W-BADSTACK, WARNING: stack corrupted; session integrity not guaranteed stepped to ALEXA\ALEXA+1: movq %rsp,%rbp DBG> This problem occurs when multiple procedure ICB (Invocation Control Block) structures are used in parallel. The Debugger uses these to provide procedure tracing or stack unwinding operations. Some of the context from one ICB was mistakenly reused in a subsequent ICB. The Debugger is merely a victim here. The problem occurs in the run-time library routine which allocates and initializes an ICB. This problem is corrected with this ECO kit. 6.43.2 Images and/or Files Affected: [SYSLIB]LIBRTL.EXE [SYSLIB]LIBRTL.STB 6.43.3 VSI case identifier Jira BO-2101, DEV-2860 6.43.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- DEBUG changes ----- 6.44 Various corrections to OpenVMS Debugger behavior 6.44.1 Problem Description The following issues in the Debugger are corrected with this ECO kit: - Many %DEBUG-I-EXPMEMPOOL messages errors are reported, which eventually causes the Debugger to become unstable. - %DEBUG-W-BADSTACK errors are often reported, usually occurring after the first STEP or GO. - Access violation errors occur under some circumstances. 6.44.2 Images and/or Files Affected: [SYSLIB]DEBUG.EXE [SYSLIB]DEBUGSHR.EXE 6.44.3 VSI case identifier Jira DEV-2860 6.44.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- ACME changes ----- NOTE: If you change the login mechanism from ACME to UAF or from UAF to ACME after installing this kit, you will need to take an additional step if you later remove the kit using PRODUCT UNDO PATCH. Refer to the information in Section 8.4 in the installation instructions below. 6.45 Generated passwords may be restricted to a maximum of 32 characters 6.45.1 Problem Description SET PASSWORD/GENERATE in a command procedure with MIXED_CHARACTER generation algorithm cannot generate passwords longer than 32 characters. Even if PWDMINIMUM is greater than 32, only a list of 32-character passwords is generated. This problem is corrected with this ECO kit. Passwords may be generated up to the supported limit of 64 characters. 6.45.2 Images and/or Files Affected: [SYSEXE]SETP0_ACME.EXE 6.45.3 VSI case identifier Jira UT-315 6.45.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.46 OpenVMS ACME Agent message improvements 6.46.1 Problem Description Trace content and error log entries for the OpenVMS ACME Agent have been updated for more consistent and accurate reporting. A few minor behavioral errors have also been corrected. 6.46.2 Images and/or Files Affected: [SYSLIB]VMS$VMS_ACMESHR.EXE 6.46.3 VSI case identifier Jira BO-1710 6.46.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.47 Batch job with multiple submitted files may fail with access violation 6.47.1 Problem Description Multiple command procedure files may be submitted for batch processing using a single SUBMIT command. The procedures will execute serially within the same batch job process. If the ACME login mechanism is enabled for user authorization on the system, such a batch job will fail with %SYSTEM-F-ACCVIO status when attempting to start the second procedure. This issue has been corrected. 6.47.2 Images and/or Files Affected: [SYSEXE]LOGIN_ACME.EXE 6.47.3 VSI case identifier Jira BO-2041 6.47.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.47.5 Workaround Create a single command procedure file which invokes each of the specific procedures in order. For example, instead of: $ SUBMIT A,B,C submit a single procedure consisting of the lines: $ @A $ @B $ @C 6.48 Malformed domain\username login may trigger ACME Server issues 6.48.1 Problem Description When configured for external authentication, attempting to login with a username string that ends in the separator character "\" triggers errant audits and possibly an ACME Server restart. Example of a malformed username at login: Username: SALES\ This problem is corrected with this ECO kit. 6.48.2 Images and/or Files Affected: [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE 6.48.3 VSI case identifier Jiras BO-673, BO-706 Netsuite NS2054 6.48.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.48.5 Workaround Do not end a username with "\". 6.49 Detached process creation failure with ACME-enabled LOGINOUT.EXE 6.49.1 Problem Description If the OpenVMS ACME login is enabled, a process created using LOGINOUT.EXE as the image parameter to $CREPRC from a program in user mode will fail to authenticate and the created process will immediately terminate. This issue is corrected with this ECO kit. 6.49.2 Images and/or Files Affected: [SYSLIB]VMS$VMS_ACMESHR.EXE 6.49.3 VSI case identifier Jira BO-2038 6.49.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- Security Server changes ----- 6.50 Security Server failure and spurious server restart 6.50.1 Problem Description A bug in the Security Server led to an incorrectly initialized structure. This eventually caused stack corruption and a resultant access violation, which in turn caused the server to restart. This issue has been corrected. 6.50.2 Images and/or Files Affected: [SYSEXE]SECURITY_SERVER.EXE 6.50.3 VSI case identifier Jiras BO-2023, BO-2024 6.50.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- I/O Device Driver changes ----- 6.51 PCI passthrough support for HPE QLogic Fibre Channel cards 6.51.1 Problem Description This change enables PCI passthrough support for HPE SN1100Q, SN1600Q, and SN1610Q QLogic Fibre Channel cards on ESXi, Red Hat Enterprise Linux, and Oracle QEMU/KVM Linux Hypervisors. This provides support only for Fibre Channel data disks. Booting from a Fibre Channel disk is not supported. 6.51.2 Images and/or Files Affected: [SYS$LDR]SYS$PGQDRIVER.EXE [SYSEXE]SYS$CONFIG.DAT 6.51.3 VSI case identifier Jiras DRIV-192, DRIV-503, DRIV-511, DRIV-516, DRIV-560 6.51.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.52 Configuration enhancements for SATA devices 6.52.1 Problem Description The OpenVMS SATA device driver (PKDDRIVER) has been modified to enable these enhancements: - Allow LUNs higher than 7 for secondary SATA volumes. This allows more devices to be configured. - Allow shared interrupts with other devices on the same PCI bus. This prevents potential lost interrupts. 6.52.2 Images and/or Files Affected: [SYS$LDR]SYS$PKDDRIVER.EXE 6.52.3 VSI case identifier Jiras BO-1763, DRIV-523 Netsuite NS7612 6.52.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.53 VirtIO-SCSI device hangs under heavy load 6.53.1 Problem Description A synchronization error in the VirtIO-SCSI device driver could lead to VirtIO-SCSI device stalls or system hangs. This has been corrected with this ECO kit. 6.53.2 Images and/or Files Affected: [SYS$LDR]SYS$VSPDRIVER.EXE 6.53.3 VSI case identifier Jira BO-1885 6.53.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 ----- LAN changes ----- 6.54 Net applications using a VirtIO-Net device may hang on start 6.54.1 Problem Description Network connectivity can be lost due to stale MAC address use during net application initialization. A network application (such as DECnet) may change the MAC address. Should that application be stopped when no other applications are present, the MAC address should be changed back to the default value. A bug in the VirtIO-Net driver (EVDRIVER) incorrectly left the device with the now-closed application MAC value. A new application starting would assume it is using the default MAC address, but the device is still using the stale MAC address. The result is failure to transmit and receive packets using the default MAC address. This problem is corrected with this ECO kit. 6.54.2 Images and/or Files Affected: [SYS$LDR]SYS$EVDRIVER.EXE 6.54.3 VSI case identifier Jira DRIV-555 6.54.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 6.54.5 Workaround Reset the device when found to be non-functional. For example, if the device is EIA: $ MCR LANCP UPDATE DEVICE/RESET EIA This will reset the default MAC address properly. ----- MACRO programming support ----- 6.55 Issues with MACRO programs using floating-point instructions 6.55.1 Problem Description Programs written in MACRO that use floating-point instructions for arithmetic, conversions, or comparisons may not work properly. The code which emulates VAX floating-point instructions sometimes returns incorrect operation condition codes. For example: o Floating-point instructions may not report the result of an operation is greater than zero. o Conversion from floating-point to integer may not indicate an overflow error. o Compare instructions with floating-point operands may not return expected status. These issues resulted from subtle differences between I64 assembly code and x86-86 assembly code when the routines were ported to x86-64. These issues do not affect programs written in high-level languages. Only programs written in MACRO which use floating-point instructions are affected. Such programs must be re-linked after installing this ECO kit in order to use the corrected floating-point emulation. 6.55.2 Images and/or Files Affected: XMAC_FLOAT.OBJ, a module in [SYSLIB]STARLET.OLB 6.55.3 VSI case identifier Jiras BO-2085, BO-2090 6.55.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS x86-64 release after V9.2-3 7 IMAGES OR FILES REPLACED: [SYS$LDR]EXCEPTION.EXE Image name: "EXCEPTION" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:11.43 Image Checksum (MD5): 7705D0588822C4196259D2BA680DA8FF [SYS$LDR]EXCEPTION.STB File creation date and time: 4-DEC-2025 22:38:11.61 Checksum (MD5): 59181C066D3DE546233945D49540A4DB [SYS$LDR]EXCEPTION_MON.EXE Image name: "EXCEPTION_MON" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:11.82 Image Checksum (MD5): 4875ED63BF490EBF0E75DB3B7F49C899 [SYS$LDR]EXCEPTION_MON.STB File creation date and time: 4-DEC-2025 22:38:11.89 Checksum (MD5): 7BAFE0DB8666BDEC4217D0292EFD2BA9 [SYS$LDR]EXEC_INIT.EXE Image name: "EXEC_INIT" Image file identification: "X-284" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:12.40 Image Checksum (MD5): F859B58FB76F4E59F8DA47C3DFFFA921 [SYS$LDR]EXEC_INIT.STB File creation date and time: 4-DEC-2025 22:38:12.56 Checksum (MD5): FA1A031ADB6115221BE1AF3E98220D34 [SYS$LDR]F11BXQP.EXE Image name: "F11BXQP" Image file identification: "XQP V923R_4 GRV" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:12.16 Image Checksum (MD5): 220BEF05B4B30D5270642A04C6BBE995 [SYS$LDR]F11BXQP.STB File creation date and time: 4-DEC-2025 22:38:12.30 Checksum (MD5): EF1C157E5C04F21F51F34D84A4EE296F [SYS$LDR]IO_ROUTINES.EXE Image name: "IO_ROUTINES" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:14.43 Image Checksum (MD5): 8940A8EA99D4AA2E369916B261527206 [SYS$LDR]IO_ROUTINES.STB File creation date and time: 4-DEC-2025 22:38:14.97 Checksum (MD5): DD84AB10864970F2956EF72AC76A8D82 [SYS$LDR]IO_ROUTINES_MON.EXE Image name: "IO_ROUTINES_MON" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:15.72 Image Checksum (MD5): 85310DE55E5EC8D6329E671BF4B72C8A [SYS$LDR]IO_ROUTINES_MON.STB File creation date and time: 4-DEC-2025 22:38:15.94 Checksum (MD5): 4629AD7ACD4FAD0262A06298BAF0DEB7 [SYS$LDR]MESSAGE_ROUTINES.EXE Image name: "MESSAGE_ROUTINES" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:19.53 Image Checksum (MD5): E4FBD59E2384CBB344BBC10D72962D95 [SYS$LDR]MESSAGE_ROUTINES.STB File creation date and time: 4-DEC-2025 22:38:19.57 Checksum (MD5): 416F6F5871BDB8F44A57EC7E26C3853E [SYS$LDR]PROCESS_MANAGEMENT.EXE Image name: "PROCESS_MANAGEMENT" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:20.66 Image Checksum (MD5): CA6FB5CE5C7B4BA93E82460FDF1BE083 [SYS$LDR]PROCESS_MANAGEMENT.STB File creation date and time: 4-DEC-2025 22:38:20.98 Checksum (MD5): 0CED93F405985BF0F59000E4CD096860 [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE Image name: "PROCESS_MANAGEMENT_MON" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:21.31 Image Checksum (MD5): 90F94168ABBE2F02BA6733CE2C57BF69 [SYS$LDR]PROCESS_MANAGEMENT_MON.STB File creation date and time: 4-DEC-2025 22:38:21.50 Checksum (MD5): 1B2D73C26BB68F19B581AB4128C7F6CE [SYS$LDR]RMS.EXE Image name: "RMS" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:13.31 Image Checksum (MD5): E72B4F730DD9A8DFA95684DACB8F9829 [SYS$LDR]RMS.STB File creation date and time: 4-DEC-2025 22:38:13.45 Checksum (MD5): 4DA8FBA6842104AC0BDE1875657502A2 [SYS$LDR]SYS$ACPI.EXE Image name: "SYS$ACPI" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:12.82 Image Checksum (MD5): FA9F1E40979EC0468B3F448B19D299F8 [SYS$LDR]SYS$ACPI0006.EXE Image name: "SYS$ACPI0006" Image file identification: "X-35" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:17.92 Image Checksum (MD5): 6EA14B4974B8A87A2EE3179D2C9632FE [SYS$LDR]SYS$CLUSTER.EXE Image name: "SYS$CLUSTER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:16.27 Image Checksum (MD5): D0A2995AAE2D1F4508C14A30A2C965D9 [SYS$LDR]SYS$CLUSTER.STB File creation date and time: 4-DEC-2025 22:38:16.41 Checksum (MD5): D32122F34B6754EB346D1B73FE30E10F [SYS$LDR]SYS$CLUSTER_MON.EXE Image name: "SYS$CLUSTER_MON" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:16.69 Image Checksum (MD5): 59FCD13D26FE5464ABA8724C49AF9B44 [SYS$LDR]SYS$CLUSTER_MON.STB File creation date and time: 4-DEC-2025 22:38:16.78 Checksum (MD5): 190FA65C432BF414A1DB79650B0C484A [SYS$LDR]SYS$DKDRIVER.EXE Image name: "SYS$DKDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:15.48 Image Checksum (MD5): 73E096D7F2EB0E0D99FB71A58CD2C4C4 [SYS$LDR]SYS$EI1000X.EXE Image name: "SYS$EI1000XDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:13.69 Image Checksum (MD5): 8554032207140598F202833A77EEF504 [SYS$LDR]SYS$EVDRIVER.EXE Image name: "SYS$VIRTIODRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:14.85 Image Checksum (MD5): 067CFC23536C9EB356B34A15D24EB4DC [SYS$LDR]SYS$LAN.EXE Image name: "SYS$LAN" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:19.19 Image Checksum (MD5): CB5F0E4B8139341C6181F09FC1A29F69 [SYS$LDR]SYS$LAN_CSMACD.EXE Image name: "SYS$LAN_CSMACD" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:19.31 Image Checksum (MD5): 71747DEB442A1CAF554A735A8DD248B1 [SYS$LDR]SYS$LDDRIVER.EXE Image name: "SYS$LDDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:14.98 Image Checksum (MD5): 6FB010EDC550A2EE567B336C89AB9A35 [SYS$LDR]SYS$LLDRIVER.EXE Image name: "SYS$LLDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:16.19 Image Checksum (MD5): DA2CAC3775D85084EC7471E93C15D272 [SYS$LDR]SYS$PCIE_SUPPORT.EXE Image name: "SYS$PCIE_SUPPORT" Image file identification: "X-4" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:17.28 Image Checksum (MD5): E37B59E392DD264B9C71A425C7C13DFF [SYS$LDR]SYS$PCI_SUPPORT.EXE Image name: "SYS$PCI_SUPPORT" Image file identification: "X-4" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:17.41 Image Checksum (MD5): 54743097DF24AAD18622579396DC9BCD [SYS$LDR]SYS$PEDRIVER.EXE Image name: "SYS$PEDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:12.72 Image Checksum (MD5): 8ABA6079D9102BB8989B368578519F65 [SYS$LDR]SYS$PEDRIVER.STB File creation date and time: 4-DEC-2025 22:38:12.92 Checksum (MD5): 81018D26001882B015CDB99E7F804BEE [SYS$LDR]SYS$PEDRIVER_MON.EXE Image name: "SYS$PEDRIVER_MON" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:13.51 Image Checksum (MD5): E5B5B4FEB3451978963E306BB7BC4388 [SYS$LDR]SYS$PEDRIVER_MON.STB File creation date and time: 4-DEC-2025 22:38:13.66 Checksum (MD5): E69EADA9BAF30705BCD2006CA7F2C0B7 [SYS$LDR]SYS$PGQDRIVER.EXE Image name: "SYS$PGQDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:19.70 Image Checksum (MD5): B15FCB1149D5528C1E4FFDAB971F1C41 [SYS$LDR]SYS$PKDDRIVER.EXE Image name: "SYS$PKDDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:18.55 Image Checksum (MD5): 6DC40316894ADDC5BC728BF2F40764FE [SYS$LDR]SYS$PKMDRIVER.EXE Image name: "SYS$PKMDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:17.84 Image Checksum (MD5): 8ADD3B5D00EEA9F3027020AC60EDE58E [SYS$LDR]SYS$SEDRIVER.EXE Image name: "SYS$SEDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:13.44 Image Checksum (MD5): EC429C3462EC9D6EABBF51AAECCC8476 [SYS$LDR]SYS$VLANDRIVER.EXE Image name: "SYS$VLANDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:15.68 Image Checksum (MD5): D85C1CD3AAE135D06AEE6A259E4460E0 [SYS$LDR]SYS$VM.EXE Image name: "SYS$VM" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:17.12 Image Checksum (MD5): 7E759BB47957DE8436E06CEF2DCF5F8B [SYS$LDR]SYS$VM.STB File creation date and time: 4-DEC-2025 22:38:17.96 Checksum (MD5): 18C6496359DE44FD1E5DEA45E90A3FE3 [SYS$LDR]SYS$VMXNET3.EXE Image name: "SYS$VMXNET3DRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:15.37 Image Checksum (MD5): B8F820994A56B9BB7FF1FF7AD0FF85F7 [SYS$LDR]SYS$VM_MON.EXE Image name: "SYS$VM_MON" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:18.21 Image Checksum (MD5): FACA88AEE736ED9F2F9F573A4DD46CCE [SYS$LDR]SYS$VM_MON.STB File creation date and time: 4-DEC-2025 22:38:18.44 Checksum (MD5): F00D7B716AC9919B37F952F639E838E5 [SYS$LDR]SYS$VSPDRIVER.EXE Image name: "SYS$VSPDRIVER" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:20.56 Image Checksum (MD5): E2FBC1B5C251B9FE2E9EA2415AFB1F74 [SYS$LDR]SYS$VSPDRIVER.STB File creation date and time: 4-DEC-2025 22:38:20.74 Checksum (MD5): 3E7AB5E05D70CC56E8FF103DB3A8E7AF [SYS$LDR]SYSGETSYI.EXE Image name: "SYSGETSYI" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:19.15 Image Checksum (MD5): 864036302BBE28E8CEE9C59D8C1BB140 [SYS$LDR]SYSGETSYI.STB File creation date and time: 4-DEC-2025 22:38:19.24 Checksum (MD5): 71F6E4FA1E01F5729CDB52152976E184 [SYS$LDR]SYSTEM_PRIMITIVES.EXE Image name: "SYSTEM_PRIMITIVES" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:22.39 Image Checksum (MD5): AAE11046A8F4BBF106AA0FF1AD326B4B [SYS$LDR]SYSTEM_PRIMITIVES.STB File creation date and time: 4-DEC-2025 22:38:23.18 Checksum (MD5): F02BC736984796AB438957DA85E98A82 [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE Image name: "SYSTEM_PRIMITIVES_MIN" Image file identification: "X-16" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:25.35 Image Checksum (MD5): DA7C33AE0A14D37E7E462A914E46DB90 [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB File creation date and time: 4-DEC-2025 22:38:25.74 Checksum (MD5): 464BCD09F9886D6D4308ED9B0BAD85DD [SYSEXE]ACME_SERVER.EXE Image name: "ACME_SERVER" Image file identification: "X-46" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:11.27 Image Checksum (MD5): F359C14D4439BA009E8D35B9B7826644 [SYSEXE]AUTHORIZE.EXE Image name: "AUTHORIZE" Image file identification: "X-38" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:16.73 Image Checksum (MD5): F0A8AB71AC813C3840011CDE91EDEE10 [SYSEXE]JBC$COMMAND.EXE Image name: "JBC$COMMAND" Image file identification: "X-6" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:16.56 Image Checksum (MD5): 5CA5A32745D47C4AF07810EC8FA12D21 [SYSEXE]LANACP.EXE Image name: "LANACP" Image file identification: "X-40" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:17.57 Image Checksum (MD5): B0A0586287131D84405807844B344E4E [SYSEXE]LANCP.EXE Image name: "LANCP" Image file identification: "X-128" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:17.17 Image Checksum (MD5): C1A8670F0E366B67E96E2412C24502EC [SYSEXE]LINK.EXE Image name: "LINK" Image file identification: "I02-99" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:15.91 Image Checksum (MD5): DFF2ED53D0F3A831E81CA4095545F000 [SYSEXE]LOGIN_ACME.EXE Image name: "LOGIN_ACME" Image file identification: "LOGIN_ACME" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:16.39 Image Checksum (MD5): BA483A7D6B1E08B47E6FD82551C3169B Note: If the system is using the ACME login mechanism when this kit is installed, the image content from LOGIN_ACME will also be copied to [SYSEXE]LOGINOUT.EXE. [SYSEXE]LOGIN_UAF.EXE Image name: "LOGIN_UAF" Image file identification: "LOGIN_UAF" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:16.79 Image Checksum (MD5): 9E18A87802F04CE361962E55CB3196D2 Note: If the system is using the UAF login mechanism when this kit is installed, the image content from LOGIN_UAF will also be copied to [SYSEXE]LOGINOUT.EXE. [SYSEXE]MACRO.EXE Image name: "MACRO" Image file identification: "60-118-50F9M" Image build identification: "" Link identification: "Linker I02-99" Link Date/Time: 24-NOV-2025 14:41:16.01 Image Checksum (MD5): 861242DCF72F4918A35C39ED820DD53A [SYSEXE]SCACP.EXE Image name: "SCACP" Image file identification: "X-36" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:11.60 Image Checksum (MD5): 5EB5FBB5E97A8FAA212FC814CA4F2C0D [SYSEXE]SDA.EXE Image name: "SDA" Image file identification: "X-6" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 23:03:03.19 Image Checksum (MD5): 9A8AF2B9A55BA594A381813038245558 [SYSEXE]SEARCH.EXE Image name: "SEARCH" Image file identification: "X02-08" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:15.65 Image Checksum (MD5): 56093A0BDCC57C16632D70307A53CE6A [SYSEXE]SECURITY_SERVER.EXE Image name: "SECURITY_SERVER" Image file identification: "X-4" Image build identification: "" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:16.07 Image Checksum (MD5): C5A7383611C618A0C91545CF49E4579C [SYSEXE]SETP0_ACME.EXE Image name: "SETP0_ACME" Image file identification: "LOGIN_ACME" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:39:00.41 Image Checksum (MD5): 37BC047BA9F5E29818C0FE6167096C37 Note: If the system is using the ACME login mechanism when this kit is installed, the image content from SETP0_ACME will also be copied to [SYSEXE]SETP0.EXE. [SYSEXE]SETP0_UAF.EXE Image name: "SETP0_UAF" Image file identification: "LOGIN_UAF" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:39:00.54 Image Checksum (MD5): 3856ECBCBCD43C7B618CCD47A29C702B Note: If the system is using the UAF login mechanism when this kit is installed, the image content from SETP0_UAF will also be copied to [SYSEXE]SETP0.EXE. [SYSEXE]SETSHOWPATH.EXE Image name: "SETSHOWPATH" Image file identification: "X-6" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:39:01.28 Image Checksum (MD5): E59742E1722934F461ACBDC4497ECB9F [SYSEXE]SHOW.EXE Image name: "SHOW" Image file identification: "X-9" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:59.55 Image Checksum (MD5): F91910998BA61F78AA7B4C5B77129D44 [SYSEXE]SHUTDOWN.COM File creation date and time: 23-DEC-2025 04:28:46.21 Checksum (MD5): A5DEA998A1C6690C36C0A43D4D40E9F5 [SYSEXE]SYS$CONFIG.DAT File creation date and time: 30-SEP-2025 13:10:53.19 Checksum (MD5): 986B7C60631462A29EA0AEE6C5C0FC44 [SYSEXE]SYS$DUMP_KERNEL.EXE Image name: "SYS$DUMP_KERNEL" Image file identification: "X-88" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:11.22 Image Checksum (MD5): C95A5A1C7831531955174D6B56BCAFED [SYSEXE]SYSBOOT.EXE Image name: "SYSBOOT" Image file identification: "X-3" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:14.39 Image Checksum (MD5): 1E80750C02B785E12151A7472BEC27F2 [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.PDF File creation date and time: 4-DEC-2025 22:14:34.06 Checksum (MD5): 74E4BB873FBBB2BD668A3A67610D6FC1 [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.TXT File creation date and time: 23-JAN-2025 09:26:58.68 Checksum (MD5): AADC5FC7665427D39443932C36DEAA7A [SYSHLP]LANCP$HELP.HLB File creation date and time: 4-DEC-2025 22:33:42.93 Checksum (MD5): F28CC0D4808747FE526A581B8FF3ADA2 [SYSLIB]CLUE$SDA.EXE Image name: "CLUE$SDA" Image file identification: "X-92" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:10.23 Image Checksum (MD5): 1F170EA1ADF5DBB9A9652F705D535152 [SYSLIB]DBG$HA_KERNEL.EXE Image name: "DBG$HA_KERNEL" Image file identification: "V9.3-013" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:17.33 Image Checksum (MD5): 0548804B86CDEA4DA97F107004CAA939 [SYSLIB]DBG$HA_MAIN.EXE Image name: "DBG$HA_MAIN" Image file identification: "V9.3-013" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:16.95 Image Checksum (MD5): D00B0EAA56FC71334FC41EFB7A9E0A47 [SYSLIB]DEBUG.EXE Image name: "DEBUG" Image file identification: "V9.3-013" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:17.44 Image Checksum (MD5): 6C410CCCEC4F0511C847D7661B22ED35 [SYSLIB]DEBUGSHR.EXE Image name: "DEBUGSHR" Image file identification: "V9.3-013" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:12.43 Image Checksum (MD5): 3F2C63978D097251DB83B3659252903A [SYSLIB]DEBUGUISHR.EXE Image name: "DEBUGUISHR" Image file identification: "V9.3-013" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:14.11 Image Checksum (MD5): 79584C8A98DDD5A0895FA74181D796A9 [SYSLIB]DEC$BASRTL.EXE Image name: "DEC$BASRTL" Image file identification: "X01-039" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:37:59.51 Image Checksum (MD5): FFCD57582CC32797AB68B8CF0F6764C7 [SYSLIB]IOGEN$VIRTIO_CONFIG.EXE Image name: "IOGEN$VIRTIO_CONFIG" Image file identification: "X-6" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:37:43.78 Image Checksum (MD5): 9AA201A0D4490A2D1F8CC01DE04F7C72 [SYSLIB]LAN$SDA.EXE Image name: "LAN$SDA" Image file identification: "X-93" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:18.87 Image Checksum (MD5): 8C30DE3C35DAFCB30090B27FC8D06897 [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE Image name: "LDAPACME$LDAP-STD_ACMESHR" Image file identification: "LDAP-STD V1.30" Image build identification: "" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:11.23 Image Checksum (MD5): EA103AF7CB6355945357FCDC9F3CAFF8 [SYSLIB]LIBCXX.EXE Image name: "LIBCXX" Image file identification: "V1.0" Image build identification: "" Link identification: "Linker I02-99" Link Date/Time: 19-NOV-2025 14:10:21.37 Image Checksum (MD5): A0A4837CF195FDBCE2E400C5E3D7F33D [SYSLIB]LIBCXX.OLB File creation date and time: 4-DEC-2025 22:33:45.25 Checksum (MD5): ACEC37FCECB548C600A489E72B75F38D [SYSLIB]LIBCXXABI.EXE Image name: "LIBCXXABI" Image file identification: "V1.0" Image build identification: "" Link identification: "Linker I02-99" Link Date/Time: 19-NOV-2025 14:10:20.86 Image Checksum (MD5): B3C2EC22D19F6302998A8A4DDCFDB7CB [SYSLIB]LIBCXXABI.OLB File creation date and time: 4-DEC-2025 22:33:45.45 Checksum (MD5): C0A47A9D84B1DD7795A876DEB01BF6C4 [SYSLIB]LIBOTS.EXE Image name: "LIBOTS" Image file identification: "V1.0-1" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:37:18.76 Image Checksum (MD5): D30C1ED676D0552CA4AE5EEFA25BE9F1 [SYSLIB]LIBOTS.STB File creation date and time: 4-DEC-2025 22:37:18.86 Checksum (MD5): 74B9F77B67277AF24F32E85E1F2DA4CB [SYSLIB]LIBRTL.EXE Image name: "LIBRTL" Image file identification: "X01-001" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:37:18.78 Image Checksum (MD5): 87B6E2F655071BF69B79AF489ED4350B [SYSLIB]LIBRTL.STB File creation date and time: 4-DEC-2025 22:37:18.86 Checksum (MD5): 0A8D97121BE9EA2013C40A07DDCABFA8 [SYSLIB]PAS$RTL.EXE Image name: "PAS$RTL" Image file identification: "PAS$RTL V5.0-31" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:37:43.91 Image Checksum (MD5): 41000A2D77EEFF54EE508EFE14648C5A [SYSLIB]SDA$SHARE.EXE Image name: "SDA$SHARE" Image file identification: "X-2" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 23:03:02.62 Image Checksum (MD5): 4306C5807EEFDF7A795927C7ABADCC8A [SYSLIB]SMI$OBJSHR.EXE Image name: "SMI$OBJSHR" Image file identification: "X40-A9" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:11.24 Image Checksum (MD5): 2984A030AE81F306B80881332E0C62F8 [SYSLIB]VMS$VMS_ACMESHR.EXE Image name: "VMS$VMS_ACMESHR" Image file identification: "VMS_AGENT V2.0" Image build identification: "" Link identification: "Linker I02-97" Link Date/Time: 23-DEC-2025 04:46:55.32 Image Checksum (MD5): D5D33239B40A7BC6613A4B935EFF4C24 [SYSMGR]VMS$IMAGES_MASTER.DAT File creation date and time: 4-DEC-2025 22:14:46.18 Checksum (MD5): A9D317C7D2E59192031A796BDA4CF90C [SYSMSG]CLIUTLMSG.EXE Image name: "CLIUTLMSG" Image file identification: "0" Image build identification: "XGRV-K6N-000052" Link identification: "Linker I02-97" Link Date/Time: 4-DEC-2025 22:38:13.76 Image Checksum (MD5): CEE98A968CAE65DABD994D243D459447 [SYSUPD]VMSINSTAL.COM File creation date and time: 4-DEC-2025 22:24:26.06 Checksum (MD5): DBAEB09F957B0DB70AA6D2ABF726142F 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 ECO 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 an ECO 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 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. Info-ZIP's freeware ZIP and UNZIP tools are provided for use on this VSI OpenVMS version. Your site may have already set up symbols for these tools or other equivalent ZIP tools. If not, use the following command to define a symbol to run the UNZIP image: $ UNZIP == "$SYS$SYSDEVICE:[VMS$COMMON.SYSHLP.UNSUPPORTED.UNZIP]UNZIP" Then invoke UNZIP to unpack the kit using the command: $ UNZIP VMS923X_UPDATE-V0300 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. 8.2 Installation Command Install this kit with the POLYCENTER Software Installation Utility by logging into the SYSTEM account and typing the following command at the DCL prompt: $ PRODUCT INSTALL VMS923X_UPDATE [/SOURCE=location of kit] The kit location may be a 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 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 Should you need to remove this kit via PRODUCT UNDO PATCH, the same mandated reboot requirement is in effect as the memory disk image is changed back to the prior system content. The kit will update the memory disk image automatically as the final part of installation. There is currently no mechanism within the PCSI utility to cleanly invoke a system reboot for PRODUCT UNDO PATCH. You will be instructed as the kit exits that you must perform this function manually in this case. NOTE: When the SYS$MD.COM procedure is executing to update the memory disk image, some errors similar to these may be reported: %INSTALL-I-NONRESSHRADR, image installed ignoring '/RESIDENT' -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region or %INIT-F-GHREGIONFULL, An allocation was attempted from GH region GH_RES_CODE_S2 but there is not enough space in the region for the allocation. These are due to having both old and new copies of some images which are still being used until the system is rebooted. Typically they may be ignored as they will clear up during the reboot. Should there still be similar messages during system startup after reboot, you may need to use AUTOGEN to adjust the related system parameters. NOTE: During PRODUCT INSTALL or PRODUCT UNDO PATCH, the PCSI utility may issue the following message: There is not enough space on the memory disk. You must take these steps now to complete this installation: - Run @SYS$UPDATE:SYS$MD - Reboot the system In both cases, the kit procedure will run SYS$MD automatically. There is no need for you to execute SYS$MD before the reboot. For PRODUCT INSTALL, the reboot is also automatically handled by the kit procedure and you need not do a reboot yourself. For PRODUCT UNDO PATCH, you must manually reboot the system after the operation completes. The kit dialogue will remind you of this requirement at the end of the operation. There is currently no mechanism in PCSI to automatically invoke the system shutdown and reboot for UNDO PATCH operations. 8.4 Special Instructions for PRODUCT UNDO PATCH If you change the login mechanism from ACME to UAF or from UAF to ACME after installing this kit, you will need to take an additional step if you later remove the kit using PRODUCT UNDO PATCH. During PRODUCT UNDO PATCH, the PCSI utility is unaware that the LOGINOUT and SETP0 images in use by the system have different content from when the kit was installed. This can result in stale content or the wrong login style images in use after PRODUCT UNDO PATCH. To avoid a spurious change in the system login mechanism, use the SYS$MANAGER:SYS$LOGIN_SWITCH.COM procedure to reset the login style to the desired mechanism, using the command: $ @SYS$MANAGER:SYS$LOGIN_SWITCH You may use SYS$LOGIN_SWITCH.COM to either: - Restore the initial login style before using PRODUCT UNDO PATCH if you want to return to the original style. - Reset the login type back and forth from the new style after using PRODUCT UNDO PATCH. For example, if you are now using the ACME login and want to continue to use it, invoke the SYS$LOGIN_SWITCH.COM procedure twice, changing it to UAF and then back to ACME. This will correctly reset the ACME login images using the pre-kit installation images. If you have not changed the login style, PRODUCT UNDO PATCH will correctly restore the login state with no additional user actions required. 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 2025 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 X86VMS-VMS923X_UPDATE-V0300--4 Note: The terms "ECO kit" and "patch kit" may be used interchangeably in this document. This also applies for other VSI OpenVMS documentation when describing PCSI kits which provide remedial updates to a particular product. APPENDIX A - User-selectable control options and scripting considerations 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 OpenVMS ECO 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 updates, followed by a "Do you want to continue?" yes/no question, default = 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 = 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 a VSI OpenVMS ECO kit regarding the initial questions, define one or more of the following logical names before issuing the PRODUCT INSTALL command. o To skip one or more of the questions, define the corresponding logical name shown here to YES: SKIP$BACKUP - Skip system backup awareness question. SKIP$REBOOT - Skip system reboot awareness question. SKIP$ARCHIVE_OLD - Skip question about saving "_OLD" files. This will take the default, which is NO. SKIP$INTRO - Skip all three of the above questions. o To specifically override the default for saving "_OLD" files, define this logical name to YES or NO: VSIKIT$ARCHIVE_OLD - Sets an answer for saving "_OLD" files behavior. This will skip the archive "_OLD" files question regardless of the above SKIP$* logical names. o Two additional logical names may be defined as YES to modify the amount of explanatory text displayed for each question: VSIKIT$VERBOSE - Shows all explanatory text for questions. VSIKIT$BRIEF - Skips 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 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. For example, if aborting the current operation may have side effects for the system. Additionally: - 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 which provides the particular value, such as VSIKIT$ARCHIVE_OLD. 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 VMS923X_UPDATE/VERSION=V3.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= 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. Deprecated logical names from HPE ECO kits ------------------------------------------ The three names listed below were used by older VSI OpenVMS ECO kits for compatibility with HPE ECO 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 name New name --------------- -------------------- NO_ASK$BACKUP SKIP$BACKUP NO_ASK$REBOOT SKIP$REBOOT ARCHIVE_OLD VSIKIT$ARCHIVE_OLD