ECO NUMBER: VAXF11X02_073
PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.3
UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.3
COVER LETTER
1 KIT NAME:
VAXF11X02_073
2 KITS SUPERSEDED BY THIS KIT:
VAXF11X01_073
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:
None.
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]F11BXQP.EXE (new image)
o [SYSEXE]F11CACP.EXE (new image)
o [SYSEXE]F11DACP.EXE (new image)
5 PROBLEMS ADDRESSED IN VAXF11X02_073 KIT
o The VAXF11X01_073 ECO kit was missing an installation file
which prevented the kit from installing.
-- COVER LETTER -- Page 2
12 September 2002
6 PROBLEMS ADDRESSED IN VAXF11X01_073 KIT
o If multiple processes on the same node are attempting to obtain
or convert the same lock, which is being mastered on another
node, it is possible to get an SS$_CVTUNGRANT error in addition
to an SS$_IVLOCKID error during this race. The problem arises
because the new, faster lock manager, adds timing
considerations that were not previously present. The code now
traps this error and retries the lock conversion attempt.
Images Affected:
- [SYS$LDR]F11BXQP.EXE
o A system can crash with a MAPCNTZER bugcheck, in XQP routine
MAKE_POINTER, when trying to expand or create a new
PAGEFILE.SYS.
Crash Dump Summary Information:
------------------------------
Bugcheck Type: MAPCNTZER, Attempted to generate
zero length map pointer
Current Image: DSA0:[SYS0.SYSCOMMON.][SYSEXE]SYSGEN.EXE
Failing PC: FFFFFFFF.A89F6B98 MAKE_POINTER_C+00044
Failing PS: 30000000.00000000
Module: F11BXQP (Link Date/Time:
24-AUG-2000 07:20:45.47)
Offset: 00026B98
This problem occurs in the XQP only on volumes where the
cluster size exceeds 256 and the volume is so fragmented that
the file in question would need to expand beyond the first file
header. The fix for this problem will result in a
SS$_HEADERFULL error for SYSGEN CREATE instead the bugcheck
encountered.
Images Affected:
- [SYS$LDR]F11BXQP.EXE
o The system can crash with a UNXSIGNAL bugcheck in routine
ACL_BUILDACL. The exception occurs because the XQP tries to
access a null FCB (which was loaded from a previous FCB that
had FCB$L_EXFCB = 0).
Crash Dump Summary
------------------
Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP
Current Process: BATCH_488
Failing PS: 20000000.00000000
Module: F11BXQP (Link Date/Time:
24-AUG-2000 07:20:45.47)
Offset: 00052DC4
-- COVER LETTER -- Page 3
12 September 2002
Images Affected:
- [SYS$LDR]F11BXQP.EXE
o When using SYS$CHECK_ACCESS against a file that resides on a
CD-ROM the process disappears and the accounting record shows a
final status of ACCVIO. If BUGCHECK_FATAL or SYSTEM_CHECK are
set, the system bugchecks with SSRVEXCEPT in SYS$$CHECK_ACCESS.
The same program, when used against a file that is not on a
CD-ROM, works as expected.
The problem occurs because SYS$$CHECK_ACCESS calls
FIL$OSR_CLONE_PROFILE. FIL$OSR_CLONE_PROFILE does a $QIO
against the file for IO$_ACPCONTROL, with a FIB control
function of FIB$C_CLONE_FIL_PROFILE. This $QIO returns good
status even though this control function is not implemented in
ACPCONTROL.B32. So, routine FIL$OSR_CLONE_PROFILE returns
SS$_NORMAL and the returned ORB is null (which leads to the
exception).
Also, it was found that the embedded ORB associated with the
file (FCB) was not being initialized in the case of an XAR not
being supplied.
Images Affected:
- [SYSEXE]F11CACP.EXE
- [SYSEXE]F11DACP.EXE
o SYS$CHECK_ACCESS uses the FIB option FIB$V_NO_READ_DATA to read
the ACL/protection attributes of a file object. When the file
is opened with read sharing dis-allowed, this service returns
SS$_ACCONFLICT. If the service adds the FIB$V_CONTROL flag,
this does not occur.
The problem occurs because the code presumes that for access to
a file open for exclusive access would require the user specify
control access. The security group decided that this was not
needed so the use of CONTROL was removed. The use of
FIB$V_NOLOCK, which also allows this, still requires SYSPRV if
the file data is to be read.
This change relaxes the requirement for specifying
FIB$V_CONTROL, which implies the need for write access to the
file. This is not the case and FIB$V_NO_READ_DATA prevents the
file system from mapping the data in the file.
Images Affected:
-- COVER LETTER -- Page 4
12 September 2002
- [SYS$LDR]F11BXQP.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 VAXF11X02_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.
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 5
12 September 2002
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.