======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_ICAP-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 2.2 Reboot Requirement: No reboot is necessary after installation of this kit, however, there are additional steps that must be performed in order to use the images provided by this kit. Refer to the section titled Special Installation Instructions for required post-installation actions. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: Yes 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: - VMS84I_PCSI-V0200 - VMS84I_UPDATE-V0500 - HPI64VMSSSL V1.4-334 - HPI64VMSWBEMCIM V2.96-A100211 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: - HPI64VMSWBEMCIMV V2.99-A100614 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84I_ICAP-V0100 KIT 5.1 New functionality addressed in this kit 5.1.1 Global Instant Capacity 5.1.1.1 Functionality Description: Global Instant Capacity, or GiCAP, provides HP customers with the flexibility to move usage rights (RTUs) for Instant Capacity components within a group of servers. It also provides "pooled temporary capacity" across the group. This provides more cost-effective and higher availability, more adaptable load balancing, and more efficient and easier use of temporary capacity. Additional information on the features, requirements and usage of GiCAP can be obtained in the following materials: - GiCAP CookBook - iCAP Users Manual Images Affected: - [SYSEXE]ICAPREPAIR.EXE - [SYSEXE]GICAP.RULES - [SYSEXE]GICAP.RULES_LIST - [SYSMGR]GICAP$CONFIG.COM - [SYSMGR]GICAP$MENU.COM - [SYSMGR]ICAP$CHILD.COM - [SYSMGR]ICAP$CONFIG.COM - [SYSUPD]ICAP_CLD.COM - [SYSUPD]ICAP.MOF 5.1.1.1.1 Restrictions/Known issues: 1. After installation of this kit, the following error message appears for the ICAP SHOW STATUS command on a prospective GiCAP member system (which is not yet added as a member to any group) where GiCAP was configured as a part of iCAP configuration. ERROR:Unexpected error Cannot open /sys$specific/iCAP/GiCAP.configFile: bad file number Due to this issue ICAP SHOW STATUS/SNAPSHOT & ICAP APPLY CODEWORD command fails. Page 3 $ icap show status /snapshot Cannot open /sys$specific/iCAP/GiCAP.configFile: bad file number ERROR: Unable to read Instant Capacity status information. $ icap apply codeword "31dw9sj.6eEVddx.19v1r1d.RaKVCjg-MDUGFT7.DTcc2he.Vk4eheD.3ck7uh3" Cannot open /sys$specific/iCAP/GiCAP.configFile: bad file number ERROR: Application of the codeword to this system failed. However, the error message disappears when you add this GiCAP configured system under a GiCAP group during which the GiCAP.configFile gets created under sys$specific:[iCAP] directory. The customer is highly recommended not to configure a system with GiCAP unless there is an immediate plan to add this system under any GiCAP group. As a workaround, customer is advised to configure iCAP only by answering the question "Enter (Y)es if you want to support GiCAP functionality(Y):" as "NO" while configuring iCAP with SYS$MANAGER:ICAP$CONFIG.COM script. Configure GiCAP separately with the GiCAP configuration script SYS$MANAGER:GICAP$CONFIG.COM only just before adding this system as a member under any GiCAP group. 2. ICAP MANAGE commands hang intermittently and the following error message is thrown on the GiCAP Group Manager system when CIMSERVER goes into a non-responding state. ERROR: The following low-level error occurred: Cannot connect to krmt46b.fc.hp.com:5989. Connection failed. The customer is advised to wait about 5 minutes in case of such hangs (which is due to the no response from CIMSERVER) until it comes out of the hang and then try the same command again. Alternatively customer can interrupt the command execution during such hangs using Ctrl+Y and then restart the CIMSERVER in order to execute the command again. CIMSERVER can be restarted by executing the following scripts. SYS$STARTUP:WBEM_SERVICES$SHUTDOWN.COM SYS$STARTUP:WBEM_SERVICES$STARTUP.COM 5.1.2 New ICAP server shutdown script 5.1.2.1 Functionality Description: A new SYS$MANAGER:ICAP_SERVER$SHUTDOWN.COM file is supplied and is the supported method to stop the ICAP_SERVER process and/or to stop the iCAP software Page 4 after actions like iCAP software upgrades, WBEM Services Product upgrades or TCP/IP host address name/number changes. Images Affected: - [SYSMGR]ICAP_SERVER$SHUTDOWN.COM 5.2 Problems addressed in this kit 5.2.1 Corrupted OPCOM message from ICAP_SERVER displayed 5.2.1.1 Problem Description: After an ip address or name change is done on an iCAP system, the ICAP_SERVER displayed the following error messages. This problem has been fixed. icapd: ERROR: The following low-level error occurred:ERROR: The following low-level WBEM error occurred: Invalid locator: ip.host.name.com:5989 Images Affected: - [SYSEXE]ICAP_SERVER.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001076085 5.2.1.2.2 PTR(s) None. 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.1.4 Work-arounds: None. 5.2.2 Temporary iCAP inappropriately consumed on rx8640 experiencing MP / Hardware problems Page 5 5.2.2.1 Problem Description: Temporay iCAP was inappropriately consumed on rx8640 experiencing MP/hardware problems. A power down of the complex cleared the TiCAP consumption. Under certain hardware problem conditions, the iCAP discovery of processors on cell boards did not return the correct count. This problem has been fixed. Images Affected: - [SYSEXE]ICAP_SERVER.EXE 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001076042,QXCM1001023420 5.2.2.2.2 PTR(s) None. 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.2.4 Work-arounds: Power cycle and reboot all partitions of the system. 5.2.3 ICAP_SERVER process not starting 5.2.3.1 Problem Description: On some systems containing more than nine iCAP cores, the ICAP_SERVER process was not start iCAP components. This problem has been fixed. Images Affected: - [SYSLIB]DYNAMICPROFILE.EXE 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1000950751 5.2.3.2.2 PTR(s) Page 6 75-13-2255 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.3.4 Work-arounds: None. 5.2.4 Fix problems applying iCAP Portal Codewords 5.2.4.1 Problem Description: Trying to apply an emergency codeword obtained from WTEC on an OpenVMS partition returned the error "Codeword has expired". Applying a codeword to activate 12gb of iCAP memory resulted in only .5gb of iCAP memory being activated Images Affected: - [SYSEXE]ICAP_MODIFY.EXE - [SYSLIB]LIBICODPROVIDERMODULE.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases None. 5.2.4.2.2 PTR(s) 75-13-2308,75-13-2309 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.4.4 Work-arounds: Apply the codeword on a partition running HP-UX in the same cellular system. Page 7 5.2.5 System shutdown hangs on iCAP system 5.2.5.1 Problem Description: System shutdown hangs. A T from the process running shutdown displays iCAP_NOTIFY as the current image. This problem is fixed. Images Affected: - [SYSEXE]ICAP_NOTIFY.EXE - [SYSMGR]ICAP$CLI_UTILS.COM 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases None. 5.2.5.2.2 PTR(s) 75-13-2298 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.5.4 Work-arounds: Issue Y from shutdown process to continue shutdown. Issue STOP/IMAGE/id=process id of process executing shutdown, to terminate the ICAP_NOTIFY image and let shutdown continue. 5.2.6 Eliminate ICAP_SERVER not running message from ICAP KILL command 5.2.6.1 Problem Description: After issueing the iCAP KILL command to stop the ICAP_SERVER process, an error message: "The Instant Capacity server (ICAP_SERVER) is not running" is displayed. This message no longer displays as the iCAP server is not supposed to be running after the KILL command. Images Affected: Page 8 - [SYSEXE]ICAPMANAGE.EXE - [SYSEXE]ICAP_MODIFY.EXE - [SYSEXE]ICAP_NOTIFY.EXE - [SYSEXE]ICAP_SERVER.EXE - [SYSEXE]ICAP_STAT.EXE - [SYSLIB]LIBICODPROVIDERMODULE.EXE 5.2.6.2 Quix and PTR cases reporting this problem: 5.2.6.2.1 Quix Cases None. 5.2.6.2.2 PTR(s) 75-13-2298 5.2.6.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.6.4 Work-arounds: None. 5.2.7 Speed up ICAP_SERVER process startup 5.2.7.1 Problem Description: The startup of the ICAP_SERVER process during system startup can take a long time. One issue causing the delay was the need to wait for the ERRFMT process to reach a quiescent state. This wait was to ensure ERRFMT had populated the CELLULAR_SYSTEM system cell. The state was checked in a 5 minute wait loop. The startup is now streamlined to first check the hardware model number instead of the cellular system flag. If we know the hardware model is cellular, (i.e. rx84xx, rx76xx, etc.), we can proceed to read the nvram groupb data profile to see if the system contains iCAP components. Images Affected: - [SYSEXE]ICAPINIT.EXE - [SYSMGR]ICAP$CLI_UTILS.COM 5.2.7.2 Quix and PTR cases reporting this problem: Page 9 5.2.7.2.1 Quix Cases None. 5.2.7.2.2 PTR(s) 75-74-248 5.2.7.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.7.4 Work-arounds: None. 5.2.8 Fix CIM_ERR_INVALID_PARAMETER error during iCAP configuration 5.2.8.1 Problem Description: When configuring iCAP with @SYS$MANAGER:ICAP$CONFIG, various error messages are seen during the WBEMCIM repository update. Example error are: CIM_ERR_INVALID_PARAMETER: HP_NParCellSlot CIM_ERR_INVALID_PARAMETER: HP_NParIOChassisSlot CIM_ERR_INVALID_SUPERCLASS: HP_NParSlotInCabinet CIM_ERR_INVALID_SUPERCLASS: HP_NParSlotInCabinet These errors are generated by the Wbem Services CIMMOF compiler. Stricter compilation rules for class and subclass location in the mof file in newer versions of CIMMOF required the NPAR mof files be rearranged. Images Affected: - [SYSUPD]NPAR.MOF 5.2.8.2 Quix and PTR cases reporting this problem: 5.2.8.2.1 Quix Cases None. 5.2.8.2.2 PTR(s) 75-13-2135 Page 10 5.2.8.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.8.4 Work-arounds: None. 5.2.9 Suppress the 'SEARCH-I-NOMATCHES' error message which used to be included in the output when issuing SYS$SYSTEM:SHUTDOWN.COM 5.2.9.1 Problem Description: A 'SEARCH-I-NOMATCHES' message is included in the output when issuing SYS$SYSTEM:SHUTDOWN.COM. The informational message makes it appear that something didn't properly execute during shutdown. The problem has been solved by redirecting the message to NL: device. Images Affected: - [SYSMGR]ICAP$CLI_UTILS.COM 5.2.9.2 Quix and PTR cases reporting this problem: 5.2.9.2.1 Quix Cases QXCM1001086354 5.2.9.2.2 PTR(s) 75-13-2328 5.2.9.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.9.4 Work-arounds: None. 5.2.10 Fix inappropriate error message thrown on ICAP SHOW STATUS command when issued from an user account without CMKRNL & SYSPRV privileges. Page 11 5.2.10.1 Problem Description: Unexpected/inappropriate error message was thrown on ICAP SHOW STATUS command when issued from a user account that didn't have CMKRNL & SYSPRV privileges. The problem has been fixed by using the icod_check_root routine from the iCAP version prior to the iCAP 9.x code merge and use it in the affected images to catch and display the correct error message. Images Affected: - [SYSEXE]ICAPMANAGE.EXE - [SYSEXE]ICAP_MODIFY.EXE - [SYSEXE]ICAP_NOTIFY.EXE - [SYSEXE]ICAP_STAT.EXE - [SYSLIB]LIBICODPROVIDERMODULE.EXE - [SYSEXE]ICAP_SERVER.EXE 5.2.10.2 Quix and PTR cases reporting this problem: 5.2.10.2.1 Quix Cases QXCM1001107826 5.2.10.2.2 PTR(s) 75-13-2381 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.10.4 Work-arounds: None. 5.2.11 Fix ICAP$$INIT process hang on a system where ICAP$CLI_UTILS.COM is called directly/indirectly from SYSTARTUP_VMS.COM. 5.2.11.1 Problem Description: ICAP$$INIT process hangs on a system where ICAP$CLI_UTILS.COM is called directly/indirectly from SYSTARTUP_VMS.COM. This bug got introduced when a modified WBEM_Services$startup.com script (containing a call to ICAP$CLI_UTILS.COM), which was provided to EDS/ESI as a fix for the QXCM1001023420, was called by the SYSTARTUP_VMS.COM which in turn creating a deadlock for ICAP$INIT process. The problem has been resolved by putting a check in ICAPINIT.EXE Page 12 main routine in order to determine which process has invoked the image and if it is OpenVMS "STARTUP" process, exit the ICAP$INIT gracefully rather than going into the hang due to the deadlock to be encountered in the subsequent code block. Images Affected: - [SYSEXE]ICAPINIT.EXE 5.2.11.2 Quix and PTR cases reporting this problem: 5.2.11.2.1 Quix Cases QXCM1001107862 5.2.11.2.2 PTR(s) 75-13-2382 5.2.11.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.11.4 Work-arounds: Comment off the calling of ICAP$CLI_UTILS.COM from the WBEM_Services$startup.com script. 5.2.12 Fix the version wrap issue of ICAP$CORES.DAT on reaching the version number 32767 and above. 5.2.12.1 Problem Description: The iCAP software creates ICAP$CORES.DAT files on a daily basis or whenever there is change in the active core count. A customer noticed that the version number of ICAP$CORES.DAT file on their systems was rapidly approaching 32,767 which is the maximum version number permitted by the OpenVMS operating system. The problem has been resolved by modifying ICAP$CLI_UTILS.COM so that before a new ICAP$CORES.DAT file is created, the existing ICAP$CORES.DAT file is renamed to version 2 and the file prior to that is renamed to version 1. All other versions are deleted. The latest/newest file becomes version 3. Images Affected: - [SYSMGR]ICAP$CLI_UTILS.COM Page 13 5.2.12.2 Quix and PTR cases reporting this problem: 5.2.12.2.1 Quix Cases QXCM1001107868 5.2.12.2.2 PTR(s) 75-13-2383 5.2.12.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.12.4 Work-arounds: None. 5.2.13 Fix for the "ICAP-E-BADDP" error thrown during system reboot 5.2.13.1 Problem Description: Generally, on a system boot, it takes OpenVMS some time to build up the system hardware inventory (which is basically made available via IPMI). In VMS831H1I_ICAP-V0400 ECO kit, iCAP engineering had put some proactive performance improvement by optimizing the code which in turn makes ICAP$INIT execution faster. Due to the optimization introduced, it looks like we were starting too fast for the higher end systems such as RX86XX and superdomes even before the hardware inventory buildup could be completed (specially the Dynamic Profile population). The optimized code was never tested on higher end systems like RX86XX and superdomes which take more time in the hardware inventory buildup compared to the entry level cell based systems such as RX7620 and RX7640. iCAP engineering has re-looked at the optimization and has done the necessary changes in the code so that similar issues don t occur in future. Images Affected: - [SYSEXE]ICAPINIT.EXE 5.2.13.2 Quix and PTR cases reporting this problem: 5.2.13.2.1 Quix Cases QXCM1001126076, QXCM1001129965 Page 14 5.2.13.2.2 PTR(s) None 5.2.13.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.13.4 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYSEXE]ICAPINIT.EXE (new image) Image Identification Information Image name: "ICAPINIT" Image file identification: "X-21" Image build identification: "0100000004" Link identification: Linker I02-37 Link Date/Time: 17-MAY-2011 12:22:46.90 Overall Image Checksum: 2F4E55BD o [SYSEXE]ICAPMANAGE.EXE (new image) Image Identification Information Image name: "ICAPMANAGE" Image file identification: "V1.0" Image build identification: "0100000004" Link identification: Linker I02-37 Link Date/Time: 17-MAY-2011 12:23:13.35 Overall Image Checksum: 32630246 o [SYSEXE]ICAPREPAIR.EXE (new image) Image Identification Information Image name: "ICAPREPAIR" Image file identification: "V1.0" Image build identification: "0100000004" Link identification: Linker I02-37 Link Date/Time: 17-MAY-2011 12:23:31.73 Overall Image Checksum: 8F5D31D6 Page 15 o [SYSEXE]ICAP_MODIFY.EXE (new image) Image Identification Information Image name: "ICAP_MODIFY" Image file identification: "V1.0" Image build identification: "0100000004" Link identification: Linker I02-37 Link Date/Time: 17-MAY-2011 12:23:19.57 Overall Image Checksum: 7BFCAC27 o [SYSEXE]ICAP_NOTIFY.EXE (new image) Image Identification Information Image name: "ICAP_NOTIFY" Image file identification:" V1.0" Image build identification: "0100000004" Link identification: Linker I02-37 Link Date/Time: 17-MAY-2011 12:23:07.93 Overall Image Checksum: EE0FB6C6 o [SYSEXE]ICAP_SERVER.EXE (new image) Image Identification Information Image name: "ICAP_SERVER" Image file identification:"V1.0" Image build identification: "0100000004" Link identification: Linker I02-37 Link Date/Time: 17-MAY-2011 12:23:25.57 Overall Image Checksum: F88A81EB o [SYSEXE]ICAP_STAT.EXE (new image) Image Identification Information Image name: "ICAP_STAT" Image file identification: "V1.0" Image build identification: "0100000004" Link identification: Linker I02-37 Link Date/Time: 17-MAY-2011 12:22:52.26 Overall Image Checksum: 6E393573 o [SYSLIB]DYNAMICPROFILE.EXE (new image) Image Identification Information Image name: "DYNAMICPROFILE" Image file identification: "X-3" Image build identification: "0100000004" Link identification: Linker I02-37 Link Date/Time: 17-MAY-2011 12:23:24.31 Overall Image Checksum: BD319C4E Page 16 o [SYSLIB]LIBICODPROVIDERMODULE.EXE (new image) Image Identification Information Image name: "LIBICODPROVIDERMODULE" Image file identification: "V1.0" Image build identification: "0100000004" Link identification: Linker I02-37 Link Date/Time: 17-MAY-2011 12:23:27.46 Overall Image Checksum: 2113012D o [SYSEXE]GICAP.RULES (new file) o [SYSEXE]GICAP.RULES_LIST (new file) o [SYSMGR]GICAP$CONFIG.COM (new file) o [SYSMGR]GICAP$MENU.COM (new file) o [SYSMGR]ICAP$CHILD.COM (new file) o [SYSMGR]ICAP$CLI_UTILS.COM (new file) o [SYSMGR]ICAP$CONFIG.COM (new file) o [SYSMGR]ICAP_SERVER$SHUTDOWN.COM (new file) o [SYSUPD]ICAP.CLD (new file) o [SYSUPD]ICAP_CLD.COM (new file) o [SYSUPD]ICAP.MOF (new file) o [SYSUPD]NPAR.MOF (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 17 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 VMS84I_ICAP-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 VMS84I_ICAP[/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 18 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=HP/BASE=I64VMS/VER=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_ICAP-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_ICAP/PRODUCER=HP/BASE=I64VMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 7.5 Special Installation Instructions: After successful installation of the kit, you will need to execute the iCAP configuration script, SYS$MANAGER:ICAP$CONFIG.COM on each cluster member separately. This procedure updates the WBEM services repository to the V9.2 iCAP and nPAR definitions. It also allows usage of the Global Instant Capacity (GiCAP) feature If (or after) the following software is installed: - HP I64VMS WBEMCIM V2.99-A100614 or later 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2011 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. Page 19 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.