**************************** ECO SUMMARY INFORMATION **************************** Kit Name: VMS722_F11X-V0200 DEC-AXPVMS-VMS722_F11X-V0200--4.PCSI Kit Applies To: OpenVMS ALPHA V7.2-2 Approximate Kit Size: 1008 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - Rolling Reboot Superseded Kits: VMS722_F11X-V0100 Mandatory Kit Dependencies: VMS722_UPDATE-V0100 VMS722_PCSI-V0100 Optional Kit Dependencies: None ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS722_F11X-V0200 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 1 KIT NAME: VMS722_F11X-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. This 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) 2.2 Reboot Requirement: Reboot Required. HP 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. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-2 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS722_F11X-V0100 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS722_PCSI-V0100 - VMS722_UPDATE-V0100 Page 2 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 FILES PATCHED OR REPLACED: o [SYS$LDR]F11BXQP.EXE (new image) Image Identification Information image name: "F11BXQP" image file identification: "XQP V7.2-2R-005" image file build identification: "X71Z-0050170011" link date/time: 17-JUL-2003 10:55:33.00 linker identification: "A11-39" o [SYS$LDR]F11BXQP.STB (new file) 6 PROBLEMS ADDRESSED IN THIS KIT 6.1 New problems addressed in the VMS722_F11X-V0200 kit 6.1.1 System can crash with a "UNXSIGNAL, Unexpected signal name in ACP" bugcheck 6.1.1.1 Problem Description: The system can crash with a "UNXSIGNAL, Unexpected signal name in ACP" bugcheck in routine ACL_BUILDACL. Crashdump Summary Information ----------------------------- Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP Failing PC: FFFFFFFF.C9114E54 ACL_BUILDACL_C+00594 Failing PS: 20000000.00000000 Module: F11BXQP (Link Date/Time: 24-AUG-2000 07:20:45.47) Offset: 00052E54 Images Affected: - [SYS$LDR]F11BXQP.EXE Page 3 6.1.1.2 CLDs, and QARs reporting this problem: 6.1.1.3 CLD(s) CFS.83831,CFS.85044,CFS.88565,CFS.90523 6.1.1.4 QAR(s) None. 6.1.1.5 Problem Analysis: 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. 6.1.1.6 Work-arounds: None. 6.1.2 "%SYSTEM-W-ACCONFLICT, file access conflict" error 6.1.2.1 Problem Description: When using sys$check_access against a file opened in write mode, a "%SYSTEM-W-ACCONFLICT, file access conflict" error is returned. Images Affected: - [SYS$LDR]F11BXQP.EXE 6.1.2.2 CLDs, and QARs reporting this problem: 6.1.2.3 CLD(s) 70-3-6002,CFS.92708 6.1.2.4 QAR(s) None. 6.1.2.5 Problem Analysis: 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 to not allow read sharing, this service would return SS$_ACCONFLICT. If the service adds the FIB$V_CONTROL flag this does not occur. Page 4 The change relaxes the requirement for the need to specify FIB$V_CONTROL, which implies the need 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. 6.1.2.6 Work-arounds: None. 6.1.3 "UNXSIGNAL, Unexpected signal name in ACP" bugcheck 6.1.3.1 Problem Description: The system can crash with a "UNXSIGNAL, Unexpected signal name in ACP" bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP Current Image: Failing PC: FFFFFFFF.802163C8 EXTEND_C+00B68 Failing PS: 10000000.00000000 Module: F11BXQP (Link Date/Time: 17-MAR-2001 03:16:47.08) Offset: 0001A3C8 Stack Pointers: KSP = 00000000.7AC7EF30 ESP = 00000000.7FFA6000 SSP = 00000000.7FFAB6C0 USP = 00000000.7AB75AF0 Images Affected: - [SYS$LDR]F11BXQP.EXE 6.1.3.2 CLDs, and QARs reporting this problem: 6.1.3.3 CLD(s) None. 6.1.3.4 QAR(s) 75-13-0895 Page 5 6.1.3.5 Problem Analysis: The crash occurs when, during a header extension, the LAST_FCB value is zero as the last header on disk has not yet mapped to an FCB. 6.1.3.6 Work-arounds: None. 6.1.4 Failing UIC not reported when a diskquota operation fails 6.1.4.1 Problem Description: If a diskquota operation fails, the UIC of the current thread may not reflect the UIC operation on the file created. This may be due to privileges of the thread or the use of Resource Identifiers on a file/directory. Images Affected: - [SYS$LDR]F11BXQP.EXE 6.1.4.2 CLDs, and QARs reporting this problem: 6.1.4.3 CLD(s) None. 6.1.4.4 QAR(s) None. 6.1.4.5 Problem Analysis: As the ability to create a file with differing resource ownership increased, the failure mechanism did not provide means of determining the failing resource value. 6.1.4.6 Work-arounds: None. Page 6 6.1.5 System can crash with an "XQPERR, Error detected by file system XQP" bugcheck 6.1.5.1 Problem Description: The system can crash with an "XQPERR, Error detected by file system XQP" bugcheck: Crashdump Summary Information: ------------------------------ Bugcheck Type: XQPERR, Error detected by file system XQP VMS Version: V7.3-1 Current Process: BATCH_875 Current Image: DSA1:[SYS5.SYSCOMMON.] [SYSEXE]LOGINOUT.EXE Failing PC: FFFFFFFF.80248600 SEARCH_FCB_C+00E70 Failing PS: 00000000.00000000 Module: F11BXQP (Link Date/Time: 18-JUL-2002 19:55:23.70) Offset: 00014600 Images Affected: - [SYS$LDR]F11BXQP.EXE 6.1.5.2 CLDs, and QARs reporting this problem: 6.1.5.3 CLD(s) CFS.98483,70-3-6831 6.1.5.4 QAR(s) None. 6.1.5.5 Problem Analysis: If a process on one node performs a FID_TO_SPEC operation (ATR$C_FILE_SPEC) on a file, as the operation traces the directory path it may release the serialization on the FCB and, at the same time, increase the REFCNT. If another node, processing this same file for delete, does not notice that the file is locked elsewhere in the cluster, it succeeds with a full delete of the file. With the file now free, another process can create a file with the header and search for the FCB. The FCB in memory references an old header and the system bugchecks with an XQPERR bugcheck (in RES_SEQ_MISMATCH). Page 7 6.1.5.6 Work-arounds: None. 6.1.6 "UNXSIGNAL, Unexpected signal" bugcheck 6.1.6.1 Problem Description: Use of the undocumented and unsupported command SET WATCH FILE could result in an ACCVIO or UNXSIGNAL bugcheck if the process P1 space allocation area becomes corrupt. Crashdump Summary Information: ------------------------------ Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP Current Image: DSA100:[SYS1.SYSCOMMON.] [SYSEXE]COBOL.EXE;3 Failing PC: FFFFFFFF.80040510 EXE$ALLOCATE_C+00070 Failing PS: 00000000.00000000 Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time: 17-OCT-2001 00:50:50.04) Offset: 00012510 Stack Pointers: KSP = 00000000.7B042E70 ESP = 00000000.7B09E0F8 SSP = 00000000.7FFAC100 USP = 00000000.7AE20FA0 Images Affected: - [SYS$LDR]F11BXQP.EXE 6.1.6.2 CLDs, and QARs reporting this problem: 6.1.6.3 CLD(s) CFS.99020,70-3-6915 6.1.6.4 QAR(s) None. 6.1.6.5 Problem Analysis: See Problem Description Page 8 6.1.6.6 Work-arounds: None. 6.1.7 "UNXSIGNAL, Unexpected signal name in ACP" bugcheck 6.1.7.1 Problem Description: The system can crash with an "UNXSIGNAL, Unexpected signal name in ACP" bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP Current Process: TC_ESG_0 Current Image: Failing PC: FFFFFFFF.802442C0 F11BXQP+222C0 Failing PS: 30000000.00000000 Module: F11BXQP (Link Date/Time: 18-JUL-2002 19:55:23.70) Offset: 000222C0 Stack Pointers: KSP = 00000000.7AEE4DF0 ESP = 00000000.7FFA6000 SSP = 00000000.7FFAC230 USP = 00000000.7ADA9AF0 Images Affected: - [SYS$LDR]F11BXQP.EXE 6.1.7.2 CLDs, and QARs reporting this problem: 6.1.7.3 CLD(s) None. 6.1.7.4 QAR(s) 75-83-1048 6.1.7.5 Problem Analysis: When a header is extended, the FCB may not yet be built on a particular node. The FCB chain is incomplete or may have been truncated and not rebuilt. As the location of the next extent is found, the header chain is completed, but the FCB chain is not. Thus an ACCVIO (UNXSIGNAL)occurs. Page 9 6.1.7.6 Work-arounds: None. 6.1.8 Revision date moves backwards 6.1.8.1 Problem Description: When reading the revision date, the use of the FCB field on an ODS-2 disk can result in the revision date moving backwards. That is, the ATR$C_REVDATE would read the FCB modification when in reality, it is not valid for an ODS-2 disk. This is also true in the case where access_dates are not enabled on an ODS-5 disk. Images Affected: - [SYS$LDR]F11BXQP.EXE 6.1.8.2 CLDs, and QARs reporting this problem: 6.1.8.3 CLD(s) None. 6.1.8.4 QAR(s) None. 6.1.8.5 Problem Analysis: See Problem Description 6.1.8.6 Work-arounds: None. 6.1.9 DIRECTORY/FULL command gives incorrect revision dates 6.1.9.1 Problem Description: When a program, such as BACKUP, accesses the secondary header, information from the header in the form of a date will be improperly moved into the FCB$Q_xxxDATE field. The result can be a fairly strange (far in the future) date in the revision section of a DIRECTORY/FULL command output. Page 10 Images Affected: - [SYS$LDR]F11BXQP.EXE 6.1.9.2 CLDs, and QARs reporting this problem: 6.1.9.3 CLD(s) CFS.102062,70-3-7296 6.1.9.4 QAR(s) None. 6.1.9.5 Problem Analysis: The IMAGE_GET_DATE routines do not account for secondary headers. 6.1.9.6 Work-arounds: None. 7 INSTALLATION INSTRUCTIONS: 7.1 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS722_F11X /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt 7.2 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following definitions and commands: Page 11 - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V2.0 - De-assign the logicals assigned For example, a sample command file to install the VMS722_F11X-V0200 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS722_F11X/PROD=DEC/BASE=AXPVMS/VER=V2.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2003 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries 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. Neither HP nor any of its subsidiaries shall 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 HP 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 Page 12 REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.