IBM(R) Multipath Subsystem Device Driver V1.6.0.5 README for AIX™ December 16, 2005 ------------------------------------------------------------------------------- CONTENTS 1.0 About this README file 1.1 Who should read this README file 1.2 How to get help 2.0 Prerequisites for SDD 2.1 Procedure for upgrading AIX OS, Host attachment, and/or SDD 3.0 SDD change history 3.1 Defects Fixed 3.1.1 Common 3.1.2 ESS/DS8000/DS6000 defects 3.1.3 SVC defects 3.1.4 SVCCISCO defects 3.2 New Features 3.3 Feature Details 3.4 Known issues 3.5 Correction to User's Guide 4.0 User license agreement for IBM device drivers 4.1 Background / Purpose 4.2 Definitions 4.3 License grant 4.4 Responsibilities 4.5 Confidential information 4.6 Limitation of liability 4.7 Termination 4.8 Representations and warranties 4.9 General provisions 4.10 Appendix A 5.0 Notices 6.0 Trademarks and service marks ------------------------------------------------------------------------------- 1.0 About this README file Welcome to IBM Multipath Subsystem Device Driver (SDD). This README file contains the most recent information about the IBM Multipath Subsystem Device Driver, Version 1 Release 6 Modification 0 Level 5 (SDD 1.6.0.5) for AIX. IBM recommends that you go to the following Web site to get the most current information about this release of SDD: http://www.ibm.com/servers/storage/support/software/sdd/ You should carefully review the following information available through the website: 1. The most current README file. This will contain corrections to this readme file, corrections to the SDD User's Guide, and other documentation updates discovered since this copy of the README was prepared. 2. The Multipath SDD User's Guide. Because SDD can be installed in so many different environments / configurations, detailed information about each environment is placed in the appropriate chapter of the Multipath SDD Users Guide. The 'Summary of Changes' section of the SDD Users' Guide can help you quickly determine if the latest changes affect you. 3. The Flashes. As we become aware of any information that is likely to impact a broad set of our customers, Flashes are prepared and posted on this site. You should review this section periodically to see any new Flashes that have been posted since your last review. For prerequisites information, be sure to look in the Multipath SDD User's Guide as well as the prerequisites section of this readme file for the latest updates. 1.1 Who should read this README file This README file is intended for storage administrators, system programmers, and performance and capacity analysts. The information in this file only applies to customers who run: 1. Enterprise Storage Server (ESS), DS8000, DS6000, SAN Volume Controller (SVC), or SAN Volume Controller for Cisco MDS 9000 (SVCCISCO) 2. ESS and SVC 3. ESS and SVCCISCO 1.2 How to get help Go to the following Web site for SDD technical support and for the most current SDD documentation and support information: http://www.ibm.com/servers/storage/support/software/sdd/ Go to the following Web site for the IBM ESS Open Systems support: http://www.ibm.com/servers/storage/disk/ess/ Go to the following Web site for IBM TotalStorage DS8000 support: http://www.ibm.com/servers/storage/disk/ds8000/index.html Go to the following Web site for IBM TotalStorage DS6000 support: http://www.ibm.com/servers/storage/disk/ds6000/index.html Go to the following Web site for IBM TotalStorage SAN Volume Controller support: http://www.ibm.com/servers/storage/support/software/sanvc/ Go to the following Web site for IBM TotalStorage SAN Volume Controller for Cisco MDS 9000 support: http://www.ibm.com/servers/storage/support/software/sanvccisco/ Call one of the following numbers to obtain nontechnical or administrative support, such as hardware and software orders, hardware maintenance, services contract of entitlement, and invoices: .For commercial or state and local support operations: 1-877-426-6006 (Listen to the voice prompts) .For business partner support operations: 1-800-426-9990 .For federal government support operations: 1-800-333-6705 ------------------------------------------------------------------------------- 2.0 Prerequisites for SDD Prior to installing SDD, you should install the latest version of AIX host attachment script. - For ESS (2105) devices: Install ibm2105.rte. The latest version is 32.6.100.25. Attention: Starting from ibm2105.rte version 32.6.100.21, ESS FC devices will be configured as "IBM FC 2105", as seen from the "lsdev -Cc disk" output. This is changed from "IBM FC 2105XXX", where 'XXX' is the ESS device model, such as F20 or 800. There are two side effects of this change: a) To avoid ODM corruption, you will need to remove all ESS FC hdisks on your host system with the "rmdev" command if you are upgrading from ibm2105.rte version 32.6.100.19 or earlier to ibm2105.rte version 32.6.100.21 or later. b) HACMP processing will fail to bring up volume groups in concurrent mode. In order to work around this issue, the /etc/cluster/conraid.dat HACMP file must be updated to include the following line: 2105*** If the /etc/cluster/conraid.dat HACMP file does not exist, it should be created and contain this line. - For the following devices, install the devices.fcp.disk.ibm.rte package. The latest version is v1.0.0.2. a) DS8000 (2107) b) DS6000 (1750) c) SAN Volume Controller (2145) d) SAN Volume Controller for Cisco MDS 9000 (2062) NOTE: Since SDD v1.6.0.0, host attachment packages for the above devices are consolidated into one package, devices.fcp.disk.ibm.rte. For details, please refer to the Readme files of the host attachment. ================================================================================= 2.1 Procedure for upgrading AIX OS, Host attachment, and/or SDD The following procedure should be used when you want to upgrade: - AIX OS only** - Host attachment + AIX OS** - SDD + AIX OS - Host attachment + SDD - Host attachment only - SDD + Host attachment + AIX OS ** Upgrading the AIX OS will always require you to install the SDD which corresponds to the new AIX OS level. In the case where you want to upgrade SDD only, follow the procedure in the SDD User's Guide. 1. Have rootvg on local SCSI disks. 2. Stop all activities related to SDD devices: - Stop application running on SDD volume groups/file systems. - If your host is in an HACMP environment, gracefully stop the cluster services. - If there is active paging space created with SDD devices, deactivate the paging space. - Umount all file systems of SDD volume group - Vary off all SDD volume groups. 3. Remove SDD vpath devices with the command 'rmdev -dl dpo -R'. 4. Remove hdisk devices with the command 'lsdev –C –t 2105* -F name | xargs -n1 rmdev -dl' for 2105 devices 'lsdev –C –t 2145* -F name | xargs -n1 rmdev -dl' for 2145 devices 'lsdev –C –t 2062* -F name | xargs -n1 rmdev -dl' for 2062 devices 'lsdev –C –t 2107* -F name | xargs -n1 rmdev -dl' for 2107 devices 'lsdev –C –t 1750* -F name | xargs -n1 rmdev -dl' for 1750 devices 5. Check if hdisk devices are successfully removed with the command. 'lsdev –C –t 2105* -F name' for 2105 devices 'lsdev –C –t 2145* -F name' for 2145 devices 'lsdev –C –t 2062* -F name' for 2062 devices 'lsdev –C –t 2107* -F name' for 2107 devices 'lsdev –C –t 1750* -F name' for 1750 devices 6. If upgrading OS, run 'stopsrc -s sddsrv' to stop sddsrv daemon. 7. If upgrading OS, deinstall SDD. 8. If required, upgrade to the latest version of the host attachment. Package names are: ibm2105.rte for 2105 devices devices.fcp.disk.ibm.rte for 2145, 2062, 2107, and 1750 devices 9. If not upgrading OS, configure hdisks with the 'cfgmgr -vl fcsX' command for each FC adapter. 10. If upgrading OS, migrate to the new AIX OS level first. 11. If OS is upgraded, boot to the new AIX OS level with no disk groups online except rootvg which is on local SCSI disks. Reboot will automatically start at the end of migration. 12. If OS is upgraded, install or upgrade the corresponding SDD level for the new AIX OS level. 13. Configure SDD vpath devices by running 'cfallvpath'. 14. If your current SDD version is earlier than 1.6.0.0, run 'hd2vp' on all SDD volume groups. Otherwise, skip this step. 15. Resume all activities related to SDD vpath devices: - If there were active paging space created with SDD vpath devices, activate the paging space. - If your host was in an HACMP environment, start the cluster services. - Vary on all SDD volume groups. - Mount all file system. - Start application running on SDD volume groups/file systems. ------------------------------------------------------------------------------- 3.0 SDD Change History =============================================================================== 3.1 Defects Fixed 3.1.1 Common 3367 (mc 162234) Improve sddsrv path probing and reclamation performance 3613 In a particular case, SDD missed closing a device, leaving a device in an INVALID state 2361 Include timestamp in sdd trace 3394 Rescan lun size when vpath gets reconfigured 3477 Verify path serial number when opening a single path 3522 (PMR01065) System crash with reserve on device; open (SC_NOSERV) 3131 Incorrect RAID10 message in datapath query essmap 3130 chdev fails to create pvid attribute with SDD vpath device 3098 (PMR 00938,6xm,760) SDD chgvpath method should clear path pvid attributes of SDD vpath devices from ODM database 3097 (PMR 88711,031,724) Support SVC vdisk dynamic resizing 3083 (PMR 31737,075,724) I/O hung if daemon stack is paged out 3007 The display for RaidMode in the "datapath query essmap" command is changed from hex to text string 2912 Rename and consolidate SDD MAX LUN ODM attributes 2816 Sddsrv needs to collect trace when it starts and shuts down 2711 Add -B option in smit panel for mkvg4vp command 2743 Incorrect adapter state during dead path restoration 2748 Update default controller information in driver during addpaths 2741 Datapath query adapter should reject "-d" option 2744 SDD configuration should only read boot disk hdisks at Available state 2613 (PMS23390) Dynamic enable/disable queue depth may not enable/disable queue depth for all vpaths. On systems running heavy I/O, this exposes a SDD problem in which queued I/O could be lost, causing the application that's sending the I/O to hang (PMR51777) With 2 paths per vpath configured, and queue depth is disabled, there is a possibility that I/O failover may fail 2682 Improve performance of datapath remove adapter, especially with large configurations 2692 sddsrv may hang on device collection and stop doing path probing and path reclamation 2597 Attributes that were changed dynamically changed back to default after a host reboot 3.1.2 ESS/DS8000/DS6000 defects None 3.1.3 SVC defects 3519 (PMR 15562,082,000) Querysn fails on SVC devices if 2105 Host Attachment package is not installed 3.1.4 SVCCISCO defects None =============================================================================== 3.2 New Features 3180/3507 Provide a data collection tool, sddgetdata, for problem analysis 3484 Add sddsrv error messages into AIX error log 3096 (PCR 2886) Mark non-preferred paths in 'datapath query device -l', 'datapath query essmap', and 'datapath query portmap' commands 2624 Support new devices, DS6000(1750) and DS8000(2107) 2825 Enhance SDD configuration methods and migration 2715 hd2vp, vp2hd, and dpovgfix will not fail if volume group is mixed with non-SDD devices 2740 New migration option for large device configuration 2642 Increase the size of some adapter counters to 64-bit so datapath can display larger select counts. =============================================================================== 3.3 Feature Details 3096 (PCR 2886) Mark non-preferred paths in 'datapath query device -l', 'datapath query essmap', and 'datapath query portmap' commands SDD 1.6.0.1 has introduced a new feature to aid users to verify their SAN configurations in a controller environment. For example, if users have 4 paths per SDD vpath device and they would like to configure a equal distribution between preferred controller and non-preferred controller, they will configure their environment with 2 paths from a preferred controller and another 2 paths from a non-preferred one. This feature will help users to verify their configuration by indicating which path is from the non-preferred controller before the device starts operation. There are the three datapath commands that offer this feature: datapath query device datapath query essmap datapath query portmap For 'datapath query device', a new option, '-l', is added to mark the non-preferred paths with an asterisk. This option can be used in addition to the existing datapath query device commands. Here are the examples: datapath query device -l datapath query device -l datapath query device -d -l The following is a sample output of this new option in 'datapath query device'. > datapath query device 0 -l DEV#: 0 DEVICE NAME: vpath0 TYPE: 2145 POLICY: Optimized SERIAL: 6005076801818008C000000000000065 LUN IDENTIFIER: 6005076801818008C000000000000065 ========================================================================== Path# Adapter/Hard Disk State Mode Select Errors 0* fscsi1/hdisk72 OPEN NORMAL 0 0 1 fscsi0/hdisk22 OPEN NORMAL 5571118 0 2* fscsi0/hdisk32 OPEN NORMAL 0 0 3 fscsi1/hdisk62 OPEN NORMAL 5668419 0 In 'datapath query essmap' output, non-preferred paths are marked with an asterisk under the column 'P'. Disk Path P Location adapter LUN SN Type Size LSS Vol Rank C/A S ... ------ ---- - ----------- ------ ----------- ----------- ---- ---- --- ----- ---- - ... vpath20 hdisk1 30-60-01[FC] fscsi1 13AAAKA1200 IBM 1750-500 1.1 18 0 0000 01 Y ... vpath20 hdisk720 * 30-60-01[FC] fscsi1 13AAAKA1200 IBM 1750-500 1.1 18 0 0000 01 Y ... vpath20 hdisk848 20-60-01[FC] fscsi0 13AAAKA1200 IBM 1750-500 1.1 18 0 0000 01 Y ... vpath20 hdisk976 * 20-60-01[FC] fscsi0 13AAAKA1200 IBM 1750-500 1.1 18 0 0000 01 Y ... In 'datapath query portmap' output, non-preferred paths are designated by lower case letters 'y', 'o' and 'n'. BAY-1(B1) BAY-2(B2) BAY-3(B3) BAY-4(B4) ESSID DISK H1 H2 H3 H4 H1 H2 H3 H4 H1 H2 H3 H4 H1 H2 H3 H4 ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD BAY-5(B5) BAY-6(B6) BAY-7(B7) BAY-8(B8) H1 H2 H3 H4 H1 H2 H3 H4 H1 H2 H3 H4 H1 H2 H3 H4 ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD 13AAAKA vpath20 O--- ---- ---- ---- o--- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- 13AAAKA vpath21 Y--- ---- ---- ---- y--- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- Y = online/open y = (alternate path) online/open O = online/closed o = (alternate path) online/closed N = offline n = (alternate path) offline - = path not configured PD = path down 2825 Enhance SDD configuration methods and migration Starting from SDD 1.6.0.0, SDD introduces a new feature in the configuration method to read the pvid from the physical disks and convert the pvid from hdisks to vpaths during the SDD vpath configuration. With this feature, you can skip the process of converting the pvid from hdisks to vpaths after configuring SDD devices. Furthermore, SDD migration can now skip the pvid conversion process. This tremendously reduces the SDD migration time, especially with a large number of SDD devices and LVM configuration environment. For details of this feature, refer to SDD User's Guide, section "Migrating or upgrading SDD packages automatically without system restart" and its sub-section, "Customizing SDD migration or upgrade". 2715 hd2vp, vp2hd, and dpovgfix will not fail if volume group is mixed with non-SDD devices Although SDD does not support mixed volume group, three SDD LVM conversion scripts, hd2vp, vp2hd, and dpovgfix, will not fail the pvid conversion between SDD vpath devices and SDD supported storage hdisk devices even if the volume group consists of non-SDD supported devices. These non-SDD supported devices include IBM RDAC, EMC Powerpath, NEC MPO, and Hitachi Dynamic Link Manager devices. This fix only aims at handling cases where volume groups are temporarily mixed with SDD vpath devices and non-SDD supported devices. 2740 New migration option for large device configuration Starting from SDD 1.6.0.0, SDD offers a new environment variables, SKIP_SDD_MIGRATION for you to customize the SDD migration or upgrade to maximize performance. The SKIP_SDD_MIGRATION environment variable is an option available to permit the bypass of the SDD automated migration process (backup, restoration, and recovery of LVM configurations and SDD device configurations). This variable could help to decrease SDD upgrade time if you choose to reboot the system after upgrading SDD. For details of this feature, refer to SDD User's Guide, section "Migrating or upgrading SDD packages automatically without system restart" and its sub-section, "Customizing SDD migration or upgrade". =============================================================================== 3.4 Known Issues None ================================================================================= 3.5 Correction to User's Guide On page 93 of the SDD User's Guide, the title of the section "Migrating an existing non-SDD volume group to SDD vpath devices in concurrent mode" is incorrect. Its title should be "Detailed instructions for migrating a non-SDD volume group to a supported storage device SDD multipath volume group in concurrent mode". This section is a sub-section of "Migrating a non-SDD volume group to a supported storage device SDD multipath volume group in concurrent mode" On page 29 of the SDD User's Guide, under the section, "Increasing the maximum number of disk storage system LUNs", an additional step is needed between Step 2. and Step 3.: 2. Determine how many paths each SDD vpath device currently has by issuing the command datapath query device. Stop the SDD server by entering the following command: stopsrc -s sddsrv 3. Change all the existing vpaths state to DEFINED by executing rmdev -l dpo -R. On page 32 and 33, an additional step is required after Step 4. 4. Execute ’cfallvpath’ to configure the vpaths. Start the SDD server by entering the following command: startsrc -s sddsrv ------------------------------------------------------------------------------ 4.0 User license agreement for IBM device drivers NOTICE: PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM AND DOCUMENTATION. IBM(R) WILL ONLY LICENSE THIS PROGRAM AND DOCUMENTATION TO YOU IF YOU FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY USING THE PROGRAM AND DOCUMENTATION, YOU AGREE TO ABIDE BY THESE TERMS AND APPLICABLE COPYRIGHT LAWS. IBM LIMITS YOUR ACCEPTANCE OF THE PROGRAM AND DOCUMENTATION TO THE TERMS OF THIS AGREEMENT. The Program and Documentation is owned by International Business Machines Corporation or one of its subsidiaries (IBM) or IBM suppliers, and is copyrighted and licensed, not sold. IBM does not transfer title to this Program and Documentation to you. The terms of this Agreement apply to any additional license copy of the Program or Documentation that IBM authorizes you to make. The term "Program" means the original program and all whole or partial copies of it, including portions merged with other programs. A Program consists of machine-readable instructions and related license materials. Under this Agreement, IBM provides you with a license to use the Program and Documentation only. 4.1 Background/Purpose IBM provides certain device drivers and Documentation under this Agreement. The device drivers and library support that IBM provides under this Agreement are in object code form only. Appendix A of this Agreement indicates the server platforms that are supported. IBM uses announcements to withdraw service for device drivers, feature codes, etc., on hardware and/or operating system platforms. IBM reserves the right to change the Programs or Documentation at any time without prior notice. 4.2 Definitions Derivative Work is a work based on a preexisting work, including a compilation. A Derivative Work prepared without the authorization of the copyright owner of the preexisting work would constitute a copyright infringement. Documentation is the Program documentation that IBM provides to you as follows: IBM Subsystem Device Driver and README files. Object Code is machine-readable instructions in Object Code format. It is substantially in binary form and directly executable by a computer after suitable processing but without the intervening steps of compilation or assembly. Program is the IBM Subsystem Device Driver in Object Code form. 4.3 License grant IBM grants you a revocable, nontransferable, nonexclusive, worldwide, paid-up copyright license to: 1. Use the Program and Documentation solely on the platforms and with the applicable IBM devices described in Appendix A of this Agreement. 2. Maintain one copy of the Program for backup purposes only. Your license to the Programs and Documentation terminates when you no longer rightfully possess the IBM device described in Appendix A. This Agreement does not grant you any right or license to prepare Derivative Works of the Program and Documentation. Nothing in this Agreement grants either party any rights or licenses under any patents or patent applications regardless of whether use and/or execution of the software licensed herein may be construed to practice one or more patents. 4.4 Responsibilities You agree to use the Program and Documentation only with the IBM device described in Appendix A of this Agreement. You will not: 1. otherwise copy, display, transfer, adopt, modify or distribute in any form, the Program and Documentation, except as IBM expressly authorizes in the Documentation 2. decompile, disassemble, reverse engineer, or in any way modify the Program or Documentation 3. sell, rent, lease, sublicense the Program or Documentation, unless explicitly permitted by law without the possibility of contractual waiver; and sublicense or assign the license for the Program and Documentation 4.5 Confidential information Any information which either party may disclose to the other party shall not be deemed to be confidential. If the parties require the exchange of confidential information, such exchange will be made under a separate written confidentiality agreement. 4.6 Limitation of liability IN NO EVENT SHALL IBM OR ITS SUPPLIERS BE LIABLE FOR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LOSS OF DATA, LOST PROFITS, BUSINESS INTERRUPTION OR ANY SPECIAL, INCIDENTAL, INDIRECT, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES , EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND NOTWITHSTANDING THE FAILURE OF ESSENTIAL PURPOSE OF ANY REMEDY. You acknowledge that circumstances may arise where, because of a default on IBM's part or other liability, you may be entitled to recover damages. Under any such circumstances, you agree that in each such instance, regardless of the basis on which you are entitled to claim damages, IBM shall be liable only up to an amount equal to five thousand U.S. dollars ($5,000). This limitation will not apply to claims relating to bodily injury (including death), and damage to real property and personal property. 4.7 Termination Termination for Cause. If either party fails to perform its obligations hereunder, then the other party may terminate this Agreement or the license granted hereunder for cause. Effect of Termination. The rights and licenses granted to you under this Agreement shall automatically terminate upon the termination of this Agreement. 4.8 Representations and warranties THE PROGRAM AND DOCUMENTATION IS PROVIDED ON AN "AS IS" BASIS. IBM MAKES NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE PROGRAM AND DOCUMENTATION.IBM DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. THE ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE OF THE PROGRAM AND DOCUMENTATION REMAINS WITH YOU. 4.9 General Provisions Transfer. You may transfer possession of the program and its media and Documentation to another pay with the transfer of the IBM device described in Appendix A on which such Program is used with. If you do so, you must give the other party a copy of these terms and provide all user documentation to that party, and such party must first agree to such terms before it uses the Program and Documentation. Upon transfer of the Program and Documentation, you must destroy all your copies of the Program and Documentation. Severability. If any provision of this Agreement is found to be illegal or unenforceable, the remainder of this Agreement shall continue in full force and effect provided that the Agreement still effectuates the parties' original intent. Governing Law and Jury Trial Waiver. This Agreement shall be governed by the laws of the State of New York, excluding its conflict of law rules. Each party hereby agrees to waive its rights to a trial by jury. Modifications. No modification to this Agreement, nor any waiver of any rights, shall be effective unless agreed to in a writing that is executed by both parties, and the waiver of any breach or default of this Agreement shall not constitute a waiver of any other right or of any subsequent breach or default. Limitations on Legal Actions. Neither party will bring a legal action against the other more than two (2) years after the cause of action arose. Both parties will act in good faith to resolve disputes. Order of Precedence. In the event of a conflict in terms between this Agreement and another agreement, the terms of this Agreement shall take precedence and prevail over such other terms. Entire Agreement. This Agreement constitutes the entire and exclusive agreement between the parties with respect to this subject matter. All previous discussions and agreements with respect to this subject matter are superseded by this Agreement. 4.10 Appendix A This Appendix indicates: Which specific IBM devices the Program and Documentation are to be used with: IBM devices: IBM Enterprise Storage Server (ESS) IBM devices: IBM TotalStorage DS8000 IBM devices: IBM TotalStorage DS6000 IBM devices: IBM TotalStorage SAN Volume Controller IBM devices: IBM TotalStorage SAN Volume Controller for Cisco MDS 9000 CONTINUING WITH THIS INSTALLATION CONSTITUTES YOUR ACCEPTANCE OF THE TERMS OF THE ABOVE 'USER LICENSE AGREEMENT FOR IBM DEVICE DRIVERS' ------------------------------------------------------------------------------- 5.0 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services,or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries,in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Information Enabling Requests Dept. DZWA 5600 Cottle Road San Jose, CA 95193 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM License Agreement for Non-Warranted Programs. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. =============================================================================== IBM agreement for licensed internal code +---- Read Before Using -----------------------------------------------+ |IMPORTANT | | | |YOU ACCEPT THE TERMS OF THIS IBM LICENSE AGREEMENT FOR MACHINE CODE BY| |YOUR USE OF THE HARDWARE PRODUCT OR MACHINE CODE. PLEASE READ THE | |AGREEMENT CONTAINED IN THIS BOOK BEFORE USING THE HARDWARE PRODUCT.SEE| |IBM agreement for licensed internal code. | | | +----------------------------------------------------------------------+ You accept the terms of this Agreement(3) by your initial use of a machine that contains IBM Licensed Internal Code (called "Code"). These terms apply to Code used by certain machines IBM or your reseller specifies (called "Specific Machines"). International Business Machines Corporation or one of its subsidiaries ("IBM") owns copyrights in Code or has the right to license Code. IBM or a third party owns all copies of Code, including all copies made from them. If you are the rightful possessor of a Specific Machine, IBM grants you a license to use the Code (or any replacement IBM provides) on, or in conjunction with, only the Specific Machine for which the Code is provided. IBM licenses the Code to only one rightful possessor at a time. Under each license, IBM authorizes you to do only the following: 1. execute the Code to enable the Specific Machine to function according to its Official Published Specifications (called "Specifications"); 2. make a backup or archival copy of the Code (unless IBM makes one available for your use), provided you reproduce the copyright notice and any other legend of ownership on the copy. You may use the copy only to replace the original, when necessary; and 3. execute and display the Code as necessary to maintain the Specific Machine. You agree to acquire any replacement for, or additional copy of, Code directly from IBM in accordance with IBM's standard policies and practices. You also agree to use that Code under these terms. You may transfer possession of the Code to another party only with the transfer of the Specific Machine. If you do so, you must 1) destroy all your copies of the Code that were not provided by IBM, 2) either give the other party all your IBM-provided copies of the Code or destroy them, and 3) notify the other party of these terms. IBM licenses the other party when it accepts these terms. These terms apply to all Code you acquire from any source. Your license terminates when you no longer rightfully possess the Specific Machine. Actions you must not take You agree to use the Code only as authorized above. You must not do, for example, any of the following: 1. Otherwise copy, display, transfer, adapt, modify, or distribute the Code (electronically or otherwise), except as IBM may authorize in the Specific Machine's Specifications or in writing to you; 2. Reverse assemble, reverse compile, or otherwise translate the Code unless expressly permitted by applicable law without the possibility of contractual waiver; 3. Sublicense or assign the license for the Code; or 4. Lease the Code or any copy of it. ------------------------------------------------------------------------------- 6.0 Trademarks and service marks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: AIX AS/400 Enterprise Storage Server HACMP/6000 IBM IBM logo iSeries Netfinity NetVista Operating System/400 pSeries RS/6000 Seascape SP System/360 System/370 System/390 The eServer logo TotalStorage Versatile Storage Server xSeries zSeries z/Architecture z/OS Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. ------------------------------------------------------------------------------- (C) Copyright IBM Corporation 2000, 2002, 2003, 2004. All rights reserved.