IBM(R) Multipath Subsystem Device Driver Path Control Module (PCM) Version 2.4.0.3 README FOR AIX? October 14, 2011 --------------------------------------------------------------------------- CONTENTS 1.0 About this README file 1.1 Who should read this README file 1.2 How to get latest support version information 2.0 Prerequisites for SDDPCM 3.0 SDDPCM change history 3.1 Defects Fixed 3.2 New Features 3.3 Feature Details 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 Path Control Module(SDDPCM). This README file contains the most recent information about the IBM Multipath Subsystem Device Driver PCM, Version 2 Release 4 Modification 0 Level 3 (SDDPCM 2.4.0.3) for AIX. IBM recommends that you print and review the contents of this README file before installing and using SDDPCM on AIX with MPIO-capable disk driver. 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. DS8000 2. DS6000 3. SAN Volume Controller 4. ESS 5. DS4000 6. DS5000 1.2 How to get latest support version information Go to the following Web site for SDD/SDDPCM 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 SAN Volume Controller web site for latest SDD/SDDPCM support version for SAN Volume Controller: http://www-03.ibm.com/systems/storage/software/virtualization/svc/interop.html Go to the following System Storage Interoperation center(SSIC) web site for latest SDD/SDDPCM support version for all other supported IBM storage subsystems: http://www-03.ibm.com/systems/support/storage/config/ssic/displayesssearchwithoutjs.wss --------------------------------------------------------------------------- 2.0 Prerequisites for SDDPCM Prior to install SDDPCM,you must deinstall fileset "ibm2105.rte"(version of 32.6.100.XX) and "devices.fcp.disk.ibm.rte"(version of 1.0.0.XX) host attachment for SDD driver, along with the SDD package. The SDD driver and SDDPCM module can not coexist on one server. You must install the following host attachment for SDDPCM to support DS4000 and 5000 storage devices, and a new ESS/SVC/DS6K/DS8K storage device attribute - 'retry_timeout': ESS/DS8000/DS6000/SVC/DS4000/DS5000: devices.fcp.disk.ibm.mpio.rte (version 1.0.0.16) Following lists of required AIX and VIOS apars and service packs are cumulative. Apars required in earlier versions of SDDPCM packages are also required for later versions of SDDPCM packages, unless specifically noted as 'no longer applicable' or 'not required'. Note: VIOS is not supported with SDDPCM on DS4000 and DS5000 subsystem devices. sddpcm 2.2.0.3 or higher supports ESS/DS8000/DS6000/SVC storage devices. It requires the following AIX and VIOS releases if you are running SVC release v4.2.1.6 and above that supports LONG BUSY function: AIX Level AIX52 TL10-07 AIX53 TL06-09 AIX53 TL07-06 AIX53 TL08-04 AIX61 TL00-07 AIX61 TL01-03 AIX61 TL02-00 VIOS Level 1.5.2.5-FP-11.1 SP-01 and above sddpcm 2.4.0.0 or higher supports ESS/DS8000/DS6000/SVC/DS4000/DS5000 storage devices. It requires the following AIX and VIOS releases: AIX Level AIX53 TL06-10 AIX53 TL07-07 AIX53 TL08-05 AIX53 TL09-00 AIX61 TL00-08 AIX61 TL01-04 AIX61 TL02-00 VIOS Level 1.5.2.5-FP-11.1 SP-01 and above (NOT for DS4000 or DS5000) VIOS Level 2.1.0.10-FP-20.1 and above (NOT for DS4000 or DS5000) sddpcm 2.4.0.3 or higher supports ESS/DS8000/DS6000/SVC/DS4000/DS5000 storage devices. It requires the following AIX and VIOS releases: AIX Level APAR AIX53 TL08 IZ48395 AIX53 TL09 IZ52471 AIX53 TL10 IZ54856 AIX53 TL11 IZ50064 AIX61 TL00 IZ54857 AIX61 TL01 IZ54858 AIX61 TL02 IZ49639 AIX61 TL03 IZ52470 AIX61 TL04 IZ49804 VIOS Level 1.5.2.5-FP-11.1-SP-01 (NOT for DS4000 or DS5000) VIOS Level 2.1.0.10-FP-20.1 and above (NOT for DS4000 or DS5000) VIOS Level 2.1.1.10-FP-21 and above (NOT for DS4000 or DS5000) The AIX APARs are available from AIX fix central website: http://www-912.ibm.com/eserver/support/fixes/fixcentral/main/pseries/aix --------------------------------------------------------------------------- 3.0 SDDPCM change history =============================================================================== 3.1 Defects Fixed 4532 inconsistent adapter state after implemented rmpath/mkpath sequence. 4533 I/O fail on DS4K/5K if only 2 passive paths online, all Active paths are offline 4539 sddsrv/pcmsrv fails to recover FAILED paths after dynamic tracking event with certain dynamic tracking settings. 4541 sddsrv/pcmsrv hangs while stopping if tcpip port is enabled on AIX5.3 or older version 4547 sddsrv/pcmsrv on AIX5.2 gets hung in close function call 4542 Pcmpath query device command doesn't display total number of devices. 4544 essmap can't display LUN capacity correctly if LUN size > 2TB 4545 Need to display simple and clear error message if no device configured 4550 Cache hint disabled due to data structure mismatch 4554 Active/Passive pcm driver failed to reserve last path in OPEN state 4557 (PMR816119) remove last device may cause system crash or displaying GEN_XMDB errlog 4561 DS4K/5K reset/ccdl tests failed, caused by incorrect failover control logic 4560 incorrect adapter state after set adapter offline and close some devices. 4563 2107 disk access failed in GPFS cluster using persistent reserve policy with AIX53 and above 4564 Additional fix for displaying LUN size with capacity equals or larger than 2TB 4565 removing DS4K/5K devices may cause system crash 4572 Pull off all cables or disable all ports causing I/O hanging with DS4K/5K devices. 4575 (PMR34211) improve the error handling of cascading timeout condition not otherwise handled by adapter/switch interactions 4578 Display DS5K models generically as DS5000 4579 I/O hung on DS4K/5K devices if paths failed with reservation conflict 4581 I/O failed on Active/Active devices if only one path is left 4586 (PMR59533) System crashed with Round Robin after path/adatper is removed. =============================================================================== 3.2 New Features 4585 Add a new device attribute - 'retry_timeout', which set the timeout value for I/O retry on last path. =============================================================================== 3.3 Feature/defect Details 4575 Starting from v2.4.0.3, a new device attribute - 'retry_timeout' is added for ESS/DS6K/DS8K/SVC devices. This attribute allows user to set the timeout value for I/O retry on the last path. The default value of this attribute is 120 seconds and it is user-changeable with the valid range of 30 to 600 seconds. pcmpath provides a new CLI command to dynamically change this device retry_timeout attribute. The syntax of this command: pcmpath set device /( ) retry_timeout This feature enables user to adjust the timeout value to control how long SDDPCM will retry the I/O on last path before it fails to the application. In the situation where a device access is lost on all the paths permanently and command fails with TIMEOUT erro, which takes rw_timeout time to fail a command. By setting retry_timeout value to default (120 seconds) or smaller value, this feature enables fast path failure and avoids I/O hanging problem in this condition. In the situation where a device loss of access is only temporary, the retry_timeout value may need to be set to a larger value. For example, during certain storage concurrent code download or storage warmstart, it is possible that all the paths to a device may lost access for a short period of time temporarily, such as from a few seconds to a few minutes. Under such situation, I/O should be retried on the last path for an extended period of time to prevent failing the I/O back to application. This will open the window for path recovery from temporary errors. =============================================================================== 3.4 Known issues SDDPCM supports 'pcmpath set adapter online|offline aa|ap' command. For FC adapter connected to DS4000 or DS5000 active/passive storage devices, you should use 'ap' parameter to indicate this is an adapter connected to DS4000 and/or DS5000 storages devices. If an adapter is connected to other storage devices, then you should use 'aa' parameter. Since set an adapter OFFLINE may cause DS4000 and/or DS5000 LUN fails over to an alternate controller, this command is only supported when the AIX server has one DS4000 or DS5000 storage subsystem configured. This command may not work correctly if you have more than one DS4000 or DS5000 storage subsystem devices configured on one AIX server, and 'set adapter offline' command causes multiple subsystem device models migrating from one controller to alternate controller. Please refer to SDD User's Guide, chapter 3 for detail information of this command. There are known AIX disk driver configuration issues, which fails the migration of DS4000 and/or DS5000 subsystem devices from fcparray(RDAC) driver non mpio devices to SDDPCM mpio devices; or from AIX native mpio devices to SDDPCM mpio devices. Therefore, the SAN boot function is not supported with DS4000 and DS5000 subsystem devices at this release, until AIX disk driver configuration problem is resolved. VIOS is not supported with SDDPCM on DS4000 and DS5000 subsystem devices. If user removes host FC HBA port from DS4000 or DS5000 storage subsystem while application is running, this will cause I/O performance degradation. The correct procedures are: 1. identify the host FC HBA you plan to remove from DS4000 or DS5000 storage subsystem 2. issue 'pcmpath set adapter X offline ap' or issue 'pcmpath set device M path N offline' command to set all the paths that connected to this FC HBA you plan to remove offline. 3. from the DS4000 or DS5000 storage subsystem to remove the FC HBA port. 4. if removing this host FC HBA port is a permanent configuration change, make sure you remove this configuration on the host side by issuing either remove adapter or remove path command. =============================================================================== 3.5 Corrections to User's Guide On Page 127 the description of section "Starting the SDDPCM server manually" should be read as: If pcmsrv did not start automatically after you performed the SDDPCM Installation and configured supported storage devices, you can start pcmsrv by entering: startsrc -s pcmsrv -e "XPG_SUS_ENV=ON" On Page 127 the description of section "Stopping the SDDPCM server" should be read as: However, in certain cases when you want to permanently (not to start even after a system restart) disable pcmsrv, you must comment out the following line in the system init table (/etc/inittab): srv:2:wait:/usr/bin/startsrc -s pcmsrv -e "XPG_SUS_ENV=ON" > /dev/null 2>&1 On page 102 "Unsupported SDDPCM feature" section, "HACMP and VIO are not supported...." statement should be read as: VIO is not supported with DS4000 and DS5000 storage subsystems. On page 108 the description of #2 under "installing SDDPCM from CD-ROM" should be read as: 2. The AIX SDDPCM host attachment package (devices.fcp.disk.ibm.mpio.rte) should be installed along with SDDPCM package (devices.sddpcm.52.rte, devices.sddpcm.53.rte, or devices.sddpcm.61.rte). Note: Do not reboot the system if you only have SDDPCM host attachment package installed. On page 108, under "Installing and upgrading the AIX SDDPCM host attachment" A warning should be added: warning: Do not reboot the system if you only have SDDPCM host attachment package installed. On page 108, the last paragraph of "Installing and upgrading the AIX SDDPCM host attachment" section should be read as: For AIX SDDPCM host attachment installation and upgrade instruction from the CD, see the Host System Attachment Guide for your storage device. Do not reboot the system before SDDPCM package is installed on the system. For AIX SDDPCM host attachment installation and upgrade from the SDD download Web site, use following procedure: 1. Download code from the Web site that is appropriate for your system. 2. Move the downloaded file to the /usr/sys/inst.images directory. 3. Change directory to the /usr/sys/inst.images directory. 4. Untar the downloaded file: for example, tar -xvf devices.fcp.disk.ibm.mpio.rte.tar. 5. Update the .toc file. For example: pwd rm -i .toc inutoc . grep -i devices.fcp.disk.ibm .toc This command should reflect the newer SDDPCM host attachment version that will be uploaded. 6. From your desktop window, enter smitty install_update and press Enter to go directly to the installation panels. The install and Update Software menu is displayed. 7. Highlight Install Software and press Enter. 8. Enter . to indicate the current directory and press Enter. 9. Highlight Software to Install and press F4. The Software to install panel is displayed. 10. Select the devices.fcp.disk.ibm.mpio.rte package 11. Press Enter. The Install and Update from LATEST Available Software panel is displayed with the name of the software that you selected to install. 12. Check the default option settings to ensure that they are what you need. 13. Press Enter to install. SMIT responds with the following message: ARE YOU SURE?? Continuing may delete information you may want to keep. This is your last chance to stop before continuing. 14. Press Enter to continue. The installation process may take a few minutes to complete. 15. When the installation or upgrade is complete, press F10 to exit from SMIT. 16. If this is a host attachment installation, do not reboot the system until you have SDDPCM package installed; if this is host attachment upgrade, and SDDPCM package is already installed on the system, then reboot the system to complete the host attachment upgrade. User's Guide 1.8-2.4* version, on page 134, under "3. To query and display which type of persistent reservation is on a device, enter pcmquerypr -Vh /dev/hdisk#.", a note should be added: Note: Since SVC LUN returns Good status for SCSI-3 persistent reserve commands, even SCSI-2 reserve presents on the LUN, therefore, pcmquerypr command can not be used to verify if SCSI-2 reserve presents on the SVC LUN or not. --------------------------------------------------------------------------- 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: 1. 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 System Storage SAN Volume Controller 2. For what specific server platforms the Program and Documentation are to be used and for what software requirements apply to the use of the Program and Documentation, refer to the following websites: - IBM Enterprise Storage Server (ESS) support: www.storage.ibm.com/hardsoft/products/ess/supserver.htm - IBM TotalStorage DS8000 www.ibm.com/servers/storage/disk/ds8000/index.html - IBM TotalStorage DS6000 www.ibm.com/servers/storage/disk/ds6000/index.html - IBM System Storage SAN Volume Controller support www.ibm.com/storage/support/2145 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.