**************************** ECO SUMMARY INFORMATION **************************** Release Date: 1-MAY-2007 Kit Name: DEC-AXPVMS-VMS82A_SYS-V0700--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.2 Approximate Kit Size: 7016 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS82A_SYS-V0600 Mandatory Kit Dependencies: VMS82A_UPDATE-V0600 or later VMS82A_PCSI-V0100 or later Optional Kit Dependencies: VMS82A_DCL-V0100 Checksums: VMS82A_SYS-V0700.ZIPEXE Checksum: 3752018949 DEC-AXPVMS-VMS82A_SYS-V0700--4.PCSI$COMPRESSED Checksum: 363602905 VMS82A_SYS-V0700.ZIPEXE MD5 Checksum: 837922DAA13674BDA14B09AE8BB5BE0D DEC-AXPVMS-VMS82A_SYS-V0700--4.PCSI$COMPRESSED MD5 Checksum: 5DA11C0DA3F67A2C938E8375ECE12FFB ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS82A_SYS-V0700 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 V8.2 2.4 New functionality or new hardware support provided: YEs. 3 KITS SUPERSEDED BY THIS KIT: - VMS82A_SYS-V0600 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS82A_PCSI-V0100 - VMS82A_UPDATE-V0600 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: - VMS82A_DCL-V0100 See section "5.1.1 New $GETDVI Item Codes" for more information. 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS82A_SYS-V0700 KIT 5.1 New functionality addressed in this kit 5.1.1 New $GETDVI Item Codes 5.1.1.1 Functionality Description: The $GETDVI system service provides an item code (DVI$_MOUNTCNT) that returns the number of times a device is mounted on a single node (the use of the the /SHARE qualifier allows more than one mounter on a single node). There has been no way to get the clusterwide mount count for a device, from $GETDVI, despite the fact that $ SHOW DEVICE does correctly display the clusterwide mount count. This patch kit addresses this by adding the DVI$_MOUNTCNT_CLUSTER item code. The DVI$_ADAPTER_IDENT item code is also being added. These codes are only available for the SYS$GETDVI system service, not the LIB$GETDVI runtime library routine. After installation of the DCL Patch kit optional dependency (section 4.2), they will also be available for the F$GETDVI lexical function. The numeric value of DVI$_ADAPTER_IDENT is 492 ; the numeric value of DVI$_MOUNTCNT_CLUSTER is 494. In order to use these new item codes with the SYS$GETDVI system service, you will need to update the DVIDEF module, in the STARLET libraries for the languages you use, with these values. The easiest way to do this is to extract the definitions, make the necessary changes and re-insert the definitions into the library. For example, for the C language, the DCL command to extract the definition file is: $ LIBRARY /EXTRACT=DVIDEF/OUT =DVIDEF.TXT - SYS$LIBRARY:SYS$STARLET_C.TLB Edit the TXT file to add the values for the DVI$_MOUNTCNT_CLUSTER and DVI$_ADAPTER_IDENT item codes. Page 3 The modified DVIDEF.TXT file must then be inserted back into SYS$LIBRARY:SYS$STARLET_C.TLB with the command: $ LIBRARY/REPLACE SYS$LIBRARY:SYS$STARLET_C.TLB - DVIDEF.TXT Contact your HP services representative if you need assistance with these changes. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2 Problems addressed in this kit 5.2.1 Possible System Crash 5.2.1.1 Problem Description: The system can crash when either a tape or a disk in mount verification is dismounted. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) None. Page 4 5.2.1.3 Problem Analysis: A register was not preserved. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.1.5 Work-arounds: None. 5.2.2 Audit Server Hang 5.2.2.1 Problem Description: In rare circumstances, and during times of heavy event auditing, the Audit Server process could hang waiting for the I/O Mutex being held by another process which is deleting a device and trying to write the deletion event into the Audit_Server's full mailbox. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000361205,WFM3215964188-325 5.2.2.2.2 QAR(s) 5.2.2.3 Problem Analysis: See problem description. Page 5 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.2.5 Work-arounds: Avoid auditing device creation and deletion activies. 5.2.3 MC SYSMAN IO AUTOCONFIGURE System Crash 5.2.3.1 Problem Description: When the MPDEV_POLLER and MPDEV_D3 sysgen parameters are set, the system can crash when an "MC SYSMAN IO AUTOCONFIGURE" command is issued. Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) QXCM1000369587 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: The MPDEV_FLUSH code ( mpdev$get_next_flush_candidate) looks through the IODB and selects UCB only if the UCB matches the following criteria: o UCB must not be marked MNTVERIP o UCB must not be foreign mounted o Primary UCB must not be marked pathverip Page 6 For each UCB that is selected, the MPDEV_FLUSH code (mpdev$do_next_flush_io) queues the IRP (IO$_FLUSH_ERROR) into UCB$Q_DK_IRP_LIST for error flushing. The MPDEV_FLUSH code queued the IO$_FLUSH_ERROR IRP into a UCB that was not fully configured. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.3.5 Work-arounds: None. 5.2.4 Unable to Delete Global Section with Bad Page 5.2.4.1 Problem Description: Occasionally a global section gets stuck on the delete pending list and is never deleted. This can occur if, sometime in the past, an I/O error occurred trying to write out the section and, because of this, it had a page placed onto the bad page list. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000192113 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: See problem description. Page 7 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.4.5 Work-arounds: None. 5.2.5 System Crash 5.2.5.1 Problem Description: The system can crash. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MON.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MON.STB 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) None. 5.2.5.2.2 QAR(s) 70-3-8878,QXCM1000360250,WFM3215947250-321 5.2.5.3 Problem Analysis: See problem description. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 8 5.2.5.5 Work-arounds: None. 5.2.6 System Crash with SSRVEXCEPT Bugcheck 5.2.6.1 Problem Description: The system can crash with an SSRVEXCEPT bugcheck. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) QXCM1000369887 5.2.6.2.2 QAR(s) None. 5.2.6.3 Problem Analysis: Inside EXE$KTHREAD_DELETE_SELF, there was no call to synchronize the PSBs in use and operate on the correct PSB. 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.6.5 Work-arounds: None. Page 9 5.2.7 System Crash with INVSECURESTATE Bugcheck 5.2.7.1 Problem Description: The system can crash with an INVSECURESTATE bugcheck. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.7.2 CLDs, and QARs reporting this problem: 5.2.7.2.1 CLD(s) QXCM1000369887 5.2.7.2.2 QAR(s) None. 5.2.7.3 Problem Analysis: Inside EXE$KTHREAD_DELETE_SELF, there was no call to synchronize the PSBs in use and operate on the correct PSB. 5.2.7.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.7.5 Work-arounds: None. 5.2.8 INVEXCEPTN SCH$POSTEF_SCHED Bugcheck Page 10 5.2.8.1 Problem Description: On multithreaded process, the system can crash with an "INVEXCEPTN SCH$POSTEF_SCHED" bugcheck. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.8.2 CLDs, and QARs reporting this problem: 5.2.8.2.1 CLD(s) QXCM1000385036,WFM1213687533-121 5.2.8.2.2 QAR(s) None. 5.2.8.3 Problem Analysis: The INVEXCEPTN bugcheck occurs when the code tries to queue PCB$L_POSTEF_ACB to a multithreaded process (with upcalls enabled) before the field has been completely set up (and is still 0). 5.2.8.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.8.5 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS82A_SYS ECO kits can be found in the following files: o VMS82A_SYS-V100.RELEASE_NOTES Page 11 o VMS82A_SYS-V200.RELEASE_NOTES o VMS82A_SYS-V300.RELEASE_NOTES o VMS82A_SYS-V400.RELEASE_NOTES o VMS82A_SYS-V500.RELEASE_NOTES o VMS82A_SYS-V600.RELEASE_NOTES Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS82A_SYS/VERSION= - /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS82A_SYS/VERSION= V7.0 - /SELECT=[SYSUPD]release_note_name/DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information image name: "EXCEPTION" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:29.16 linker identification: "A11-50" Overall Image Checksum: 3790472411 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information image name: "EXCEPTION_MON" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:29.82 linker identification: "A11-50" Overall Image Checksum: 2653594698 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-5" Page 12 image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:34.97 linker identification: "A11-50" Overall Image Checksum: 3419444266 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information image name: "IO_ROUTINES_MON" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:36.87 linker identification: "A11-50" Overall Image Checksum: 2944414587 o [SYS$LDR]MULTIPATH.EXE (new image) Image Identification Information image name: "MULTIPATH" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:39.30 linker identification: "A11-50" Overall Image Checksum: 3850330017 o [SYS$LDR]MULTIPATH_MON.EXE (new image) Image Identification Information image name: "MULTIPATH_MON" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:39.90 linker identification: "A11-50" Overall Image Checksum: 1966096931 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:42.49 linker identification: "A11-50" Overall Image Checksum: 2652289455 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT_MON" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:43.75 Page 13 linker identification: "A11-50" Overall Image Checksum: 119202966 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information image name: "SYS$VM" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:23.06 linker identification: "A11-50" Overall Image Checksum: 39495954 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:33.68 linker identification: "A11-50" Overall Image Checksum: 2132855103 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES_MIN" image file identification: "X-5" image file build identification: "XAJT-0070050059" link date/time: 1-MAR-2007 07:03:35.28 linker identification: "A11-50" Overall Image Checksum: 1778246318 o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYS$LDR]MULTIPATH.STB (new file) o [SYS$LDR]MULTIPATH_MON.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) Page 14 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) 8 INSTALLATION INSTRUCTIONS 8.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 8.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS82A_SYS-V0700.ZIPEXE 8.3 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 VMS82A_SYS[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. Page 15 The kit location may be a tape drive, CD, 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. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 8.4 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 logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V7.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS82A_SYS-V0700 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS82A_SYS/PRODUCER=DEC/BASE=AXPVMS/VER=V7.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! Page 16 $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2007 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 HP 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.