IBM(R) DB2(R) Performance Expert for Multiplatforms, V1 R1 IBM DB2 Performance Expert for Workgroups, V1 R1 IBM DB2 Performance Expert for z/OS, V1 R1 IBM DB2 Performance Monitor for z/OS - Workstation Online Monitor V7 and V6 IBM DB2 Buffer Pool Analyzer for z/OS, V1 R2 Fix Pack 9, README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Corrected known problems 1.3 Known problems and workarounds 2.0 PREREQUISITES 2.1 Hardware requirements 2.2 Software requirements 3.0 INSTALLATION INSTRUCTIONS 3.1 General notes 3.2 UNIX(TM)-specific installation information 3.2.1 Fix pack installation for Performance Expert Server 3.2.2 Using Extended Shared Memory on AIX 32-bit systems 3.2.3 Configuration of Performance Expert Server 3.3 Windows-specific installation information 3.3.1 Fix pack installation for Performance Expert Server 3.3.2 Fix pack installation for Performance Expert Agent 4.0 CUSTOMIZATION INSTRUCTIONS 4.1 Performance Expert Server on Red Hat Linux 5.0 RESTRICTIONS 5.1 Performance Expert 5.2 Workstation Online Monitor 5.3 Japanese version of Performance Expert 6.0 HOW TO GET HELP 7.0 NOTICES 7.1 Use of the evaluation program 7.2 Trademarks and service marks 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Performance Expert, Version 1 Release 1, Fix Pack 9, README file. This README file contains information about installing IBM DB2 Performance Expert. It is the most current README file as of 12/08/2003. In this README file, the following naming conventions apply: IBM DB2 Performance Expert for Multiplatforms, IBM DB2 Performance Expert for Workgroups, and IBM DB2 Performance Expert for z/OS are abbreviated to Performance Expert. When the name Performance Expert is used, DB2 Performance Monitor (DB2 PM) is included where applicable. 1.1 Evaluation code If you use evaluation code, the evaluation code 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. When you purchase the product, the license is enforced based upon the platform on which you run Performance Expert. Read NOTICES Section 7.1, Use of the evaluation program, and the License Agreement provided with your evaluation copy of the program. 1.2 Corrected known problems This fix pack corrects the following problems: - DB2 registry variable DB2_CORRELATED_PREDICATES not set correctly in db2pesrv-config script on UNIX. - Command 'db2 force application all' called from script db2pesrv-config on UNIX. - Performance Warehouse processes cannot be scheduled between 12 p.m. and 11:59 p.m. - The DB2 instance that is used for Performance Expert Server must be configured on partition 0. After installing Fix Pack 9, any partition can be used for the Performance Expert Server DB2 instance. - Executing the db2pesrv-config script on Linux on zSeries fails if the JDK_PATH variable in the database manager configuration is not set correctly. - groupadd error when executing the db2pesrv-config script on Linux and the group used for Performance Expert is not defined. 1.2.1 Performance Expert for Multiplatforms - If you installed Performance Expert on AIX 32-bit systems, the configuration script set the DB2 configuration parameter EXTSHM=ON. On highly loaded systems, this might have caused paging I/Os. Performance Expert now provides the option to attach local databases like remote databases. This avoids the setting of EXTSHM=ON. For a detailed description of how to use Extended Shared Memory, refer to 3.2.2. Using Extended Shared Memory on AIX 32-bit systems. - The following APARs are solved with Fix Pack 9: PQ73668, If you select Statistic Details while using DB2 V8 PQ73712: Fix Pack 1, output for the monitored DB2 instance is not produced. PQ75411: View History Settings lets you enter date and time, but if you change one of these, an internal error occurs. PQ75896: If you log on to Performance Expert by using Performance Expert Client, message DGOK1456 is displayed. PQ78485: Performance Expert Server hang when connecting to Performance Expert Client. PQ78488: Starting Performance Expert by using the pestart command as root or as DB2inst * with fully qualified name does not work. PQ78490: Performance Expert Server stops if the following message is displayed: SQL1013N the database alias name or database "XXXXX" could not be found. SQLSTATE=42705. PQ78649: If you start Performance Expert on AIX and the lock list is greater than 70000, the SQL5066W database manager CFG parameter value for the token "SQLF" is truncated. PQ79019: Performance Expert shows an incorrect gateway snapshot time in the DCS Database window and in the Statistics window. PQ79073: If you select the Buffer Pool Analysis menu, an internal error occurs in Performance Expert. PQ72865: If Performance Expert is installed on DB2 EEE on AIX, Performance Expert Server does not stop but you must issue a DB2_KILL command. See also Info APAR IY42605. PQ79816: When Performance Expert Server for Multiplatforms is started, several misleading messages are displayed. 1.2.2 Performance Expert for z/OS - The following APARs are solved with Fix Pack 9: PQ68356: A thread termination error occurs in the Workstation Online Monitor. PQ77860: When you install Performance Expert Client on Windows 2000, the InstallShield error 5003 'Failed Install Kernel' occurs. PQ79751: If the GMT time is identical with the local time, the time value on the workstation GUI is incorrect. PQ79942: When you use Performance Expert and the Fix Pack 8 level L903, the History button is not active. Therefore, you cannot use the History slider. PQ80254: Performance Expert trace activation fails and the internal error 'Cannot find resource for bundle error message.' occurs. 1.2.3 Performance Monitor for z/OS - The following APARs are solved with Fix Pack 9: PQ70871: A thread termination error occurs in the Workstation Online Monitor. PQ78089: After you install the client code L904, the SQL statement is not displayed in the Thread Details window. 1.3 Known problems and workarounds - Problem: Hang situation in Performance Expert when using DB2 Version 8 Fix Pack 3. If Performance Expert is used to monitor DB2 instances based on DB2 Version 8 Fix Pack 3, and if Deadlock Exception Processing is activated, a hang occurs in Performance Expert. The Deadlock Exception Processing feature starts a deadlock event monitor on the DB2 server, which has a problem in DB2 Version 8 Fix Pack 3. The deadlock event monitor problem in DB2 Version 8 Fix Pack 3 causes the DB2 instance to hang. The instance cannot be stopped by using db2stop. It must be stopped by using, for example, db2_kill. The problem is addressed in DB2 APAR LI70239 and will be fixed in DB2 Version 8 Fix Pack 4. Workaround: Do not use the Deadlock Exception Processing feature when using DB2 Version 8 Fix Pack 3. - Problem: The Statistic Details window erroneously shows a negative value in the Buffer Pool 'Max. DB heap allocated' field. The problem is known to exist also in previous Fix Pack 8 and is currently under investigation. For the time being ignore this field. - Problem: After a Red Hat Linux machine is rebooted, Performance Expert Server on that system fails at first start. Workaround: Restart DB2, then restart Performance Expert Server. - If you issue the command DB2STOP FORCE or the command DB2 FORCE APPLICATIONS ALL on a system other than z/OS on which Performance Expert Server is installed, do the following: 1. Stop Performance Expert Server. 2. Do one of the following: - If you issued the command DB2STOP FORCE, restart DB2 by using the DB2START command. - If you issued the command DB2 FORCE APPLICATIONS ALL, wait until all applications are finished. 3. Restart Performance Expert Server. - Problem: On Windows, the following error message might be displayed during installation and configuration of a Performance Expert Server: "Error accessing the configuration file for database configuration (\bin\pe_temp.log). Without this configuration, Performance Expert Server might run inefficiently. Error: -1." Workaround: To ensure that Performance Expert Server runs efficiently, do the following after the installation and configuration is complete: 1. Open a DB2 CLP window. 2. Enter the following commands: DB2 CONNECT TO DB2PM DB2 UPDATE DB2PM.VERSION SET V_VALUE='U104-V110' WHERE V_FIELD LIKE 'DB2PM CODE%' DB2 CONNECT RESET 3. Stop and start Performance Expert Server. This causes Performance Expert Server to perform a database migration and optimization. - Problem: On Windows, the configuration of Performance Expert Server, or Performance Expert Server after the first start, or Performance Warehouse might hang because of a hanging DB2 process "db2syscs". Workaround: Reboot and redo the abended action. - On Linux on zSeries, the following error message might be displayed: "Errors occurred during the installation. - jvm "jvm" is not defined." Workaround: This implicates that no Uninstall directory is created. If you remove the program, you must remove the program files and the DB2PM database manually. - If you have Windows NT and DB2 Version 8 installed, Performance Expert Server does not run. - Problem: If Performance Expert Server runs on UNIX-based operating systems on which DB2 Version 7 Enterprise-Extended Edition (EEE) is installed, the Exception Processing function of Performance Expert might damage DB2 processes when you activate it. You must then stop DB2 by using the command DB2_KILL and restart DB2. Workaround: Do not activate the Exception Processing function in this environment. - In a DB2 EEE environment, functions based on event monitoring, such as SQL activity, buffer pool analysis, and Performance Warehouse, work only in a single partition environment for Fix Pack 9. - Problem: Rarely, Performance Expert Server abends after you start a Performance Warehouse process for the first time. An error message is displayed that Performance Expert Server is not running. Workaround: Restart Performance Expert Server. - Problem: If a DB2 Version 7 client connects to a DB2 Version 8 server, the following error message might be displayed: FRAMEWORK : SQLError : [IBM][CLI Driver][DB2/6000] SQL0551N "" does not have the privilege to perform operation "EXECUTE" on object "NULLID.SQLLF000". SQLSTATE=42501 Workaround: Enter the following commands on the DB2 Version 8 server: db2 connect to db2pm user using db2 bind @db2cli.lst blocking all grant public db2 grant execute on package nullid.sqllf000 to public db2 grant execute on package nullid.sqllf200 to public db2 grant execute on package nullid.sqllf400 to public For more information on this problem, refer to the DCF document (Technote) containing the following subject: "CLI Packages in DB2 V8.1". This document explains the changes in V8.1 regarding the CLI bind files and packages. - Problem: If a Performance Expert Client that monitors a Performance Expert Server on Linux on zSeries displays "N/P" values in the instance information in the Statistic Details window, restart Performance Expert Server. - Problem: A Performance Expert Client installed on DB2 Version 7 cannot connect to a Performance Expert Server installed on a 64-bit DB2 Version 8. Workaround: Use a Performance Expert Client that is installed on DB2 Version 8. -Problem: A Performance Expert Client installed on DB Version 8 cannot connect to a Performance Expert Server installed on a DB2 Version 7. Workaround: Use a Performance Expert Client that is installed on DB2 Version 7. For more information, refer to the DB2 connectivity matrix, which is located on the following Web site: http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support /v8infocenter.d2w/report?target=mainFrame&fn=r0009731.htm - Problem: When running an SQL Activity Tracing report from the Application Details window on Windows 2000, the report might fail and the following error message might be displayed: 'SQL086N A default table space could not be found with a page size of at least 4096 that authorization ID DB2PESERVER is authorized to use.' Workaround: In DB2, manually grant the use of this table space to the user DB2PESERVER. - If a DB2 Version 8 client cannot connect to a Performance Expert Server, enter the following bind commands on the DB2 Version 8 client: db2 connect to db2 bind @db2ubind.lst blocking all grant public - On UNIX-based operating systems note the following: If you are logged in as root, and if you stop Performance Expert Server by calling the script 'pestop', you are prompted for the process ID to be stopped. Ensure that you enter the correct process ID. Any process you specify is definitely killed. - If you use DB2 Version 8 and have configured a value greater than 70000 for LOCKLIST in your database configuration, 0 is shown in the appropriate 'Sytem Parameters' page in the Performance Expert GUI. - On Linux for S/390 no uninstall program exists to uninstall Performance Expert Server. To remove it manually, perform the following steps: 1. Remove the program files with: rm -fr /opt/IBM/db2pesrv.fp9 2. Delete the entries in the Linux Software database with: rpm -qa | grep -i db2pesrv_ | grep 1.1-9 | xargs rpm -a - Documentation error in "Installation and Customization", editions dated 2003 or earlier: Chapter "Installing Performance Expert Client on UNIX-based operating systems" erroneously lists Linux for S/390 as one of the UNIX-based operating systems. Installing Performance Expert Client on Linux for S/390 is not supported. The error will be corrected in future versions of "Installation and Customization". 2.0 PREREQUISITES Performance Expert has hardware and software requirements. 2.1 Hardware requirements Performance Expert for Multiplatforms has the following hardware requirements: - Memory and disk space sufficient to fulfill DB2 requirements. If you use Buffer Pool Analyzer for z/OS, you might need the maximum memory. - A minimum of 150 MB of free disk space. - Additional space for user data. This varies depending on the size of your databases and the amount of activity your system encounters. 2.2 Software requirements To use Performance Expert for Multiplatforms, you must have DB2 Version 7 Fix Pack 8 or later. Do not use DB2 Version 7 Fix Pack 7 because it might cause a hang of Performance Expert Client while waiting for a response of Performance Expert Server. On UNIX-based systems, Fix Pack 7 also forced users to locally connect to a Performance Expert Server. 3.0 INSTALLATION INSTRUCTIONS 3.1 General notes 1. If you plan to install Performance Expert Server for a DB2 UDB EEE configuration, install it only once. Select a partition of your choice and install it there. Note, however, that for Fix Pack 9 the functions based on event monitoring work only in a single partition environment. See also section 1.3 Known problems and workarounds. 2. Because you can install Performance Expert without installing DB2, consider the following: If DB2 is not installed, functions of Performance Expert regarding a multiplatform server or a Performance Warehouse cause an error. To enable these functions after installing the correct version of DB2, you must run the setup of Performance Expert Client again by using the Repair option. 3. Before you start installing the program, read "IBM DB2 Performance Expert for z/OS and Multiplatforms, Version 1 Release 1, Installation and Customization", SC27-1646. You can find this documentation also on the following Web site: http://www.ibm.com/software/data/db2imstools/library.html 4. If you upgrade from Fix Pack 8 to Fix Pack 9, it is recommended to stop Performance Expert Server before applying Fix Pack 9. Otherwise, certain functions of Performance Expert Client might not work as expected. If you apply Fix Pack 9 with Performance Expert running, and if you encounter such problems, restart Performance Expert. 5. Close all Performance Expert Agents and connections to Performance Expert Agent before installing Performance Expert Server. 6. Before you install Performance Expert Server, ensure that all DB2 instances to be monitored are started. 7. What to consider when you have DB2 Version 8 installed: - If Performance Expert Server is installed on a workstation that runs under DB2 Version 8, Performance Expert Client must be installed on a workstation that runs at least under DB2 Version 7 Fix Pack 8. - Performance Expert Clients running under DB2 Version 8 can connect only to Performance Expert Servers running under DB2 Version 8. 8. If you want to monitor DB2 on z/OS, ensure that the following PTFs are installed before you install this fix pack: For DB2 Performance Expert Version 1.1: - UQ80902 - UQ81175 - UQ82131 - UQ82777 For DB2 Performance Monitor Version 7.1: - UQ82132 For DB2 Performance Monitor Version 7.2: - UQ80902 - UQ81175 - UQ82131 - UQ82777 3.2 UNIX-specific installation information 3.2.1 Fix pack installation for Performance Expert Server Before you can install a fix pack, the base package of Performance Expert Server must be installed. Do not remove the installed version of Performance Expert. Instead, install the fix pack in a new directory. To install the fix pack: 1. Ensure that the fix pack installation file db2pesrv.fp.install-on- is executable. denotes the version of the fix pack. denotes your operating system. Example: db2persrv.fp9.install-on-aix. 2. Invoke the fix pack installation file. 3. When you are asked for the installation path, select /opt/IBM/db2pesrv.fp/V1.1 denotes the version of the fix pack. 4. After the installation of the fix pack completes successfully, you must copy the file nodelock from the directory /opt/IBM/db2persrv/V1.1/bin/nodelock to /opt/IBM/db2persrv.fp/V1.1/bin/nodelock denotes the version of the fix pack. 5. If Fix Pack 7 or Fix Pack 8 is not the actually installed fix pack, the InstallShield might not have removed Performance Expert properly. Remove the DB2PM database for each monitored instance manually with the following command: db2 drop db db2pm In addition, remove the old temporary files of Performance Expert Server with the following command: rm -fr /var/db2pe/ denotes the name of the DB2 instance. 6. Run the following configuration script for each DB2 instance that you want to monitor: /opt/IBM/db2persrv.fp/V1.1/adm/db2pesrv-config -i denotes the version of the fix pack. denotes the name of the instance where you want to run Performance Expert Server. The output is logged in the file /tmp/db2pesrv-config.log 3.2.2 Using Extended Shared Memory on AIX 32-bit systems During the installation you can now choose whether to use Extended Shared Memory (EXTSHM). If it is to be used, the environment variable EXTSHM is set to ON. The database is then started with this setting and can work with Extended Shared Memory. Important: Exception Processing requires that Extended Shared Memory (EXTSHM) is set to ON to avoid loss of data. However, on heavily loaded systems, this setting causes additional I/Os. Therefore, the following way is provided to set EXTSHM to OFF, but without loosing data for Exception Processing. For all databases for which you want to get Exception Processing data, perform the following steps: 1. During the installation, set the EXTSHM parameter to NO. When the configuration script shows the parameters for the DB2 instance, check the setting for EXTSHM and change it if necessary: Set EXTSHM=ON? (yes or no): [yes] - enter NO. 2. Catalog the local node, like a remote one, in the following way: a. Log on as DB2 instance owner. b. Enter the following command: db2 "catalog tcpip node remote 127.0.0.1 server " denotes the alias for the local node to be cataloged. must be identical to the database manager parameter SVCENAME. 3. Catalog each database for which you want to get Exception Processing in the following way: a. Log on as DB2 instance owner. b. Enter the following commands: db2 "catalog db as at node authentication server" denotes the name of the local node, as described in 2. denotes the local name of the database to be monitored. denotes the alias for the local database, but must not be identical to the name of the database. 4. Start Performance Expert Server by using the additional user ID parameter: ./pestart -n -u denotes the name of the local node, as described in 2. denotes the user ID that controls actions of Performance Expert Server regarding DB2. You should use the user ID of the instance owner. You are prompted for the password. 3.2.3 Configuration of Performance Expert Server To configure Performance Expert Server, perform these steps for each instance that you want to monitor: 1. Run the configuration script db2pesrv-config -i db2inst1 where 'db2inst1' is the DB2 instance user under which Performance Expert Server runs. You are asked to enter several parameters. These parameters determine: - Where the DB2PM database is stored. - The group that has access to this database. - Where trace and log files are stored. - Your Java Runtime environment for DB2. This is set in the DB2 environment variable JDK11_PATH on DB2 Version 7 or JDK_PATH on DB2 Version 8. 2. If DB2 environment variables are changed while you run this script, you are asked to invoke the following commands. These commands activate the DB2 environment variables and register the file fpesp.jar with your new Java Runtime environment setting: db2stop db2start /var/db2pe/db2inst1/peregjar.sh where '/var/db2pe' is your Performance Expert working directory as defined during the configuration. The script /var/db2pe/db2inst1/peregjar.sh tries to register the file fpesp.jar with your new Java Runtime environment setting. 3.3 Windows-specific installation information While installing the base or a fix pack of Performance Expert on Windows, the following error message might be displayed: 'Cannot find file layout.bin. Please insert disk ...' If this error message is displayed, do one of the following: - Restart Windows in the following way: Before you log on to the system, press the Shift key and keep it pressed while you log on. The system then starts without the autostart options. Then retry installing the base or the fix pack. - Delete all files in the InstallShield directory. On Windows, for example, this directory is located in: C:\Program Files\Common Files\InstallShield 3.3.1 Fix pack installation for Performance Expert Server Before you install a fix pack, the base package of Performance Expert Server must be installed. If it is not installed, the following error message is displayed: 'Could not start the DB2 Performance Expert Server (DB2) service on local computer.' Usually, the installation program performs the update automatically. If not, use the Repair option. This option repairs only program files of the Performance Expert Server installation. To repair the DB2PM database, reinstall Performance Expert Server. 3.3.2 Fix pack installation for Performance Expert Agent Usually, the installation program performs the update automatically. If not, use the Repair option. 4.0 CUSTOMIZATION INSTRUCTIONS For complete instructions on how to customize and use Performance Expert, refer to "IBM DB2 Performance Expert for z/OS and Multiplatforms, Version 1 Release 1, Installation and Customization". You can find this document on the following Web site: http://www.ibm.com/software/data/db2imstools/library.html If you install this image from CD-ROM, the documentation is located in the /doc directory. The User's Guide on the Web can contain updates to the publication on CD-ROM. 4.1 Performance Expert Server on Red Hat Linux Setting kernel parameters: To run DB2, you must set kernel parameters in the following way: 1. Display the kernel parameters by entering the following command: ipcs -l 2. Add the following lines to the file /etc/sysctl.conf: kernel.msgmni = 512 kernel.sem=250 128000 32 512 3. Activate the kernel parameters by entering the following command: sysctl -p 5.0 RESTRICTIONS 5.1 Performance Expert - Performance Expert Server needs the following database manager Configuration settings to deliver all required values to Performance Expert Client: JAVA_HEAP_SZ 2048 MON_HEAP_SZ 512 ASLHEAPSZ 30 QUERY_HEAP_SZ 2000 The configuration script checks how these parameters are set. If they are set to a value lower than the required value, the minimum values are set automatically. If you reset these parameters to a value lower than the required value, the results on Performance Expert Client might be incomplete or missing. - If you install Performance Expert Client on DB2 Version 8, you cannot connect to a Performance Expert Server that is installed on DB2 Version 7. - If you want to access a Performance Expert Server that is installed on a UNIX-based 64-bit instance, you must catalog the correspondent database alias as a DCS database. The following example shows how you can access the DB2PM database on Performance Expert Server by using the alias DB2PM64. db2 "catalog tcpip node PESRV64 remote 9.888.777.666 server 50064" db2 "catalog dcs database DCSDB2PM as DB2PM" db2 "catalog database DCSDB2PM as DB2PM64 at node PESRV64 authentication DCS" - If you install Performance Expert Server on a machine on which DB2 Version 8 for Intel Linux is installed, you must install Performance Expert Client also on a machine on which DB2 Version 8 is installed. Using Performance Expert Client on a machine on which DB2 Version 7 is installed causes Performance Expert Client to stop. - If you use Performance Expert for DB2 Version 8, and if there are connectivity problems between the DB2 client and server of this version, refer to "IBM DB2 Connectivity Supplement Version 8". - You might need to increase limits to handle too many database connections on Performance Expert. Event Exception Processing is, by default, activated by Performance Expert Server for all databases of the monitored DB2 instance. Thus, an additional connection is established for each database. It might be necessary to increase either or both of the following: - The maximum number of concurrent applications (maxappls) that can be connected to a database. - The maximum number of database manager agents (maxagents) available at any time to accept application requests. Alternatively, you can deactivate Event Exception Processing on Performance Expert Server and thus reduce the number of connections by switching it off within the Properties of the DB2 instance of Performance Expert Client. 5.2 Workstation Online Monitor - The following field contents might appear if a value is not available: N/C Not Calculated (If a division by zero would have happened) N/P Not Present (If DB2 did not deliver a value for the corresponding parameter) N/A Not Applicable (If this value does not make sense within the current context) - Launching Netscape as your HTML browser from Performance Expert Client might fail. In this case, start the browser separately. - Threshold sets that are used in Periodic Exception Processing cannot be imported from or exported to the host. Therefore, results from Exception Processing can be used only by Batch Exception Processing and ISPF-based Periodic Exception Processing. - For Performance Expert Server for Multiplatforms, Periodic Exception Processing is not available. Ignore the respective menus. - When you press the Interval button in the Statistics Details window, an internal error might occur and the following message is displayed: "...This snapshot store was released before..." Ignore this message, click Close, and then click Refresh. Interval processing works. - When the Data Collector or Performance Expert Server is restarted, Performance Expert Client might not reconnect. In this case, log off manually from the monitored DB2 subsystems or DB2 instances, then log on again. In some cases, you must restart Performance Expert Client. - When SQL activity traces for Multiplatforms are generated, several database connections are used. These connections are not released after the SQL activity trace. They are released only when you log off from the DB2 instance. 5.3 Japanese version of Performance Expert - You cannot use double-byte character set (DBCS) entries for Performance Warehouse functions and for the System Health window of the Workstation Online Monitor. - Performance Warehouse does not work with databases defined with CCSID 1390. It works, however, with databases defined with CCSID 500. 6.0 HOW TO GET HELP For complete and up-to-date source of Performance Expert information, including information on issues discovered after this README was published, go to the following Web site: Performance Expert 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. For fix packs to be installed before using the program, refer to the following Web site: http://www.ibm.com/software/data/db2imstools/support/fixpaks.html 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 character set (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 at 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. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. 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 IBM's application programming interfaces. 7.1 Use of the 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 for a complete explanation of the terms that apply. 7.2 Trademarks and service marks The following terms are trademarks or service marks of the IBM Corporation in the United States, other countries, or both: DB2 DB2 Universal Database IBM OS/390 z/OS Microsoft, Windows, Windows NT, 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. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others. (C) Copyright IBM Corporation 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.