ECO NUMBER: VAXSYS03_072 PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.2 COVER LETTER 1 KIT NAME: VAXSYS03_072 2 KITS SUPERSEDED BY THIS KIT: VAXSYS02_072 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: VAXUPDATE01_072 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: o VAXAUDS01_072 o VAXCLIU03_072 o VAXMOUN01_072 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS VAX V7.2 4.2 Files patched or replaced: o [SYS$LDR]EXCEPTION.EXE (new image) o [SYS$LDR]EXEC_INIT.EXE (new image) o [SYS$LDR]FTDRIVER.EXE (new image) o [SYS$LDR]IO_ROUTINES.EXE (new image) o [SYS$LDR]LOCKING.EXE (new image) -- COVER LETTER -- Page 2 5 February 2003 o [SYS$LDR]LOGICAL_NAMES.EXE (new image) o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) o [SYS$LDR]PAGE_MANAGEMENT.EXE (new image) o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) o [SYSLIB]SECURESHR.EXE (new image) o [SYSLIB]SECURESHRP.EXE (new image) o [SYS$LDR]SECURITY.EXE (new image) o [SYS$LDR]SYS$CLUSTER.EXE (new image) o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) o [SYSEXE]TERTIARY_VMB.EXE (new image) o [SYS$LDR]VAXCLUSTER_CACHE.EXE (new image) o [SYSEXE]SYSBOOT.EXE.EXE (new image) o [SYSEXE]SYSBOOT_XDELTA.EXE.EXE (new image) o [SYSEXE]VMB.EXE.EXE (new image) o [SYSEXE]SYS$CLUSTER.STB (new file) 5 PROBLEMS ADDRESSED IN VAXSYS03_072 KIT o On a multi-processor machine, in a small cluster, when creating or updating a clusterwide logical name, a process may hang in RWSCS state. This fix closes a small window between internal synchronization states and prevents this problem. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE o The system can crash with a CWLNMERR bugcheck. The failing PC is in routine TRNLNM, offset 7AC in PSECT EXEC$HI_USE_PAGEABLE_CODE Images Affected: - [SYS$LDR]LOGICAL_NAMES.EXE -- COVER LETTER -- Page 3 5 February 2003 o A system can crash with an INVEXCEPTN bugcheck. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE 6 PROBLEMS ADDRESSED IN VAXSYS02_072 KIT o The $GETJPI system service can crash either the sending or target node in an OpenVMS Cluster via CWSERR or INVEXCEPTN bugchecks. In most cases the target node crashes but the actual problem occurs on the sending no See the Crashdump Summary Information below. Crashdump Summary Information: ------------------------------ Bugcheck Type: KRNLSTAKNV, Kernel stack not valid Current Process: CLUSTER_SERVER Current Image: Failing PC: FFFFFFFF 80060090 Failing PS: 00000000 00000000 Module: EXCEPTION Offset: 00014090 Crashdump Summary Information: ------------------------------ Bugcheck Type: CWSERR, Error detected while processing cluster-wide service request Current Process: CLUSTER_SERVER Current Image: $1$DKB205:[SYS0.SYSCOMMON.][SYSEXE]CSP.EXE Failing PC: FFFFFFFF.801E4350 SYS$CLUSTER_NPRO+32350 Failing PS: 2C000000.00000000 Module: SYS$CLUSTER Offset: 00032350 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]SYS$CLUSTER.EXE o If a process working set is reduced, such that the working set only contains locked pages, and the process then pagefaults, the system could bugcheck in MMG$PAGEFAULT with a "FREWSLX, Free working set list index, resource wait" error. The bugcheck occurs because no free working set list entries can be found. -- COVER LETTER -- Page 4 5 February 2003 Images Affected: - [SYS$LDR]PAGE_MANAGEMENT.EXE o All FT device protection is hard-coded to (S:RWPL,O:RWPL,G,W). When the SECURITY class TERMINAL device template's profile is applied to device FTA0: at AUDIT_SERVER startup, any new settings are applied to FTA0:. However, protections are still being hard-coded within FTDRIVER for new FT devices created later. Because of this, FT devices do not inherit settings from the SECURITY class DEVICE object TERMINAL template as do other devices, such as LT, TN, RT, and TT. This change sets device protection for only FTA0:. This allows the customer the option of modifying FTA0:'s device protection later in the boot process (for example, in SYSTARTUP_VMS.COM) or manually with a command similar to the following: $ SET SECURITY/CLASS=DEVICE/PROTECTION=(S:RWLP,O:RWLP,G:RW,W:R) FTA0: This new protection will be inherited from FTA0: by any new FT devices created thereafter, (as well as other settings, such as ACLs, originating from the SECURITY class TERMINAL device template) Although, without customer intervention, this same modified code behaves the same as in prior releases. This ensures that existing applications will continue to function correctly. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]FTDRIVER.EXE o A system can crash with an "XQPERR, Error detected by file system XQP F11BXQP+11D94 %SYSTEM-F-IVLOCKID, invalid lock ID" bugcheck Note: To receive this full fix, you must also install the VAXCLIU03_072 ECO kit. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE o An attempt to close a file, whose disk has timed out in mount-verification, will fail. This causes FILCNTNONZ bugchecks during process rundown. Images Affected: -- COVER LETTER -- Page 5 5 February 2003 - [SYS$LDR]IO_ROUTINES.EXE o Application Data Corruption could occur every 45 minutes when using the TMX application on an SMP system. Applications such as TMX, which uses its own I/O synchronization, might inadvertently read and write the same block at almost the same time. The cache could sometimes contain stale data. Images Affected: - [SYS$LDR]VAXCLUSTER_CACHE.EXE o $TRNLNM code can exit without releasing the logical name mutex. If that $TRNLNM request or any subsequent kernel mode system service request made by that process exits with an error status, the system will crash with a MTXCNTNZ bugcheck. If no kernel mode system service request made by that process exits with an error status, the system will eventually hang with some processes in MUTEX wait trying to acquire the logical name mutex. If some of those processes have already acquired other mutexes, such as the I/O data base mutex and GSD mutex, there may be other processes in MUTEX wait trying to acquire those mutexes. The $TRNLNM problem is exercised by a fairly unusual combination of circumstances and is more likely to be seen on an SMP system. Crashdump Summary: ------------------ Bugcheck Type: MTXCNTNONZ, Mutex count nonzero at system service exit Current Process: ORA_PRODC0661 Current Image: $1$DGA21:[ORACLE8.RDBMS]ORACLE.EXE Failing PC: FFFFFFFF.8008EFF4 __RELEASE_SERVICE_ERROR_EXCEPT+00094 Failing PS: 38000000.00000200 Module: EXCEPTION (Link Date/Time: 28-MAY-1999 23:22:24.23) Offset: 00018FF4 Images Affected: - [SYS$LDR]LOGICAL_NAMES.EXE o Writing of full dumps of VAX systems with greater than 2 gigabytes of physical memory does not work. Symptoms can vary, but the most common is a HALT in kernel mode while trying to write the dump. -- COVER LETTER -- Page 6 5 February 2003 Images Affected: - [SYSEXE]SYSBOOT.EXE - [SYSEXE]SYSBOOT_XDELTA.EXE - [SYSEXE]TERTIARY_VMB.EXE - [SYSEXE]VMB.EXE - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXEC_INIT.EXE o MOUNT and Mount Verification sanity checks have been relaxed to correct the following issues: - A MOUNT/NOWRITE command on a disk on one cluster will now work correctly even if the disk is mounted with a /WRITE qualifier on another cluster in the SAN (Storage Area Network). Previously, depending on the order in which the mounts were executed, the mount would fail with the error message: DIFVOLMNT - different volume already mounted on this device. - If a disk is mounted with a /WRITE qualifier on one cluster and a /NOWRITE qualifier on another cluster in the SAN, MountVerification will fail with a WrongVolume status error on the system which had the disk mounted /NOWRITE. This change allows MountVerification to complete successfully in this configuration. Note: To receive this full fix, you must also install the VAXMOUN01_072 ECO kit. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE o If a packet is requested from non-paged pool that is larger than nonpaged pool's maximum allowed size (NPAGVIR), the request fails but nonpaged pool expands to its maximum size even though the request can not be satisfied. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE -- COVER LETTER -- Page 7 5 February 2003 - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE o In a mixed OpenVMS version clustered environment, a fatal invalid identifier format (%SYSTEM-F-IVIDENT) error can result on versions of OpenVMS that are not OpenVMS COE (Common Operating Environment) compliant. This can occur on non-COE compliant OpenVMS systems when attempting to display the rights identifiers of a process that is granted a valid GID COE identifier. The following commands, lexicals, (and respective system services), cause the %SYSTEM-F-IVIDENT system message to be displayed instead of the text translation of this COE GID IDENTIFIER: 1. F$GETJPI("PID_xxx","PROCESS_RIGHTS") 2. F$GETJPI("PID_xxx","RIGHTSLIST") 3. $ SHOW PROCESS/ALL 4. $ SHOW PROCESS/RIGHTS Images Affected: - [SYS$LDR]SECURITY.EXE - [SYSLIB]SECURESHR.EXE - [SYSLIB]SECURESHRP.EXE o The command reply mailbox timeout has been raised to 120 seconds for the SET AUDIT/SERVER=INITIATE command. The retry timer for Object Initiation has been dropped to 15 seconds. This allows multiple init retries before the command times out. Before this change, any object init retry would be meaningless, since it would not be attempted until after the command timed out, which could result in a failure status for a successful operation. Note: To receive this full fix, you must also install the VAXCLIU03_072 ECO kit. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]IO_ROUTINES.EXE o A cluster-wide AUDIT_SERVER hang prevents boot from completing. Note: To receive this full fix, you must also install -- COVER LETTER -- Page 8 5 February 2003 the VAXCLIU03_072 ECO kit. Images Affected: o [SYS$LDR]SECURITY.EXE o [SYS$LDR]IO_ROUTINES.EXE o The order in which certain locks are taken was changed to prevent deadlocks between blocking locks and RMS record locks on the Objects database. Note: To receive this full fix, you must also install the VAXCLIU03_072 ECO kit. Images Affected: o [SYS$LDR]SECURITY.EXE o [SYS$LDR]IO_ROUTINES.EXE o Delete an unused reply mailbox before returning to the caller. Note: To receive this full fix, you must also install the VAXCLIU03_072 ECO kit. Images Affected: o [SYS$LDR]SECURITY.EXE o [SYS$LDR]IO_ROUTINES.EXE o The command SET AUDIT/NOLISTENER fails under all circumstances. See error message below: $ SET AUDIT/NOLISTENER %SET-E-VERIFYFAIL, specified operation was not performed due to the following error: -AUDSRV-W-REQPKTINV, required packet missing or invalid; requestor PID: 00000000 $ Note: To receive this full fix, you must also install the VAXCLIU03_072 ECO kit. Images Affected: o [SYS$LDR]SECURITY.EXE -- COVER LETTER -- Page 9 5 February 2003 o [SYS$LDR]IO_ROUTINES.EXE 7 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_1 : To be installed by all customers. 8 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL VAXSYS03_072 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. This kit requires a system reboot. Compaq strongly recommends that a reboot is performed immediately after kit installation to avoid system instability If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. Copyright (c) Compaq Computer Company, 2002 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. COMPAQ, the COMPAQ logo, VAX, Alpha, VMS, and OpenVMS are registered in the U.S. Patent and Trademark Office. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from COMPAQ are required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. COMPAQ shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided as is without warranty of any kind and is subject to change without notice. The warranties for COMPAQ products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. -- COVER LETTER -- Page 10 5 February 2003 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 COMPAQ 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.