Welcome to DB2* for Windows** 95 & Windows NT** v2.1 FixPak 8116 +-- Note: ----------------------------------------------------------------+ | | After installation is complete, you will need to re-bind the DB2 | utilities against all of your databases. Refer to section 2.2 for | details. | | If you have received interim fixes from IBM support after 10/02/96, | then you should contact IBM support after the FixPak installation, 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. | +-------------------------------------------------------------------------+ For installation instructions please see section 2.1 This README file contains information for the following products and components: NT/95-Specific -------------- IBM DB2 Client Application Enabler for Windows 95 & Windows NT --------------------------------------------------------------------------- 1. Contents for FixPak 2. Installation Notes 2.1 Information for Installing this FixPak 2.1.1 Pre-Requisites 2.1.2 Installation Instructions 2.1.3 Unattended Installation Instructions 2.1.4 Handling File Copy Errors 2.2 Rebinding bind files - IMPORTANT 2.2.1 Rebinding to DB2 common server databases 2.2.2 Rebinding to DRDA databases 2.2.3 Rebinding Specific Packages 3. Miscellaneous 3.1 DB2 Family Newsletter 3.2 Customer Support 3.3 Corrective Service For additional information please see the following files. README.TXT APAR.LST =========================================================================== 2. Installation Notes 2.1 Information for Installing this FixPak 2.1.1 Pre-Requisites This FixPak does not require any DB2 for NT/95 products to be installed on the machine. It cannot be installed onto SDK for NT/95. 2.1.2 Installation Instructions Note: You must stop all database activity before applying this FixPak. This includes stopping the database manager, closing all DB2 command windows, and stopping all DB2 services. To begin the FixPak installation, run SETUP.EXE. If installing from floppy disks, this file will be on disk 1. If installing from hard disk or CD, this file will be in a DISK1 subdirectory. When SETUP is finished loading you are presented with a WELCOME screen. Click on "Next" to continue. Setup will determine what DB2 products are currently installed on your machine, and will automatically select these products for updating. To begin the update, click on "Install" on the following screen. When the installation has finished, you must reboot your machine to activate the changes. 2.1.3 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: setup /R /L where is a file outlining how to install the FixPak. specifies the fully-qualified log file name, where setup information and any error information from setup is logged. A sample response file, DB2SETUP.RSP, is included on disk 1. For each product you wish to update, a separate setup must be performed. For further information, please see the "IBM Database 2 for Windows** 95 & Windows NT** Installation and Operating Guide, Version 2", document number S33H-0312-01. 2.1.4 Handling File Copy Errors Setup attempts to replace certain files in the Windows system directory, if the current versions of these files are lower than that required by DB2. However, if a file is currently in use by another application or service, Setup will be unable to replace it. Setup logs the error message returned by the operating system during the failed copy operation and notifies the user that an error has occurred. To remedy this situation: o Shut down any other running applications. o Stop any services that are running. o Run Setup again. 2.2 Rebinding bind files - IMPORTANT Due to the new bind (.BND) files that have been shipped with this FixPak, you will need to rebind your DB2 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.2.1 Rebinding to DB2 common server databases After applying fixes, you must do the following: - At a command prompt: db2 terminate db2 CONNECT TO db2 BIND \@db2ubind.lst BLOCKING ALL GRANT PUBLIC db2 BIND \@db2cli.lst BLOCKING ALL GRANT PUBLIC db2 terminate or, - At the DB2 command line: TERMINATE CONNECT TO BIND \@db2ubind.lst BLOCKING ALL GRANT PUBLIC BIND \@db2cli.lst BLOCKING ALL GRANT PUBLIC TERMINATE Where is the name of a database to which the utilities should be bound, and where is the full path name of the directory where the bind files are located, such as \sqllib\bnd. 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.2.2 Rebinding to DRDA databases If you are using DDCS to connect to host databases, you will also need to bind the new bind files to the host. As above, use the DB2 Command Line Processor to connect to the host database, and then bind the utilities as follows: HOST COMMAND ======= =================================================== MVS BIND \@ddcsmvs.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VM BIND \@ddcsvm.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VSE BIND \@ddcsvse.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE OS400 BIND \@ddcs400.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE Please refer to Chapter 4 "Binding Applications and Utilities" of the DDCS User's Guide for a list of what bind files are used for your specific client operating system. If a bind file changes but your clients do not use that bind file, you do not need to re-bind it. 2.2.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). - At a command prompt: db2 terminate db2 CONNECT TO db2 BIND \ BLOCKING ALL GRANT PUBLIC db2 terminate or, - At the DB2 command line: TERMINATE CONNECT TO BIND \ BLOCKING ALL GRANT PUBLIC TERMINATE 3. Miscellaneous 3.1 DB2 Family Newsletter For the latest information about the DB2 family of products, you may subscribe to the "DB2 Family Newsletter" (English only). Simply send your request in a FAX to 1-905-316-4733, and include the following information: Name Company name Full mailing address Telephone number DB2 products you currently use 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 They can be downloaded electronically from the following locations: (1) CompuServe - Execute GO IBMDB2 - then go to the DB2/OS2 library to find the DB2/OS2 FixPak - or go to the CLIENTS library to find the SDK/Win FixPak. (2) Internet - FTP to anonymous server ftp.software.ibm.com (previously known as ps.boulder.ibm.com) at 198.17.57.66 - then go to ps/products/db2/fixes// where is (eg. english-us, spanish, german, etc.) is the product name/version (eg. db22v21, db2winv21, etc.) - Use a World Wide Web (WWW) browser to connect to the DB2 Service and Support Page. (http://www.software.ibm.com/data/db2/db2tech/index.html) (3) IBM PCC BBS (in US) - Call (919) 517-0001 (in Raleigh, North Carolina) - Then type "db2" on the main menu to find the FixPaks The above are the primary locations where these FixPaks are uploaded. They may also be available on other Bulletin Boards (such as the Talklink OS/2 BBS in the US). 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 look at your local IBM OS/2 BBS or call 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 1996. ** ALL RIGHTS RESERVED. ** ***********************************************************************