Kit Name: DEC-AXPVMS-VMS73_SYS-V0800--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3 Approximate Kit Size: 20624 blocks Installation Rating: INSTALL_1 Superseded Kits: VMS73_SYS-V0700 Mandatory Kit Dependencies: VMS73_UPDATE-V0300 VMS73_PCSI-V0200 Optional Kit Dependencies: None. VMS73_SYS-V0800.PCSI-DCX_AXPEXE Checksum: 928389650 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS73_SYS-V0800 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 1 KIT NAME: VMS73_SYS-V0800 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 2.4 New functionality or new hardware support provided: Yes. 3 KITS SUPERSEDED BY THIS KIT: - VMS73_SYS-V0700 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS73_PCSI-V0200 - VMS73_UPDATE-V0300 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: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:11.09 linker identification: "A11-50" Overall Image Checksum: 1558998154 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information image name: "EXCEPTION_MON" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:12.21 linker identification: "A11-50" Overall Image Checksum: 556675604 o [SYS$LDR]EXEC_INIT.EXE (new image) Image Identification Information image name: "EXEC_INIT" image file identification: "X-8" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:13.48 linker identification: "A11-50" Overall Image Checksum: 3820760792 o [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image) Image Identification Information image name: "IMAGE_MANAGEMENT" image file identification: "X-7" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:14.80 linker identification: "A11-50" Overall Image Checksum: 3201040892 Page 3 o [SYSLIB]IMGDMP.EXE (new image) Image Identification Information image name: "IMGDMP" image file identification: "X-11A1" image file build identification: "X91Y-0060010000" link date/time: 20-OCT-2001 06:06:23.85 linker identification: "A11-50" Overall Image Checksum: 3813432078 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:16.32 linker identification: "A11-50" Overall Image Checksum: 2994305689 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: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:18.86 linker identification: "A11-50" Overall Image Checksum: 2489026339 o [SYS$LDR]LOCKING.EXE (new image) Image Identification Information image name: "LOCKING" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:21.36 linker identification: "A11-50" Overall Image Checksum: 1074999934 o [SYS$LDR]LOGICAL_NAMES.EXE (new image) Image Identification Information image name: "LOGICAL_NAMES" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:23.68 linker identification: "A11-50" Overall Image Checksum: 3285387284 Page 4 o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) Image Identification Information image name: "MESSAGE_ROUTINES" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:10.60 linker identification: "A11-50" Overall Image Checksum: 4642634 o [SYS$LDR]MULTIPATH.EXE (new image) Image Identification Information image name: "MULTIPATH" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:24.56 linker identification: "A11-50" Overall Image Checksum: 383804849 o [SYS$LDR]MULTIPATH_MON.EXE (new image) Image Identification Information image name: "MULTIPATH_MON" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:25.62 linker identification: "A11-50" Overall Image Checksum: 3019832705 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:12.32 linker identification: "A11-50" Overall Image Checksum: 1857393304 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: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:15.09 linker identification: "A11-50" Overall Image Checksum: 1996272798 Page 5 o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information image name: "SDA$SHARE" image file identification: "X-6B1" image file build identification: "X9UH-0600100206" link date/time: 13-JUL-2004 10:31:11.53 linker identification: "A11-50" Overall Image Checksum: 2273858728 o [SYSLIB]SECURESHR.EXE (new image) Image Identification Information image name: "SECURESHR" image file identification: "X-9" image file build identification: "X91Y-0060010013" link date/time: 9-APR-2003 14:36:49.75 linker identification: "A11-50" Overall Image Checksum: 3754985958 o [SYSLIB]SECURESHRP.EXE (new image) Image Identification Information image name: "SECURESHRP" image file identification: "7-3" image file build identification: "X91Y-0060010013" link date/time: 9-APR-2003 14:36:48.24 linker identification: "A11-50" Overall Image Checksum: 2626894829 o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information image name: "SECURITY" image file identification: "X-5" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:17.49 linker identification: "A11-50" Overall Image Checksum: 1205347525 o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information image name: "SECURITY_MON" image file identification: "X-5" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:18.43 linker identification: "A11-50" Overall Image Checksum: 4065982831 Page 6 o [SYS$LDR]SHELL8K.EXE (new image) Image Identification Information image name: "SHELL8K" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:21.01 linker identification: "A11-50" Overall Image Checksum: 2905939791 o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information image name: "SYS$BASE_IMAGE" image file identification: "ALPHA X9UH-K5L" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:03.42 linker identification: "A11-50" Overall Image Checksum: 1284802412 o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information image name: "SYS$CLUSTER" image file identification: "X-3" image file build identification: "X9UH-0060010013" link date/time: 8-SEP-2003 21:25:28.71 linker identification: "A11-50" Overall Image Checksum: 2112574530 o [SYS$LDR]SYS$VCC.EXE (new image) Image Identification Information image name: "SYS$VCC" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:24.05 linker identification: "A11-50" Overall Image Checksum: 4164866549 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: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:24.96 linker identification: "A11-50" Overall Image Checksum: 4200336663 Page 7 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information image name: "SYS$VM" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:23.26 linker identification: "A11-50" Overall Image Checksum: 4228003509 o [SYS$LDR]SYSBOOT.EXE (new image) Image Identification Information image name: "SYSBOOT" image file identification: "X-97" image file build identification: "X91Y-0060010002" link date/time: 2-DEC-2001 01:47:08.59 linker identification: "A11-50" Overall Image Checksum: 2533104842 o [SYSEXE]SYSGEN.EXE (new image) Image Identification Information image name: "SYSGEN" image file identification: "X-3" image file build identification: "X91Y-0060010001" link date/time: 28-JUN-2001 02:30:26.79 linker identification: "A11-50" Overall Image Checksum: 2943455964 o [SYS$LDR]SYSGETSYI.EXE (new image) Image Identification Information image name: "SYSGETSYI" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:10.00 linker identification: "A11-50" Overall Image Checksum: 303340561 o [SYS$LDR]SYSLDR_DYN.EXE (new image) Image Identification Information image name: "SYSLDR_DYN" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:10.76 linker identification: "A11-50" Overall Image Checksum: 2859236494 Page 8 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:15.28 linker identification: "A11-50" Overall Image Checksum: 326488642 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: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:13.19 linker identification: "A11-50" Overall Image Checksum: 763749389 o [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE (new image) Image Identification Information image name: "SYSTEM_SYNCHRONIZATION" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:19.43 linker identification: "A11-50" Overall Image Checksum: 2681981626 o [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE (new image) Image Identification Information image name: "SYSTEM_SYNCHRONIZATION_MIN" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:20.54 linker identification: "A11-50" Overall Image Checksum: 2896367799 o [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE (new image) Image Identification Information image name: "SYSTEM_SYNCHRONIZATION_UNI" image file identification: "X-3" image file build identification: "X9UH-0060010074" link date/time: 13-JUL-2004 10:31:21.45 linker identification: "A11-50" Overall Image Checksum: 2680183499 Page 9 o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]EXEC_INIT.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]LOCKING.STB (new file) o [SYS$LDR]LOGICAL_NAMES.STB (new file) o [SYS$LDR]MESSAGE_ROUTINES.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]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYS$LDR]SHELL8K.STB (new file) o [SYS$LDR]SYS$CLUSTER.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]SYSGETSYI.STB (new file) o [SYS$LDR]SYSLDR_DYN.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.STB (new file) Page 10 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS73_SYS-V0800 KIT 6.1 New functionality addressed in this kit 6.1.1 Added PCI device ID for dual Gigabit Ethernet NIC, DEGX2-TA 6.1.1.1 Functionality Description: The PCI device ID for the dual Gigabit Ethernet NIC, DEGX2-TA, has been added. Images Affected: - [SYSEXE]SYS$CONFIG.DAT 6.2 Problems addressed in this kit 6.2.1 Process Hang 6.2.1.1 Problem Description: A user program that uses the SYS$BRKTHRU system service is allowed to do a "break through" to a template device, when it is specified as the target device. Depending on the device driver involved, this can cause the process to lose it's JIB$L_BYTLM/BYTCNT. If the remaining process byte limit quota gets too low the process could hang. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MIN.STB 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) CLD.103896 Page 11 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: SYS$BRKTHRU HAS BEEN MODIFIED to return the error SS$_NOSUCHDEV if a user program tries to do a break through to a template device. The documentation for SYS$BRKTHRU already mentions that this error status can also mean "the specified terminal does not exist, or it cannot receive the message". 6.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS following V7.3-2 6.2.1.5 Work-arounds: None. 6.2.2 INVEXCEPTN, Exception while above ASTDEL 6.2.2.1 Problem Description: The system can crash with an INVEXCEPTN bugcheck when doing an Oracle database convert on large database files: Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while Current Image: $1$DUA42:[SYS0.SYSCOMMON.] [SYSEXE]RMU71.EXE above ASTDEL Failing PC: FFFFFFFF.801A5598 SYS$VM+33598 Failing PS: 30000000.00000803 Module: SYS$VM (Link Date/Time: 1-DEC-2003 07:42:38.88) Offset: 00033598 Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB Page 12 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) CFS.105711 6.2.2.2.2 QAR(s) None. 6.2.2.3 Problem Analysis: The global section whose address space is being deleted is double mapped. 6.2.2.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS V7.3-2 6.2.2.5 Work-arounds: None. 6.2.3 6.2.4 INVEXCEPTN System Crash 6.2.4.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 Page 13 6.2.4.2 CLDs, and QARs reporting this problem: 6.2.4.2.1 CLD(s) None. 6.2.4.2.2 QAR(s) None. 6.2.4.3 Problem Analysis: See problem description. 6.2.4.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.4.5 Work-arounds: None. 6.2.5 Performance datacollector may miss START I/O's 6.2.5.1 Problem Description: A performance datacollector 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 Page 14 6.2.5.2 CLDs, and QARs reporting this problem: 6.2.5.2.1 CLD(s) CFS.107089 6.2.5.2.2 QAR(s) None. 6.2.5.3 Problem Analysis: There was a missing call to PMS$START_IO for MSCP devices. 6.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after V7.3-2 6.2.5.5 Work-arounds: None. 6.2.6 Class scheduling feature may not work. 6.2.6.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.6.2 CLDs, and QARs reporting this problem: Page 15 6.2.6.2.1 CLD(s) None. 6.2.6.2.2 QAR(s) 75-83-402 6.2.6.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.6.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.6.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed in previously released VMS73_SYS kits can be found in the following files: o [SYSHLP]VMS73_SYS-V0700.RELEASE_NOTES o [SYSHLP]VMS73_SYS-V0600.RELEASE_NOTES o [SYSHLP]VMS73_SYS-V0500.RELEASE_NOTES o [SYSHLP]VMS73_SYS-V0400.RELEASE_NOTES o [SYSHLP]VMS73_SYS-V0300.RELEASE_NOTES o [SYSHLP]VMS73_SYS-V0200.RELEASE_NOTES o [SYSHLP]VMS73_SYS-V0100.RELEASE_NOTES Page 16 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 VMS73_SYS-V0800.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 VMS73_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 17 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=V8.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS73_SYS-V0800 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS73_SYS/PRODUCER=DEC/BASE=AXPVMS- /VER=V8.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit Page 18 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.