IBM(R) SUBSYSTEM DEVICE PATH CONTROL MODULE(PCM) VERSION 2.0.0.0 README FOR AIX™ November 14, 2003 --------------------------------------------------------------------------- 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 SDDPCM 3.0 SDDPCM change history 3.1 Defects Fixed 3.1.1 ESS 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 Subsystem Device Path Control Module (PCM). This README file contains the most recent information about the IBM Subsystem Device PCM, Version 2 Release 0 Modification 0 Level 0 (SDDPCM 2.0.0.0) 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. You can find the most current documentation and support information Abut AIX MPIO capable devices on the Web site: http://publib16.boulder.ibm.com/pseries/en_US/aixbman/baseadmn/manage_mpio.htm 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 ESS. 1.2 How to get help Go to the following Web site for the IBM ESS Open Systems support: www.storage.ibm.com/hardsoft/products/ess/supserver.htm 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 SDDPCM Prior to install SDDPCM, you must deinstall "ibm2105.rte"(version of 32.6.100.XX) host attachment for SDD driver, and the SDD package. The SDD driver and SDDPCM module can not coexist. You must install ESS host attachment for SDDPCM (devices.fcp.disk.ibm2105.mpio.rte). The current version of the attachment is 33.6.100.6. Important: ESS SCSI devices are not supported in SDDPCM version 2.0.0.0 and the ESS host attachment for SCSI MPIO support (devices.scsi.disk.ibm2105.mpio.rte) is not being released. --------------------------------------------------------------------------- 3.0 SDDPCM change history 3.1 Defects Fixed 3.1.1 ESS defects None 3.2 New Features 3.3 Feature Details 3.4 Known issues 3.5 Correction to User's Guide ESS SCSI devices are not supported in SDDPCM version 2.0.0.0 and the ESS host attachment for SCSI MPIO support (devices.scsi.disk.ibm2105.mpio.rte) is not being released. Missing section in the User's Guide: Updating SDDPCM packages by applying a program temporary fix SDDPCM allows you to update SDDPCM by installing a program temporary fix (PTF). A PTF file has a file extension of bff (e.g., devices.sddpcm.52b.rte.2.1.0.1.bff) and can either be applied or committed when it is installed. If the PTF is committed, the update to SDDPCM is permanent; to remove the PTF, you must uninstall SDDPCM. If the PTF is applied, you can choose to commit or to reject the PTF at a later time. If you decide to reject the PTF, you will not need to uninstall SDDPCM from the host system. Before applying the PTF to your system, you must unconfigure all ESS devices from the Available state to the Defined state. After applying the PTF, follow the procedure in the "Configuring and unconfiguring ESS MPIO-capable devices" section on page 107 of the SDD User's Guide to reconfigure the ESS devices. Use the System Management Interface Tool (SMIT) facility to update SDDPCM. The SMIT facility has two interfaces, nongraphical (type smitty to invoke the nongraphical user interface) and graphical (type smit to invoke the graphical user interface). Tip: The list items on the SMIT panel might be worded differently from one AIX version to another. If the PTF is on a CD, you will need to mount the CD filesystem, and then 'cd' to the directory on the CD which contains the SDDPCM PTF. See 'Creating and mounting the CD-ROM filesystem' on page 104 of the SDD User's Guide for directions on how to mount the CD filesystem. Throughout this SMIT procedure, /dev/cd0 is used for the compact disc drive address. The drive address can be different in your environment. Perform the following SMIT steps to update the SDDPCM package on your system: 1. Log in as the root user. 2. From your desktop window, type smitty install_update and press Enter to go directly to the installation panels. The Install and Update Software menu is displayed. 3. Highlight Install Software and press Enter. 4. Enter '.' to select the current directory as the INPUT Device/Directory for Software panel and press Enter. The Install Software panel is displayed. 5. Highlight Software to Install and press F4. The Software to Install panel is displayed. 6. Select the PTF package that you want to install. 7. Press Enter. The Install and Update from LATEST Available Software panel is displayed with the name of the software that you selected to install. 8. If you only want to apply the PTF, highlight Commit software Updates? and tab to change the entry to no. The default setting is to commit the PTF. If you specify no to Commit Software Updates?, be sure that you specify yes to Save Replaced Files?. 9. Check the other default option settings to ensure that they are what you need. 10. 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. | +---------------------------------------------------------------------+ 11. Press Enter to continue. The installation process can take several minutes to complete. 12. When the installation is complete, press F10 to exit from SMIT. 13. Unmount the CD filesystem and remove the compact disc. Note: You do not need to reboot the system even though the bosboot message may indicate that a reboot is necessary. Missing section in the User's Guide: Committing or Rejecting a PTF Update Before you reject a PTF update, you need to unconfigure and remove all ESS devices from your host system. Committing a PTF does not require this extra step. Perform the following steps to commit or reject a PTF update with the SMIT facility. The SMIT facility has two interfaces: nongraphical (enter smitty to invoke the nongraphical user interface) and graphical (enter smit to invoke the graphical user interface). Tip: The list items on the SMIT panel might be worded differently from one AIX version to another. 1. Log in as the root user. 2. From your desktop window, type smitty install and press Enter to go directly to the installation panels. The Software Installation and Maintenance menu is displayed. 3. Highlight Software Maintenance and Utilities and press Enter. 4. Highlight Commit Applied Software Updates to commit the PTF or highlight Reject Applied Software Updates to reject the PTF. 5. Press Enter. The Commit Applied Software Updates panel is displayed or the Reject Applied Software Updates panel is displayed. 6. Highlight Software name and press F4. The software name panel is displayed. 7. Select the Software package that you want to commit or reject. 8. Check the default option settings to ensure that they are what you need. 9. Press Enter. 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. | +------------------------------------------------------------------------+ 10. Press Enter to continue. The commit or reject process can take several minutes to complete. 11. When the installation is complete, press F10 to exit from SMIT. Note: You do not need to reboot the system even though the bosboot message may indicate that a reboot is necessary. Correction to sub-section entitled 'Removing SDDPCM from an AIX host system' on page 111. When removing SDDPCM from an AIX host system, remove both the SDDPCM software package and the ESS host attachment for SDDPCM. To do this, in step two of the procedure, type the following in the SOFTWARE name field: "devices.sddpcm.52b.rte devices.fcp.disk.ibm2105.mpio.rte" Alternatively, you can press F4 in the SOFTWARE name field to bring up a list of packages and use the F7 key to select these two packages to deinstall. Attention: To remove SDDPCM, it is required that you remove both packages before you configure ESS devices or reboot the system. Otherwise, the devices will get into the Defined state and will not be able to be configured as MPIO or non-MPIO devices. Missing section in the User's Guide: Migrating from SDDPCM to the AIX default PCM or to SDD Note: If you have ESS boot devices configured with SDDPCM, then migration from SDDPCM to the AIX default PCM is not supported in this release. To migrate from SDDPCM to the AIX default PCM, or to SDD, you must first unconfigure the devices and deinstall both SDDPCM and the ESS host attachment for SDDPCM. See 'Removing SDDPCM from an AIX host system' on page 111 of the SDD User's Guide for directions on deinstalling SDDPCM. After you deinstall SDDPCM and the ESS host attachment for SDDPCM, you can then reboot the system to migrate ESS devices to the AIX default PCM. If you want to migrate to SDD, you must install the ESS host attachment for SDD (ibm2105.rte) and the appropriate SDD package for your system after deinstalling SDDPCM and the ESS host attachment for SDDPCM. Then reboot the system to configure the ESS devices to SDD. Addendum to sub-section entitled 'Maximum number of devices supported by SDDPCM' on page 107: System administrators should first determine whether the system has sufficient resources to support a large number of devices. ODM attributes: The AIX fibre-channel adapter has an ODM attribute named lg_term_dma that controls the DMA memory resource an adapter driver can use. When a host has more than 600 LUNs configured, the device open process may fail due to the lack of DMA memory resource. Before increasing the maximum number of LUNs, you should increase the lg_term_dma attribute. The default value of lg_term_dma is 0x200000 and the maximum value is 0x1000000. If you configure more than 600 LUNs, you should increase this attribute value to 0x400000 . If you still experience failure after changing this value to 0x400000, you should increase the value of this attribute again. Changing this attribute requires reconfiguration of the fibre-channel adapter and all its child devices. Because this is a disruptive procedure, You should change the lg_term_dma attribute before assigning or configuring ESS LUNs on a host system. You should also change another fiber adapter attribute, num_cmd_elems, which specifies the maximum number of commands to be queued to adapter. The default value is 200 while the maximum value is 2048. With large number of ESS LUNs configuration, you may increase this attribute to improve performance. Because reconfiguring a large number of devices is very time-consuming, you should perform the following steps to change these ODM attributes before configuring hdisks: 1. Execute lsattr -El fcsN to check the current value of lg_term_dma and num_cmd_elems. 2. Redefine all existing fibre-channel adapters by issuing rmdev -l fcsN -R. It takes long time to unconfigure a large number of devices. An alternative method to speed up this step is to disconnect all fibre-channel cables and reboot the system. 3. Execute chdev -l fcsN -a lg_term_dma=0x400000 to increase the DMA value. 4. Execute chdev -l fcsN -a num_cmd_elems=1024 to increase the maximum commands value. 5. If you disconnected the fibre-channel cables in step 2, reconnect the cables. 6. Configure the fibre-channel adapters, its children devices and hdisks using cfgmgr -l fcsN. Another ODM attribute you may need to change is the ncargs attribute of sys0. With a large number of LUNs configured, many special device files will be created in the /dev directory. Executing the "ls" command with a wildcard (*) in this directory may fail. To fix this, you will need to change the ncargs attribute, which controls the ARG/ENV list size in 4K byte blocks. The default value for this attribute is 6 (24K), and the maximum value for this attribute is 128 (512K). We suggest that you increase the value of this attribute to 30. If you still experience failures after changing the value to 30, you should increase this value to a larger number. Changing the ncargs attribute is dynamic. Use the following command to change the ncargs attribute to 30: chdev -l sys0 -a ncargs=30 Filesystem space: After changing the ODM attributes to accommodate the increase of maximum number of LUNs, use the following steps to determine whether there is sufficient space in the root file system after hdisks are configured: 1. Execute cfgmgr -l [scsiN/fcsN] for each relevant SCSI or FCP adapter 2. Execute df to ensure that root file system (that is, ’/’) size is large enough to hold the device special files. For example: Filesystem 512-blocks Free %Used Iused %Iused Mounted on /dev/hd4 196608 29008 86% 15524 32% / The minimum required size is 8 MB. If there is insufficient space, execute chfs to increase the size of the root file system. --------------------------------------------------------------------------- 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) 2. For what specific server platforms the Program and Documentation are to be used on and for what software requirements apply to the use of the Program and Documentation reference the ESS Open Systems Support Web page,located at: www.storage.ibm.com/hardsoft/products/ess/supserver.htm 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, or other countries, or both: AIX Enterprise Storage Server HACMP/6000 IBM IBM logo IBM TotalStorage iSeries Netfinity NetVista Operating System/400 RS/6000 Seascape SP StorWatch System/360 System/370 System/390 System/400 TotalStorage Versatile Storage Server xSeries zSeries z/Architecture 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. All rights reserved.