Release Notes

Tivoli Data Warehouse Release Notes

Ve r s i o n 1.2

SC32-1399-00

Tivoli Data Warehouse Release Notes

Ve r s i o n 1.2

SC32-1399-00

Note Before using this information and the product it supports, read the information in “Notices,” on page 19.

Second Edition (December 2003) This edition applies to Tivoli Data Warehouse, Version 1.2 and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces GI11–0857–00. © Copyright International Business Machines Corporation 2002, 2003. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Chapter 1. About this release . . . . .1 Report interface problem ...... 11 New in this release ...... 1 Miscellaneous problems ...... 11 Product fix history ...... 1 Internationalization problems ...... 11 Backward compatibility...... 2 Product compatibility ...... 2 Chapter 4. Documentation updates . .13 Additional troubleshooting scenarios ...... 13 Chapter 2. Installation information . . .3 Upgrades from version 1.1 to version 1.2 . . . .14 Hardware requirements...... 3 Multiple customer environments ...... 14 Software requirements ...... 4 List commands ...... 14 Database requirements ...... 4 Messages ...... 15 Report interface requirements...... 6 Installation and upgrade notes ...... 6 Chapter 5. Contacting customer support ...... 17 Chapter 3. Known limitations, problems, and workarounds...... 9 Appendix. Notices ...... 19 Limitations ...... 9 Trademarks ...... 21 Known problems and workarounds ...... 10 Installation or uninstallation problems . . . .10

iv Release Notes

Chapter 1. About this release

This document provides important information about Tivoli® Data Warehouse, Version 1.2. This information is the most current information for the product and takes precedence over all other documentation. Read the information in this document before installing or using Tivoli Data Warehouse.

New in this release Tivoli Data Warehouse, Version 1.2 has the following new and changed features:

Note: Functionality is dependent upon features provided by individual warehouse enablement packs. v Improved ease of installation, upgrade, and uninstallation. v An installation registry that contains the location and connection information for each system in your deployment. This means that you do not have to provide connection information when installing a warehouse enablement pack, hereafter referred to as warehouse pack. v Support for viewing reports with Crystal Enterprise. v Support for multiple central data warehouse databases. v Support for multiple instances of an operational data source. A warehouse pack can extract operational data from multiple instances of the same data source. v For z/OS® systems, Tivoli Data Warehouse supports one central data warehouse and multiple data mart databases, one data mart per each DB2® location. v Capability to grow your deployment over time by adding central data warehouses and data marts after initial installation. v Warehouse packs are configured during installation. v New command utilities to expedite common DB2 procedures in the DB2 Data Warehouse Center. v Improved troubleshooting tools, logs, and message documentation in the new Tivoli Data Warehouse Messages, SC09-7776. v Bash after scripts are deprecated in this release and will not be available in future releases. Use Perl to create after scripts for warehouse packs.

Product fix history The following defects were fixed for Version 1.2 of Tivoli Data Warehouse: v APAR IY46244: During the installation of fix packs for warehouse packs, changes made in central data warehouse and data mart data definition language (DDL) and data manipulation language (DML) SQL scripts that are surrounded by delta-based tags to preserve information of earlier fix packs are no longer erased by the patching utility when two or more digits are used for fix pack version numbers. v APAR IY43104: In the DB2 Data Warehouse Center, the IBM® Tivoli Enterprise Console®, Version 3.8 warehouse pack process, ECO_c05_ETL1, step ECO_c05_s010_Extract, no longer fails with the following message: Disallowed implicit conversion from data type datetime to data type int

This was a spurious ODBC error that was produced by the execsql SQL execution engine program. v APAR IY34584: A failure no longer occurs during the operation of warehouse packs when they extract data from the central data warehouse and transform and load that data into data marts. The error information that was displayed or logged when this failure occurred might have indicated an attempt to find or retrieve an expired or nonexistent component or other database object.

Backward compatibility You can install warehouse packs for Version 1.1 on Tivoli Data Warehouse, Version 1.2. See Installing and Configuring Tivoli Data Warehouse, GC32-0744 for additional details.

Product compatibility Tivoli Data Warehouse, Version 1.2 works with IBM DB2 Universal Database™ Enterprise Edition, Version 7.2 and Crystal Enterprise 9.

For compatibility of warehouse packs with Tivoli Data Warehouse, Version 1.2, see the documentation for each applicable warehouse pack.

2 Release Notes

Chapter 2. Installation information

This chapter provides hardware and software requirements.

Note: If your systems do not meet the hardware and software requirements listed in this section, you might receive confusing error messages and have problems installing and using Tivoli Data Warehouse.

Hardware requirements This section provides information about the hardware requirements for installing Tivoli Data Warehouse.

See the planning chapter in Installing and Configuring Tivoli Data Warehouse for database sizing formulas and considerations.

As the warehouse pack for each Tivoli software product is added to the Tivoli Data Warehouse installation, additional hard disk space is required. See the documentation for each warehouse pack for application planning information and hard disk space requirements.

Table 1 lists the minimum and recommended hardware requirements for Tivoli Data Warehouse. Table 1. Hardware requirements Deployment Minimum Recommended Temporary hard type Component requirements size disk space v Quick start All 512 MB RAM v 1 GB RAM 1 GB v 1 GB hard disk v 3 GB hard disk space space v 933 MHz processor v Distributed Control server 512 MB RAM v 1 GB RAM 1 GB v 800 MB hard v 1 GB hard disk disk space space v 933 MHz processor v Central data 512 MB RAM v 1 GB RAM 1 GB warehouse v 10 GB hard v 20 GB hard disk disk space space v 933 MHz processor v Data mart 512 MB RAM v 1 GB RAM 1 GB v 1 GB hard disk v 3 GB hard disk space space v 933 MHz processor

Note: The quick start deployment is convenient for small installations; thus, it requires less space.

Software requirements This section provides information about the software requirements for Tivoli Data Warehouse.

The following table lists the operating systems supported by Tivoli Data Warehouse. Table 2. Supported operating systems Operating system Data Warehouse Control Central Data mart source1 agents server data warehouse Microsoft® Windows Yes Yes Yes Yes Yes NT®, service pack 6 or higher and Microsoft Data Access Components (MDAC) 2.7 service pack 1

Windows® 2000 Server, service pack 2 or higher

Windows 2000 Advanced Server, service pack 2 or higher

Windows Server 2003 IBM AIX®, Versions Yes Yes No Yes Yes 4.3.3, 5.1, and 5.2 Sun Solaris, Versions 2.8 Yes Yes No Yes Yes and 2.9 RedHat Linux, Versions Yes No No No No 7.2, 7.3, and Advanced Server 2.1 SuSE Linux, Versions 7.2, Yes No No No No 7.3, and 8.0 Turbo Linux 7 Yes No No No No z/OS, V1R2, V1R3, and Yes No No Yes Yes V1R4 1 Data source support is determined by ODBC support in DB2 releases.

Database requirements Table 3 lists the databases that are supported by the Tivoli Data Warehouse components. In addition, Tivoli Data Warehouse supports file imports from the Merant driver as a data source. Table 3. Supported relational database management systems Database systems Data sources1 Control Central data Data mart database warehouse DB2 Universal Yes No No No Database Enterprise Edition, Version 8.1 on Windows, AIX, and Solaris

4 Release Notes

Table 3. Supported relational database management systems (continued) Database systems Data sources1 Control Central data Data mart database warehouse DB2 Universal Yes Yes2 Yes2 Yes2 Database Enterprise Edition, Version 7.2 on Windows DB2 Universal Yes No Yes2 Yes2 Database Enterprise Edition, Version 7.2 on AIX and Solaris DB2 Universal Yes No Yes Yes Database for z/OS and OS/390®, Version 7 with IBM Data Management Tools, Management Tools Package for DB2 V7 on z/OS; FMID JDB771D DB2 Universal Yes No No No Database, Version 6 or higher on Windows, AIX, and Solaris Oracle client, Version Yes No No No 8.1.7 and either: v Oracle, Version 8.1.7 on Windows, AIX, and Solaris v Oracle, Version 9i on Windows, AIX, and Solaris Microsoft SQL Server, Yes No No No Version 7.0 on Windows NT

Microsoft SQL Server 2000 on Windows 2000 Sybase, Version Yes No No No 12.0.0.8 and 12.5 Informix® Dynamic Yes No No No Server 2000 1 Data source support is determined by ODBC support in DB2 releases.

2 Fix pack 8 with its eFix, fix pack 9, fix pack 10, or fix pack 10a for DB2 Universal Database, Version 7.2 is required. Fix pack 10a is shipped with Tivoli Data Warehouse, Version 1.2. See page 6 for fix pack 10 and 10a limitations.

Table 4 on page 6 lists the DB2 requirements for each Tivoli Data Warehouse component.

Chapter 2. Installation information 5

Table 4. DB2 requirements Deployment type Component DB2 requirement Quick start All DB2 server Distributed Control server DB2 server Central data warehouse DB2 server Data mart DB2 server Crystal Enterprise server DB2 client

Report interface requirements To view and publish reports, Tivoli Data Warehouse requires Crystal Enterprise 9. Crystal Enterprise Professional v.9 is shipped with Tivoli Data Warehouse. For information about Crystal Enterprise requirements, see the documentation on the Crystal Enterprise CD.

Installation and upgrade notes This section provides information about the Tivoli Data Warehouse installation. Review the information in this section before you begin your installation. v The fully qualified host name must appear first in the /etc/hosts list. For example, the entry should look like this: 7.23.29.160 gomez.lab.ibm.com gomez

The following is an incorrect configuration: 7.23.29.160 gomez gomez.lab.ibm.com v APAR JR19393: Due to a problem with DB2 Version 7.2 fix pack 10 and 10a, you must run additional SQL manually for this installation scenario (order is significant): 1. Warehouse packs for Tivoli Enterprise™ Data Warehouse, Version 1.1 that contain data mart ETLs are installed. 2. Tivoli Data Warehouse, Version 1.2 is installed. 3. You plan to install fix pack 10 or 10a after Tivoli Data Warehouse, Version 1.2 is installed. Or, you use DB2 Warehouse Control Database Management to migrate and initialize the control database.

Immediately after step 3 from the preceding scenario, you must run the following SQL against the TWH_MD database on the control server. Use the DB2 ID and password you specified when you installed Tivoli Data Warehouse. insert into iwh.attributelink (iwhid,updated_by,update_ts,name, short_desciption,type,operatorexp,useandsep,orderno,operexp2) (select source_iwhid,’db2admin’,’2003-11-20-19.13.48.000000’, ’’,’’,’JOIN’,’’,1,0,’=’ from iwh.relationship where relation_name=’StarSchema_TO_AttLnk’ and source_iwhid not in (select iwhid from iwh.attributelink))

Note: The update_by and update_ts values, which are hardcoded above, can be changed to other values. Do not attempt to install the fix pack a second time. The rebuilding of the metadata will not work. For more information about this problem, refer to the DB2 documentation. v If the core installation of Tivoli Data Warehouse fails, the control server installs successfully, and you rerun the installation wizard, you must manually reboot

6 Release Notes

the computer where the control server is created before you can use the control server, central data warehouses, or data marts. v When installing or upgrading a warehouse pack, you might receive one of the following error messages: CDWIW0066W, CDWIW0067E, CDWIS0043W, or CDWIS0044E. In these situations, refer to the IBM Software Support Web site and the support flashes for each appropriate application for warehouse pack fixes. v To uninstall warehouse packs for IBM Tivoli Monitoring, you must remove the base warehouse pack with the product code AMY first and separately before removing any other warehouse packs for IBM Tivoli Monitoring. See the documentation for IBM Tivoli Monitoring for additional information.

Chapter 2. Installation information 7

8 Release Notes

Chapter 3. Known limitations, problems, and workarounds

This section provides information about known software limitations and defects for Tivoli Data Warehouse, Version 1.2.

The problem determination chapter of Installing and Configuring Tivoli Data Warehouse, GC32-0744 provides debugging information for installation, configuration, and other problems. It also describes how to obtain information to debug problems.

Limitations This section describes the limitations of Tivoli Data Warehouse. v On some windows of the installation wizards, the button text might be truncated. This is a limitation of the InstallShield Multiplatform product used for the installation process. Even if button text is truncated, the button action works correctly. v After the initial installation of Tivoli Data Warehouse, adding central data warehouses and data marts to the control server can fail if the port for the DB2 server is not set to the default 50000. In the Tivoli Data Warehouse installation wizard, you must set the Host Location in the Central Data Warehouse Properties window to be remote and specify the port number to use. v When you change to a new Crystal Enterprise server, the Everyone group privileges are affected by the import Tivoli process. After running the twh_update_rptsrv command, reset the permissions as required. v Some migrated reports with specific sets of data might cause X-axis labels to be truncated or overwritten. This is due to the Crystal Enterprise limitation that a graph must fit on a physical page. v When viewing reports with the ePortfolio, if you select the drop-down box to choose a specific time frame, the date and time values are reset to their default value. v If Information Catalog Manager (ICM) Version 7 is installed on the same Windows NT or Windows 2000 system as Sybase Open Client, an error occurs and the Sybase Utilities stops. An error message similar to the following is displayed: Fail to initialize LIBTCL.DLL. Please make sure the SYBASE environment variable is set correctly.

Remove the LC_ALL environment parameter from the Windows environment parameters to correct this problem. Note that if you remove the LC_ALL environment, the following ICM functions are disabled: – Information Catalog User – Information Catalog Administrator – Information Catalog Manager

LC_ALL is a locale category parameter. Locale categories are manifest constants used by the localization routines to specify which portion of the locale information a program should use. The locale refers to the locality (country or region) for which certain aspects of a program can be customized.

Locale-dependent areas include, for example, the formatting of dates, or the display format for monetary values. LC_ALL affects all categories of locale-specific behavior.

Use the following procedure to remove the LC_ ALL environment parameter: 1. On the task bar, select the Start button → Settings → Control Panel → System. The System Properties window is displayed. 2. Select the Environment tab. 3. Select LC_ALL. 4. Click Delete. v When using Sybase, the following error message might be displayed: The ’CREATE TABLE’ command is not allowed within a multi-statement transaction in the ’database_name’ database

Workaround: 1. From the ISQL command line, enter use master. 2. Enter go. 3. Enter sp_dboption dbname,"ddl in tran",true, where dbname is the name of the database. 4. Enter go. The following message is displayed: Database option ’ddl in tran’ turned ON for database ’dbname’ Run the CHECKPOINT command in the database that was changed. (return status = 0) 5. Enter use dbname. 6. Enter go. 7. Enter checkpoint. 8. Enter go. 9. Enter quit.

Known problems and workarounds This section provides information about known problems with Tivoli Data Warehouse. Workarounds are provided for some problems. Defects listed here apply to all languages. For information about defects associated with specific languages, see “Internationalization problems” on page 11. Installation or uninstallation problems v On AIX and Solaris, the vwdaemon process does not always restart after the installation of the DB2 Warehouse Manager. Workaround: Reboot the AIX or Solaris system after the installation of the DB2 Warehouse Manager. v Defect 164948: On z/OS, the installation of Tivoli Data Warehouse might fail if the values provided in the installation wizard are not valid. Also, the resources specified in the installation wizard must be available at the time of installation. The following error might be displayed: CDWIC0022E The installation program cannot run SQL script sql_script.

Workaround: Ensure that the values provided in the installation wizard are valid and that the resources specified in the installation wizard are available at the time of installation. Review the execsql2_message_log.log to determine where the failure occurred in the database script.

10 Release Notes

v Defect 167717: When you install a warehouse pack and use the default schedule to run the extract, transform, and load (ETL) processes, the default start date is December 15, 2002 (12/15/2002). Nonetheless, your scheduled ETLs will run successfully after installation. Report interface problem v Defect 163415: Extreme case reports that had an ascending output in Tivoli Enterprise Data Warehouse, Version 1.1 can only run with a descending output after migration to Tivoli Data Warehouse, Version 1.2. Miscellaneous problems v PMR 17980 br499: Steps of an ETL process might fail randomly in the DB2 Data Warehouse Center. Refer to IBM Software Support for DB2 Universal Database for more information. v Defect 167862: When incorrect command line parameters are entered for the administrative utilities, a response similar to the following is generated: twh_core_admin.pl : unrecognized option ’-r’ Try ’twh_core_admin.pl --help’ for more information.

Workaround: You must omit the text .pl from the statement. For example, use the following statement: twh_core_admin --help v Defect 157941: In the DB2 Data Warehouse Center, the Processing Options tab of the Step Properties window displays this message: The selected agent site is invalid

This message can be safely ignored. v Defect 153132: In some cases when you use the DB2 Data Warehouse Center to run steps, the characters < and > appear in pop-up messages. The DB2 Data Warehouse Center has a limitation of not displaying the greater than symbol (>) and the less than symbol (<).

Internationalization problems This section provides information about known problems with the non-English language versions of Tivoli Data Warehouse.

Note: Some defects described in “Known problems and workarounds” on page 10 might affect translated versions of Tivoli Data Warehouse. v Tivoli Data Warehouse cannot be installed in directories that are named using the double-byte character set (DBCS). Workaround: Install Tivoli Data Warehouse in a directory that is named using the single-byte character set (SBCS). v InstallShield Multiplatform and its Java™ Virtual Machine (JVM) have documented issues regarding DBCS locales. Examples of problems that might occur in this product are extra spaces between characters, truncation of characters, and unreadable default fonts.

Chapter 3. Known limitations, problems, and workarounds 11

12 Release Notes

Chapter 4. Documentation updates

This section contains updates to the Tivoli Data Warehouse library.

Additional troubleshooting scenarios In addition to the common problems described in Installing and Configuring Tivoli Data Warehouse, the following are other troubleshooting scenarios: v Possible problem: Reports might not run from the schedule in the ePortfolio or Crystal Management Console. Or, you cannot view reports. Solutions: – Ensure that the ODBC name defined on the Crystal Enterprise server matches the name specified on the report database tab in the Crystal Management Console. The case of the name must match. If you cannot resolve the issue, select DB2 as the database driver on the report database tab rather than ODBC. – After installing Tivoli Data Warehouse, you must create a connection from the Crystal Enterprise server to any data mart you created during the installation. The first ODBC data source is named TWH_MART for the data mart named TWH_MART and subsequent ODBC data sources are named TWH_MARTn for data marts named TMARTn, where n indicates the data mart number starting with ″1″. When you install a warehouse pack, this connection allows you to publish reports to the Crystal Enterprise server. When the ODBC data source name and the database name do not match, complete the following steps after installing the warehouse pack to be able to view the reports: 1. In the Crystal Management Console, click Manage Objects. 2. In Objects, click the report you installed and then click the Database tab. 3. In the Data Source(s) list, select the ODBC data source. 4. Select Use custom database logon information specified here and select ODBC from the Select a database driver pull-down list. 5. Click Update. You can now view the report in ePortfolio. v Possible problem: ETL processes fail. The processes ran successfully before upgrading to version 1.2. You might see this error message: DWC08410E The agent was unable to execute a Data Warehouse Center Program.

Solution: Ensure that the user ID for the DB2 Data Warehouse Center source defined under Warehouse Sources matches the schema name in the source database. v Possible problem: Traditional Chinese is not selected for View on Demand reports when the browser settings specify traditional Chinese. Solution: Schedule the report and select traditional Chinese from the language list.

Upgrades from version 1.1 to version 1.2 Installing and Configuring Tivoli Data Warehouse states you must apply fix pack 1.1-TDW-FP02 before you upgrade from Tivoli Enterprise Data Warehouse, Version 1.1 to Tivoli Data Warehouse, Version 1.2. In fact, you can apply either fix pack 1.1-TDW-FP02 or fix pack 1.1-TDW-FP03 before upgrading.

Multiple customer environments There is an important security aspect to consider for star schemas in the multiple customer environment. Tivoli Data Warehouse requires customers to create database users that include specific grants to only their applicable views. When views are created for specific customers, the users give access to the views by database ID and their access to views is separated between different customer users.

In addition to the steps in the warehouse pack installation chapter of Installing and Configuring Tivoli Data Warehouse, you must perform this step when configuring multiple customer environments: v Update the customer views in the data mart. Placeholder views are created for each fact and dimension table when the warehouse pack is installed, but you must customize the views with an entry for each of your customers. The implementation guide for the warehouse pack should list the views you need to update. If it does not, you can look at the definition of the views in the file %TWH_TOPDIR\apps\productCode\version\mart\ddl\ productCode_mart_schema.generic script. For example, the following SQL statements create a customer view for the fact and dimension table XYZ.F_DM_hour and XYZ.D_DM_host of the warehouse pack with product code XYZ. #Run this set of inserts to create views for each customer. #You must replace cust_id with your valid customer ID, #and code inserts for each customer. Create view XYZ.F_V_DM_cust_id_hour as (select * from XYZ.F_DM_hour where host_id in (select host_id from d_dm_host where cust_id = cust_id)); Create view XYZ.D_V_DM_host_cust_id as (select * from XYZ.D_DM_host where cust_id = cust_id);

For maintenance of multiple customer environments, you need to regularly reexamine your configuration and update it as necessary.

List commands The following information replaces the log and output documentation for the twh_list_agentsites, twh_list_cdws, twh_list_cs, and twh_list_marts commands in Installing and Configuring Tivoli Data Warehouse.

The messages for the list commands are logged to %TIVOLI_COMMON_DIR%\cdw\logs\tools\TWHListCmds_message_log.log. Additionally, the trace messages are logged to %TIVOLI_COMMON_DIR%\cdw\logs\tools\TWHListCmds_trace_log.

The output for the list commands does not contain the following line: Press any key to continue...

14 Release Notes

Messages The following are changes and additions to the Tivoli Data Warehouse messages: CDWIC0007E An argument argument that is not valid was found in the configuration file file_name. Or, the computer is not set up to use fully qualified host names. Explanation: The installation program attempted to validate the configuration file and found the specified argument is not valid. If the parameter listed is LOCAL HOST, the installation program might have attempted to install to a computer that does not use fully qualified host names. Administrator Response: Ensure that fully qualified host names are configured. If the host name is fully qualified, run FFDC and contact IBM Customer Support. CDWLS0003E The program that runs list commands failed with an error. Explanation: The list commands program failed. Administrator Response: Run FFDC and contact IBM Customer Support. CDWIS0026E The program cannot open port port on remote host host. Explanation: The program attempted to open the specified port on the specified host and failed. Administrator Response: Verify that the host name and port number are correct. Also, verify that the port is active on the host.

Chapter 4. Documentation updates 15

16 Release Notes

Chapter 5. Contacting customer support

If you have a problem with any Tivoli product, refer to the following IBM Software Support Web site:

http://www.ibm.com/software/sysmgmt/products/support/

If you have a problem with Tivoli Data Warehouse, refer to the following IBM Support Web site:

http://www-3.ibm.com/software/sysmgmt/products/support/TivoliDataWarehouse.html

If you have a problem with a DB2 product, refer to the following IBM Software Support Web site:

http://www.ibm.com/software/data/db2

If you want to contact customer support, see the IBM Software Support Guide at the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information: v Registration and eligibility v Telephone numbers and e-mail addresses, depending on the country in which you are located v Information you must have before contacting IBM Software Support

18 Release Notes

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 might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation 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.

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 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.

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

20 Release Notes

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.

If you are viewing this information in softcopy form, the photographs and color illustrations might not display.

Trademarks IBM, the IBM logo, AIX, DB2, DB2 Universal Database, Informix, Tivoli, Tivoli Enterprise, Tivoli Enterprise Console, OS/390, and z/OS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

Microsoft and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

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.

Appendix. Notices 21

22 Release Notes

Printed in USA

SC32-1399-00