IBM(R) SUBSYSTEM DEVICE DRIVER 1.3.2.11 README FOR AIX™ --------------------------------------------------------------------------- CONTENTS 1.0 About this README file 1.1 Who should read this README file 1.2 How to get help 2.0 SDD defects and fixes 2.1 Defect Details 3.0 Support notice for AIX 4.2.1 4.0 Utilities for SDD on an Enterprise Storage Server™ (ESS) 4.1 Description and example of an lsvp program 4.2 Description and example of an lsess program 4.3 Descriptions and examples of ls2105 and lssdd programs 5.0 User license agreement for IBM device drivers 5.1 Background / Purpose 5.2 Definitions 5.3 License grant 5.4 Responsibilities 5.5 Confidential information 5.6 Limitation of liability 5.7 Termination 5.8 Representations and warranties 5.9 General provisions 5.10 Appendix A 6.0 Notices 7.0 Trademarks and service marks --------------------------------------------------------------------------- 1.0 About this README file Welcome to IBM Subsystem Device Driver (SDD). This README file contains the most recent information about the IBM Subsystem Device Driver, Version 1 Release 3 Modification 2 Level 11 (SDD 1.3.2.11) for AIX. IBM recommends that you print and review the contents of this README file and the Subsystem Device Diver User’s Guide before installing and using SDD. You can find the most current documentation and support information on the Web site: www.ibm.com/storage/support/techsup/swtechsup.nsf/support/sddupdates/ 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 1. Go to the following Web site for SDD technical support: ssddom01.storage.ibm.com/techsup/swtechsup.nsf/support/sddsupport/ 2. Go to the following Web site for the most current SDD documentation and support information: www.ibm.com/storage/support/techsup/swtechsup.nsf/support/sddupdates/ 1.3 Go to the following Web site for the IBM ESS Open Systems support: www.storage.ibm.com/hardsoft/products/ess/supserver.htm 1.4 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 SDD defects and fixes The following table lists the defects that are corrected in this release. Note: The defect numbers listed in the table are for IBM internal reference use only. ================================================================ Description =============================================================== 73126 HACMP customers will have to disable or stop the sddsrv daemon prior to using SDD functionality. 73656 HACMP customers will have to manually recover adapter/paths when the sddsrv daemon is disabled. 74334 URL incorrect on pages 30, 31, 32, and 33. The www needs to be dropped. Documentation incorrect in the SDD User's Guide HACMP section. Failover should state fallover, failback should state fallback. 72889 Instructions on page 4, entitled "Concurrent download of ESS licensed internal code" are incorrect. Instruction should read: To perform concurrent download of LIC, refer to "2105 Model E10/E20 F10/F20 Microcode Installation Instructions" for instructions. To perform concurrent download of LIC for the 2105 Model 800, refer to 2105 Model 800 Microcode Installation Instructions for instructions. Instructions on page 25, entitled "Using ESS concurrent download of licensed internal code" are incorrect. Instruction should read: To perform concurrent download of LIC, refer to "2105 Model E10/E20 F10/F20 Microcode Installation Instructions" for instructions. To perform concurrent download of LIC for the 2105 Model 800, refer to 2105 Model 800 Microcode Installation Instructions for instructions. 76319 The information about stopping sddsrv daemon under HACMP environment is not clear. See details in section 2.1. 371571 AIX users with Fibre Channel support and the SDD server daemon can experience performance degradation. 76531 Upgrading from AIX 4.3.3 to AIX 5.1.0 using migration or an installation package not listed in Table 9 on page 22 of the SDD User's Guide requires that you uninstall the existing SDD and then install the new version of AIX. 2.1 Details The following section provides additional information, as applicable, about the defects and fixes listed previously. ================================================================ Details ================================================================ The SDD server daemon is an integrated component of SDD 1.3.2.9 (or later). This component consists of a UNIX application daemon that is installed in addition to Subsystem Device Driver. The SDD server daemon starts automatically after the SDD Device Driver package is installed. It scans to find failing paths regularly between 2-5 minutes intervals. It probes the idle paths at 1-minute intervals. During the HACMP fallover process, we found the following problem: the fallover time took longer to complete when running with broken paths if the SDD server daemon was running in the background. This problem is caused by the current locking design in AIX FC driver. Because there is no way to guarantee that all paths are functional prior to and during cluster fallovers, you should disable the SDD server daemon on all HACMP nodes. Please refer the SDD User's Guide for the information on how to stop the SDD server daemon on the system. If the SDD server daemon is stopped, the feature of automatically recovering failed paths (DEAD or CLOSE_DEAD path) is disabled. During the concurrent Storage bay quiesce/resume process, you must manually recover the adapter/paths after the quiesce/resume is completed on one bay, and before the quiesce/resume starts on the next bay. Without doing so, the application may fail. Please refer to the SDD User's Guide. On pages 30,31,32,33 of the PDF (physical pages 6, 7, 8, and 9) the following URL is incorrect: www.techsupport.services.ibm.com/server/support. It should be as follows: techsupport.services.ibm.com/server/support There is a correction to the section entitled "Adding paths to SDD devices of a volume group", on page 21. The section title should be "Dynamically adding paths to SDD devices of a volume group". The addpaths program can run while the I/O is running on the existing vpaths devices. Step number 4 needs to be removed. The instructions should read: 1. Issue the lspv command to list the physical volumes. 2. Identify the volume group that contains the SDD devices to which you want to add more paths. 3. Verify that all the physical volumes belonging to the SDD volume group are SDD devices (N s ). If they are not, you must fix the problem before proceeding to the next step. Otherwise, the entire volume group loses the path-failover protection. You can issue the dpovgfix vg-name command to ensure that all physical volumes within the SDD volume group are SDD devices. 4. Run the AIX configuration manager in one of the following ways to recognize all new hdisk devices. Ensure that all logical drives on the ESS are identified as hdisks before continuing. . Issue the cfgmgr command n times, where n represents the number of paths for SDD, or . Issue the cfgmgr -l [scsiN/fcsN] command for each relevant SCSI or FCP adapter. 5. Issue the addpaths from the AIX command line to add more paths to the SDD devices. 6. Type the lsvpcfg command from the AIX command line to verify the configuration of the SDD devices in the volume group. SDD devices should show two or more hdisks associated with each SDD device when the failover protection is required. AIX users with Fibre Channel support and the SDD server daemon can experience performance degradation that grows worse over time. Normal performance can be restored by unconfiguring and reconfiguring the Fibre Channel adapter or by rebooting the system. To avoid this problem, users should apply the fixes for the following APARs: AIX 5.1 APAR IY32325 (available in either of PTF U476971 devices.pci.df1000f7.com 5.1.0.28 PTF U482718 or 5.1.0.35) AIX 4.3.3 APAR IY35177 (soon to be available in PTF U483803 devices.pci.df1000f7.com 4.3.3.84) Users can disable the SDD server daemon until the PTF for the APAR is applied. There is a correction to the first paragraph of the section entitled "Upgrading SDD manually" on page 23. The first paragraph should be: "If you are upgrading from a previous version of the SDD that you installed with an installation package not listed in Table 9 on page 22 of the SDD User's Guide, or if you use migration to upgrade from AIX 4.3.3 to AIX 5.1.0, you cannot perform an installation upgrade. Instead, you must uninstall the existing SDD and then install the new version of SDD." There is also a correction to the procedure in the section entitled "Upgrading SDD manually" on page 23. The following step should be inserted after step 8 and the remaining step numbers should be incremented by 1: 9. If you have an AIX migration system, use the smitty command to upgrade your operating system from AIX 4.3.3 to AIX 5.1.0. --------------------------------------------------------------------------- 3.0 Support notice for AIX 4.2.1 The SDD-AIX 4.2.1 package (ibmSdd_421.rte) will not be enhanced after version 1.3.0.1. You will not receive future fixes for this package. --------------------------------------------------------------------------- 4.0 Utilities for IBM Subsystem Device Driver on an ESS The lsvp is a utility program that displays the SDD vpath status from an ESS physical code perspective. You can use the lsvp program to set the SDD vpath paths offline using an ESS location code. The lsvp program is available from the ibmpfe.essutil.rte file set (install package) for an AIX host system. You can obtain the ibmpfe.essutil.rte install package from the following Web site: http://www.ibm.com/storage/support/techsup/swtechsup.nsf/ support/sddlink/ Tip: On the Web site, click "Utilities for IBM Subsystem Device Driver / Data Path Optimizer on an ESS." The following files are included in the ibmpfe.essutil.rte fileset: /usr/lpp/ibmpfe.essutil/README /usr/lib/methods/scsimap /usr/lib/methods/fcmap /usr/bin/lsess /usr/bin/ls2105 /usr/bin/lssdd /usr/bin/lsvp /usr/bin/get_ess_port /usr/bin/get_ess_vpd /usr/bin/get_ess_cudv Perform the following steps to install the ibmpfe.essutil.rte fileset: 1. Use smitty to install ibmpfe.essutil.rte fileset. 2. Choose the next set of options according to your needs. - For SCSI device support: Use smitty to install ibmpfe.essutil.scsi.data fileset. - For FC device support: Use smitty to install ibmpfe.essutil.fibre.data fileset. Attention: You can install both the SCSI and FC support. However, to avoid the error messages described below, you should only install the support for the device types you have configured. You can run the following four programs from the command line: 1) lsvp 2) lsess 3) ls2105 4) lssdd Header definitions for all programs are as follows: Disk - hdisk name assigned by the host Location - physical location code of host adapter lun is accessed through LUN SN - unique serial number for each lun within the ESS Type - device and model Size - configured capacity of lun in giga bytes LSS - logical subsystem where lun resides Vol - volume number within the LSS Rank - unique identifier for each raid-array with the ESS C/A - cluster and adapter accessing the array S - shared by two or more ESS ports, Yes or No Connection - physical location code of ESS adapter lun is accessed through The following sections provide descriptions and give examples of each utility program. 4.1 Description and example of an lsvp program The lsvp shows the SDD vpath status from an ESS physical location code perspective. Included is the capability to set the SDD vpath paths offline using an ESS location code. Usage: lsvp [-adt] [-o] [-l location_code] -a Display SDD logical path to ESS physical location code -d Display path status for each vpath device -t Test physical access to hdisks, can only be used with the -d option -o Attempts to set all SDD paths ONLINE -l Set SDD paths OFFLINE for specified ESS location code The location_code must be in one of the following formats: single port = R1-Bx-Hy-Zz all ports on card = R1-Bx-Hy all ports on bay = R1-Bx Type the following command at the prompt: # lsvp -d The output should look similar to the following output: BAY-1(B1) BAY-2(B2) BAY-3(B3) BAY-4(B4) H1 H2 H3 H4 H1 H2 H3 H4 H1 H2 H3 H4 H1 H2 H3 H4 A B A B A B A B A B A B A B A B A B A B A B A B A B A B A B A B 0 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 1 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 2 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 3 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 4 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 5 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 6 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 7 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 8 - - - - - - O - - - - - - - O - - - - - - - O - - - - - - - O - 9 - - - - - - O - - - - - - - O - - - - - - - O - - - - - - - O - 10 - - - - - - O - - - - - - - O - - - - - - - O - - - - - - - O - 11 - - - - - - O - - - - - - - O - - - - - - - O - - - - - - - O - Y = online/open O = online/closed N = offline X = not-available - = path not configured ? = path information not available PD = path down 4.2 Description and example of an lsess program The lsess program displays data collected from the fcmap and scsimap programs that are invoked by cfgmgr. fcmap and scsimap issue scsi commands directly to the disks (inquiry,read capacity, and log sense) to collect the information displayed. Note: To run lsess, you need to either restart your host system or run cfgmgr (AIX command to configure disks) with all 2105 vg's offline. This is only necessary for the initial run. Type the following command at the prompt: # lsess The output should look similar to the following output: Disk Location LUN SN Type Size LSS Vol Rank C/A S Connection ------ ------------ -------- ------------ ----- ----- ---- ----- ---- -- ----------- hdisk1 10-68-01[FC] 008FC106 IBM 2105-E20 2.0 10 8 1001 01 Y R1-B2-H4-ZA 4.3 Descriptions and examples of ls2105 and lssdd programs: The ls2105 and lssdd programs format data collected by AIX and stored in the ODM when the disks were configured to the host. Type the following command at the prompt: # ls2105 The output should look similar to this: Hostname VG hdisk Location LUN SN S Connection Size LSS Vol Rank -------- -- ----- -------- ------ - ---------- ---- --- --- ---- hashark1 None hdisk1 10-68-01 008FC106 Y R1-B2-H4-ZA 2.0 10 8 1001 Type the following command at the prompt: # lssdd The output should look similar to this: Hostname VG vpath hdisk Location LUN SN S Connection Size LSS Vol Rank -------- ------- ----- ----- -------- ------ - ---------- ---- --- --- ---- hashark1 sharkvg vpath0 hdisk1 10-68-01 008FC106 Y R1-B2-H4-ZA 2.0 10 8 1001 hashark1 sharkvg vpath0 hdisk9 10-68-01 008FC106 Y R1-B1-H4-ZA 2.0 10 8 1001 Note: The ls2105, lssdd, and lsvp programs do not require a system restart or vg's to be offline for initial run. However, they do require the ibm2105.rte package to be at 32.6.100.3 code level (or higher). If lsess has not been run, the lssdd output will not contain LSS, volume, and rank information. Attention: If you are getting one of the following errors when running cfgmgr, it is because your 2105 devices are either all native SCSI or all FC. Method error (/usr/lib/methods/scsimap >> /var/adm/essmap.out): 0514-023 The specified device does not exist in the customized device configuration database. Method error (/usr/lib/methods/fcmap >> /var/adm/essmap.out): 0514-023 The specified device does not exist in the customized device configuration database. If you do hnot intend to have a mix of 2105-SCSI and 2105-FC, then you can eliminate the error by performing either: . Using smitty to remove ibmpfe.essutil.fibre.data fileset (do this for all 2105-SCSI configurations) . Using smitty to remove ibmpfe.essutil.scsi.data fileset (do this for all 2105-FC configurations) Note: Both actions will remove support for the device types you do not have configured. --------------------------------------------------------------------------- 5.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. 5.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. 5.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. 5.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. 5.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 5.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. 5.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. 5.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. 5.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. 5.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. 5.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' --------------------------------------------------------------------------- 6.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. 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. 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. --------------------------------------------------------------------------- 7.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 IBM Netfinity RS/6000 TotalStorage Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation. 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. All rights reserved.