V9.2-3 Update V3.0 ECO Kit for VSI OpenVMS x86-64

INSTALL_1: To be installed by all customers.

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

Reference the Disclaimer of Warranty and Limitation of Liability Statement.

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.

VSI OpenVMS x86-64 V9.2-3

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 600 000 block minimum applies. To check fragmentation requirements, you can use the following commands:

$ ANALYZE/DISK/EXTENTS/REQUIRED=200000/NOOUTPUT disk
$ 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.

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:

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

VSI Case Identifiers

Jira BO-2131, BO-2132, BO-2169

Netsuite NS8441

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

On x86-64, the system may trigger a "math fault" exception if a floating-point exception occurs. Many of these are masked or handled by compiler-generated code, but those that 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.

Images and/or Files Affected

• [SYS$LDR]EXCEPTION.EXE
• [SYS$LDR]EXCEPTION.STB
• [SYS$LDR]EXCEPTION_MON.EXE
• [SYS$LDR]EXCEPTION_MON.STB

VSI Case Identifiers

Jira BO-2243, BO-2244

Netsuite NS8690

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

An error accessing the created schedule array would cause the code to unexpectedly exit without releasing the CLASS mutex. A later sanity check would then trigger the MTXCNTNONZ bugcheck.

This issue is corrected with this ECO kit.

Images and/or Files Affected

• [SYSLIB]SMI$OBJSHR.EXE

VSI Case Identifiers

Jira UT-362, UT-363

Netsuite NS8863

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

Under rare circumstances, the OPCOM process would sometimes encounter an access violation and end up in a compute-bound infinite loop.

The OPCOM mailbox MBA2 would sometimes get full when heavy system load generated many OPCOM messages. This could result in a stale timer context that caused an access violation. The OPCOM processing looped on the broken context, sending the process compute bound. A system reboot was likely the only way to clear the condition.

This issue is corrected with this ECO kit.

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

VSI Case Identifier

Netsuite NS8922

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

On all versions of VSI OpenVMS 9.x, 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

Images and/or Files Affected

• [SYS$LDR]EXCEPTION.EXE
• [SYS$LDR]EXCEPTION.STB
• [SYS$LDR]EXCEPTION_MON.EXE
• [SYS$LDR]EXCEPTION_MON.STB

VSI Case Identifiers

Jira BO-2340

Netsuite NS8996

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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

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.

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

Images and/or Files Affected

• [SYS$LDR]MESSAGE_ROUTINES.EXE
• [SYS$LDR]MESSAGE_ROUTINES.STB

VSI Case Identifier

Jira UT-382

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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 issue is corrected with this ECO kit.

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

VSI Case Identifiers

Jira DRIV-638

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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:

Images and/or Files Affected

• [SYSEXE]SYS$DUMP_KERNEL.EXE

VSI Case Identifiers

Jira BO-2240, DRIV-638

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

RTL Changes

Problem Description

The following issues are corrected with this ECO kit:

Images and/or Files Affected

• [SYSLIB]LIBCXX.EXE
• [SYSLIB]LIBCXX.OLB
• [SYSLIB]LIBCXXABI.EXE
• [SYSLIB]LIBCXXABI.OLB

VSI Case Identifiers

Jira DEV-3106, DEV-3165

Netsuite NS8777

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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. These include the memory handling routines to move, compare, search, and translate characters.

Images and/or Files Affected

• [SYSLIB]LIBOTS.EXE
• [SYSLIB]LIBOTS.STB

VSI Case Identifier

Jira RTLS-518

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

DEBUG Changes

Problem Description

The following issues in the Debugger are corrected with this ECO kit:

Images and/or Files Affected

• [SYSLIB]DEBUG.EXE
• [SYSLIB]DEBUGSHR.EXE
• [SYSLIB]DEBUGUISHR.EXE

VSI Case Identifiers

Jira DEV-1807, DEV-2456, DEV-2761, DEV-2768, DEV-2777, DEV-2778, DEV-2800, DEV-2901, DEV-2903, DEV-2908, DEV-2974, DEV-3012, DEV-3015, DEV-3023, DEV-3024, DEV-3036, DEV-3058, DEV-3066, DEV-3078, DEV-3079, DEV-3088, DEV-3108, DEV-3114, DEV-3123, DEV-3142, DEV-3147, DEV-3151, DEV-3181, DEV-3205

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Security Changes

Problem Description

The following changes for the SET PASSWORD/GENERATE command are provided in this ECO kit:

Images and/or Files Affected

• [SYSEXE]AUTHORIZE.EXE
• [SYSEXE]LOGIN_ACME.EXE
• [SYSEXE]LOGIN_UAF.EXE
• [SYSEXE]SETP0_ACME.EXE
• [SYSEXE]SETP0_UAF.EXE

VSI Case Identifiers

Jira UT-352, UT-358

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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:

Images and/or Files Affected

• [SYSEXE]SECURITY_SERVER.EXE

VSI Case Identifiers

Jira BO-1829, BO-2100, BO-2189, BO-2190, BO-2215, BO-2241

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

The SHOW AUDIT command output for process events requiring multiple display lines would sometimes include extra "Process:" prefixes.

For example, prior to the correction from this ECO kit, you would see output similar to the following:

$ 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 from this ECO kit, you will see output similar to the following:

$ 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

Images and/or Files Affected

• [SYSEXE]SHOW.EXE

VSI Case Identifier

Jira BO-886

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

ACME Changes

Problem Description

The following changes or issues in the OpenVMS ACME Agent are addressed in this ECO kit:

Images and/or Files Affected

• [SYSLIB]VMS$VMS_ACMESHR.EXE

VSI Case Identifiers

Jira BO-2128, BO-2171, BO-2325, BO-2383, BO-2384, LDAP-185

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

Output from the SHOW SERVER ACME command would sometimes contain null characters as part of the node name string. With the correction in this ECO kit, the null characters are now correctly replaced with spaces.

Images and/or Files Affected

• [SYSEXE]ACME_SERVER.EXE

VSI Case Identifiers

Jira BO-881, BO-2182

Netsuite NS3354

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

I/O Device Support Changes

Problem Description

If a DVD was mounted with the /MEDIA_FORMAT=FILES11 qualifier to use the file system to read OpenVMS content, the process would sometimes hang or encounter incorrect data when the device was read. A DVD- or CD-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.

Images and/or Files Affected

• [SYS$LDR]SYS$DKDRIVER.EXE

VSI Case Identifier

Jira BO-2133

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

VirtIO-SCSI devices on Oracle OCI would appear as offline and could not 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.

Images and/or Files Affected

• [SYS$LDR]SYS$DKDRIVER.EXE

VSI Case Identifier

Jira DRIV-566

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

Files on VirtIO-SCSI disks would sometimes encounter spurious data corruption. This was highly dependent on data format and usually only occurred on very large files.

This issue is corrected with this ECO kit.

Images and/or Files Affected

• [SYS$LDR]SYS$VSPDRIVER.EXE
• [SYS$LDR]SYS$VSPDRIVER.STB

VSI Case Identifiers

Jira BO-2147, BO-2148

Netsuite NS8343

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

The system would sometimes hang at boot if a large number of VirtIO-Net and/or VirtIO-SCSI adapters were configured.

Some device-specific capability checks were incorrectly using the wrong interrupt mode. The platform bus probing now correctly finds and configures these devices.

Images and/or Files Affected

• [SYS$LDR]SYS$PCIE_SUPPORT.EXE
• [SYS$LDR]SYS$PCI_SUPPORT.EXE

VSI Case Identifier

Jira DRIV-549

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

If an LD CONNECT command was issued to a physical device instead of the usual container file target, then the created LDxxx device could not be mounted and the error status SS$_ILLBLKNUM was returned.

This issue is corrected with this ECO kit.

Images and/or Files Affected

• [SYS$LDR]SYS$LDDRIVER.EXE

VSI Case Identifier

Jira DRIV-559

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

A system would sometimes fail to boot from an LSI Logic SCSI disk if the physical memory size was 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.

Images and/or Files Affected

• [SYS$LDR]SYS$PKMDRIVER.EXE

VSI Case Identifiers

Jira DRIV-592, BO-2174, BO-2175

Netsuite NS8549

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

SATA devices (like a CD-ROM) would sometimes 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.

This issue is corrected with this ECO kit.

Images and/or Files Affected

• [SYSEXE]SYS$CONFIG.DAT

VSI Case Identifiers

Jira BO-2233, BO-2234

Netsuite NS8662

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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.

Images and/or Files Affected

• [SYS$LDR]SYS$PGQDRIVER.EXE

VSI Case Identifiers

Jira DRIV-574, DRIV-611

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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:

Images and/or Files Affected

• [SYS$LDR]SYS$PGQDRIVER.EXE

VSI Case Identifier

Jira IN-188

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

LAN Changes

Problem Description

When time goes backwards (for example, when Daylight Savings Time ends), 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.

These issues are corrected with this ECO kit.

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

VSI Case Identifiers

Jira DRIV-549, DRIV-556, DRIV-617

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Workaround

The suggested workaround for this issue is to restart bandwidth monitoring after the time change using the following command:

$ MCR LANCP SET DEVICE/ALL/BANDWIDTH=RESTART

Problem Description

The LANCP commands to enable or disable jumbo frames were inconsistent for LAN Failover devices and other devices.

To resolve this issue, the /STANDARD qualifier has been added, and the /JUMBO and /STANDARD qualifiers are now equivalent to the respective /SIZE=JUMBO|STANDARD qualifier.

The following 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

Images and/or Files Affected

• [SYSEXE]LANCP.EXE
• [SYSHLP]LANCP$HELP.HLB

VSI Case Identifier

Jira DRIV-521

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

The following improvements have been made to LANCP tracing:

Images and/or Files Affected

• [SYSEXE]LANCP.EXE
• [SYSHLP]LANCP$HELP.HLB

VSI Case Identifiers

Jira DRIV-549, DRIV-556

Netsuite NS8314

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

MACRO Programming Support

Problem Description

The following changes were made to the MACRO compiler:

Images and/or Files Affected

• [SYSEXE]MACRO.EXE

VSI Case Identifiers

Jira DEV-3098, DEV-3112

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Cluster Changes

Problem Description

"Lost connection" and "Re-established connection" cluster messages lacked 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, such as listen timeouts. However, 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

--- <systemname> 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 eight 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 eight reasons are saved and shifted up 4 bits after each event to make room for the new reason code.

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

VSI Case Identifiers

Jira DRIV-556, DRIV-557

Netsuite NS8314

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Problem Description

PEDRIVER Load Class would sometimes be wrong for devices that saw link up later than when PEDRIVER discovered the devices. These were usually LAN Failover devices where no failset member had 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 priority 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.

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

VSI Case Identifiers

Jira DRIV-577

Netsuite NS-8314

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

RMS Changes

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 the V9.2-3 Update V1.0 ECO Kit for VSI OpenVMS x86-64 Release Notes).

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.

Images and/or Files Affected

• [SYS$LDR]RMS.EXE
• [SYS$LDR]RMS.STB

VSI Case Identifiers

Jira BO-2042, BO-2043, BO-2176, BO-2177

Netsuite NS7912,NS8558

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

XQP Changes

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 that 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 returning an SS$_ACCONFLICT (access conflict) status back to the user.

Images and/or Files Affected

• [SYS$LDR]F11BXQP.EXE
• [SYS$LDR]F11BXQP.STB

VSI Case Identifier

Netsuite NS8738

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

Miscellaneous Changes

Problem Description

The SHOW PATH/DEVICE command may exit with an access violation error.

This issue is corrected with this ECO kit.

Images and/or Files Affected

• [SYSEXE]SETSHOWPATH.EXE

VSI Case Identifier

Jira BO-2277

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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.

Images and/or Files Affected

• [SYSEXE]JBC$COMMAND.EXE

VSI Case Identifier

Jira UT-284

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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 would always reject the password if the PWDMIX flag was set for the account.

This issue is corrected with this ECO kit.

Images and/or Files Affected

• [SYSUPD]VMSINSTAL.COM

VSI Case Identifiers

Jira UT-289

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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.

This issue is corrected with this ECO kit.

Images and/or Files Affected

• [SYSEXE]SHUTDOWN.COM

VSI Case Identifiers

Jira SSH-1813, SSH-1814

Netsuite NS9031

Release Version of VSI OpenVMS That Will Contain This Change

The next VSI OpenVMS x86-64 release after V9.2-3.

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.

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, "User-Selectable Control Options and Scripting Considerations" for further details.

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

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.

%INSTALL-I-NONRESSHRADR, image installed ignoring '/RESIDENT' image_name
-INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region

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

   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

If you change the login mechanism from ACME to UAF (or vice versa) after installing this kit, you will need to take an additional step if you later remove the kit using the PRODUCT UNDO PATCH command.

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 following command:

$ @SYS$MANAGER:SYS$LOGIN_SWITCH.COM

You may use SYS$LOGIN_SWITCH.COM to either:

If you have not changed the login style, the PRODUCT UNDO PATCH command will correctly restore the login state with no additional user actions required.