IBM(R) DB2(R) Test Database Generator for Multiplatforms Version 2.2 FP 2 README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation Program 1.2 Language Support 1.3 Corrected known problems 1.4 Enhancements 2.0 PREREQUISITES 2.1 Hardware Requirements 2.1.1 Server hardware requirements 2.1.2 Java client hardware requirements 2.2 Software Requirements 2.2.1 Server software requirements 2.2.1.1 Windows specific software requirements 2.2.1.2 UNIX and LINUX specific software requirements 2.2.1.3 Optional Software 2.2.2 Java Client software requirements 2.3 Help system prerequisites 3.0 INSTALLATION INSTRUCTIONS 3.1 Installing the DB2 Test Database Generator Server 3.2 Installing the DB2 Test Database Generator Client 4.0 RESTRICTIONS 5.0 CORRECTIONS TO DOCUMENTATION 6.0 HOW TO GET HELP 7.0 NOTICES 7.1 Use of Evaluation Program 7.2 Trademarks and service marks 1.0 ABOUT THIS README FILE Welcome to the IBM DB2 Test Database Generator, Version 2.2 FP2 README file. This file contains information about DB2 Test Database Generator Version 2.2 FP2. DB2 Test Database Generator has been tested and validated with all supported releases of DB2 Universal Database Version 8 through Version 9. Subsequent releases might require additional maintenance. 1.1 Evaluation Program If you are using an evaluation version of the program, it enables you to try this product for a period of 60 days. After 60-days, you must purchase a license to continue to use the product. For information on license enforcement please see the DB2 Test Database Generator User's Guide. Read NOTICES Section 7.1, Use of Evaluation program and the License Agreement provided with your evaluation copy of the program. 1.2 Language support DB2 Test Database Generator is a translated product that supports the following languages: English, Japanese, Korean, Russian, Simplified Chinese, and Traditional Chinese. The product will select the appropriate language according to the system locale definition. The default language is English. 1.3 Corrected known problems The following known problems were corrected for Version 2 Release 2 Fix Pack 2: - PK35334 & PK37861: DB2 Test Database Generator client fails to populate Locations list if there is an improperly catalogued database node. - PK37442: Using sample group set table(s) not related with RI, with WHERE clause added to the seed table results in error SQL0104N. - PK37861: griServerAdmin.sh generates "no rsjndb2api file in library path" message. - PK38291: JAVA.LANG.UNSATISFIEDLINK ERROR: CAN'T FIND LIBRARY RSJNDB2API (RSJNDB2API.DLL) when running the TDBG ADMINISTRATOR SERVER 1.4 Enhancements The following enhancements were added for Version 2 Release 2 Fix Pack 2: - Added DB2 V9 support. - Added feature to invoke DB2 Table Editor from DB2 Test Database Generator. - Added support for ROWID. - Added support for sequence data types. - Added variable support to transformation rules. - Added support for XML column type. - Added support for XML column as a source. - Added support for identity columns. - Added skip locked rows feature. - Added secondary AUTHID support - Added support to allow empty sources. - Added support for BIGINT and DECFLOAT data types. - Added support for hidden columns. - Enhancement for exception handling on error message "No Locations Are Available. Check Server Setup." when missing a license file. - Added message on Server Administrator to reflect necessary database administrator authority. - Test Database Generator 2.2 MP Client - triggers rebuild of HELP Search Index - Upgraded workstation Java SDK/JRE to support the US Daylight Savings Time changes in 2007 on the DB2 Test Database Generator Version 2.2 FP2 Multiplatforms Windows client. 2.0 PREREQUISITES DB2 Test Database Generator has hardware and software requirements. 2.1 Hardware Requirements 2.1.1 Server hardware requirements DB2 Test Database Generator requires the same hardware that is required to install DB2 Version 8 Fix Pack 7, along with sufficient disk space to store data generated by DB2 Test Database Generator. The disk space that is required will vary depending on the amount and type of test data that you are generating. 2.1.2 Java Client hardware requirements - Minimum 70 MB free disk space - A network connection - The resolution on your monitor set to 800 x 600 at a minimum 2.2 Software requirements 2.2.1 Server software requirements 2.2.1.1 Windows specific software requirements - One of the following operating systems: - Windows 2000 - Windows 2003 - Windows XP - IBM DB2 Universal Database for Windows Version 8 Fix Pack 7 or higher for Windows (2000/XP) - Java stored procedures must be configured. Requirement: You must configure DB2 to use the appropriate JDK for your environment. DB2 Test Database Generator supports the JDK versions that are supported by IBM DB2 Universal Database for Windows Version 8 Fix Pack 7 or higher for Windows (2000/XP). More information on the JDK versions that are supported by DB2 is available at the following URLs (which were current at the time that this file was written): http://www.ibm.com/software/data/db2/udb/ad/v8/java/ In order to run Java stored procedures, you must update the DB2 database manager configuration on the machine on which the DB2 Test Database Generator server will reside to include the path where the JDK is installed. You can do this by typing the following DB2 commands: db2 update dbm cfg using JDK_PATH Ensure that you install the most recent update of the supported version of the JDK listed at the above URLs. You can check the DB2 database manager configuration to verify that the value for the JDK_PATH by entering the following command on the server: db2 get dbm cfg - The Java Virtual Machine (JVM) heap size must be set to at least 2048. You must set the Java Virtual Machine (JVM) heap size to at least 2048. You can set the JVM heap size using the following command: DB2 UPDATE DBM CFG USING JAVA_HEAP_SZ 2048 2.2.1.2 UNIX and Linux specific software requirements - One of the following operating systems: - AIX 5L V 5.2 - AIX 5L V 5.3 - 32-bit Linux for xSeries - 64-bit Linux for zSeries - 64-bit Linux for pSeries. - Solaris V 5.8 - Solaris V 5.9 - Solaris V 5.10 - During installation you must have X-Windows running. The DB2 Test Database Generator Server does not have a console-mode method of installation. - (Linux on Power PC and Linux on S/390 only): If invoking the griServerAdmin.sh and the list of DATABASES is empty, the user needs to manually create links to the correct version of librsjndb2api.so. To manually create these links: -For 64-bit DB2 instances: ln -sf /opt/IBM/DB2TOOLS/TestDatabaseGenerator2.2/lib/64bit/ librsjndb2api.so [path/to/db2]/lib/librsjndb2api.so -For 32-bit DB2 instances: ln -sf /opt/IBM/DB2TOOLS/TestDatabaseGenerator2.2/lib/32bit/ librsjndb2api.so [path/to/db2]/lib/librsjndb2api.so where [path/to/db2] is the path to the DB2 install directory. - IBM DB2 Universal Database Version 8 Fix Pack 7 or higher for the UNIX platform on which you are working (AIX, Linux, or Solaris) Restriction: When working on 64 bit AIX or Solaris, it is recommended that you work with DB2 V8 Fix pack 7 or higher. When working with DB2 V8 Fix Pack 7, 8, or 9 ensure that the file db2jarsp is present in your DB2 install location. If not, contact DB2 support to get this file. - Java stored procedures must be configured. Requirement: You must configure DB2 to support Java stored procedures. If you do not have the JDK that is supported by your version of DB2 Universal Database, DB2 Test Database Generator will not function properly. Information on the JDK vendors and versions that are supported by DB2 is available at the following URL (which was current at the time that this book was written): http://www.ibm.com/software/data/db2/udb/ad/v8/java/ Ensure that you install the most recent update of the supported version of the JDK listed at the above URL. In order to run Java stored procedures, you must update the DB2 database manager configuration on the machine on which the DB2 Test Database Generator server will reside to include the path where the JDK is installed. You can do this by typing the following DB2 commands: db2 update dbm cfg using JDK_PATH full_path_to_directory_where_JDK_is_located You can check the DB2 database manager configuration to verify that the value for the JDK_PATH by entering the following command on the server: db2 get dbm cfg - The Java Virtual Machine (JVM) heap size must be set to at least 2048. You must set the Java Virtual Machine (JVM) heap size to at least 2048. You can set the JVM heap size using the following command: DB2 UPDATE DBM CFG USING JAVA_HEAP_SZ 2048 2.2.1.3 Optional Software If you want to use the Referential integrity features available with DB2 Test Database Generator, you must install the DB2 Grouper component version 1.1. Be sure to apply the latest DB2 Grouper Fix Pack which can be obtained at this website: http://www-1.ibm.com/support/docview.wss?rs=434&uid=swg27008647 The DB2 Grouper component has software and hardware requirements associated with it. If you choose to use the DB2 Grouper component, refer to the DB2 Grouper component User’s Guide and follow the requirements specified there. In order to use the optional DB2 Table Editor features released in this fix pack, you must install DB2 Table Editor Version 4.3 Fix Pack 9 before the DB2 Test Database Generator client is installed. 2.2.2 Java Client software requirements In order to run the DB2 Test Database Generator client, you must have the following software installed and running on your machine: - IBM DB2 JDBC Driver V 2.0 - DB2 Universal Database for Windows DB2 Connect (to enable connections to remote databases) V8 Fix Pack 7 or higher. - Windows 2000 or Windows XP 2.3 Help system prerequisites Eclipse-based help system: If you have previously installed an Eclipse-based help system with an IBM tool, you must complete the following steps before installing the DB2 Test Database Generator client: 1. Locate the Eclipse301 folder on your system. The default location for this folder is: C:\Program Files\IBM\DB2TOOLS\eclipse301. If you do not have an Eclipse301 folder on your machine, proceed with the installation of the DB2 Test Database Generator client as described in section 3.0 of this document. 2. When you have located the Eclipse301, issue the following command: ...\IBM\DB2TOOLS\Eclipse301\ibm_help\help_end.bat 3. Remove all files under ...\Eclipse301\ibm_help\eclipse\configuration, except config.ini. 4. Install the DB2 Test Database Generator client as described in section 3.0 of this document. 3.0 INSTALLATION INSTRUCTIONS 3.1 Installing the DB2 Test Database Generator Server There are two parts to the DB2 Test Database Generator Server installation. You must install the DB2 Test Database Generator Server component and the DB2 Test Database Generator Server Administrator component. This section describes how to install the DB2 Test Database Generator multiplatform server. You can install the DB2 Test Database Generator server at more than one DB2 location if desired, provided that you have the necessary licenses. Information: When installing on Windows, the JVM V 1.5.0 is installed as part of the DB2 Test Database Generator Windows server installation process. This JVM is a shared DB2 Tools component and is used by DB2 Test Database Generator. It is not used by DB2 to run java stored procedures. To install the DB2 Test Database Generator server: 1. Ensure that you are running the version of the JDK that is appropriate to your environment and that Java stored procedures are enabled on the DB2 database where you are installing the DB2 Test Database Generator server. For more information on JDK requirements, see the section "Server software requirements". 2. Ensure that you have the necessary authority to install the Server component on your computer. * If you are installing on UNIX or LINUX, you must be logged in as Root. * If you are installing on Windows, the UserID that you are using must have Database Administrator privileges. 3. Run the install file that corresponds to your platform: AIX: TDBG_2.2_FP2_srv_aix.bin Linux for xSeries TDBG_2.2_FP2_srv_xLinux.bin Linux on Power PC: TDBG_2.2_FP2_srv_pLinux.sh Linux on S/390 TDBG_2.2_FP2_srv_zLinux.sh Solaris TDBG_2.2_FP2_srv_solaris.bin Windows TDBG_2.2_FP2_srv_win32.exe For example, on AIX, copy the TDBG_2.2_FP2_srv_aix.bin file to a temporary directory on the machine where you want to install the DB2 Test Database Generator server, and run the following command: ./TDBG_2.2_FP2_srv_aix.bin This install file installs the Server component of the DB2 Test Database Generator server. 4. Follow the instructions on the InstallShield windows. During this process you will specify the serverPath, userPath, and DB2 install directories. * The serverPath specifies the location where the DB2 Test Database Generator server is installed. This directory exists on the machine where files associated with the DB2 Test Database Generator server are installed. Information: The serverPath directory path cannot contain any DBCS characters. * The userPath specifies the location where data profiles are stored. This directory exists on the machine where the DB2 Test Database Generator server is installed. Note: You must have read, write, and execute permissions for this directory. * The DB2 install directory is the directory where DB2 is installed. Note: (UNIX and LINUX only): The Installshield installer creates a symbolic link in the DB2 library directory which points to the appropriate librsjndb2api.so file in the Test Database Generator library directory. These links can be created manually using the following commands: For 64-bit systems: ln -s /opt/IBM/DB2TOOLS/TestDatabaseGenerator2.2/lib/64bit/ librsjndb2api.so [path/to/db2]/lib64/librsjndb2api.so For 32-bit systems: ln -s /opt/IBM/DB2TOOLS/TestDatabaseGenerator2.2/lib/32bit/ librsjndb2api.so [path/to/db2]/lib/librsjndb2api.so Where [path/to/db2] is the path to the DB2 install directory. 5. When you have specified all of the requested information on the InstallShield panels, click Finish. The InstallShield installer closes. 6. Install the DB2 Test Database Generator server on your local DB2 database by using the DB2 Test Database Generator Server Administrator component. a. Launch the DB2 Test Database Generator Server Administrator. - If you are installing the DB2 Test Database Generator server on Windows, select Start --> Programs --> IBM DB2 Test Database Generator --> Server --> Server Administrator. - If you are installing the DB2 Test Database Generator server on UNIX, log on as the DB2 instance owner for the database where you are installing the DB2 Test Database Generator server and run: serverPath/griServerAdmin.sh where serverPath is the location where the DB2 Test Database Generator is installed. The default serverPath is: /opt/IBM/DB2TOOLS/TestDatabaseGenerator An InstallShield installer is launched. b. Follow the instructions on the InstallShield windows. Note: The User ID and password that the Server Administrator asks for must have database administrator authorities. Tip: You can install the DB2 Test Database Generator server on multiple local DB2 databases at the same time. This step can be repeated for each local database on which you want to install the DB2 Test Database Generator server. 7. Stop and re-start the DB2 Instance where the DB2 Test Database Generator server is installed. Connect to the database on which the DB2 Test Database Generator server is installed. 8. Catalog the database locations that you want the DB2 Test Database Generator client to connect to. When working with a Type 2 JDBC driver, it is necessary to catalog any databases that you want the DB2 Test Database Generator client to connect to. Use the DB2 Configuration Assistant to catalog databases. For more information on cataloguing databases with the DB2 Configuration Assistant, see the IBM DB2 documentation. Note: It is not necessary to catalog database locations when you are working with a Type 4 JDBC driver. 9. Populate the SYSTOOLS.GRI_LOCATIONS table on the database(s) on which the DB2 Test Database Generator server is installed, with the locations that you want to be able to connect to when you are using the DB2 Test Database Generator Java client. You can populate the GRI_LOCATIONS table manually when working with Multiplatforms or z/OS databases, or with the stored procedure GRI.LOCATIONDB2POPULATE that is included with DB2 Test Database Generator when working with Multiplatforms databases: - The stored procedure GRI.LOCATIONDB2POPULATE can be used to populate the GRI_LOCATIONS table on Multiplatforms. For more information on running stored procedures in DB2, see the IBM DB2 documentation. To populate GRI_LOCATIONS using the stored procedure: a. Open the DB2 command window (in Windows) or the DB2 command prompt (in AIX, UNIX, or LINUX). b. Run the GRI.LOCATIONDB2POPULATE stored procedure. This stored procedure reads information about the databases cataloged on the DB2 instance in order to build populate the locations table. The first argument, DRIVERTYPE, indicates the driver type that the locations will be configured to use. The following syntax is used to call the stored procedure: – For a type 2 driver: call GRI.LOCATIONDB2POPULATE(’2’, ?) – For a type 4 driver: call GRI.LOCATIONDB2POPULATE(’4’, ?) Note: If a type 4 driver is specified, the results that are placed in SYSTOOLS.GRI_LOCATIONS will be a best estimate, as the DB2 API does not provide platform information to allow detection of the node or database name. c. Open the SYSTOOLS.GRI_LOCATIONS table to review the results and ensure that the location information is correct. The SYSTOOLS.GRI_LOCATIONS table is located in the database where the DB2 Test Database Generator server is installed. d. Set the PUBLISH column of the SYSTOOLS.GRI_LOCATIONS table to 1. All of the locations that you want to appear in the location list in the DB2 Test Database Generator clients must have the PUBLISH column set to 1. - Alternatively, when you are working with Multiplatforms or z/OS databases, you can manually populate the SYSTOOLS.GRI_LOCATIONS table. The SYSTOOLS.GRI_LOCATIONS table is located in the database where the DB2 Test Database Generator server is installed. For more information on populating tables, see the IBM DB2 documentation. Populate the SYSTOOLS.GRI_LOCATIONS table as follows: – Specify the name of the location in the LOCATION column. Note: When you are working with The DB2 Test Database Generator Server on Multiplatforms and cataloging a DB2 for z/OS database in the SYSTOOLS.GRI_LOCATIONS table, the Location name that you use in the SYSTOOLS.GRI_LOCATIONS table must be the same as the name of the database location on your DB2 for z/OS database. – Specify the vendor of the location in the VENDOR column. – Specify the location driver in the DRIVER column. – Specify the location URL in the URL column. – Specify 1 in the PUBLISH column. Commit the updates and close the SYSTOOLS.GRI_LOCATIONS table. 10. Optional: Install the DB2 Grouper component. To simplify the process of locating related tables while you are defining test databases, you can use the DB2 Grouper component from within DB2 Test Database Generator. To install and configure the DB2 Grouper component, see the DB2 Grouper component User’s Guide. Before you can begin using DB2 Test Database Generator, you must install the DB2 Test Database Generator Java client. 3.2 Installing the DB2 Test Database Generator Client This section describes how to install DB2 Test Database Generator Java client. To install DB2 Test Database Generator Java client: 1. On the DB2 Test Database Generator distribution media, locate: TDBG_2.2_FP2_cli_win32.exe 2. Run TDBG_2.2_FP2_cli_win32.exe 3. Follow the instructions on the Install Shield windows. Note: During installation, you specify where (in which directory) you want DB2 Test Database Generator to be installed on your machine. The location you choose to install DB2 Test Database Generator is referred to as the installRoot. The installRoot directory cannot contain any DBCS characters in the directory path. You can now begin using DB2 Test Database Generator. For more information on working with the DB2 Test Database Generator Java client, see the online help and “Using the DB2 Test Database Generator Java client,” in the DB2 Test Database Generator User's Guide. Information: When installing on Windows, the Java Virtual Machine 1.5.0 is installed as part of the DB2 Test Database Generator Windows client installation. This Java Virtual Machine is a shared DB2 Tools component and is used by the DB2 Test Database Generator Java client. 4.0 Restrictions - (LINUX on S-39 (zLinux) and Linx on Power PC (pLinux) only): If invoking the griServerAdmin.sh, and the list of DATABASES is empty, the user needs to manually create links to the correct version of librsjndb2api.so. Solution: Manually create links to the correct version of librsjndb2api.so. For 64-bit DB2 instances: ln -sf /opt/IBM/DB2TOOLS/TestDatabaseGenerator2.2/lib/64bit/ librsjndb2api.so [path/to/db2]/lib/librsjndb2api.so For 32-bit DB2 instances: ln -sf /opt/IBM/DB2TOOLS/TestDatabaseGenerator2.2/lib/32bit/ librsjndb2api.so [path/to/db2]/lib/librsjndb2api.so where [path/to/db2] is the path to the DB2 install directory. - Symptom: DB2 Test Database Generator Help doesn’t work with Internet Explorer Verstion 7 or Firefox Version 2.0. Solution: Set Internet Explorer Version 6 or Firefox Version 1.5 as your default browser - Symptom: During installation and usage of the DB2 Test Database Generator Java client, error messages similar to the following may appear in the console window that is associated with running the Java client. MsgMgr: loadFromResourceBundle Can't find bundle for base name com.rocketsoftware.ismp.tdbg.EmptyInputFieldValidatorx, locale en Solution: These error messages do not represent a problem and can be ignored. No action is necessary. - Symptom: Uninstalling the DB2 Test Database Generator Java Client fails to complete when using uninstaller.exe or when using the Windows Add or Remove Programs functionality. It may be necessary to stop the uninstallation process using the Windows Task Manager. Explanation: The DB2 Test Database Generator Java Client cannot be uninstalled using uninstaller.exe or by using the Windows Add or Remove Programs functionality. Solution: To uninstall the DB2 Test Database Generator Java Client, double click uninstall.jar. The uninstall.jar file can be found in the DB2 Test Database Generator Java Client install directory: \client\_uninst\uninstall.jar The default install directory is: C:\Program Files\IBM\DB2TOOLS\TestDatabaseGenerator2.2\client\_uninst\uninstall.jar If double-clicking uninstall.jar does not cause it to run: 1. Open a command prompt window. 2. From the command prompt, navigate to the directory where uninstall.jar resides. 3. Issue the following command: java -cp uninstall.jar run - The following error can occur when connecting to remote DB2 Test Database Generator 2.2 Server that is installed on Linux for pSeries: "TDBG Server not properly licensed for operation" This problem is under investigation. The following work-around can be used until a permanent solution is found: 1. Check to see if your license is properly installed. If not, install the license properly, if it is properly installed, go to step 2. 2. Restart DB2 on the Linux for pSeries platform. Note: In order to continue to use DB2 Test Database Generator, you must restart DB2, however, other DB2 processes are unaffected, so you can restart DB2 at your convenience. If you encounter this problem, please open a PMR with IBM service. - When installing DB2 Test Database Generator, no DBCS characters can be used in the path to the directory where DB2 Test Database Generator is being installed. 5.0 Corrections to the Documentation To obtain the latest refresh of DB2 Test Database Generator publications refer to: http://www.ibm.com/software/data/db2imstools/db2tools-library.html 6.0 How to Get Help For a complete and up-to-date source of Test Database Generator information, including information on issues discovered after this README was published, go the following Web site: DB2 Test Database Generator Online Support: http://www.ibm.com/software/data/db2imstools/support.html If you are not able to find your answer searching the listed URL, call 1-800-IBM-SERV to speak to an IBM representative for assistance. 7.0 NOTICES This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10594-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 publication 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 as your own risk. Licensees of this program who want 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 J74/G4 555 Bailey Avenue San Jose, CA 95141-1003 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 information 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 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. 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 illustrates 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. 7.1 Use of Evaluation Program If you are using an evaluation copy of the program, the following terms apply: This program contains a disabling device that will prevent it from being used upon expiration of this license. You will not tamper with this disabling device or program. You should take precautions to avoid any loss of data that might result when the program can no longer be used. See the License Agreement terms that apply to the use of evaluation code. 7.2 Trademarks and service marks The following terms are trademarks or service marks of the IBM Corporation in the United States or other countries or both: DB2 IBM z/OS Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows XP, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. (C) Copyright IBM Corporation 2003, 2006; Copyright Rocket Software, Inc., 2003.2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.