IBM DB2 Universal Database* Version 6.1 for Windows 95** and Windows NT** PTF No: WR21302 VRMF: 06.01.0000.0060 +-- Note: ----------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 2002/04/01, | 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: NT/95 Specific -------------- DB2 Connect Personal Edition, V6.1 DB2 Connect Enterprise Edition, V6.1 DB2 Universal Database Enterprise Edition, V6.1 DB2 Universal Database Workgroup Edition, V6.1 DB2 Universal Database Personal Edition, V6.1 DB2 Universal Database Extended Enterprise Edition, V6.1 DB2 Software Developer's Kit, V6.1 DB2 Datalinks Manager, V6.1 DB2 Administration Client, V6.1 DB2 Run-Time Client, V6.1 DB2 Satellite Edition, V6.1 DB2 Query Patroller, V6.1 --------------------------------------------------------------------------- 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 Install 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 2.5.4 DataJoiner Replication Administration Tool 2.5.5 Rerun db2classes.exe on the web server 2.6 Uninstallation Notes 2.7 Stored Procedures with PROGRAM TYPE MAIN 2.8 Java Method Signature in PARAMETER STYLE JAVA procedures and functions 3. Miscellaneous 3.1 Product and Service Technical Library 3.2 Customer Support 3.3 Corrective Service 3.4 MIN_DEC_DIV_3 Database Configuration Parameter For additional information please see the following files: C:\SQLLIB\RELEASE.TXT X:\APARLIST.TXT =========================================================================== 2. Installation Notes 2.1 Pre-requisites This Fixpak requires that at least one Version 6.1 DB2 UDB for NT/95 product be already installed on your system. To determine the version and level of the currently installed DB2 product, type regedit from an MS-DOS prompt and check the following values under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\\CurrentVersion. The values should be the following: Version "6" Release "1" Modification "0" Service Level "WR21163" 2.1.1 Prerequisites for APAR IX73249 Incorrect Output for DB2 LIST DCS APPLICATIONS SHOW DETAIL The DB2 for 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 It is recommended you stop all database activity before applying this FixPak. To do this, please stop all applications and issue the commands: db2stop db2admin stop 2.3 Installation Instructions To start the FixPak, run X:\SETUP.EXE. 2.4 Unattended Install Instructions The version of SETUP.EXE shipped with this FixPak is capable of running via an "unattended install" option. The syntax for this feature is documented in the Quick Beginnings book. A sample response file (DB2FIXPK.RSP) is included in this FixPak: 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 SQLERROR CONTINUE GRANT PUBLIC VM BIND C:\SQLLIB\BND\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VSE BIND C:\SQLLIB\BND\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC OS400 BIND C:\SQLLIB\BND\@ddcs400.lst BLOCKING ALL SQLERROR 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 2.5.4 DataJoiner Replication Administration Tool The location of the DataJoiner Replication Administration (DJRA) tool (djra.exe) is now installed in the directory SQLLIB\DJRA. 2.5.5 Rerun db2classes.exe on the web server If the Control Center was served as an applet using the V6.1 GA of DB2 UDB on Win32 platforms, after installing the fixpak you must re-run db2classes.exe on the web server. 2.6 Uninstallation Notes When upgrading or uninstalling the DB2 product(s) on a Windows NT system, it is recommended that you manually shut down all DB2 services and processes on your machine. 2.7 Stored Procedures with PROGRAM TYPE MAIN To ensure family compatibility, PROGRAM TYPE MAIN stored procedures have been changed to pass in the procedure name as the first argument (ie, argv[0]). Existing PROGRAM TYPE MAIN stored procedures can be changed to use this feature by incrementing the indices used to access the argv[] argument array. Alternatively, the original behaviour of PROGRAM TYPE MAIN for Version 6.1 can be restored by turning on the registry variable DB2_RESTORE_PTMAIN_BEHAVIOUR 2.8 Java Method Signature in PARAMETER STYLE JAVA procedures and functions If specified after the Java method name in the EXTERNAL NAME clause of the CREATE PROCEDURE or CREATE FUNCTION statement, the Java method signature must correspond to the default Java type mapping for the sql signature specified after the procedure or function name. For example, the default Java mapping of the SQL type INTEGER is 'int', not 'java.lang.Integer'. If the signatures do not match, and exception will be raised when the procedure or function is invoked. 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 from 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. 3.4 MIN_DEC_DIV_3 Database Configuration Parameter The addition of the MIN_DEC_DIV_3 database configuration parameter is provided as a quick way to enable a change to computation of the scale for decimal division in SQL. It is possible that this may not continue as this exact same database configuration parameter in the future. Default=NO. Values: YES, NO. This db cfg parameter changes the resulting scale of a decimal arithmetic operation involving division. If the value is NO, the scale is calculated as 31-p+s-s' (see SQL Reference, Chapter 3, "Decimal Arithmetic in SQL"). If set to YES, the scale is calculated as MAX(3, 31-p+s-s'). This causes the result of decimal division to always have a scale of at least 3 (precision is always 31). Attention: Changing this db cfg parameter may cause changes to applications for existing databases. This can occur when the resulting scale for decimal division would be impacted by changing this db cfg parameter. Here are some possible scenarios that may impact applications. A view that was defined in an environment with one setting could fail with SQLCODE -344 when referenced after the db cfg parameter was changed to the other setting if the resulting scale of one of the view columns is changed. The message SQL0344N refers to recursive common table expressions, however, if the object name (first token) is a view, then you will need to drop the view and create it again to avoid the error. A static package will not change behaviour until the package is rebound, either implicitly or explicitly. For example, after changing from NO to YES, the additional scale digits may not be included in the results until rebind occurs. For any static packages that may experience this change, an explicit rebind command can be used to force a rebind. A check contraint involving a decimal division may restrict some values that were previously accepted by the check constraint. Such rows now violate the constraint but will not be detected until the one of the columns involved in the check constraint row is updated or SET INTEGRITY with IMMEDIATE CHECKED is processed. To force checking of such a constraint, ALTER TABLE to DROP the check constraint and then ALTER TABLE to ADD the constraint again. If any of these scenarios are possible on a database server with existing databases, the implications of changing the MIN_DEC_DIV_3 setting should be carefully considered. Also Note: there are no new message text for this parameter in the v6 or v71 timeframe. This implies the following two limitations: 1) The command "GET DB CFG FOR " will not display the MIN_DEC_DIV_3 setting. The best way to determine the current setting is to observe the side-effect of a decimal division result. For example, if the following db2 statement: VALUES (DEC(1,31,0)/DEC(1,31,5)) Returns sqlcode sql0419n, then the database does not have MIN_DEC_DIV_3 support or it is set to OFF. But if the statement returns "1.000", then MIN_DEC_DIV_3 is ON. 2) The command "? UPDATE DB CFG" displays a list of "config-keywords". MIN_DEC_DIV_3 does not appear in the list. --------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. --------------------------------------------------------------------------- *************************************************************************** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001. ** ALL RIGHTS RESERVED. ** ***************************************************************************