**************************** ECO SUMMARY INFORMATION **************************** Release Date: 23-MAR-2007 Kit Name: DEC-AXPVMS-VMS83A_XFC-V0100--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.3 Approximate Kit Size: 3963 blocks Installation Rating: INSTALL_2 Required Features: XFC Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: VMS83A_UPDATE-V0200 or later Optional Kit Dependencies: None Checksums: VMS83A_XFC-V0100.ZIPEXE Checksum: 3614989292 DEC-AXPVMS-VMS83A_XFC-V0100--4.PCSI$COMPRESSED Checksum: 4008306271 VMS83A_XFC-V0100.ZIPEXE MD5 Checksum: A4416DA988C415A4FEA6EC13050F0EB7 DEC-AXPVMS-VMS83A_XFC-V0100--4.PCSI$COMPRESSED Checksum: 270B8EF778FED77921941938094F22A4 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS83A_XFC-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - XFC 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.3 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS83A_UPDATE-V0200 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 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS83A_XFC-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Performance Improvement 5.2.1.1 Problem Description: The performance of the pool zone purge code was improved, leading to an overall improvement in XFC performance. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE 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. 5.2.1.3 Problem Analysis: The purpose of the purge routine is to take a request for free pages and return that number of empty pages from the zone to the system. If the request was larger than the actual number of available empty pages, then the entire list of pages in the zone was scanned. On large systems where a zone might contain 50,000 pages, this scan could take 50 to 100 milliseconds. A second problem was that the empty pages were scattered along the list of pages in use, making the scan time to release a page Page 3 unpredictable. 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 Readahead Performance Improvement 5.2.2.1 Problem Description: Improve the performance of XFC readahead. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: XFC attempts to read blocks ahead when it detects that a process is reading a file sequentially. This could actually cause a performance degradation if an application was processing on an otherwise idle disk. This was particularly true if the application issued multiple simultaneous sequential IOs. Page 4 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: None. 5.2.3 Remove use of SYSGEN parameter SMP_SPINWAIT to calculate timeouts 5.2.3.1 Problem Description: Some operations within XFC can require long periods of time to complete. Examples are removing a volume and all its files from the cache, deleting a file, and reducing the amount of memory allocated to the cache. In order to prevent crashes from timeouts or excessive system slowdowns during this work, XFC limits the amount of time doing the work. Prior to this change, the time limit was based on the the SYSGEN parameter SMP_SPINWAIT. The typical wait was either 2/3 or 3/4 of this value. In OpenVMS V8.3, the default value for SMP_SPINWAIT was increased, for Integrity systems, from 1 second (100000 microseconds) to 5 seconds (500000 microseconds). This resulted in XFC running times that were much too long, sometimes holding the XFC spinlock for as long as 4 seconds. The code in XFC was rewritten to set the maximum for this work to about 5 milliseconds (there are some rare cases where it can go to 6 or 7 milliseconds). The work is then resumed after either a 1 or 5 millisecond timer delay. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE 5.2.3.2 CLDs, and QARs reporting this problem: Page 5 5.2.3.2.1 CLD(s) None. 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: See problem description. 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 Excessive Use of Non-paged Pool by XFC Closed Files 5.2.4.1 Problem Description: Excessive use of non-paged pool by XFC closed files could lead to non-paged pool allocation failures and bugchecks. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE 5.2.4.2 CLDs, and QARs reporting this problem: Page 6 5.2.4.2.1 CLD(s) QXCM1000381194 5.2.4.2.2 QAR(s) 75-109-1201,75-109-1838 5.2.4.3 Problem Analysis: XFC did not limit the number of closed files retained in the cache. Normally this was not an issue, but on some large systems, the number of closed files can exceed 500,000. Since XFC uses a small amount of non-paged pool for each file, in the extreme case, this large number of files could result in non-paged pool allocation failures and bugchecks. 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 REFCNTNEG Bugcheck 5.2.5.1 Problem Description: The system can crash with an "REFCNTNEG, PFN reference count is negative" bugcheck. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE Page 7 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) QXM1000381970 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: XFC was leaving the IRP in a state where I/O post processing was miscalculating the length of the PTE list. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.5.5 Work-arounds: None. 5.2.6 INVPTEFMT Bugcheck 5.2.6.1 Problem Description: The system can crash with an INVPTEFMT bugcheck. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE 5.2.6.2 CLDs, and QARs reporting this problem: Page 8 5.2.6.2.1 CLD(s) None. 5.2.6.2.2 QAR(s) None. 5.2.6.3 Problem Analysis: irp$l_diabuf was not being restored when converting a readthrough or writethrough I/O to a readaround or writearound I/O. 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. 6 FILES PATCHED OR REPLACED: o [SYS$LDR]SYS$XFCACHE.EXE (new image) Image Identification Information image name: "SYS$XFCACHE" image file identification: "V1.0" image file build identification: "XBCA-0080070003" link date/time: 7-MAR-2007 14:58:33.37 linker identification: "A13-03" Overall Image Checksum: 1640148127 o [SYS$LDR]SYS$XFCACHE_MON.EXE (new image) Image Identification Information image name: "SYS$XFCACHE_MON" image file identification: "V1.0" image file build identification: "XBCA-0080070003" link date/time: 7-MAR-2007 14:58:35.59 linker identification: "A13-03" Overall Image Checksum: 947787436 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information Page 9 image name: "SYSTEM_PRIMITIVES" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:49.10 linker identification: "A13-03" Overall Image Checksum: 85166119 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: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:50.16 linker identification: "A13-03" Overall Image Checksum: 396578336 o [SYSLIB]XFC$SDA.EXE (new image) Image Identification Information image name: "XFC$SDA" image file identification: "V1.0" image file build identification: "XBCA-0080070003" link date/time: 7-MAR-2007 14:58:36.60 linker identification: "A13-03" Overall Image Checksum: 3412882693 o [SYS$LDR]SYS$XFCACHE.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) 7 INSTALLATION INSTRUCTIONS 7.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. Page 10 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. 7.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 VMS83A_XFC-V0100.ZIPEXE 7.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 VMS83A_XFC[/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. 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. 7.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 Page 11 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=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS83A_XFC-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS83A_XFC/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 8 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 Page 12 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. ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS83A_XFC-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - XFC 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.3 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS83A_UPDATE-V0200 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 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS83A_XFC-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Performance Improvement 5.2.1.1 Problem Description: The performance of the pool zone purge code was improved, leading to an overall improvement in XFC performance. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE 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. 5.2.1.3 Problem Analysis: The purpose of the purge routine is to take a request for free pages and return that number of empty pages from the zone to the system. If the request was larger than the actual number of available empty pages, then the entire list of pages in the zone was scanned. On large systems where a zone might contain 50,000 pages, this scan could take 50 to 100 milliseconds. A second problem was that the empty pages were scattered along the list of pages in use, making the scan time to release a page Page 3 unpredictable. 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 Readahead Performance Improvement 5.2.2.1 Problem Description: Improve the performance of XFC readahead. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: XFC attempts to read blocks ahead when it detects that a process is reading a file sequentially. This could actually cause a performance degradation if an application was processing on an otherwise idle disk. This was particularly true if the application issued multiple simultaneous sequential IOs. Page 4 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: None. 5.2.3 Remove use of SYSGEN parameter SMP_SPINWAIT to calculate timeouts 5.2.3.1 Problem Description: Some operations within XFC can require long periods of time to complete. Examples are removing a volume and all its files from the cache, deleting a file, and reducing the amount of memory allocated to the cache. In order to prevent crashes from timeouts or excessive system slowdowns during this work, XFC limits the amount of time doing the work. Prior to this change, the time limit was based on the the SYSGEN parameter SMP_SPINWAIT. The typical wait was either 2/3 or 3/4 of this value. In OpenVMS V8.3, the default value for SMP_SPINWAIT was increased, for Integrity systems, from 1 second (100000 microseconds) to 5 seconds (500000 microseconds). This resulted in XFC running times that were much too long, sometimes holding the XFC spinlock for as long as 4 seconds. The code in XFC was rewritten to set the maximum for this work to about 5 milliseconds (there are some rare cases where it can go to 6 or 7 milliseconds). The work is then resumed after either a 1 or 5 millisecond timer delay. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE 5.2.3.2 CLDs, and QARs reporting this problem: Page 5 5.2.3.2.1 CLD(s) None. 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: See problem description. 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 Excessive Use of Non-paged Pool by XFC Closed Files 5.2.4.1 Problem Description: Excessive use of non-paged pool by XFC closed files could lead to non-paged pool allocation failures and bugchecks. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE 5.2.4.2 CLDs, and QARs reporting this problem: Page 6 5.2.4.2.1 CLD(s) QXCM1000381194 5.2.4.2.2 QAR(s) 75-109-1201,75-109-1838 5.2.4.3 Problem Analysis: XFC did not limit the number of closed files retained in the cache. Normally this was not an issue, but on some large systems, the number of closed files can exceed 500,000. Since XFC uses a small amount of non-paged pool for each file, in the extreme case, this large number of files could result in non-paged pool allocation failures and bugchecks. 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 REFCNTNEG Bugcheck 5.2.5.1 Problem Description: The system can crash with an "REFCNTNEG, PFN reference count is negative" bugcheck. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE Page 7 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) QXM1000381970 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: XFC was leaving the IRP in a state where I/O post processing was miscalculating the length of the PTE list. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.5.5 Work-arounds: None. 5.2.6 INVPTEFMT Bugcheck 5.2.6.1 Problem Description: The system can crash with an INVPTEFMT bugcheck. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYSLIB]XFC$SDA.EXE 5.2.6.2 CLDs, and QARs reporting this problem: Page 8 5.2.6.2.1 CLD(s) None. 5.2.6.2.2 QAR(s) None. 5.2.6.3 Problem Analysis: irp$l_diabuf was not being restored when converting a readthrough or writethrough I/O to a readaround or writearound I/O. 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. 6 FILES PATCHED OR REPLACED: o [SYS$LDR]SYS$XFCACHE.EXE (new image) Image Identification Information image name: "SYS$XFCACHE" image file identification: "V1.0" image file build identification: "XBCA-0080070003" link date/time: 7-MAR-2007 14:58:33.37 linker identification: "A13-03" Overall Image Checksum: 1640148127 o [SYS$LDR]SYS$XFCACHE_MON.EXE (new image) Image Identification Information image name: "SYS$XFCACHE_MON" image file identification: "V1.0" image file build identification: "XBCA-0080070003" link date/time: 7-MAR-2007 14:58:35.59 linker identification: "A13-03" Overall Image Checksum: 947787436 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information Page 9 image name: "SYSTEM_PRIMITIVES" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:49.10 linker identification: "A13-03" Overall Image Checksum: 85166119 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: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:50.16 linker identification: "A13-03" Overall Image Checksum: 396578336 o [SYSLIB]XFC$SDA.EXE (new image) Image Identification Information image name: "XFC$SDA" image file identification: "V1.0" image file build identification: "XBCA-0080070003" link date/time: 7-MAR-2007 14:58:36.60 linker identification: "A13-03" Overall Image Checksum: 3412882693 o [SYS$LDR]SYS$XFCACHE.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) 7 INSTALLATION INSTRUCTIONS 7.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. Page 10 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. 7.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 VMS83A_XFC-V0100.ZIPEXE 7.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 VMS83A_XFC[/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. 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. 7.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 Page 11 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=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS83A_XFC-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS83A_XFC/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 8 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 Page 12 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.