IBM(R) DB2 Web Query Tool, Version 1 Release 3, FixPak 3 README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Corrected known problems 2.0 PREREQUISITES 2.1 Hardware Requirements 2.2 Software Requirements 3.0 FIXPAK INSTALLATION INSTRUCTIONS 3.1 To upgrade to DB2 Web Query Tool version 1.3 FixPak 3 when working with WebSphere Application Server Version 4.0.3 on Multiplatforms and iSeries 3.2 To install DB2 Web Query Tool version 1.3 FixPak 3 when working with WebSphere Application Server Version 4.0.3 on z/OS 3.3 To upgrade to DB2 Web Query Tool version 1.3 FixPak 3 when working with WebSphere Application Server Version 3.5.6 4.0 CUSTOMIZATION INSTRUCTIONS 5.0 RESTRICTIONS 6.0 CORRECTIONS TO DOCUMENTATION 7.0 HOW TO GET HELP 8.0 NOTICES 8.1 Use of Evaluation Program 8.2 Notices of other companies 8.3 TRADEMARKS AND SERVICE MARKS ___________________________________________________________________________ 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Web Query, Version 1 Release 3 FixPak 3, README file. This README file contains information about installing IBM DB2 Web Query. IBM DB2 Web Query has been tested and validated with all supported releases of DB2 Universal Database(TM) through Version 8 Release 1 for Multiplatforms. Subsequent releases might require additional maintenance. This is the most current README file as of 8/07/2003. 1.1 Evaluation code If you are using 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 to which you are connecting IBM DB2 Web Query. Read NOTICES Section 8.1, USE OF EVALUATION PROGRAM, and the License Agreement provided with your evaluation copy of the program. 1.2 Corrected known problems - The performance of the DB2 Web Query navigation tree has been improved. - Stored Procedures now work properly on OS/390. - Output variables on Stored Procedures are not modifiable. - Stored Procedures that do inserts, updates, and deletes no longer result in an error message. - The missing context sensitive help panels have been added. 2.0 PREREQUISITES 2.1 HARDWARE REQUIREMENTS Hardware requirements are those needed to run the software that is described in 2.2 Software Requirements. DB2 Web Query has the following hardware requirements: - Approximately 64 MB of free disk space on any supported platform - Additional space for user data - A minimum of 64 MB memory - Memory to fulfill WebSphere and DB2 minimum requirements 2.2 SOFTWARE REQUIREMENTS In order to work with IBM DB2 Web Query Tool, you need to have a Web server, a Web Application server (such as IBM WebSphere Application Server), JDBC and DB2 installed on your system. You also need to be able to connect to a DB2 database. When you are using DB2 Web Query Tool, you are working in a browser. Information that you send to DB2 Web Query Tool first goes through your Web Server. Your Web Server passes the information to your Web Application Server (IBM WebSphere Application Server). Your Web Application Server passes the information to DB2 through JDBC. The following table indicates the operating systems, DB2 Web Query Tool products, and the WebSphere products that you can choose for your business. Operating systems, DB2 Web Query Tool products, and the WebSphere products that are supported by DB2 Web Query v 1.3: Operating System | DB2 Web Query Tool Product | IBM WebSphere Product ------------------------------------------------------------------------------- UNIX and Linux | IBM DB2 Web Query Tool | IBM WebSphere Application | for Multiplatforms | Server V3.5.6 Advanced, or | | V4.0.3 Advanced Edition -------------------------------------------------------------------------------- Windows NT or | IBM DB2 Web Query Tool | IBM WebSphere Application Windows 2000 | for Multiplatforms | Server V3.5.6 Advanced, or | | V4.0.3 Advanced Edition --------------------------------------------------------------------------------- OS/400 Version 4.4 or | IBM DB2 Web Query Tool | IBM WebSphere Application later | for iSeries | Server V3.5.6 Advanced, or | | V4.0.3 Advanced Edition --------------------------------------------------------------------------------- z/OS, OS/390 | IBM DB2 Web Query Tool | IBM WebSphere Application Operating System, | for z/OS | Server V3.5.6 Advanced, or Version 2 Release 5 or | | V4.0.3 Advanced Edition higher with UNIX | | System Services | | installed on MVS | | ---------------------------------------------------------------------------------- It is recommended that you keep up to date as updates to WebSphere V3.5 and V4.0 become available. Note: IBM WebSphere Application Server is recommended (versions 3.5.6 Advanced, and 4.0.3 Advanced Edition are supported). However, DB2 Web Query Tool is compatible with any application server that supports JSDK 1.3 and above, J2EE and JDBC 1.0. Functional Dependency: If you use WebSphere Application Server on z/OS or OS/390, Version 4.0 is required in order to use the SOAP functions. Database: IBM DB2 Version 6.x and above with a JDBC Type-2 Driver, with the applicable updates to enable JDBC. DB2 Web Query will also work with Informix Dynamic Server 9.3. Note: JDBC Drivers other than those for DB2 can be used to view but not edit database data. IBM DB2 Web Query has been tested and validated with all DB2 V 6.x and above. Web Browser: To use DB2 Web Query, you must use a Web Browser that supports Java 1.1.x and has cookies and Java script enabled. Microsoft Internet Explorer version 5.5, with fixpack 2 is installed and higher is supported. Netscape Version 4.7 and higher is supported. Tip: Ensure that the current fix levels are applied for the JDBC driver, JDK, HTTPD, and IBM WebSphere. 3.0 FIXPAK INSTALLATION INSTRUCTIONS Install the selected updates using either PKZIP for zip file format or GUNZIP for tar file format. 3.1 To upgrade to DB2 Web Query Tool version 1.3 FixPak 3 when working with WebSphere Application Server Version 4.0.3 on Multiplatforms and iSeries: 1. Download the FixPak file from the IBM web site: http://www.ibm.com/software/data/db2imstools/support/fixpaks.html 2. In the WebSphere Administrative Console, expand the navigation tree in the left pane until you find the Enterprise Applications branch. 3. In the Enterprise Applications branch of the navigation tree, remove the cwqEA application. 4. Navigate to the /servlet directory. Delete the /servlet directory. 5. Decompress the source files that you downloaded for the latest version of DB2 Web Query Tool into your installRoot directory. (Either un-tar or unzip the files from within the installRoot directory.) Where duplicates exist, overwrite the existing files with the new files. 6. In WebSphere Application Server, deploy the cwq-1.3.3.ear file. For specific instructions on deploying the .ear file on your platform see the instructions specific to that platform: - “Configuring IBM WebSphere Application Server Version 4.0.3 to work with IBM DB2 Web Query on Multiplatforms and iSeries” in the DB2 Web Query User's Guide - “Configuring IBM WebSphere Application Server Version 4.0.3 to work with IBM DB2 Web Query on z/OS” in the DB2 Web Query User's Guide 7. From the WebSphere Administrative Console, start the DB2 Tools Application Server. Alternately you can start the DB2 Tools Application server by running the following script: wqstart.bat on Windows platforms or wqstart.sh on UNIX platforms. 3.2 To Install DB2 Web Query Tool version 1.3 FixPak 3 when working with WebSphere Application Server Version 4.0.3 on z/OS 1. Download the FixPak file from the IBM web site: http://www.ibm.com/software/data/db2imstools/support/fixpaks.html 2. Ensure that WebSphere Application Server Version 4.0.1 is installed and functioning properly. a) Install WebSphere Application Server 4.0.1 for z/OS b) Install WebSphere Service Level 95 and all associated updates for related systems. c) Start WebSphere and associated services. d) Verify that the IVP is operational. To check that the IVP is operational, access the following URL: http:///webapp/examples/ 3. Stop all WebSphere Web servers. To stop the servers, issue the following cancel commands for the J2EE and HTTPd servers from SDSF: /c bboasr2.bboasr2a /c httpd1 4. Create a table called manager in any database with DB2 Web Query as the owner. Use the following syntax: CREATE TABLE WQ.manager ( cwqName VARCHAR (40) NOT NULL, PRIMARY KEY (cwqName) ) Note: This table must be accessible from the system on which DB2 Web Query is running. If you are working on z/OS or os/390, you must also create a unique or primary index for wq.manager using the following syntax: CREATE UNIQUE INDEX wq.manageridx ON wq.manager ( cwqname asc ) 5. Decompress the DB2 Web Query files into the DB2 Web Query installRoot. To determine the appropriate archive to decompress, see section 2.2, SOFTWARE REQUIREMENTS. 6. Ensure that you have read and write permission to the DB2 Web Query installRoot directory so that configuration and log files can be created and written. 7. Update the HTTPd configuration. To update the HTTPd configuration, add the following directory to httpd.conf: Service /DB2Tools/* /usr/lpp/WebSphere/WebServerPlugIn/bin/was400plugin.so:service_exit Ensure that the path to was400plugin.so is correct. 8. Add the following lines to the jvm.properties file: client.encoding.override=UTF-8 com.ibm.db2.cwq.installRoot= Note: The default location is for the jvm.properties file is: /WebSphere390/CB390/controlinfo/envfile/SVSCPLEX/BBOASR2A/jvm.properties 9. In the webcontainer.conf file, locate the following line: session.invalidatetime= Update its value to your desired timeout. This value is in milliseconds. The default value is 180000 (3 minutes). The recommended value is 3600000 (1 hour) and it may be changed to fit your requirements. NOTE: The default location for this file is: /WebSphere390/CB390/controlinfo/envfile/SVSCPLEX/BBOASR2A/webcontainer.conf 10. Install and start the WebSphere Application Server for z/OS and os/390 Administration client. 11. From the WebSphere Application Server for z/OS and os/390 Administration client, connect to WebSphere. 12. In WebSphere Application Server for z/OS and os/390 Administration client, create a new conversation. To create a new conversation using the WebSphere Administration client for z/OS: a) From WebSphere Application Server for z/OS and os/390 Administration client, connect or login to the z/OS or os/390 machine where DB2 Web Query is installed. b) Click the Conversation Node on the left side of the screen. c) Right click the Conversation node in the left side of the screen. From the pop-up menu, select Add. d) Type a name for the conversation that is appropriate for your environment in the Name field. e) Click Save. 13. Identify data locations (subsystems) that you want to access using DB2 Web Query. 14. Create a new data source for each data location that you want to access using DB2 Web Query. Make note of the name of the new data sources. These data source names will be used during the DB2 Web Query configuration as the data source name. Data sources are needed in order for DB2 Web Query to connect to any DB2 data location, including the DB2 Web Query manager table. 15. In WebSphere Application Server for z/OS and os/390 Administration client, install the DB2 Web Query J2EE Application. To install the DB2 Web Query J2EE Application: a) In the WebSphere Application Server for z/OS and os/390 Administration client, expand the navigation tree in the left pane to J2EEApplications: Conversations//Sysplexes//J2EEServers/ b) Right click the defined server and select: Install J2EE application c) Specify the cwq-1.3.3_390.ear file and click OK. The Reference and Resource Resolution window opens NOTE: cwq-1.3.3_390.ear must be located on the machine from which you are running the WebSphere Application Server for z/OS and os/390 Administration client. The default location for this file is the /Conf directory on the machine where DB2 Web Query is installed. 16. In the Reference and Resource Resolution window, expand the following directories in the navigation tree in the left pane of the window: cwqEA/cwqManagerEJB/CwqManager click the J2EE Resource tab and select the data source where the DB2 Web Query Manager table is located. 17. In the navigation tree in the left pane of the Reference and Resource Resolution window expand the following directories: cwqEA/cwqWA_WebApp.jar/cwqWA_WebApp 18. Click the EJB tab. The EJB page opens. 19. On the EJB page, click the Set Default JNDI Path & Name button. 20. Click the Reference tab. The Reference page opens. 21. From the Reference page, select (ejb-link)CwqManager from the JNDI Name drop-down list. 22. Click OK to finish installing the DB2 Web Query Enterprise Application. 23. Activate the Conversation. a) Right click: Conversations/cwqEA A pop-up menu appears. From the pop-up menu, select Validate. b) Right click: Conversations/cwqEA A pop-up menu appears. From the pop-up menu, select Commit. c) Right click: Conversations/cwqEA A pop-up menu appears. From the pop-up menu, select Complete --> All Tasks. d) Right click: Conversations/cwqEA A pop-up menu appears. From the pop-up menu, select Activate. The cwqEA Conversation is active. A lock symbol with a lightening bolt appears. This may take some time. 24. Start the WebSphere Web servers. To start the WebSphere Web servers, issue the start command for the J2EE and HTTPd servers To start the J2EE and HTTPd servers using TSO SDSF, issue the following commands: /s bboasr2.bboasr2a /s httpd1 25. Access the DB2 Web Query Configuration Utility by going to the following URL: http:///DB2Tools/WebQuery/Configure 26. From the Configuration utility, set the configuration parameters. For more information on the DB2 Web Query Configuration parameters, see the "Parameter List" in Chapter 2 of the DB2 Web Query User's guide. NOTE: You must add a database driver entry for each database location that was installed in the WebSphere Application Server for z/OS and os/390 Administration client. You can select from the list of default database drivers or you can create a custom database driver by checking the Custom check box and filling in the Name and Connection Pool fields. You must Click the Update button after each database driver that you add. NOTE: Ensure that the wqUserId has select authority on the following tables at each location to which DB2 Web Query connects: - SYSIBM.SYSTABLES - SYSIBM.SYSTABAUTH - SYSIBM.SYSADMAUTH - SYSIBM.SYSDBAUTH - WQ.STORE_TABLE - WQ.INDEX_TABLE - WQ.SMTP 27. Start DB2 Web Query. Using a Web browser open the following URL: http:///DB2Tools/WebQuery The DB2 Web Query login screen opens. 3.3 To upgrade to DB2 Web Query Tool version 1.3 FixPak 3 when working with WebSphere Application Server Version 3.5.6: 1. Download the FixPak file from the IBM web site: http://www.ibm.com/software/data/db2imstools/support/fixpaks.html 2. Stop your Web server and your application server. 3. Delete the .jar file associated with the previous version of DB2 Web Query Tool. 4. Decompress the DB2 Web Query files into the installRoot directory on your machine. (Either un-tar or unzip the files from within the installRoot directory.) Where duplicates exist, overwrite the existing files with the new files. NOTE: If you store .jar files in a location other than the installRoot directory, remember to copy the new.jar file to that location. 5. Ensure that IBM WebSphere and DB2 are fully installed, configured, and running. 6. Ensure that the Xerces, Xalan, and SOAP support jar files must be made available to the CWQ and the Application Server. These files have been included in the installRoot/servlet directory. 7. Stop the WebSphere Administrative Console and the Administration client service if they are started. 8. Navigate to the following file and open it: WebSphere\AppServer\bin\admin.config 9. Find com.ibm.ejs.sm.adminserver.classpath in admin.config. Append the following to the front of com.ibm.ejs.sm.adminserver.classpath: /servlet/xercesImpl.jar; /servlet/xml-apis.jar;/servlet/xalan.jar; NOTE: If you are working in Windows, the path to the install root must use the following syntax: \:/ For further illustration, see the example below. For example, in Windows: e\:/ibm/CWQ/servlet/xercesImpl.jar;e\:/ibm/CWQ/servlet /xml-apis.jar;e\:/ibm/CWQ/servlet/xalan.jar; 10. Restart the administration client and Administrative Console. 11. Create a table called manager in any database with DB2 Web Query as the owner. Use the following syntax: CREATE TABLE WQ.manager ( cwqName VARCHAR (40) NOT NULL, PRIMARY KEY (cwqName) ) NOTE: This table must be on a database that is on the server on which WebSphere Application Server V 3.5.6 is running. If you are working on z/OS or os/390, you must also create a unique or primary index for wq.manager using the following syntax: CREATE UNIQUE INDEX wq.manageridx ON wq.manager ( cwqname asc ) 12. Navigate to the installRoot on the machine that is running CWQ. For example: CWQ\conf\multiplatform\win\was35x 13. Edit the wqenvset.bat file. In wqenvset.bat, change the following variable values as appropriate for your environment: - wqt_wasRoot - The directory where WebSphere Application server has been installed. - wqt_installRoot - The directory where Web Query is installed. - wqt_nodeName - The name of the WebSphere node that needs to be configured. This variable is case sensitive. - wqt_rootURI - the prefix of the URL that will be used to access DB2 Web Query. 14. Run wqinstall.bat. 15. Run wqstart.bat. 16. Open the WebSphere Administrative Console. There will now be a "DB2 Tools Server" under Nodes NOTE: If the "DB2 Tools Server" is not visible, close the console and start it again. 17. Expand DB2 Tools Server under the Node Name. 18. Click ejbContainer on Administrative Console navigation tree. 19. Click the Data Source tab. 20. In the Userid box, type the User ID that is used to access the WQ.manager table that you created in the step 11. 21. In the Password box, type the password that is used to access the WQ.manager table that you created in the step 11. 22. Click Apply. 23. Click jdbc/cwqManagerDB on Administration Console navigation tree. Ensure the driver that it is attached to is a valid DB2 Driver - if it is not, create a new driver and attach jdbc/cwqManagerDB to it (the steps to create a new driver are below). It should also be attached to the database that WQ.manager is under. To create a new JDBC driver: a. Choose Console --> Tasks --> Create Data Source b. Create and Install a new JDBC driver. c. Name your newly created JDBC driver. d. From the drop-down list, select a class name or type a class name in the Class Name field. Typically COM.ibm.db2.jdbc.app.DB2Driver for DB2 on Windows - this one is not in the list) NOTE: these are case sensitive. e. Select Node. f. Specify the location of the db2 driver's file (typically db2java.zip even though it may ask for a .jar file) g. Type a data source name in the Data Source Name field h. Type the name of the database where the WQ.manager table is located, in the Database name field. i. Click Finish. 24. Open the DB2 Web Query configuration Utility by accessing the following URL: http://server/DB2Tools/WebQuery/Configure The initial user id is: cwq. The initial password is: cwq 25. On the Configuration screen, change the initialContextfactory parameter to: com.ibm.ejs.ns.jndi.CNInitialContextFactory 26. In the Configuration Utility, specify the DB2 Web Query initial Parameters. (For more information on initial parameters, see the Parameter List in the DB2 Web Query User's Guide.) NOTE: Ensure that the user ID that you specify for the wqUserId parameter has select authority on the following tables at each location to which DB2 Web Query connects: - SYSIBM.SYSTABLES - SYSIBM.SYSTABAUTH - SYSIBM.SYSADMAUTH - SYSIBM.SYSDBAUTH - WQ.STORE_TABLE - WQ.INDEX_TABLE - WQ.SMTP 27. Configure DB2 Web Query. See Section 3.0 28. Start DB2 Web Query. 4.0 CUSTOMIZATION INSTRUCTIONS For complete instructions on how to customize and use DB2 Web Query, refer to DB2 Web Query for Multiplatforms User's Guide. If you received your copy of DB2 Web Query electronically, locate the User's Guide here: http://www.ibm.com/software/data/db2imstools/library.html If you are installing this image from a CD-ROM, the documentation is located in /doc directory. The User's Guide on the Web can contain updates to the publication on CD-ROM. 5.0 RESTRICTIONS The following are the current restrictions to DB2 Web Query: - Temporary result sets cannot be compared. - When running stored procedures, use the Next button to run the stored procedure, rather than the Run button. - After saving a result set, the saved result set may not appear in the DB2 Web Query navigation tree. - When using the DB2 Table Editor functionality through DB2 Web Query, if you are using Microsoft Internet Explorer Version 6, you must have the Java 2 SDK V 1.4.1 or higher installed. - When using the DB2 Table Editor functinality through DB2 Web Query, if you are working with DB2 sample tables that contain primary keys, you need to upgrade to DB2 Table Editor 4.3 Fixpak 3. - WebQuery Tool must not be installed in a folder with double byte characters in the name. - SOAP functionality is supported on WebSphere Application Server 4.0.3 and higher only. SOAP functionality is not supported on WebSphere Application Server 3.5.6. SOAP functionality is not supported on non-J2EE compliant servers. - When using Netscape 4.7, resizing the Web Query window has the side effect of resetting the main display back to the about screen consequently loosing the current work screen. - In some cases an Error 500 is produced when the http session has expired. In this event, your connection(s) to the databases have been closed. To restart your session the main Web Query URL must be entered again. - DB2 Synonyms appear as Alias objects when connecting to DB2 Universal Database on Multiplatforms. - Web Services are restricted when running on z/OS using WebSphere 3.5 6 .0 CORRECTIONS TO DOCUMENTATION To obtain the latest refresh of DB2 Web Query Tool publications refer to: http://www.ibm.com/software/data/db2imstools/library.html The following text should be added to the Troubleshooting section of the DB2 Web Query User's Guide: - The wqUserId is now used to retrieve all objects that are used by DB2 Web Query (including: cwq catalog objects, tables, views, stored procedures). If the wqUserId is not a valid id, has an incorrect password, or does not have the authority to select from the following tables: - SYSIBM.SYSTABLES - SYSIBM.SYSTABAUTH - SYSIBM.SYSADMAUTH - SYSIBM.SYSDBAUTH - WQ.STORE_TABLE - WQ.INDEX_TABLE - WQ.SMTP Nothing will be listed in the DB2 Web Query navigation tree. - The create table statements in the Web Query install instructions should read as follows: CREATE TABLE WQ.manager ( cwqName VARCHAR (40) NOT NULL, PRIMARY KEY (cwqName) ) Note: This table must be accessible from the system on which DB2 Web Query is running. If you are working on z/OS or os/390, you must also create a unique or primary index for wq.manager using the following syntax: CREATE UNIQUE INDEX wq.manageridx ON wq.manager ( cwqname asc ) 7.0 HOW TO GET HELP For a complete and up-to-date source of DB2 Web Query Tool information, including information on issues discovered after this readme was published, go the to following website: DB2 Web Query Tool 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. 8.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. 8.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 for a complete explanation of the terms that apply. 8.2 Notices of other companies Apache Xerces The Apache Software, Version 1.1 Copyright(c) 1999-2000 The Apache Software Foundation. All rights reserved 1. "This product includes software developed by the Apache Software Foundation (http:/www.apache.org/)." alternatively, this acknowledgment must appear in the software itself, if and wherever such third-party acknowledgments appear. 2. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 3. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED 'AS IS' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see http://ww.apache.org." Apache Xalan The Apache Software, Version 1.1 Copyright(c) 1999 The Apache Software Foundation. All rights reserved 1. "This product includes software developed by the Apache Software Foundation (http:/www.apache.org/)." alternatively, this acknowledgment must appear in the software itself, if and wherever such third-party acknowledgments appear. 2. The names "Xalan" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org." 3. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED 'AS IS' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, Lotus Development Corporation., http://www.ibm.com. For more information on the Apache Software Foundation, please see http://www.apache.org." 8.3 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 iSeries z/OS zSeries Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. In the United States or other countries, or both. 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. Other company, product, and service names may be trademarks or service marks of others. (C) Copyright IBM Corporation 2001, 2002. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.