IBM DB2 Universal Database* for Windows** 3.x Version 5.2 FixPak WR21168 +-- Note: ----------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 11/15/99, | then you must contact IBM support instead of installing this FixPak, to | request an updated version of the interim fixes. By doing this, you are | assured that your system is in a consistent state and no interim fixes | are lost. | | Throughout this document X: is used to refer to the cdrom drive into | which the FixPak CD is placed and C:\SQLLIB is where the DB2 products | are installed. +-------------------------------------------------------------------------+ This README file contains information for the following products and components: Windows 3.1 Specific -------------------- DB2 Connect Personal Edition, V5 DB2 Software Developer's Kit, V5 DB2 Client Application Enabler, V5 --------------------------------------------------------------------------- 1. Contents of FixPak 2. Installation Notes 2.1 Pre-requisites 2.1.1 Prerequisites for APAR IX73249 2.2 Prior to Installation 2.3 Installation Instructions 2.4 Unattended Installation Instructions 2.5 After Installation 2.5.1 Rebinding to non-DRDA DB2 databases 2.5.2 Rebinding to DRDA databases 2.5.3 Rebinding Specific Packages 3. Miscellaneous 3.1 Product and Service Technical Library 3.2 Customer Support 3.3 Corrective Service For additional information please see the following files: C:\SQLLIB\WIN\RELEASE.TXT X:\APARLIST.TXT =========================================================================== 2. Installation Notes 2.1 Pre-requisites To determine if the required pre-requistes are installed, do the following: -Double-click on the 'Installation Utility' icon in the 'DB2 for Windows' folder. -Select 'View', 'Installed Products'. -Select the appropriate DB2 product. -Select 'Details', 'Product Status'. The version should be 05.00.00. -Select a component. Click on 'Service level'. The level should be 0000000. 2.1.1 Prerequisites for APAR IX73249 Incorrect Output for DB2 LIST DCS APPLICATIONS SHOW DETAIL The MVS APAR PQ11645 must be applied in conjunction with DB2 Connect APAR IX73249 in order to provide the meaningful correlation token display on both the LIST DCS APPLICATIONS and the DB2 MVS DSP THD commands. 2.2 Prior to Installation You must stop all database activity before applying this FixPak. Stop all applications and issue 'db2 terminate'. 2.3 Installation Instructions To start the FixPak install, type X:\DB2\\INSTALL\INSTALL where is the appropriate language directory. You will be presented with a list of products currently installed. Select a product and then select UPDATE from the Action pull-down menu. You must install the FixPak for every product listed (it is not necessary to re-boot after each one even if the completion message says so, it is sufficient to re-boot after all products have been updated). If you use ODBC applications, re-run the ODBC Installer after re-booting, by double-clicking on the icon. IMPORTANT: Do not select the "Save a backup version?" checkbox. This will not properly backup the changes, and restoring from the backup may damage the installed DB2 UDB product(s). This will be remedied in the future. 2.4 Unattended Installation Instructions The FixPak install program (INSTALL.EXE) uses the same syntax and response file keywords as DB2 UDB. Refer to the Quick Beginnings book for a description of these keywords. o Each product must be updated separately. o Every DB2 UDB product that is installed on the system must be updated with this FixPak at the same time. You cannot mix service levels between the products. o A /P:"product name" command line parameter is required. See the following sample command files on the first FixPak diskette for the exact product titles: DB2CONPE.BAT DB2 Connect Personal Edition DB2SDK.BAT DB2 Software Developer's Kit DB2CAE.BAT DB2 Client Application Enabler 2.5 After Installation Due to the new bind (.bnd) files that have been shipped with this FixPak, you will need to rebind your utilities against all your databases after the FixPak installation. This step is necessary for the fixes in this FixPak to become effective. The procedure of rebinding, outlined below, only needs to be performed once per database. 2.5.1 Rebinding to non-DRDA DB2 databases After applying fixes, you must do the following: db2 terminate db2 CONNECT TO db2 BIND C:\SQLLIB\BND\@db2ubind.lst GRANT PUBLIC db2 BIND C:\SQLLIB\BND\@db2cli.lst GRANT PUBLIC db2 terminate Where is the name of a database to which the utilities should be bound. Examine the DB2PATH environment variable to determine the correct path. DB2UBIND.LST and DB2CLI.LST contain lists of commonly required bind files used for DB2. If is a DB2 v1.x database, do not bind db2cli.lst. Instead, use the db2cliv1.lst or specifically bind db2clics.bnd, db2cliur.bnd, db2clirr.bnd, and db2cliv1.bnd individually. 2.5.2 Rebinding to DRDA databases If you are using DB2 Connect to access host databases, you will also need to bind the new bind files. As above, connect to the host database, and then bind the utilities as follows: HOST COMMAND ===== =================================================================== MVS BIND C:\SQLLIB\BND\@ddcsmvs.lst BLOCKING ALL SQLEROR CONTINUE GRANT PUBLIC VM BIND C:\SQLLIB\BND\@ddcsvm.lst BLOCKING ALL SQLEROR CONTINUE GRANT PUBLIC VSE BIND C:\SQLLIB\BND\@ddcsvse.lst BLOCKING ALL SQLEROR CONTINUE GRANT PUBLIC OS400 BIND C:\SQLLIB\BND\@ddcs400.lst BLOCKING ALL SQLEROR CONTINUE GRANT PUBLIC 2.5.3 Rebinding Specific Packages If you wish to bind only the specific .bnd files to the database, issue the following command for each database (where is the name of the bind file, and is the name of your database). db2 terminate db2 CONNECT TO db2 BIND C:\SQLLIB\BND\ BLOCKING ALL GRANT PUBLIC db2 terminate 3. Miscellaneous 3.1 Product and Service Technical Library For a complete and up-to-date source of DB2 information, including information on issues discovered after this readme was published, use the Product and Service Technical Library on the World Wide Web at: http://www.software.ibm.com/data/db2/library 3.2 Customer Support To speak to an IBM representative regarding assistance with this product, please call 1-800-992-4777. Customer support is also provided via Electronic Question and Answer (Q&A) forums. These forums are accessible through CompuServe, IBMLink, and Usenet Newsgroup. (1) CompuServe - To access the forums on CompuServe, execute GO IBMDB2. - If you don't have access to CompuServe, call 1-800-848-8199 for membership information in Canada or the US. (2) Usenet Newsgroup: comp.databases.ibm-db2 - This Internet Newsgroup is a general forum for discussing questions and/or problems encountered using the DB2 family of products. (3) (IBMLink) Talklink OS/2 BBS - To access the forums on IBMLink, go to the OS2BBS section. - If you don't have access IBMLink, call 1-800-547-1283 for membership information in Canada or the US. 3.3 Corrective Service Corrective service can be downloaded electronically by either: (1) FTP to anonymous server ftp.software.ibm.com (previously known as ps.boulder.ibm.com) at 198.17.57.66. Go to ps/products/db2/fixes/%L/%P/ where %L is the appropriate locale (e.g. english-us, spanish, german, etc.), and %P is the product name/version (eg. db22v5, db2aixv5, etc.). (2) Use a World Wide Web (WWW) browser to connect to the DB2 Service and Support Page at: http://www.software.ibm.com/data/db2/db2tech/index.html (3) On CompuServe, execute GO IBMDB2. Then go to the appropriate library to find the FixPak. (4) On IBM PCC BBS (in US), call (919) 517-0001 (in Raleigh, North Carolina) and then type "db2" on the main menu to find the FixPaks. If you do not have access to any of the above locations, please call 1-800-992-4777 to request these FixPaks be sent to you in the mail. For countries other than US and Canada, please contact your local DB2 Customer Service number for assistance in obtaining them. --------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. --------------------------------------------------------------------------- *************************************************************************** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1999. ** ALL RIGHTS RESERVED. ** ***************************************************************************