**************************** ECO SUMMARY INFORMATION **************************** Release Date: 20-JUL-2004 Kit Name: DEC-AXPVMS-VMS731_SYS-V0700--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 14192 blocks Installation Rating: INSTALL_1 Superseded Kits: VMS731_SYS-V0600 Mandatory Kit Dependencies: VMS731_UPDATE-V0400 VMS731_PCSI-V0200 Optional Kit Dependencies: None. VMS731_SYS-V0700.PCSI-DCX_AXPEXE Checksum: 1211405783 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS731_SYS-V0700 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 1 KIT NAME: VMS731_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 V7.3-1 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS731_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: - VMS731_PCSI-V0200 - VMS731_UPDATE-V0400 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]EXCEPTION.EXE (new image) Image Identification Information image name: "EXCEPTION" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:15.86 linker identification: "A11-50" Overall Image Checksum: 3797900338 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information image name: "EXCEPTION_MON" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:16.92 linker identification: "A11-50" Overall Image Checksum: 2643497102 o [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image) Image Identification Information image name: "IMAGE_MANAGEMENT" image file identification: "X-8A2" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:25.19 linker identification: "A11-50" Overall Image Checksum: 1703700117 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:31.07 linker identification: "A11-50" Overall Image Checksum: 13414987 Page 3 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information image name: "IO_ROUTINES_MON" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:36.81 linker identification: "A11-50" Overall Image Checksum: 4240489970 o [SYS$LDR]LOGICAL_NAMES.EXE (new image) Image Identification Information image name: "LOGICAL_NAMES" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:42.17 linker identification: "A11-50" Overall Image Checksum: 1272209683 o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) Image Identification Information image name: "MESSAGE_ROUTINES" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:14.94 linker identification: "A11-50" Overall Image Checksum: 3548559127 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:18.38 linker identification: "A11-50" Overall Image Checksum: 774098925 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT_MON" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:21.63 linker identification: "A11-50" Overall Image Checksum: 1036205962 Page 4 o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information image name: "SECURITY" image file identification: "X-5" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:29.03 linker identification: "A11-50" Overall Image Checksum: 2104507211 o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information image name: "SECURITY_MON" image file identification: "X-5" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:30.07 linker identification: "A11-50" Overall Image Checksum: 3402035241 o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information image name: "SYS$CLUSTER" image file identification: "X-3" image file build identification: "XA2Q-0060030012" link date/time: 7-JUL-2004 09:46:14.94 linker identification: "A11-50" Overall Image Checksum: 2867515603 o [SYS$LDR]SYS$CLUSTER_MON.EXE (new image) Image Identification Information image name: "SYS$CLUSTER_MON" image file identification: "X-3" image file build identification: "XA2Q-0060030012" link date/time: 7-JUL-2004 09:46:16.87 linker identification: "A11-50" Overall Image Checksum: 2460278774 o [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE (new image) Image Identification Information image name: "SYS$CPU_ROUTINES_2308" image file identification: "X-1" image file build identification: "X9TD-0060030004" link date/time: 12-JUN-2003 16:27:22.19 linker identification: "A11-50" Overall Image Checksum: 1959835550 Page 5 o [SYS$LDR]SYS$CPU_ROUTINES_270F.EXE (new image) Image Identification Information image name: "SYS$CPU_ROUTINES_270F" image file identification: "X-1" image file build identification: "X9TD-0060030011" link date/time: 12-JUN-2003 16:27:22.19 linker identification: "A11-50" Overall Image Checksum: 1338162834 o [SYS$LDR]SYS$VCC.EXE (new image) Image Identification Information image name: "SYS$VCC" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:39.55 linker identification: "A11-50" Overall Image Checksum: 4081249760 o [SYS$LDR]SYS$VCC_MON.EXE (new image) Image Identification Information image name: "SYS$VCC_MON" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:40.22 linker identification: "A11-50" Overall Image Checksum: 4133157280 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information image name: "SYS$VM" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:41.54 linker identification: "A11-50" Overall Image Checksum: 1475831962 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:26.07 linker identification: "A11-50" Overall Image Checksum: 522082621 Page 6 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES_MIN" image file identification: "X-3" image file build identification: "XA2Q-0060030063" link date/time: 7-JUL-2004 09:46:19.84 linker identification: "A11-50" Overall Image Checksum: 3428211844 o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]IMAGE_MANAGEMENT.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYS$LDR]LOGICAL_NAMES.STB (new file) o [SYS$LDR]MESSAGE_ROUTINES.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYS$LDR]SYS$CLUSTER.STB (new file) o [SYS$LDR]SYS$CLUSTER_MON.STB (new file) o [SYS$LDR]SYS$VCC.STB (new file) o [SYS$LDR]SYS$VCC_MON.STB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_SYS-V0700 KIT Page 7 6.1 New functionality addressed in this kit None. 6.2 Problems addressed in this kit 6.2.1 sys$_ioperformw returns unexpected status 6.2.1.1 Problem Description: In a multi-CPU system in a multithread environment, sys$_ioperformw returns a SS$_FANDLEBUSY status. This return status is not expected from the sys$io_performw system service. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) 70-3-7654 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: When fastio was complete, iosa status was set, then the event flag was posted. Then, the fastio_done bit was set. The fastio_done bit needs to be set before the event flag is posted. 6.2.1.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 Page 8 6.2.1.5 Work-arounds: None. 6.2.2 System may crash when deleting global sections. 6.2.2.1 Problem Description: If a system uses more global sections than specified by the system parameter GBLSECTIONS, the system may crash when deleting global sections. The possibility of a crash is dependant on the value of GBLSECTIONS. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) None. 6.2.2.2.2 QAR(s) None. 6.2.2.3 Problem Analysis: The sizing of an internal data structure did not take into account that there could be more global sections than specified by the GBLSECTIONS system parameter. 6.2.2.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 Page 9 6.2.2.5 Work-arounds: None. 6.2.3 INVEXCEPTN System Crash 6.2.3.1 Problem Description: A timing window problem may affect some EV6 systems, causing a system crash. The crash is usually an INVEXCEPTN with the PC in IO_ROUTINES. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.2.1 CLD(s) None. 6.2.3.2.2 QAR(s) None. 6.2.3.3 Problem Analysis: See problem description. 6.2.3.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.3.5 Work-arounds: None. Page 10 6.2.4 Performance data collector may miss START I/O's 6.2.4.1 Problem Description: A performance data collector may miss START I/O's in the ioperform buffers when MSCP devices are monitored. The normal sequence is START REQUEST / START IO / END IO / END REQUEST, For MSCP devices, the START IO was missing which results in invalid I/O statistics. Normally, this will only be seen on SMP systems with FAST_PATH enabled. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 6.2.4.2 CLDs, and QARs reporting this problem: 6.2.4.2.1 CLD(s) CFS.107089 6.2.4.2.2 QAR(s) None. 6.2.4.3 Problem Analysis: There was a missing call to PMS$START_IO for MSCP devices. 6.2.4.4 Release Version of OpenVMS that will contain this change: Next openvms release after V7.3-2 6.2.4.5 Work-arounds: None. Page 11 6.2.5 Class scheduling feature may not work. 6.2.5.1 Problem Description: The class scheduling feature may not work, causing requested CPU percentages to not be assigned to class-scheduled processes. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 6.2.5.2 CLDs, and QARs reporting this problem: 6.2.5.2.1 CLD(s) None. 6.2.5.2.2 QAR(s) 75-83-402 6.2.5.3 Problem Analysis: The class scheduler was modified to use the TBS_PENDING bit instead of the IN_TBS bit. SCH$STATE_TO_COM_SCHED_1CPU was setting the IN_TBS bit rather than the TBS_PENDING bit causing the class scheduler to be broken. 6.2.5.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.5.5 Work-arounds: None. Page 12 6.2.6 System can crash with an INVEXCEPTN bugcheck in SYSTEM_PRIMITIVES_MIN 6.2.6.1 Problem Description: The system can crash with an INVEXCEPTN bugcheck in SYSTEM_PRIMITIVES_MIN: Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Failing PC: FFFFFFFF.8004AB8C EXE_STD$IOFORK_CPU_C+0034C Failing PS: 20000000.00000804 Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time: 1-DEC-2003 07:42:14.56) Offset: 0001EB8C Stack Pointers: KSP = FFFFFFFF.BEF89C68 ESP = FFFFFFFF.BEF8B000 SSP = FFFFFFFF.BEF85000 USP = FFFFFFFF.BEF85000 Failing Instruction: EXE_STD$IOFORK_CPU_C+0034C: REMQUEL/D Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE - [SYS$LDR]SYS$CLUSTER.STB - [SYS$LDR]SYS$CLUSTER_MON.EXE - [SYS$LDR]SYS$CLUSTER_MON.STB 6.2.6.2 CLDs, and QARs reporting this problem: 6.2.6.2.1 CLD(s) 70-3-7768,CFS.105611,70-3-7679,CFS.104888,70-3-8071 6.2.6.2.2 QAR(s) 75-13-1185 6.2.6.3 Problem Analysis: When a node is shutting down, it attempts to remaster all lock trees off the current system. The fast remaster code uses connection manager block transfers to move the lock trees in large chunks to the new master node. If a cluster connection is lost while a block transfer is in Page 13 progress, an error routine cleans up the SCS resources allocated to the block transfer. This error routine also checks to see if the node has been removed from the cluster in order to clean up lock manager data structures involved in the remastering. The lock manager data structure involved in the remaster operation may be queued to the IPL 8 fork queue as the SCS spinlock is dropped and the LCKMGR spinlock is obtained. Deleting the data structure in those cases causes the crash. 6.2.6.4 Release Version of OpenVMS that will contain this change: Next OpenVMS release after V7.3-2 6.2.6.5 Work-arounds: None. 6.2.7 CPUSPINWAIT, CPU spinwait timer expired bugcheck 6.2.7.1 Problem Description: The system can crash with a CPUSPINWAIT, CPU spinwait timer expired bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: CPUSPINWAIT, CPU spinwait timer expired Failing PC: FFFFFFFF.8008A3A4 SMP$TIMEOUT_C+00064 Failing PS: 08000000.00000B03 Module: SYSTEM_SYNCHRONIZATION_MIN (Link Date/Time: 19-FEB-2003 11:27:32.44) Offset: 000003A4 Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB Page 14 6.2.7.2 CLDs, and QARs reporting this problem: 6.2.7.2.1 CLD(s) CFS.107998 6.2.7.2.2 QAR(s) None. 6.2.7.3 Problem Analysis: In responding to a nonpaged pool allocation request where the requested size is greater than NPAGEVIR, a galaxy system could flush all the lookaside lists and expand nonpaged pool in an effort to meet the apparent demand. If the variable nonpaged pool freelist becomes too fragmented, the system could bugcheck with the CPUSPINWAIT bugcheck, waiting for the POOL spinlock. 6.2.7.4 Release Version of OpenVMS that will contain this change: Next OpenVMS release after V7.3-2 6.2.7.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed in previously released VMS731_SYS kits can be found in the following files: o [SYSHLP]VMS731_SYS-V0600.RELEASE_NOTES o [SYSHLP]VMS731_SYS-V0500.RELEASE_NOTES o [SYSHLP]VMS731_SYS-V0400.RELEASE_NOTES o [SYSHLP]VMS731_SYS-V0300.RELEASE_NOTES o [SYSHLP]VMS731_SYS-V0200.RELEASE_NOTES o [SYSHLP]VMS731_SYS-V0100.RELEASE_NOTES Page 15 8 INSTALLATION INSTRUCTIONS 8.1 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS731_LAN-V0700.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the Decompress into "(file specification)" question, either a or an alternate directory specification 8.2 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 VMS731_SYS /SAVE_RECOVERY_DATA [/SOURCE=location of Kit] 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. 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. Page 16 8.3 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/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS731_SYS-V0700 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS731_SYS/PRODUCER=DEC/BASE=AXPVMS- /VER=V7.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit Page 17 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 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.