====================================================================== Readme file for: Interim Fix 4 for IBM Tivoli Remote Control, Version 5.1.2 IBM Corp. 15th April 2010 ====================================================================== Contents 1.0 Copyright statement 2.0 Product fix history 2.1 Defects fixed 2.2 APARs fixed 3.0 Function added since GA release 3.1 Since GA release 3.1.1 Report computer description to server on Windows systems. 3.1.2 Security lock policies for session disconnect. 3.1.3 Visual indication for session in progress. 3.1.4 New improved icons for windows 7. 3.2 Function improvement in IF0004 3.2.1 Privacy without bitmap (MR111109327). 3.2.2 Disable controller splash screen (MR120309201). 3.2.3 Search Targets report can be set as the default homepage. 3.2.4 Add capability to define rules to be applied when searching for targets 3.2.5 Authorities for some Menus options are configurable. 3.2.6 Workaround to handle sessions after a Remote Desktop (admin or console mode) session with Windows 2003(MR0317104941) 4.0 Installation information 4.1 Tivoli Remote Control 5.1.2 Windows, Derby Database and eWAS Server Installation 4.2 Tivoli Remote Control 5.1.2 LINUX, Derby Database and eWAS Server Installation 4.3 Manual Installation 4.3.1 Tivoli Remote Control 5.1.2 Websphere Application Server(WAS), AIX, Linux, Solaris and Windows. 4.4 Target requirements 4.5 Admin id for manual AIX install 4.6 Installing the fix pack after installing the GA Level (5.1.2.1080) 5.0 Uninstallation information 6.0 Contacting IBM Support 7.0 Notices and trademarks ====================================================================== 1.0 Copyright statement (c) Copyright International Business Machines Corporation 2010. All rights reserved. U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM(R) Corp. ====================================================================== 2.0 Product fix history 2.1 Defects fixed -------------- N/A 2.2 APARs fixed ----------- IZ70770 ------- In certain keyboard configurations ALT-GR key injection triggers local input being disabled for 1 second and further characters are lost. Using the mouse in combination with SHIFT, ALT or CTRL keys does not work. Typing a character with an alt-code results in double characters or additional unwanted characters being injected. IZ71086 ------- TRC Icon can fails to indicate a session is in progress if the controller user reboots the target with the option to reconnect after reboot. IZ72729 ------- This APAR fixes a race condition on keyboard input that may occur when launching a Remote Desktop session, from a computer that is being controlled with TRC. The symptoms are that modifier keys (shift, ctrl and alt) injected from the ontroller into the Remote Desktop client do not always work. IZ72732 ------- When using the wrc command incorrect IP address for target being returned from the server which results in a remote control session with the wrong target. IZ72773 ------- When gateways are configured in the server and user acceptance is enabled,incorrect messages are being displayed on the controller during a remote control session. This happens when the target user refuses the session or the user acceptance times out. When gateways are configured and session is refused by target user on a target with multiple IP addresses, a connection to all of the IP addresses is tried before ending the connection attempt. IZ73107 ------- The controller console fails to launch on Windows 7 systems running Sun Java 1.6. This APAR also removes the dependency on route.exe for other versions of Java (MR0408106025). IZ73119 ------- Users and policy settings are deleted if the connection to the LDAP server is lost during the LDAP synchronisation. IZ73359 ------- Windows translated to Fenetres on remote install screen when using French language settings. Perform action on target menu displays Ctrl+Shift+Del instead of Ctrl+Alt+Del when using german language settings. When viewing "Support Info" for Tivoli Remote Control in Add/Remove Programs, the Publisher information uses default translations for non-English languages, displaying "COMPANY-NAME" instead of "IBM United Kingdom Ltd". Note: An upgrade will not update this information, a reinstall is required. IZ74589 ------- Fixed an issue by which the gateways did not close all connections successfully. Additionally, an issue causing excessive logging by the controller has also been resolved as part of this APAR IZ74593 ------- Deleted targets details do not appear in the session history reports. This APAR is related to APAR IZ65905 which fixed a similar problem when users were deleted. 3.0 Function added since GA release 3.1 Since GA release * Report computer description to server on Windows systems (MR100609167) - see 3.1.1 * Security lock policies for session disconnect (MR112609168)- see 3.1.2 * Visual indication for session in progress - see 3.1.3 * New improved icons for windows 7 3.1.1 Report computer description to server on Windows systems (MR100609167) ____________________________________________________________________________ The computer description is now reported to the server for environments where important information is stored in this field, however, this information is not added by default to the "All targets" report. In order to add this information: - From the "All Targets" report, click on "Edit SQL" - Select "Add Column" and locate the Asset.Description column, click on "Add" and then "Submit". The report will now show the computer description, but the change needs to be saved. To do this, click on "Reports > Save as custom report" and complete the required information. 3.1.2 Security lock policies for session disconnect (MR112609168) _________________________________________________________________ A new policy, "Lock target on disconnect" has been introduced that, if enabled, will automatically lock the workstation after a TRC session is terminated. 3.1.3 Visual indication for session in progress _______________________________________________ The TRC target icon will now change from a faded red colour when no session is in progress, to a bright red colour icon when a TRC session is in progress. 3.2 Function improvement in IF0004 * Privacy without bitmap (MR111109327) - see 3.2.1 * Disable controller splash screen (MR120309201) - see 3.2.2 * Search Targets report can be set as the default homepage - see 3.2.3 * Number and type of characters entered into the search targets field can be limited - see 3.2.4 * Authorities for some Menus options are configurable - see 3.2.5 * Workaround to handle sessions after a Remote Desktop (admin or console mode) session with Windows 2003 (MR0317104941) - see 3.2.6 3.2.1 Privacy without bitmap (MR111109327) ___________________________________________________________ A new feature has been introduced which will allow the configuration of a policy to determine whether the privacy bitmap is displayed on the target screen or not,when in Privacy Mode. Two new policies have been introduced to work in conjunction with existing policies. Display screen on locked target ------------------------------- This policy works in conjunction with the existing 'Set target locked' policy which enables or disables privacy mode at session start up depending on the value set in the policies for the session. Display screen on locked target allows you to enable or disable the display of the privacy bitmap on the target when privacy mode is enabled. The property can be set to Yes or No, default is No. Yes - The target screen will be visible to the target user during the session but their mouse and keyboard control will be disabled. No - The privacy bitmap will be displayed on the target during the session and their mouse and keyboard control will be disabled. Note: Set target locked should be set to Yes to allow Disable screen on locked target to take effect. Allow input lock with visible screen ------------------------------------ This policy works in conjunction with the existing Allow input lock policy. Allow input lock with visible screen allows you to enable or disable the privacy bitmap on the target when privacy mode is enabled during a remote control session. The property can be set to Yes or No, default is No. Yes - The 'lock target input' menu item will be available for selection in the Perform action in target menu in the controller window. You can select this item to allow the target screen to be visible to the target user when you enable privacy mode during a remote control session.The target users mouse and keyboard will be disabled. No - The 'lock target input' menu item will be not available for selection in the Perform action in target menu in the controller window. When you enable privacy mode during the session the privacy bitmap will be displayed on the target screen and the target users mouse and keyboard will be disabled. Note: Allow input lock should be set to Yes before 'Allow input lock with visible screen' can take effect. 3.2.2 Disable controller splash screen (MR120309201) ___________________________________________________________ The property, rc.show.controller.splash, has been introduced in the trc.properties file to allow you to define whether to display the controller splash screen when starting a remote control session. To disable the display of the controller splash screen complete the following steps: 1) Logon to TRC with a valid admin ID and password. 2) Select Admin > Edit properties file. 3) Select trc.properties. 4) Set rc.show.controller.splash to the required value true - (default value) The controller splash screen will be displayed during the initiation of a remote control session. false - The controller splash screen will not be displayed during the initiation of a remote control session. 5) Click Submit. 3.2.3 Search Targets report can be set as the default homepage ___________________________________________________________ A property has been introduced which allows an admin user to set the search targets page as the default homepage. This property is useful if you have numerous targets registered in the TRC database. The default homepage set by the server is the All targets report which may take some time to load then you will have to scroll through this to find the required target(s), therefore setting the search page as the homepage will allow you to search for specific targets as soon as you log on. Setting the search page as default ---------------------------------- To set the search page as the default homepage complete the following steps: 1) Logon to TRC with a valid admin ID and password. 2) Select Admin > Edit properties file. 3) Select trc.properties. 4) Scroll to the end of the file and set default.homepage.method to the required value. search - this will set the search page as the default homepage. report - this will set the report that is defined in the default.query property as the default homepage. Note: The method for determining the homepage for a user when they log on is still as described in the TRC infocenter here: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/ com.ibm.itrc.doc_5.1.2/trc-admin100.htm#wq399 However it should be noted now that the value set in the property default.homepage.method will determine the homepage if the user does not have a homepage already assigned by themselves or by the group(s) that they belong to. 5) Click Submit. 3.2.4 Add capability to define rules to be applied when searching for targets. ___________________________________________________________________ When using the search targets page you can limit the number and type of characters typed into the search field by using two properties in the trc.properties file. target.search.minimum.nonwildcards ---------------------------------- Sets the minimum number of non wildcard characters that are allowed to be entered when searching for a target. Default value = 0 Note: If you have set view.all.targets.auth to S or A ( see 3.2.5) you should set target.search.minimum.nonwildcards to > 1 to prevent users with user authority being able to use the search targets page to display all of the targets. target.search.maximum.wildcards ---------------------------------- Sets the maximum number of wildcard characters that are allowed to be entered when searching for a target.The wildcard characters allowed are *, %, * and _. Default value = 0 3.2.5 Authority for viewing some Menu options is configurable. ________________________________________________________________ Properties have been introduced in the trc.properties file to allow you to configure the presence of certain menu options depending on user authority. browse.targets.auth ------------------- Determines which levels of user authority will see the Browse option displayed in the Targets menu. U - All user authorities will see the Browse option in the Targets menu. S - Only Super Users and Admin users will see the Browse option in the Targets menu. A - Only Admin users will see the Browse option in the Targets menu. view.all.targets.auth --------------------- Determines which levels of user authority will see the All targets option displayed in the Targets menu. U - All user authorities will see the All targets option in the Targets menu. S - Only Super Users and Admin users will see the All targets option in the Targets menu. A - Only Admin users will see the All targets option in the Targets menu. Notes: 1) If the homepage of the user logging on is set to the All targets report but they do not have the authority to view the All targets report due to the value set for view.all.targets.auth, they will see the Search targets page as their homepage when they log on. 2) If you have set view.all.targets.auth to S or A you should set target.search.minimum.nonwildcards to > 1 ( see 3.24) to prevent users with user authority being able to use the search targets page to display all of the targets. search.session.history.auth --------------------------- Determines which levels of user authority will see the Search option displayed in the Sessions menu. U - All user authorities will see the Search option in the Sessions menu. S - Only Super Users and Admin users will see the Search option in the Sessions menu. A - Only Admin users will see the Search option in the Sessions menu. To configure the properties complete the following steps:- 1) Logon to TRC with a valid admin ID and password. 2) Select Admin > Edit properties file. 3) Select trc.properties. 4) Set the required value for the property. 5) Click Submit. Note: For the new values to take effect, you must now restart the IBM Tivoli Remote Control Server service. 3.2.6 Workaround to handle sessions after a Remote Desktop (admin or console mode) session with Windows 2003 ______________________________________________________________________ When a Remote Desktop user uses the /admin or /console option to start a Remote Desktop session with a Windows Server 2003 system and a TRC user starts a remote control session before, during or after the Remote Desktop session, remote control is unable to capture the display resulting in a grey screen in the controller. The root cause of this behaviour is that after this Remote Desktop session starts, the new console session started by Windows does not seem to be fully functional. To restore functionality,the sessions need to be reset using the Windows'reset session' command. Since this is a limitation in Windows Server 2003, this fixpack introduces a workaround that will reset the Windows session either after each Remote Desktop session terminates, or before a TRC session starts, as configured by the TRC administrator. You can configure this in two ways:- In both cases, there are three possible options: - Do not apply workaround (default) - Reset the session automatically when the Remote Desktop user logs out. - Reset the Windows session when a TRC session is started. Note: The Windows sessions takes a couple of minutes to initialize and the controller will see a blank desktop until the initialisation is complete. A dialogue will inform the controller that the session is being reset and it may take a few minutes. Using a server property ----------------------- The property workaround.rdp.console.w2k3 in trc.properties can be configured to apply to all targets groups. To configure the workaround globally, for all target groups complete the folowing steps: 1) Logon to TRC with a valid admin ID and password. 2) Select Admin > Edit properties file. 3) Select trc.properties. 4) Set the required value the for the workaround.rdp.console.w2k3 property 0 - The workaround is disabled (default value) 1 - Reset the session automatically when a TRC session is started 2 - Reset the session automatically when the Remote Desktop user logs out. 5) Click Submit. Note: The default value is "0" Applying to a target group -------------------------- An attribute has been introduced for target groups which you can configure when creating or editing a target group by selecting "Automatically reset the console after a Remote Desktop console session". To configure the workaround for specific target groups: 1) Logon to TRC with a valid admin ID and password. 2) Select All Target Groups and tick the group you want to configure, then click on Edit Group. 3) Select the required value the for the "Automatically reset the console after a Remote Desktop console session" attribute from the drop down menu. Never - The workaround is disabled At session start - Reset the session automatically when a TRC session is started After console is logged out - Reset the session automatically when the Remote Desktop user logs out. 5) Click Submit. Note: The default value is "Not set". You can also set the attribute on the New Target Group screen when creating a target group. Note: If both the server property and target group attribute is set to different values the target group value will take precedence over the server value for those targets who are members of the specific target group. If a target belongs to more than one target group with different values for this attribute, the higher value takes precedence. For example: If a target belongs to groups A and B and the value of this attribute is 1 (reset at session start up) for group A and 2 for group B (reset automatically after the Remote Desktop user logs out), the final value that will be applied to any sessions with this target will be 2. If a Remote Desktop session (admin or console) is actually in progress when the controller attempts to connect to a target, a dialogue has been introduced that will inform the controller of the situation and provide details of the Remote Desktop user and the ip address/computer name the session is running from. Warning: The workaround is defined through a target group attribute and not a policy, therefore, if you start a session immediately after changing the setting, it may not have updated in the target yet. ===================================================================== 4.0 Installation information Note: There are new properties introduced in the properties files therefore you should backup your existing property files before installing the fix pack. After completing the fix pack installation and confirming that 5.1.2.1108 is installed,edit the new trc.properties, common.properties and ldap.properties files and update them with the values in your saved files. 4.1 Tivoli Remote Control 5.1.2 Windows, Derby Database and eWAS Server Installation 1)Unzip TRC_Disk_1_v512.zip and navigate to trc_server_setup.exe. 2)Run trc_server_setup.exe. 3)Follow the on screen instructions to install the fix pack. 4)If more detailed information is required refer to the IBM Tivoli Remote Control infocenter at:- http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic /com.ibm.itrc.doc_5.1.2/welcome.htm In the left pane select the Installation Guide then Running an automated server install. 4.2 Tivoli Remote Control 5.1.2 LINUX, Derby Database and eWAS Server Installation 1) Untar TRC_Disk_2_v512.tar and navigate to trc_server_setup.bin. 2) Run trc_server_setup.bin. 3) Follow on the screen instructions to install the fix pack. 4)If more detailed information is required refer to the IBM Tivoli Remote Control infocenter at:- http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic /com.ibm.itrc.doc_5.1.2/welcome.htm In the left pane select the Installation Guide then Running an automated server install. 4.3 Manual Installation If you are using Disk 3 to perform a manual installation of this release, please note:- A manual installation can only be performed on a system that has the previous release of IBM Tivoli Remote Control already installed. 4.3.1 Tivoli Remote Control 5.1.2 Websphere Application Server (WAS), AIX, Linux, Solaris and Windows Server Installation IMPORTANT *************************************************************************** Please back up your video recordings and customised properties files *************************************************************************** 1) Backup the following property files:- common.properties ldap.properties trc.properties log4j.properties These files are found in the following directory For Windows based systems: [TRCInstallDir]\TRCAPP.ear\trc.war\WEB-INF\classes\ For UNIX based systems [TRCInstallDir]/TRCAPP.ear/trc.war/WEB-INF/classes/ Where TRCInstallDir is the IBM Tivoli Remote Control installation directory. The video recordings folder is defined in the rc.recording.directory property in the trc.properties file. 2) Untar TRC_Disk_3_v512.tar and navigate to \Disk1\InstData\[platform]\VM where [platform] is relevant to your operating system : For example : \Disk1\InstData\windows\VM AIX : Run trc_additional_setup.bin Linux : Run trc_additional_setup.bin Solaris: Run trc_additional_setup.bin Windows: Run trc_additional_setup.exe For AIX/Linux and Solaris ------------------------- 1) Run trc_additional_setup.bin. ( InstallAnywhere will validate that you have the GA version installed or extracted.) 2) Follow the instructions in the IBM Tivoli Remote Control infocenter for extracting the server installation media at http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic /com.ibm.itrc.doc_5.1.2/trc-install122.htm#addinstall The new War file will be saved to a place of your choice or the InstallAnywhere default location. 3) Use the WAS Administrative Console to update the war file. 4) There are new properties introduced in the trc.properties file and the LDAP.properties file. After completing the update and confirming that 5.1.2.1108 is installed, edit the new trc.properties and ldap.properties files and update them with the values in your saved files. 5) Restore your other saved properties files and video recordings. For Windows ----------- 1) Run trc_additional_setup.exe ( InstallAnywhere will validate that you have the GA version installed or extracted.) 2) Follow the instructions in the IBM Tivoli Remote Control infocenter for extracting the server installation media at http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic /com.ibm.itrc.doc_5.1.2/trc-install122.htm#addinstall The new War file will be saved to a place of your choice or the InstallAnywhere default location. 3) Use the WAS Administrative Console to update the war file. 4) There are new properties introduced in the trc.properties file and the LDAP.properties file. After completing the update and confirming that 5.1.2.1108 is installed, edit the new trc.properties and ldap.properties files and update them with the values in your saved files. 5) Restore your other saved properties files and video recordings. 4.4 Target requirements ------------------- Detailed Hardware and Software requirements can be found at: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic= /com.ibm.itrc.doc_5.1.2/trc-install24.htm 4.5 Admin id for manual AIX install ------------------------------------- After a manual install of the IBM Tivoli Remote Control Server on an AIX system, the default admin id and password should be typed in camel case as follows id = Admin password = password 4.6 Installing the fix pack after installing the GA Level (5.1.2.1080) ------------------------------------------------------------------------ If you are installing the fix pack immediately after installing the GA Level (5.1.2.1080), logon to the GA Level application after it has installed to ensure that the database initialisation has completed before applying the fix pack . ===================================================================== 5.0 Uninstallation information To uninstall this interim fix complete the following steps:- * backup and save your properties files These files are found in the following directory for windows based systems [TRCInstallDir]\TRCAPP.ear\trc.warWEB-INF\classes\ for UNIX based systems [TRCInstallDir]/TRCAPP.ear/trc.warWEB-INF/classes/ where TRCInstallDir is the IBM Tivoli Remote Control installation directory * backup your database - Derby database save a copy of the database by taking a copy of the following directory [TRCInstallDir]\DB\TRCDB - windows systems [TRCInstallDir]/DB/TRCDB - UNIX based systems - All other databases follow the standard procedure for backing up the database * Uninstall the IBM Tivoli Remote Control Server To uninstall the Server complete one of the following steps - Add/Remove programs Uninstall Tivoli Remote Control 5.1.2 - Running the uninstall application Run the file 'Uninstall Tivoli Remote Control.exe' which can be found in the IBM Tivoli Remote Control installation directory * Install the previous version of IBM Tivoli Remote Control For installation instructions go to the following site http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic /com.ibm.itrc.doc_5.1.2/welcome.htm In the left pane select Installation Guide * Stop the IBM Tivoli Remote Control service * Restore your properties files and database * Start the IBM Tivoli Remote Control Service ===================================================================== 6.0 Contacting IBM Support Additional help or information can be found at the following Web sites http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic= /com.ibm.itrc.doc_5.1.2/welcome.htm http://www.ibm.com/software/sysmgmt/products/support/ ===================================================================== 7.0 Notices and trademarks Appendix. 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. 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 that has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 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. Customers are responsible for ensuring their own compliance with various laws such as the Graham-Leach-Bliley Act, the Sarbanes-Oxley Act, and the Health Insurance Portability and Accountability Act. It is the customer's sole responsibility to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws that may affect the customer's business and any actions the customer may need to take to comply with such laws. IBM does not provide legal, accounting or auditing advice, or represent or warrant that its products or services will ensure that customer is in compliance with any law. 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. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. 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. A.1 Trademarks The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: AIX DB2 IBM IBM logo iSeries pSeries Tivoli Tivoli logo xSeries zSeries Java(TM) and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT(R), and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. UNIX(R) 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.