IBM(R) DB2 Table Editor, Version 4 Release 3, FixPak 1 README CONTENTS 1.0 ABOUT THIS README FILE 2.0 CORRECTED KNOWN PROBLEMS 3.0 PREREQUISITES 3.1 Hardware Requirements 3.2 Software Requirements 4.0 INSTALLATION INSTRUCTIONS 4.1 UPDATES TO SHARED DYNAMIC LINK LIBRARIES 4.2 CONFIGURATION FOR UNATTENDED INSTALLATION 4.3 INSTALLING THE DB2 TABLE EDITOR CONTROL CENTER PLUG-IN 5.0 CORRECTIONS TO DOCUMENTATION 6.0 SERVICE 7.0 FUNCTIONALITY NOT SUPPORTED 8.0 NOTICES 8.1 Notices of other companies 8.2 Trademarks and service marks __________________________________________________________________ 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Table Editor, Version 4 Release 3, FixPak 1 that contains the latest fixes for DB2 Table Editor V4.3. This FixPak is a complete replacement of the product without the License Use Management (LUM) key. 2.0 CORRECTED KNOWN PROBLEMS - Button lables changed on the object list dialog - Error message improved when making changes in a form but not updating a primary table - Float data type is now listed with correct size - Thousands separator now works in the list control - Memory reference error when initial action has been set in the developer application has been eliminated. - Numbers are fomatted with a thousands separator by default in both the DB2 Table Editor and the DB2 Table Editor Developer applications - When listing objects such as tables and views, the error message reflects the correct object type. 3.0 PREREQUISITES 3.1 Hardware Requirements Hardware requirements are those needed to run the Windows software as described in 3.2 Software Requirements. DB2 Table Editor has the folowing requirements: - Approximately 16 MB of free disk space on a Windows machine - A minimium of 32 MB memory. Additional memory improves performance. 3.2 Software Requirements DB2 Table Editor runs on the following operating systems: - Microsoft® Windows 95 - Microsoft Windows 98 - Microsoft Windows NT® 4.0 - Microsoft Windows 2000 - Microsoft Windows XP 4.0 INSTALLATION INSTRUCTIONS To install DB2 Table Editor: 1. Download the FixPak from the FTP web site: ftp://ftp.software.ibm.com/software/dmtools/fixpaks/ Download the file to a temporary directory on the system where the DB2 Table Editor is installed. 2. Browse to the Disk1 directory and double-click setup.exe. The DB2 Table Editor install starts. 3. Follow the steps in the DB2 Table Editor Install wizard. For specific information on items in the install wizard, click the Help button to access the online help. 4. When the installation is complete, start the DB2 Table Editor Console and create a server definition file for each server that you want to access using DB2 Table Editor. For more information on creating a server definition file, see the DB2 Table Editor User's Guide. Note: You must set up server definition files for the servers that you want to access using DB2 Table Editor before you can access these servers using DB2 Table Editor Developer, Windows User, or Java Player. Use the DB2 Table Editor Console to setup server definition files. 4.1 UPDATES TO SHARED DYNAMIC LINK LIBRARIES DB2 Table Editor installs the Visual C Runtime library (MSVCRT.DLL v4.21.7303) and Microsoft(R) Foundation Classes library (MFC42.DLL v5.00.7303) to the Windows(R) System directory. If you are running on Windows NT(R) 3.51, DB2 Table Editor will additionally install the Microsoft 3D Windows Control Library (CTL3D32.DLL v2.31.000). 4.2 CONFIGURATION FOR UNATTENDED INSTALLATION An unattended installation allows you to select the installation options for your DB2 Table Editor users before beginning the installation process. By using this method you can designate all of the options for multiple installations rather than having to select the same options repeatedly for each individual installation. Use the following steps to enable unattended installation. STEP ONE - Edit setup.ini Using a text editor such as NotePad, edit setup.ini. This file, on Disk 1 of the installation diskettes, controls the installation process and determines the settings used for the installation. The settings you can control are described below. Specify the settings that you want in setup.ini. _____________________________________________________________________________ [Options] Setting Effect AutoInstall= 0,1 Specify 1 to perform an unattended installation. All other settings in setup.ini are ignored if this setting is not 1. FileServerInstall= 0,1 Specifies whether DB2 Table Editor is already installed on a file server. If the settings is 0, all DB2 Table Editor files are installed to the directory specified in the InstallPath variable. If the settings is 1, DB2 Table Editor must be previously installed into the directory specified in the InstallPath variable. To enable a file server installation, you also must set SetupType=2. SetupType= 0,1,2 Specifies the type of installation to perform. 0 indicates a typical installation, 1 indicates a compact installation, 2 indicates a custom installation. If you select 2, you must indicate which components to install. Note: Option 2, the custom installation, is strongly recommended. Most users do not require the Console or Developer. InstallPath= Specifies the directory to receive the DB2 Table Editor installation (if FileServerInstall=0) or the file server directory that already contains the installation (if FileServerInstall=1). ProgramGroup= Specifies the name of the program group to create (under Program Manager) or the program folder to create (for the Windows 95(R), Windows 98(R), and Windows NT(R) 4.0 Start Menu). _____________________________________________________________________________ [Components] Setting Effect Admin 0,1 Specifies whether to install DB2 Table Editor Console. If FileServerInstall=1, files are not copied to the local machine, but program group icons are still created. Always set this option to 0 for user installations. Developer 0,1 Specifies whether to install DB2 Table Editor Developer. If FileServerInstall=1, files are not copied to the local machine, but program group icons are still created. Always set this option to 0 for user installations. _____________________________________________________________________________ Setup.ini example This setup.ini file specifies an unattended installation. A typical installation is performed, copying files to the C:\Programs\DB2 Table Editor directory, and creating a program group or program folder named DB2 Table Editor. [Options] AutoInstall=1 FileServerInstall=0 SetupType=0 InstallPath=C:\Programs\DB2 Table Editor ProgramGroup=DB2 Table Editor STEP TWO - Save setup.ini After you edit and save setup.ini, copy it to Disk 1 of the DB2 Table Editor installation diskettes. STEP THREE - Run DB2 Table Editor Setup Run the installation from the source diskettes or server. The installation proceeds automatically. 4.3 INSTALLING THE DB2 TABLE EDITOR CONTROL CENTER PLUG-IN The DB2 Table Editor Control Center Plug-in is an extension to the DB2 Control Center. For more information about the Control Center, refer to the IBM DB2 Administration Guide. The DB2 Table Editor Control Center plug-in adds DB2 Table Editor menu items to the table popup menu and adds a tool bar button to start DB2 Table Editor as an add in tool. To install the DB2 Table Editor Control Center Plug-in: 1. Copy the following files and directories to the SQLLIB\cc: - db2forms.jar - One or more of the following license files. – dbehost.lic – dbe400.lic – dbework.lic You must copy the license file that corresponds to the platform on which the DB2 database to which you want to connect resides. - HtmlHelp Directory (Including all sub folders) By default this directory is SQLLIB\cc. The Control Center requires that these files be located in the Java classpath so that they can be loaded when the Control Center is started. 2. Copy the version of db2plug.zip that corresponds to the version of DB2 that you are using, into SQLLIB\cc directory. There are two version of db2plug.zip: db2plug.v6zip and db2plug.v7zip. If you are using DB2 Version 6, then copy db2plug.v6zip, if you are using DB2 V7, then copy db2plug.v7zip. 3. Rename the release specific version that you copied to: db2plug.zip Note: If there is already another version of db2plug.zip in SQLLIB\cc, you must combine the contents of the existing db2plug.zip and the DB2 Table Editor db2plug.zip. For Example, if you are using the Zip utility, use the following command: zip -r0 db2plug.zip com\companyname\myplugin\*.class Where the plug-in package name is: com.companyname.myplugin 4. Locate the db2cc file in the SQLLIB\bin. If you are using Windows, the file is named db2cc.bat. If you are using the Unix or Linux, the file is named db2cc. 5. Update db2cc to include both ?db2plug.zip? and db2forms.jar. The file names must follow a -c option. With newer releases of DB2, you must add the -c option. If you are using an older version of DB2 which has the -c option specified in db2cc, you can append the values to the end of the existing -c option. The following is an example of db2cc after you have added the files if you are working with DB2 V6: IF "%1" == "wait" GOTO WAIT db2javit -j:"CC" -d:"CC" -c:"db2plug.zip;db2forms.jar" -o:"-mx128m -ms32m" -a:"%1 %2 %3 %4 %5 %6 %7 %8" GOTO END :WAIT db2javit -j:"CC" -d:"CC" -c:"db2plug.zip;db2forms.jar" -w: -o:"-mx128m -ms32m" -a:"%2 %3 %4 %5 %6 %7 %8 %9" GOTO END :end The following is an example of db2cc after you have added the files if you are working with DB2 V7: IF "%1" == "wait" GOTO WAIT db2javit -j:"CC" -d:"CC" -c:"db2forms.jar" -o:"-mx128m -ms32m" -a:"%1 %2 %3 %4 %5 %6 %7 %8" GOTO END :WAIT db2javit -j:"CC" -d:"CC" -c:"db2forms.jar" -w:-o:"-mx128m -ms32m" -a:"%2 %3 %4 %5 %6 %7 %8 %9" GOTO END :end 6. If you are running the Control Center as a Java applet, complete the following steps: a. Copy the db2forms.jar file where the tag points to in db2cc.htm. b. Update db2cc.htm to include db2plug.zip and db2forms.jar in the archive list. You can now start Table Editor from within Control Center by selecting a DB2 Table Editor menu item from the Table popup menu or the new tool bar button. If you are running the Control Center as a Java applet, complete the following steps: 1. Copy the db2forms.jar file where the tag points to in db2cc.htm. 2. Update db2cc.htm to include "db2plug.zip" and "db2forms.jar" in the archive list. 5 .0 CORRECTIONS TO DOCUMENTATION To obtain the latest documentation updates refer to the Support Flashes category: http://www.ibm.com/software/data/db2imstools/support.html To obtain the latest refresh of DB2 Table Editor publications refer to: http://www.ibm.com/software/data/db2imstools/library.html If you are connecting to an Informix database using DB2 Table Editor Java Player, you must specify the values for the following applet parameters in your HTML file: Where: Informix_Server - Specifies the name of the Informix server from which the JDBC applet will run. Informix_port - Specifies the port number that the JDBC applet server is listening on. Informix_Database - Specifies the name of the Informix database to which you want to connect. Informix_host – Specifies the name of the Informix host. For more information on connecting to Informix databses, see "Connecting to an Informix Database" in the DB2 Table Editor Java Player online help. For more information on setting applet perameters see "Applet Parameters" in the DB2 Table Editor Java Player online help. 6.0 SERVICE For a complete and up-to-date source of DB2 Table Editor information, including information on issues discovered after this readme was published, go the to following websites: DB2 Table Editor Product: http://www.ibm.com/software/data/db2imstools/index.html DB2 Table Editor Publications: http://www.ibm.com/software/data/db2imstools/library.html DB2 Table Editor Online Support: http://www.ibm.com/software/data/db2imstools/index.html If you are not able to find your answer searching the listed URLs, call 1-800-237-5511 to speak to an IBM representative for assistance. 7.0 FUNCTIONALITY NOT SUPPORTED There are four restrictions to the DB2 Table Editor functionality in Version 4.3 fixpak 1 - In DB2 Table Editor Java Player viewing a LOB in a form that contains ROWID data is not possible. This is only applicable when accessing data from DB2 on z/OS. You can view LOBs accessed from DB2 on z/OS in forms that do not contain ROWID data. - In order to insert 100 or more rows at a time you must change the following values in your Server Definition (SDF) file. NumDynamicSectionsForCall=100 NumDynamicSectionsWithHold=100 NumDynamicSectionsWithoutHold=100 In the example above the value of 100 indicates the number of rows that can be inserted at a time. Change this number to the number of rows that you want to insert. The maximum allowable value here is 999. - In DB2 Table Editor Java player, buttons that launch LOBs are not supported - In the DB2 Table Editor Console, all creator names must be 8 characters or shorter. 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 Notices of other companies XMLParser.Java, AELfred, Version 1.1: AElfred, Version 1.1 Microstar's Java-Based XML Parser Copyright (c) 1997, 1998 by Microstar Software Ltd. Home page: http://www.microstar.com/XML/ Licensing Terms: "AElfred is free for both commercial and non-commercial use and redistribution, provided that Microstar's copyright and disclaimer are retained intact. You are free to modify AElfred for your own use and to redistribute AElfred with your modifications, provided that the modifications are clearly docuented." Disclaimer: "This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of merchantability or fitness for a particular purpose. Please use it AT YOUR OWN RISK." 8.2 Trademarks and service marks. The following terms are trademarks or service marks of the IBM Corporation in the United States or other countries or both: DB2 IBM 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.