ECO NUMBER: VAXSYS01_073
PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.3
UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.3
COVER LETTER
1 KIT NAME:
VAXSYS01_073
2 KITS SUPERSEDED BY THIS KIT:
None.
3 KIT DEPENDENCIES:
3.1 The following remedial kit(s), or later, must be installed
BEFORE installation of this, or any required kit:
None.
3.2 In order to receive all the corrections listed in this kit,
the following remedial kits, or later, should also be
installed:
VAXMOUN01_073
4 KIT DESCRIPTION:
4.1 Version(s) of OpenVMS to which this kit may be applied:
OpenVMS VAX V7.3
4.2 Files patched or replaced:
o [SYS$LDR]EXCEPTION.EXE (new image)
o [SYS$LDR]EXEC_INIT.EXE (new image)
o [SYS$LDR]IO_ROUTINES.EXE (new image)
o [SYS$LDR]LOGICAL_NAMES.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)
-- COVER LETTER -- Page 2
28 October 2002
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 [SYSEXE]SYSBOOT.EXE (new file)
o [SYSEXE]SYSBOOT_XDELTA.EXE (new file)
o [SYSEXE]VMB.EXE (new file)
5 PROBLEMS ADDRESSED IN VAXSYS01_073 KIT
o A process can hang in a MUTEX wait state.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
o Taking 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 take a
dump.
Note that, after this fix is applied, while a dump is being
taken, you may see a string of dots displayed indicating
progress through the dumping procedure. On some terminals,
only one line of dots is displayed. There may be a long delay
before the "Dump Complete" message is displayed. Please be
patient during this process, and wait until the "Dump Complete"
message appears.
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:
-- COVER LETTER -- Page 3
28 October 2002
o 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.
** Note **
In order to receive the complete MOUNT corrections that are
contained in this kit you will also need to install the
VAXMOUN01_073 ECO kit.
Images Affected:
- [SYS$LDR]IO_ROUTINES.EXE
- [SYS$LDR]IO_ROUTINES_MON.EXE
- [SYS$LDR]IO_ROUTINES.STB
- [SYS$LDR]IO_ROUTINES_MON.STB
o If a packet is requested from nonpaged pool that is larger than
nonpaged pool's maximum allowed size (NPAGVIR), the request
fails. However, nonpaged pool expands to its maximum size,
even though the request can not be satisfied.
Images Affected:
- [SYS$LDR]SYSTEM_PRIMITIVES.EXE
- [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
- [SYS$LDR]SYSTEM_PRIMITIVES.STB
- [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB
o In an OpenVMS mixed version clustered environment, a fatal
invalid identifier format (%SYSTEM-F-IVIDENT) error can result
in 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:
-- COVER LETTER -- Page 4
28 October 2002
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
- [SYS$LDR]SECURITY_MON.EXE
- [SYS$LDR]SECURITY.STB
- [SYS$LDR]SECURITY_MON.STB
o After an upgrade to V7.3, some VAX nodes take somewhat longer
to boot than the pre-V7.3 boot times. Some take a lot longer
to boot. This delay occurs between the "OpenVMS" banner
message and the "%WBM-..." message. This ECO will bring the
boot time between these two banner messages down to pre-V7.3
boot times.
Images Affected:
- [SYS$LDR]EXEC_INIT.EXE
o The system can crash with a CWLNMERR bugcheck at various
locations in the LOGICAL_NAMES executive image.
Images Affected:
- [SYS$LDR]LOGICAL_NAMES.EXE
o A system can crash with an INVEXCEPTN bugcheck.
Images Affected:
- [SYSLDR]PROCESS_MANAGEMENT.EXE
- [SYSLDR]PROCESS_MANAGEMENT.STB
- [SYSLDR]PROCESS_MANAGEMENT_MON.EXE
- [SYSLDR]PROCESS_MANAGEMENT_MON.STB
o If there is a lot of cluster-wide $GETJPI activity, a process
may hang waiting for the completion of an RMS $FLUSH operation.
The I/O request resulting from this may wait forever because
-- COVER LETTER -- Page 5
28 October 2002
the IOSB is not filled in.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
6 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.
7 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 VAXSYS01_073 [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.
7.1 Special Installation Instructions:
7.1.1 VAXMOUN01_073 Kit
In order to receive the complete MOUNT corrections that are
contained in this kit you will also need to install the
VAXMOUN01_073 ECO kit.
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
-- COVER LETTER -- Page 6
28 October 2002
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.
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.