IBM Systems IBM UpdateXpress System Pack Installer Readme Version 3.00 Contents 1.0 About UpdateXpress System Pack Installer 2.0 Information resources 2.1 Documentation 2.2 Web resources 3.0 Installation and upgrade information 4.0 Known limitations, problems, and workarounds 4.1 Limitations and problems 4.2 Workarounds 5.0 Notices 5.1 Trademarks 1.0 About UpdateXpress System Pack Installer IBM® UpdateXpress System Pack Installer is a software application that applies UpdateXpress System Packs and individual updates to your system. UpdateXpress System Packs contain Windows® and Linux® firmware and device driver updates. UpdateXpress System Pack Installer allows you to acquire and deploy these updates, as well as compare updates and create bootable-media, and is available with the UpdateXpress System Pack. 2.0 Information resources You can find additional information about IBM UpdateXpress System Pack Installer in the product documentation and on the World Wide Web. 2.1 Documentation The following documentation resource provides additional information about UpdateXpress System Pack Installer. In addition to these release notes, you can find information about how to use UpdateXpress System Pack Installer, v3.00 in the IBM UpdateXpress System Pack Installer User's Guide. This publication is available in the IBM System x® and BladeCenter® Tools Center on the Web at publib.boulder.ibm.com/infocenter/toolsctr/v1r0/topic/uxspi/uspi30_bk.pdf. This documentation is available in Portable Document Format (PDF). You need Adobe® Acrobat Reader or Xpdf to view it. If you need the Adobe Acrobat Reader, you can download it directly from Adobe at www.adobe.com/products/acrobat/readstep2.html. 2.2 Web resources The following Web pages provide resources for understanding, using, and troubleshooting IBM System x and systems-management tools. Web sites * IBM ToolsCenter for System x and BladeCenter www.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=TOOL-CENTER&brandind=5000016 View this Web site to download tools that support IBM System x and IBM BladeCenter products. * UpdateXpress www.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=SERV-XPRESS&brandind=5000016 View this Web site to download the tool, UpdateXpress System Pack libraries and tools, including UpdateXpress System Pack Installer. * Support for IBM BladeCenter www-304.ibm.com/systems/support/supportsite.wss/brandmain?brandind=5000020 View this Web site to find information about online technical support, downloads and drivers, and RETAIN® tips, and to provide feedback about IBM BladeCenter products. * Support for IBM System x www-304.ibm.com/jct01004c/systems/support/supportsite.wss/brandmain?brandind=5000008 View this Web site to find information about online technical support, downloads and drivers, and RETAIN tips, and to provide feedback about IBM System x products. * IBM ServerProven www.ibm.com/servers/eserver/serverproven/compat/us/ View this Web site to learn about hardware compatibility of IBM System x and IBM BladeCenter systems with IBM applications and middleware. Forums * IBM System x Forum www.ibm.com/developerworks/forums/forum.jspa?forumID=740 View this Web site on ibm.com® to learn about various forums that are available to discuss technology-related and product-related issues pertaining to IBM System x hardware and software products. This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. * IBM BladeCenter Forum www.ibm.com/developerworks/forums/forum.jspa?forumID=819 View this Web site on ibm.com to learn about various forums that are available to discuss technology-related and product-related issues pertaining to IBM BladeCenter hardware and software products. This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. 3.0 Installation and upgrade information Complete installation instructions, including supported hardware, operating systems and bootable media, such as USB keys, are provided in the IBM System x ToolsCenter information center on the Web at publib.boulder.ibm.com/infocenter/toolsctr/v1r0/topic/uxspi/uspi_r_requirements.html. 4.0 Known limitations, problems, and workarounds The following limitations, problems, and workarounds are applicable to IBM UpdateXpress System Pack Installer, v3.00. 4.1 Limitations and problems The following limitations are applicable to IBM UpdateXpress System Pack Installer. A confirmation message is not provided when removing machine types from the GUI. From the Target Systems page in IBM ToolsCenter Bootable Media Creator graphical user interface, when you select Remove to remove any machine types from the target systems list, a message is not displayed to confirm the removal. All machine types that you selected will be immediately removed. You must re-launch the tool to add the machine types back to the target systems list. Downloading bootable media might take a long time. When acquiring the bootable media from the IBM UpdateXpress System Pack Installer, the download might take a long time. The acquisition indicator does not change during this download. AMD Driver Pack current version is always undetectable UpdateXpress System Pack Installer does not detect the current version of the AMD Driver Pack. The resulting behavior is that the AMD Driver Pack update package will be recommended for deployment on every execution of the UpdateXpress System Pack Installer, regardless of the current version. Intel® Driver Pack current version is always undetectable UpdateXpress System Pack Installer does not detect the current version of the Intel Driver Pack. The resulting behavior is that the Intel Driver Pack update package will be recommended for deployment on every execution of the UpdateXpress System Pack Installer, regardless of the current version. UpdateXpress System Pack Installer automatically selects undetected updates If UpdateXpress System Pack Installer is not able to detect the current version of the device driver or firmware, but an update is available, then UpdateXpress System Pack Installer will select that update as a recommended update (will always update that component). UpdateXpress System Pack Installer always installs the LSI driver If the hardware for a driver component isn't present in the system or is disabled, the installer will not install the driver. The one exception is for the Windows LSI driver. This driver is always installed. You cannot physically remove the LSI chip because it is a standard component on the planar of the system. However, you can disable it. Thus, even in instances when it is disabled, the UpdateXpress System Pack Installer installs the LSI driver. Broadcom NetXtreme firmware update requires version 3.58b or greater of the tg3 driver The Broadcom NetXtreme firmware update requires version 3.58b or greater of the tg3 driver to support the firmware update process. Version 3.58b or greater of the driver must be loaded and currently running before the firmware update will apply successfully. Linux device driver updates require specific packages The Linux device driver update packs require the following packages to be installed: * rpm-build, perl, and bash for Redhat Enterprise Linux. * perl and bash for SuSE Enterprise Linux. Linux drivers always undetectable in RHEL3 All Linux drivers display as undetectable from the UpdateXpress System Pack Installer UI in RHEL3. The 2.4 kernel used in RHEL3 does not support reporting the version of the installed drivers using the modinfo command. There is no known workaround. Broadcom firmware always undetectable in RHEL3 All Broadcom firmware displays as undetectable from the UpdateXpress System Pack Installer UI in RHEL3. ServeRAID(TM) 8i, 8k/8k-l, 8s, 8e and 7t Firmware is only detected on Windows when the Filter driver is active Detection of ServeRAID 8i, 8k/8k-l, 8s, 8e and 7t Firmware versions requires a filter driver. This filter driver is installed as part of the ServeRAID Manager. It is also installed whenever the ServeRAID firmware update packages from the UpdateXpress System Packs are installed. The ServeRAID firmware update packages will return an error code when executed without the filter driver installed. The Windows system requires a reboot before this driver becomes active. Re-run the ServeRAID firmware update to complete the update. 7e SATA/SCSI HostRAID and 8e SAS/SATA HostRAID controllers are not supported on Windows 2008 32 bit and 64 bit. Baseboard Management Controller (BMC) and CPLD firmware updates require IPMI drivers BMC and CPLD firmware updates require installed and running IPMI drivers. If the IPMI drivers are not running the BMC and CPLD firmware version cannot be detected and the online updates will not install. On IBM System x3655, Baseboard Management Controller (BMC) firmware at level 24a will be reported in hexadecimal (base-16) (18.00) instead of decimal (base-10) (24) This only applies on x3655 for BMC firmware at level 24a. All other BMC firmware levels will report the correct build/version number. This will not affect future BMC updates since all of the release levels are greater than 18. Gathering inventory may take 15 to 20 minutes when Linux Remote Supervisor Adapter II (RSA II) daemon is installed without Linux RSA II card installed On Linux systems, the gathering inventory phase of the install can take as long as 18-20 minutes when the system has the RSA II daemon installed without having the RSA II card installed. The updates you select will still be applied after the delay in the gathering inventory phase. Gathering inventory may be delayed on RHEL3 (32-bit) when applying updates over the network On RHEL 3 (32-bit) systems, the gathering inventory phase of the installation can take as long as 25 minutes when installing over the network. Updates will still be installed after the delay. On Windows, only active and loaded drivers associated with a device are detected For Windows systems, the UXSP Installer only detects the presence and version information for drivers that are active and loaded. A driver for a device may have been installed, but it won't be detected until the operating system associates the driver with its matching device. Drivers that are not associated with a matching device are not detected. Different 'New Version' displayed before and after update The 'New Version' displayed before and after update may differ if the update is undetectable before updating. If the update is currently uninstalled or undetected, this field displays the version of the overall update package. If the update is detected, this field displays the individual update contained within the update package. The version of the overall update package may be different than the version of the individual update file. Offline updates are not deployed Offline updates are not compared or deployed by UpdateXpress System Pack Installer. Offline updates are legacy firmware updates that cannot be directly applied from the OS. x460 / MXE-460 / x3950 is only supported in single node Multi node support is not available for the x460 / MXE-460 / x3950. If you wish to update an x460 / MXE-460 / x3950 multi node, you must break apart the nodes and update as single nodes. Only BIOS versions of QLogic FC firmware are detected The QLogic Fibre Channel firmware update updates both QLogic FC BIOS and firmware. However, the firmware versions of QLogic Fibre Channel firmware updates are not reported. Only the BIOS versions of the QLogic FC firmware are detected. Comparing the update BIOS version to the installed BIOS version is sufficient to determine if the QLogic firmware is backlevel. Only Firmware versions of LSI 1064, 1068 and 1078 firmware updates are detected The LSI 1064, 1068 and 1078 firmware update updates both LSI BIOS and firmware. However, the BIOS versions of LSI firmware updates are not reported. Only the firmware versions of the LSI firmware are detected. For example, instead of displaying: Update : SAS1064 Firmware New Version : 1.23.81.00 Installed Version : 1.23.81.00 Update : SAS1064 Bios New Version : 6.18.01.00 Installed Version : 6.18.01.00 Only the firmware version is displayed: Update : SAS1064 Firmware New Version : 1.23.81.00 Installed Version : 1.23.81.00 Unable to read inserted CD-ROM while updates are being applied on Windows When applying updates on a Windows system using the UXSP Installer, a CD-ROM that is inserted into the CD-ROM drive cannot be read until all updates have completed. An existing CD-ROM that is in the drive can be read provided it is inserted before the updates start. Emulex firmware update requires either the Corekit or the HBA Anywhere application Detection of Emulex firmware update and deployment of Emulex firmware update require either the Emulex CoreKit or the HBA Anywhere application to be already installed. On LS21/LS41, the LSI 1064 onboard cannot be distinguished from expansion card On the LS21/LS41, the LSI 1064 onboard cannot be distinguished from the LSI 1064 expansion adapter. This means that when running in compare or update mode each installed LSI 1064 adapter will be displayed under each LSI 1064 update that is present. The version comparison will be performed and depending on the versioning, the update may be incorrectly determined to be backlevel and may be selected. The updates themselves can distinguish between the adapters and will flash the correct firmware on each adapter. Acquisition of Windows updates does not distinguish between the different versions of Windows Windows 2000, Windows 2003 and Windows 2008 updates are organized in a single Windows UXSP. Similarly the tool acquires all Windows updates (either UXSP or latest individual) for a given system by selecting the OS of Windows. This means that although Windows updates for a given system can be acquired, there may not be updates for the Windows version of interest. For example the acquired UXSP may support Windows 2000 and Windows 2003, but not support Windows 2008. You may wish to use this UXSP to update on Windows 2008. In that case you will get an error code of 33, "Cannot find UpdateXpress System Pack XML file for this Machine Type and Operating System." There is no built-in timeout for completion of updates UpdateXpress System Pack Installer doesn't require that updates complete within a certain time period. If an update doesn't end UpdateXpress System Pack Installer will run indefinitely. Emulex firmware version not detected on Windows when using Emulex Corekit UpdateXpress System Pack Installer cannot detect the Emulex firmware version installed on Windows when the Emulex Corekit is used to install the device driver and utility. For firmware detection to work correctly, you have to install Emulex HBAnyware application utility. The LSI HBA expansion card is undetectable on HS20 (8843) and LS20 blade servers The LSI HBA expansion card (LSI 1064) is undetectable on HS20 (8843) and LS20 blade servers. The LSI HBA expansion card update can still be applied even if the installed version is not detected. The version number is not reported for the RSA 2 firmware Only the build ID of RSA 2 firmware is reported. The version number is not reported. For example: [ ] IBM System x3350 Remote Supervisor Adapter II Update Severity : Initial Release Reboot : Reboot Required to take effect Update ID : ibm_fw_rsa2_k3ep05a_linux_i386 New Version : 1.00 (K3EP05A) Installed Version : (K3EP05A) The version number is not always reported for Diagnostics The build number of the Diagnostics is always reported; the version number is not always reported. The build number of the BMC is not always reported The version number of the Baseboard Management Controller (BMC) is always reported; the build number is not always reported. PXE cannot concurrently boot on all 14 blades Stagger the blade booting so that PXE images do not all load at one time. 8e SATA Controller will not be detected in Windows 2008 environment. Don't try to run the update for this adapter because it will fail. This is a limitation with the Adaptec HRCCONF tool. ServeRAID BR10i and IBM 3Gb SASHBA v2 add-on cards are not distinguishable. When running in compare or update mode, when a system can support both of these add-on cards, both updates will be listed separately. If at least one of the cards is installed, the same installed firmware version of the only installed card (or one of two cards installed) will show up under the installed version of both updates listed. The version comparison will be performed and, depending on the versioning, the update may be incorrectly determined to be backlevel and may be selected. The updates themselves can distinguish between the adapters and will flash the correct firmware on each adapter. Second OS image not always updated when using an ICPM card. If the tftp server is set up on the AMM that the ICPM card is plugged into, UpdateXpress System Pack Installer will update the boot image and only one OS image. You will see the error, "Could not find update file" when the product tries to update the second OS image. The AMM version must be at least BPET42D in order to properly configure the ICPM card. UXSPI 3.00 only supports updating two files for legacy Management Modules. Cobia card on Windows 64-bit will require a 64-bit native build Broadcom CIM provider. 4.2 Workarounds The following know problems and workarounds are applicable to UpdateXpress System Pack Installer, v3.00. 'Enable Task Autorun' and 'Use Text-based User Interface' selections are not preserved on GUI. From Media Purpose page of the IBM ToolsCenter Bootable Media Creator GUI, when you select Enable Task Autorun and Use Text-based User Interface and then click Next, you will navigate to the Acquire Location page. From that page, if you click Previous to navigate back to the Media Purpose page, the Enable Task Autorun and Use Text-based User Interface check boxes are cleared. Workaround: Select the Enable Task Autorun and Use Text-based User Interface again. Machine types are not preserved in the UXSPI GUI when you move from one type of update to another Machine types are not preserved in the UXSPI GUI when you moves from one type of update to another-that is, from UXSPI to Latest Update or from Latest Update to UXSPI). Workaround: Reselect the machine types when you move from one type of update to another. When creating PXE bootable image, the --force option increases the image size. If you create a PXE image in the same directory as an existing PXE image and use the --force option to overwrite existing data, the new PXE image will include the previous PXE image making the new image much larger. Booting from the PXE image might fail if the target machine does not have enough memory to handle the increased size. To boot from a PXE image, the target system must have at least 2.5 times the memory of the created PXE image. For example, if the created PXE image is 600 MB, the required memory is 2.5 * 600 MB = 1.5 GB to boot the PXE image. Workaround: Delete the existing PXE image directory before creating another PXE image in the same directory. More than one instance of UXSPI cannot be run at the same time. Exiting from the current instance." error message is displayed when only one instance of UXSPI is running. UXSPI uses semaphores to prevent UXSP Installer from running multiple instances at the same time. When UXSP Installer exits ungracefully, the semaphore might not get released, preventing another instance of UXSP Installer from starting. Workaround: Run UXSP Installer from command line with -semdestroy option. Then, run UXSP Installer as usual. Keyboard does not work for expanding and collapsing the list of downloaded updates Keyboard keys such as + and - do not expand and collapse the list of downloadable updates in the UXSPI graphical user interface. Workaround: Use the mouse to expand and contract lists in the GUI, or run UXSPI from the command line interface. Cancelling remote Update System Pack Installer instance might cancel other running Update System Pack Installers A remote Update System Pack Installer, started using the --remote option or from a third party connection package such as Windows Remote Desktop Connection, cannot detect another Update System Pack Installer instance running on the same remote system. Running multiple instances on the same system is supported; however, clicking Cancel from the graphical user interface terminates all Update System Pack Installers instances running on the remote system. Workaround: It is preferred that you do not run multiple instances of Update System Pack Installer on the same remote system. If you do, manually check if any other administrators are running Update System Pack Installer before clicking Cancel. Unable to execute UpdateXpress System Pack Installer from USB key Some Linux operating systems (for example, SLES 10) automatically mount USB devices with the noexec parameter. This parameter disallows any user to run a program directory from the mounted device. Workaround: To run a file from a USB device in this configuration, either copy the entire UXSP to your hard disk drive, and execute from that location, or remount the USB device with the exec parameter. You can accomplish the second option by first unmounting the USB device by issuing: umount /mnt/usbkey as root (assuming /mnt/usbkey is the mount point of your USB device). You can then remount the device by specifying the mount command with the exec parameter. For example: mount /dev/sdb1 /mnt/usbkey -o exec). Linux drivers are not active immediately The Linux device drivers require activation. The UpdateXpress System Pack Installer loads the new driver into the file system, but the operating system does not use the new driver until it is loaded. Workaround: To modify this behavior, remove the existing driver with the rmmod command, and load the new driver with the modprobe command. Alternatively, the new driver can become active upon reboot of the system. Linux LSI Logic SCSI 1020/1030/1064/1068 Controllers are not detected after install The Linux device drivers require activation. The UpdateXpress System Pack Installer loads the new driver into the file system, but the operating system does not use the new driver until it is loaded. Workaround: The mptctl driver must be loaded. Run the lsmod command to verify that mptcl is loaded. If it is not loaded, run the following command to load the driver: modprobe mptctl. Linux version of UpdateXpress System Pack Installer requires compatibility libraries The 64-bit UXSP Installer requires the compatibility libraries. However, the compatibility libraries are not installed by default in RHEL4. Thus, when you execute the installer, it returns an error that says there is a missing library file. Workaround: Ensure you install the legacy software development packages. The path passed to the local path argument (-l or --local) must not exceed 234 characters The local path argument cannot exceed 234 characters Workaround: Copy the UpdateXpress System Pack to a directory that is less than 234 characters. Firmware updates for Broadcom network card on Linux or CD/DVD and USB-Key bootable-media are not applied when the network card is not up and active On Linux, a Broadcom network interface controller must be up and active in order for firmware Paiutes to be applied. Also, on Linux and when updating from the bootable-media each network Port must be connected to a switch or router. Workaround: Ensure the network interface controller that you are updating is up and active for each port and connected to a switch or router. UXSP Installer does not always start on Linux systems In rare cases the UXSP installer may fail to successfully start on Linux. In those cases the following error message is sent to stderr: ---------------------------------------------------------- WARNING! This package doesn't appear to match your system. It is likely that it will not properly execute. The following information was determined for your system: distribution = Red Hat release = 4 processor architecture = Intel 64-bit" ---------------------------------------------------------- Distribution, release and processor architecture will vary to match the Linux system. The installer will return an error code of 1. Workaround: Restart the Installer. It will succeed the next time. USB key fails on RHEL5 When a USB key is inserted on RHEL5, by default it is mounted as noexec. This means no application can run, including the UpdateXpress System Pack Installer. Workaround: Override the default noexec mount option. For example, mount a USB key device of /dev/sdc1 as /media/disk. To do so, perform the following steps: umount /dev/sdc1 mkdir /media/disk mount -o exec /dev/sdc1 /media/disk Bootable-media does not automatically boot from USB key on all systems This may occur on some systems. Workaround: * Press the F12 key during boot phase and explicitly select the USB key for booting. This is sometimes necessary on subsequent boots even if the setting is saved. * Some xSeries® BIOS versions do not explicitly give the user the option of selecting the USB Key for booting. In this case, it is necessary to: 1. Press F1 setup at boot phase. 2. Select Startup Option -> Startup Sequence Options. 3. Select the USB Key from the Select the Boot Hard Disk list or the Select the Boot Removable Devices list and press the + key to promote to the top of the list. The list the USB Key will appear in varies depending on the type of USB Key used. 4. Reboot the system and press F12 at boot. Select Removable Devices or Hard Drives as it was detected by the BIOS. * On some earlier models, including the Series 236, the USB Key will not be listed as a boot option. It is necessary to select Diskette from the list of boot options and press F1 at the reminder to insert the floppy disk. This will send you back to the list of boot options where the USB Key should then be available. User Account Control (UAC) on Windows Vista and Windows Server 2008 prevents the installer from running without popup The UAC is a security control that will normally prompt the user before running application at a privileged level on Windows Vista and Windows Server 2008. Workaround: To disable this feature for the UpdateXpress System Pack Installer, launch the install300.exe command prompt with elevated privileges. 1. Right-click install300.exe and select Run as Administrator. 2. Click Yes at the UAC prompt command window. UpdateXpress System Pack Installer will be launched with a full administrator security token. Broadcom firmware is not detected or updated from CD/DVD bootable-media on x3550 system On x3550 system, the CD/DVD bootable-media may not detect the Broadcom firmware version or successfully apply the firmware update. Workaround: Use USB key instead of CD/DVD bootable-media. Or ensure the Baseboard Management Controller (BMC) is updated to version 1.27 build level GFBT43A or later and reboot the system. Multiple instances of UXSP Installer cannot be run simultaneously Multiple instances of UXSP Installer cannot be run simultaneously. If you wish to invoke UXSP Installer to remotely update multiple systems, do not run the Installer simultaneously. Workaround: Wait for UXSP Installer to finish updating a remote system before starting a new instance. Unable to boot from USB Key bootable-media on systems with onboard SATA drives Systems which only support onboard SATA drives, systems such as x306m systems, will fail to boot the USB Key bootable-media. Systems using ServeRAID adapters, or with LSI onboard 1064 or higher, will not experience this problem. Workaround: Create a CD bootable-media and apply the firmware updates from CD-ROM instead of the USB key. Booting from USB Key bootable-media on a x3755 may display video error messages When booting from USB Key bootable-media on a x3755 you may see video error messages about the video resolution. The error is displayed for 30 seconds unless you press the Enter key. Workaround: Ignore this error message. 8GB SanDisk USB key doesn't always mount on RHEL3 and VMware ESX 3 Server On RHEL3 and VMware ESX 3 Server, the 8-GB SanDisk USB key doesn't always mount. However, if you create an 8-GB SanDisk bootable USB key it will successfully boot and update the system from the 8-GB SanDisk USB key. Workaround: Use a different USB key type, for example a 2-GB SanDisk or a n 8-GB Lexar disk. When running latest updates on Linux or VMware stems two RSA 2 Daemon Drivers may be displayed Applying updates with the -L | --latest argument may display 2 different RSA 2 Daemon Driver versions in the update list. Workaround: Clear the older RSA 2 Daemon Driver, or use the -e | --exclude argument to exclude the older driver from the update list Unable to view all the update versions on VMware On the VMware console it is not always possible to view the compete update screen because the updates scroll off the page. Workaround: Redirect the output of the compare command to a file. For example, export to a .txt file by running install300.rhel3 co > output.txt. Then view the file using "more" application or log in remotely using an ssh session to the VMware system and scroll thru the updates on the ssh client. User Account Control (UAC) on Windows Vista and Windows Server 2008 may not show the results screen When logging in as a domain ID and running from the command line, the UAC may cause the UXSP Installer to launch a new command prompt window. This new command prompt window exits when UXSP Installer finishes. This means you will not be able to review the results screen. Workaround: Disable UAC for the command prompt window: 1. Right-click the command prompt application (cmd.exe) and select Run as Administrator. 2. Click Continue at the UAC prompt command window. This launches the command prompt with the full administrator security token. 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 grant 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-0032, 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. 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. 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 Software Interoperability Coordinator, Department 49XA 3605 Highway 52 N Rochester, MN 55901 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 Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. 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 measurements 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. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. 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. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: © your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information softcopy, the photographs and color illustrations may not appear. 5.1 Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. Microsoft®, Windows, Windows NT®, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Java(TM) and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Intel is a trademark of Intel Corporation in the U.S. and other countries. Other company, product, or service names may be trademarks or service marks of others.