File Name: readme.txt **************************************************************** ** ** ** IBM(R) Director Version 4.1 ** ** Server Plus Pack ** ** Software Distribution (Premium Edition) ** ** ** ** Part number 01R0544 ** ** ** ** (C) Copyright IBM Corp. 1999, 2003 All rights reserved. ** ** ** ** Note to U.S. Government Users Restricted Rights -- Use, ** ** duplication or disclosure restricted by GSA ADP Schedule ** ** Contract with IBM Corp. ** ** ** **************************************************************** ================================================================ | This readme.txt is provided only in English on the "IBM | | Director 4.1" CD. | | | | You can obtain the latest version of the readme file from | | the IBM Support Web site. | ================================================================ CONTENTS 1.0 Overview 2.0 Installation 2.1 New installation 2.1.1 Installing on Windows 2.1.2 Installing on Linux 2.2 Upgrading 3.0 Known problems and workarounds 3.1 General 3.1.1 Server-model specific problems and workarounds 3.2 Management Processor Assistant 3.3 Active PCI Manager 3.4 Web-based Access 3.4.1 Microsoft Internet Explorer 3.4.2 Netscape Navigator 3.5 Software Distribution 3.6 BladeCenter products 3.6.1 BladeCenter Deployment wizard 3.6.2 BladeCenter chassis 4.0 Corrections to the publications 4.1 Installation and Configuration Guide (dir41_install.pdf) 4.2 Systems Management Guide (dir41_sysmgt.pdf) 5.0 Support Web sites 6.0 Notices 6.1 Trademarks and service marks 1.0 OVERVIEW IBM Director Version 4.1 is an upgrade release to IBM Director Version 3.1 and Version 3.1 Service Pack 1. The following publications are available on the "IBM Director Version 4.1" CD: o "IBM Director 4.1 Installation and Configuration Guide" o "IBM Director 4.1 Systems Management Guide" These guides are in the docs directory on the CD. The guides are in Portable Document Format (PDF) and require Adobe Acrobat Reader to view them. 2.0 INSTALLATION The following instructions are available for IBM Director 4.1: o Installation o Unattended installation o Upgrading o Configuration These instructions are provided in the "IBM Director 4.1 Installation and Configuration Guide." This guide is in the docs directory on the "IBM Director Version 4.1" CD. The guide is in Portable Document Format (PDF) and requires Adobe Acrobat Reader to view it. 2.1 New Installation 2.1.1 Installing on Windows o (IBM Director Agent 4.1 only) If you cancel the IBM Director Agent installation, files might remain in the following directories: \IBM\Director\data \IBM\Director\data\map \IBM\Director\data\script \IBM\Director\data\snmp where is the drive and directory you designated for the installation. These directories and files can be deleted safely. o (Microsoft(R) Windows(R) XP only) When installing IBM Director Agent, message windows might occur that are hidden behind the installation window. These message windows stop the installation from continuing. To check for hidden message windows, press Alt+Tab to cycle through the active windows. Note: You cannot perform an unattended (silent) installation of IBM Director Agent because of these message windows. o (Windows XP only) During the installation, a message window for driver installation is displayed. Click "Next" to install the drivers required by IBM Director Agent. When the installation is completed, another message window is displayed to restart the system. If you click "Finish", when the system restarts, it detects hardware for which drivers were not installed. To avoid this situation, when the installation is completed, click "No" to decline restarting the system. Wait approximately 5 minutes while the installation program detects the hardware. Then, for each message window that is displayed, click "Next" to install the applicable drivers. 2.1.2 Installing on Linux o When configuring the database, you must provide and confirm the database password. If the confirmation password does not match the password, you must cancel the database configuration and exit the cfgdb program. Then, start the database configuration again by typing: ./cfgdb When you provide and confirm the database password, be sure to type them correctly so they match. o The following IBM SMBus device driver for Linux(R), version 4.1 files are not located on the "IBM Director 4.1" CD: o ibmsmb-src-redhat-4.10-1.i386.rpm o ibmsmb-src-suse-4.10-1.i386.rpm o smbusdriver_linux.xml You must download these files from IBM. See "Section 5.0 Support Web Sites" for more information. o To install the IBM SMBus device driver using the Software Distribution task, the binary RPM file must be located in the same directory as the smbusdriver_linux.xml file. 2.2 Upgrading o (Windows only) If you receive error message 1306, complete the following steps to correct the problem: 1. Access the Windows Administrative Tools window. 2. Double-click "Services". The Services window opens. 3. Double-click "Director Support Program". The Properties window opens. 4. In the "Startup type" list, click "Manual". 5. Click "OK". 6. Restart the system. 7. Start the IBM Director upgrade. o (Japanese, Simplified and Traditional Chinese, and Korean only) Upgrading from version 3.1 to version 4.1 results in corrupted characters in the Description field of Alert Forwarding Profiles in the Management Processor Assistant task. To avoid this, make a note of your Description field contents before upgrading. After installing IBM Director 4.1, you can reenter the description; however, you must reenter the information in English because all input fields that are interpreted by the service processor must be provided in US ASCII. o (Linux only) You cannot upgrade to IBM Director Agent 4.1 on managed systems running SuSE Linux 8.0. o All user-defined temperature thresholds are lost when upgrading from IBM Director 3.x to 4.1. To avoid losing threshold settings, prior to upgrading make a note of the temperature thresholds, install IBM Director 4.1, and then reset the thresholds. o (Upgrading from IBM Director Server 2.2 to 3.1 to 3.1.1 to 4.1) In the Simple Event Filter Builder, the UM Services tree is obsolete and cannot be used to filter events. Right-click the UM Services tree and click Delete. Use the Director Agent Services tree to filter events. o (Upgrading from IBM Director Server 2.2 to 3.1 to 3.1.1 to 4.1) Complete the following steps if you receive either error message 1921 or 1922: 1. Access the Windows Administrative Tools window. 2. Double-click "Services". The Services window opens. 3. Double-click "Director Support Program". The Properties window opens. 4. In the "Startup type" list, click "Manual". 5. Click "OK". 6. Restart the system. 7. Restart the upgrade of IBM Director Server. 3.0 KNOWN PROBLEMS AND WORKAROUNDS 3.1 General o (Windows 2000 Server only) The initial discovery performed by the management server is resource intensive. After the initial discovery is completed, the resource utilization returns to normal. o (Windows only) If you receive error message 1306 during an uninstallation, complete the following steps: 1. Access the Windows Administrative Tools window. 2. Double-click "Services". The Services window opens. 3. Double-click the "Director Support Program". The Properties window opens. 4. In the "Startup type" list, click "Manual". 5. Click "OK". 6. Repeat steps 3-5 for the Director Web Server, if it is installed. 7. Restart (reboot) the system. 8. Restart the uninstallation. o (Windows 2000 and Windows XP only) If you uninstall IBM Director Server, the following Web server log files might be locked by a process that is assumed to have ended and prevent the uninstall from continuing: apache_log .txt stderr.log where is the date the file was created. If this occurs, a message is displayed stating the file cannot be deleted. Clicking "Retry" only redisplays the message. This is a Windows timing issue with locked files and it should occur very infrequently. To work around the locked file, open the Windows Task Manager and end the process dirservlet.exe. Then, click "Retry" to continue the uninstall or click "Cancel" and restart the uninstall process. o With IBM Director Server 4.1, the management server communicates with the service processor even when a user is not managing the system actively. IBM Director 3.1 Agents generate events when the service processor is accessed. If you manage an IBM Director 3.1 Agent from an IBM Director 4.1 management server, you will receive frequent Remote Sensor Login alerts. o (Linux only) When no default router is configured or a nonroutable private network is used, IBM Director might not add any discovered systems on these networks to the IBM Director Console Group Contents pane. To work around this configuration, do one of the following: o Seed the network in the System Discovery (IP) pane. In IBM Director Console, click "Options" -> "Discovery Preferences"; then, click the System Discovery (IP) pane. Setting System Discovery seeds enables discovery of systems running IBM Director Agents. For more information on seeding, see the online help for the System Discovery (IP) pane or the "Discovery" section in the "Configuring IBM Director 4.1" chapter of the "IBM Director 4.1 Installation and Configuration Guide." o Set a default router using the following command: route add default gw where is your IP address. For more information, see the "route" man page. Setting a default router enables discovery of systems that are accessible using the specified router. o (Multi-node server (complex) and static partition managed objects only, in IBM Director Console) If you drag an event action plan task onto either a multi-node server or static partition managed object, the task appears to complete successfully. However, the events for these managed objects do not work. Instead, you must view the events on the individual systems physical platform managed object (PPMO). o (Japanese, Simplified and Traditional Chinese, and Korean only) System Availability does not support managed systems running IBM Director Agent 3.x. o (Linux only) IBM Director Server inventory fields may appear corrupt when collected from double-byte character set (DBCS) systems. To work around this problem, use a single-byte language to store information for configurable fields such as OwnerName. o If a system is not connected to the Internet when IBM Director Agent 4.1 is installed, the FRU inventory might be empty. To populate the FRU inventory, run the GETFRU command. For more information, see Appendix B of the "IBM Director 4.1 Systems Management Guide." o (Linux only) IBM Director Server might shut down with a fatal error under the following circumstances: o The management server is running Linux and using DB2 as the Director database. o ServeRAID Manager is not installed. o Another IBM Director Server discovers or inventories this system. To resolve this problem, modify the IBM Director Server installation to include ServeRAID Manager. o (IBM Director Agent 4.1 on Windows only) You must restart the managed system in the following situations: o You upgrade from IBM Director Agent 3.x to IBM Director Agent 4.1 and add either ServeRAID Manager or MPA Agent. o After installing IBM Director Agent, you use the Windows Add/Remove Programs feature to add either ServeRAID Manager or MPA Agent. After the InstallShield wizard has completed the installation or modification, restart the managed system to ensure that the new components are detected. 3.1.1 Server-model specific problems and workarounds o (xSeries(TM) server models 440, 360, 255, 235, 342, 345, 335, 232 only) Server power-supply alerts have changed from IBM Director 3.1. In IBM Director 4.1, if no power is running through an installed power supply, whether it is plugged in or in a failing state, the following alert is generated for that power supply: Power supply device identified as PowerSupply reports critical state with possible loss of redundancy. where is the power supply number. o (xSeries 360 and 440 servers attached to an RXE-100 Remote Expansion Enclosure only) The Remote Supervisor Adapter installed in the server manages the RXE-100 Remote Expansion Enclosure. Under these circumstances, you cannot use the Remote Supervisor Adapter as the RS-485 gateway to communicate with the ASM, ASM PCI, or Remote Supervisor Adapter service processors on the ASM interconnect network. o (xSeries 230 servers only) You cannot use the Asset ID task to view System GUID on managed systems running Windows or Linux. On systems running Windows, the System GUID is displayed as an empty string; on systems running Linux, the System GUID is displayed as a string of zeros. 3.2 Management Processor Assistant o NetVista(TM) desktop computers and IntelliStation(R) workstations might show a location of "unknown" in the Management Processor Assistant temperature graphical user interface (GUI). If a temperature event occurs on a system with a temperature location of "unknown," see the hardware maintenance manual for more information. o Occasionally, the Communications Configuration subtask might not display connection information. To solve this problem, you can do either of the following: o Exit Management Processor Assistant and wait a few minutes. Then, start the Management Processor Assistant task and try again. o Click Communications Configuration subtask, click "Global Settings" in the left pane to refresh the Communications Configuration subtask for each selected system. 3.3 Active PCI Manager o You cannot stop a PCI adapter with logical disks using IBM Active(TM) PCI Unplug or Eject Hardware dialog if the PCI adapter and disks are present when IBM Director is started. This problem is resolved with Microsoft Hotfix Q325463_W2K_SP4_X86_EN.exe available from www.microsoft.com. o After using Software Distribution to install the Active PCI Manager extension (a part of the Server Plus Pack) on an IBM Director Agent managed system, you must restart (reboot) the system. If you do not restart the system, in IBM Director Console, the Slot Manager subtask periodically fails to display the Slot Manager window and instead displays empty boxes (a blank data table with no icons). This limitation occurs only when using Software Distribution to install the Active PCI Manager extension. 3.4 Web-based Access 3.4.1 Microsoft Internet Explorer o For Internet Explorer to work properly with IBM Director Web-based Access, you must use 56-bit encryption or higher. o (Windows XP only) A message is displayed about requiring the Java(R) Virtual Machine (JVM) for Internet Explorer. Web-based Access must have the JVM installed to function properly. If you have a copy of the Microsoft JVM, install it; otherwise, download and install the JVM from java.sun.com. 3.4.2 Netscape Navigator o After repeated installations, users might experience problems logging into the IBM Director Agent Web Server using the Netscape Navigator Web browser. To solve this problem, save the configuration data when prompted during the uninstall. This saves the old Secure Sockets Layer (SSL) certificate and allows the login to the Web Server to proceed after IBM Director Agent is reinstalled. o (Traditional and Simplified Chinese only) Opening IBM Director Agent in a Netscape Web browser might display all Chinese characters as boxes. To ensure Chinese characters display properly, install the Java plug-in 1.4.1 that is available at java.sun.com and check the Windows Display Properties settings to ensure they are set correctly for Chinese language display. 3.5 Software Distribution o You cannot use the Software Distribution task to modify an existing installation of IBM Director Agent 4.1. o You cannot distribute software-distribution files to a Microsoft network share because system accounts cannot write to the network share. If a package is distributed to a network share, the system log indicates a lack of hard drive space. Because the failure is due to authentication, modify the distribution to distribute to a local drive. o When creating a Microsoft Windows Installer Package for Software Distribution and specifying a user account under which to install the package, some .MSI files specify certain user restrictions that might prevent successful distribution of the package if the user account is not logged into the managed system at the time of distribution. This is a current limitation of the Software Distribution functionality. o When using the Custom Package Editor to build a software package, if you want to include all subdirectories in a parent directory, select the "Move Subdirectories with Parent" check box on the Files page; then, select the directory and click "Add". o In the File Distribution Servers Manager window, "Maximum Managed Systems" refers to the maximum number of managed systems that can access the file-distribution server at one time. o When using the Director Update Assistant to import the IBM Director Server Plus Pack, in the details view, each package indicates that this update forces a restart (reboot) of the managed system; specifically, the Reboot Specification field specifies "Reboot forced by Update." However, the operating system of the managed system is not restarted; instead, IBM Director Agent on the managed system is restarted. When creating or modifying a package category that includes packages from the IBM Director Server Plus Pack, the Reboot Option check box is selected and you cannot clear the check box. However, the operating system is not restarted (rebooted) after each package is distributed. Instead, IBM Director Agent is restarted after package distribution is complete. While IBM Director Agent is restarting, the managed system appears offline in IBM Director Console. After IBM Director Agent has restarted, the managed system appears online in IBM Director Console. o (Japanese only, on managed systems running Windows) In the Distribution Preferences window, the Share Name field is filled in with the following example share name by default: YYsystemYshare where Y represents the Yen symbol. However, when you press the Yen key, the Share Name field incorrectly displays the backslash (\) symbol. DO NOT overtype or delete the example share name. You MUST retain the Yen symbols in the example and replace ONLY "system" and "share" with the system name and share name you want to use. If you press the Yen key, DO NOT use the backslashes; the backslashes cause redirected distribution to fail. You must exit the Distribution Preferences window, re-enter this window, and be sure to retain the Yen symbols in the Share Name field example. o (Korean only, on managed systems running Windows) In the Distribution Preferences window, the Share Name field is filled in with the following example share name by default: WWsystemWshare where W represents the Won symbol. However, when you press the Won key, the Share Name field incorrectly displays the backslash (\) symbol. DO NOT overtype or delete the example share name. You MUST retain the Won symbols in the example and replace ONLY "system" and "share" with the system name and share name you want to use. If you press the Won key, DO NOT use the backslashes; the backslashes cause redirected distribution to fail. You must exit the Distribution Preferences window, re-enter this window, and be sure to retain the Won symbols in the Share Name field example. o When you use Update Assistant to import software packages for managed systems running Windows that require the managed system to restart (reboot) for the software update to take effect, verify that the "Reboot at end of Category Distribution" check box is selected for any category that contains such packages. After the package category has been created, double-click the package category. The Category Editor window opens. If it is not already selected, select the "Reboot at end of Category Distribution" check box. 3.6 BladeCenter products o Upgrading from IBM Director 4.0 for BladeCenter(TM) products to IBM Director 4.1 is NOT supported. However, you can export the following IBM Director 4.0 data and import it after installing IBM Director 4.1: o Event action plans o Thresholds o Dynamic Group Definitions o BladeCenter Deployment wizard profiles Instructions are available from the IBM Support Web site at www.ibm.com/pc/support. o A BladeCenter discovery does not function properly when multiple network interface cards (NICs) are enabled. To resolve this problem, try one of the following: o Change the network interface card that is attached to the BladeCenter unit network. You might have to search to find the working network interface card. o Disable the network interface cards that are not connected to the management module and then perform the discovery. When the discovery is completed, enable the network interface cards. You must do this each time you perform a discovery. o In some situations, the IBM Director event log is slow to report the insertion of a blade server. If, after inserting a blade server in a BladeCenter chassis, a physical platform managed object (PPMO) is not displayed in IBM Director Console, run the Inventory task against the BladeCenter chassis. 3.6.1 BladeCenter Deployment wizard o To modify a pre-existing BladeCenter chassis profile, complete the following steps: 1. In the IBM Director Console Tasks pane, expand the BladeCenter Assistant task. 2. Drag the Deployment Wizard task onto the BladeCenter chassis with the profile you want to modify. The BladeCenter Deployment wizard starts and the "Welcome to the BladeCenter Deployment wizard" window opens. 3. In the right pane, click the profile you want to modify in the "Load existing profile" list. 4. Click "Next" to continue through the Deployment wizard. You can edit the provided information in each Deployment wizard window. For more information about the BladeCenter Deployment wizard, see the "IBM Director 4.1 Installation and Configuration Guide," chapter 6, "Configuring the IBM BladeCenter chassis," in the section "Using the BladeCenter Deployment wizard." o When a BladeCenter Deployment wizard profile is run against a BladeCenter chassis, IBM Director applies the chassis detect- and-deploy policy only to those bays for which a deployment policy was configured. In addition, IBM Director applies the policy only to blade servers that are shut down; it does not shut down or restart (reboot) running blade servers, unless you have configured Remote Deployment Manager (RDM) to force managed systems to restart. o When a blade server is inserted into a BladeCenter chassis, IBM Director automatically sets the blade server boot sequence to local hard disk drive followed by network. The chassis detect- and-deploy policy is only applied if the blade server fails to start from the local hard disk drive. o When the following conditions exist, IBM Director does not apply the chassis detect-and-deploy policy: o The BladeCenter chassis contains an IBM HS20 SCSI Storage Expansion Unit. o The blade server used in conjunction with the storage expansion unit is set to start (boot) from a SCSI hard disk drive. o The SCSI hard disk drive from which the blade server starts (boots) is removed and reinserted into the storage expansion unit. To ensure that the chassis detect-and-deploy policy is applied, after hotswapping the SCSI hard disk drive, remove and reinsert the blade server. o When you designate a BladeCenter Deployment wizard profile as the chassis detect-and-deploy policy, IBM Director applies the detect-and-deploy policy in either of the following situations: o IBM Director automatically discovers a BladeCenter chassis. o You manually create a BladeCenter chassis managed object. If you delete and then recreate a BladeCenter chassis managed object, IBM Director applies the chassis detect-and-deploy policy to the BladeCenter chassis. 3.6.2 BladeCenter chassis and blade servers o Make sure you have installed the latest version of the management module firmware. Go to the IBM Support Web site to download the firmware. See "Section 5.0 Support Web sites" for more information. o After you remove or insert a blade server, IBM Director might take several minutes to register the changes to the BladeCenter chassis. This can affect the speed with which IBM Director applies chassis detect-and-deploy policies, runs event action plans, updates the chassis association, and writes to the event log. If, after you insert or remove a blade server and wait several minutes, the BladeCenter chassis and blade servers are not properly represented in IBM Director Console, run the Inventory task against the BladeCenter chassis. o When a blade server is removed from the BladeCenter chassis and not reinserted, the Hardware Status indicator might clear automatically. 4.0 CORRECTIONS TO THE PUBLICATIONS 4.1 Installation and Configuration Guide (dir41_install.pdf) o (Chapter 5. Upgrading IBM Director Server and IBM Director Console, on page 55) When upgrading from IBM Director 3.x to 4.1, the fields in the "IBM Director service account information" window are filled in automatically with the service account information that was used for the IBM Director 3.x installation. Note: The upgrade program queries Windows and the fields are filled in based on the information returned by Windows. If the user performing the upgrade is logged in using an account that does not have the appropriate privileges to perform the query, the fields remain blank and the user must provide the IBM Director service account information that was used for the IBM Director 3.x installation. o (Chapter 7. Installing IBM Director Agent, on page 94) Step 5 of the installation procedure should state: Open an ASCII text editor and modify the "User configuration" section of the installation script. This file is fully commented. You can specify the location of the PKG files, select the IBM Director Agent features you want to install, and choose log file options. 4.2 Systems Management Guide (dir41_sysmgt.pdf) o (Chapter 3. Working with managed systems using IBM Director Console tasks, on page 82) You cannot indicate which drives or directories you want IBM Director to search during the software inventory collection process. 5.0 SUPPORT WEB SITES The following Web pages provide resources for understanding, using, and troubleshooting IBM Director and systems-management tools. o IBM Online Assistant and e-Mail http://www.ibm.com/pc/qtechinfo/MIGR-4Z7HJX.html This Web page offers a quick resource to help solve your technical questions. Follow the instructions on this page to find additional solutions for your systems-management tools. If you do not find an acceptable solution, or if you just want to bypass looking for your own solution, you can submit an electronic question. From any page within the IBM Online Assistant, click "None of the above" to submit an electronic inquiry. Response times vary between 24 and 48 hours. o IBM Universal Manageability Discussion Forum http://www7.pc.ibm.com/~ums/ IBM forums put you in contact with other IBM users. The forums are monitored by IBM technicians. o IBM Systems Management Software: Download/Electronic Support page http://www.ibm.com/pc/us/eserver/xseries/systems_management/ dwnl.html Use this Web page to download IBM systems-management software, including IBM Director. o IBM xSeries Systems Management page http://www.ibm.com/pc/ww/eserver/xseries/systems_management/ index.html This Web page presents an overview of IBM systems management and IBM Director. Click "IBM Director 4.1" for the latest information and publications. o Systems Management - Quick Reference Guide http://www.ibm.com/pc/qtechinfo/MIGR-4WEP53.html? This Web page includes links to software downloads, eFixes, Microsoft Service Packs, and publications for supported releases of IBM Director. o IBM Universal Manageability page http://www.ibm.com/pc/us/pc/um/index.html This Web page links to an IBM portfolio of advanced management tools that help lower costs and increase availability throughout the life cycle of a product. o IBM ServerProven(R) page http://www.ibm.com/pc/us/compat/index.html This Web page provides information about IBM hardware compatibility with IBM Director 4.1. o IBM Director Agent page http://www.ibm.com/pc/ww/eserver/xseries/systems_management/ nfdir/agent.html This Web page includes the Compatibility Documents for IBM Director 4.1. It lists all the supported operating systems and is updated every 6 to 8 weeks. o IBM Support page http://www.ibm.com/pc/support/ This is the IBM Support Web site for IBM hardware and systems- management software. For systems-management software support, click "Systems management". If you are preparing to install IBM Director and you need to download updates for your server, click "Servers" on the IBM Support Web site. The IBM xSeries, Netfinity(R), and PC Server support Web page opens. On the left, click "Downloadable files". The Downloadable files by category drop-down list is displayed. Click the category of downloadable files that you need. If you want to use UpdateXpress(TM) to update your server, on the right click "UpdateXpress CD" for the latest release of UpdateXpress. 6.0 NOTICES 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 jurisdictions 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. 6.1 Trademarks and service marks The following terms are trademarks of the IBM Corporation in the United States, other countries, or both: Active PCI BladeCenter the e-business logo eServer IBM IntelliStation Netfinity NetVista ServerProven UpdateXpress xSeries Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds. (C) Copyright IBM Corporation 1999, 2003. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. End