***
*** This file has been placed in the FixPak302 image
*** for information only.  The CD referenced is the
*** original VisualAgeTeamConnection CD.
***
IBM VisualAge TeamConnection Enterprise Server Version 3.0 
----------------------------------------------------------------------

Welcome to VisualAge TeamConnection Enterprise Server Version 3.0!

This file contains information you need for installing the DB2 FixPak
and interim fixes to DB2 required by TeamConnection.  The DB2 FixPak
instructions have been updated to include steps for applying the
fixes from the VisualAge TeamConnection cdrom.

The DB2 fixes are located as follows (where 'Z:' refers to the cdrom drive):
     This file................................ Z:\dbfilesw\fixes\en\readme.tc
     DB2 FixPak............................... Z:\dbfilesw\fixes\en
     DB2 interim fixes for TeamConnection..... Z:\dbfilesw\fixes\hotfixtc

Please, follow the instructions below to apply the DB2 FixPak and
interim fixes that are required by VisualAge TeamConnection 3.0.




 IBM DB2 Universal Database* for Windows 95** and Windows NT** Version 5.0
                              FixPak WR09044
                            ID: 5.0.0.WR09044

+-- Note: ----------------------------------------------------------------+
|
| To read this file more easily, set your font to monospace.
|
| If you have received interim fixes from IBM support after 10/29/97,
| 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 drive onto which the FixPak is unziped
|     Z: is used to refer to the VisualAge TeamConnection cdrom
|     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, V5
 DB2 Connect Enterprise Edition, V5
 DB2 Universal Database Enterprise Edition, V5
 DB2 Universal Database Workgroup Edition, V5
 DB2 Universal Database Personal Edition, V5
 DB2 Universal Database Extended Enterprise 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 Install Instructions
2.5 After Installation
  2.5.0  Copy VisualAge TeamConnection interim fixes
  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\RELEASE.TXT
    X:\APARLIST.TXT


===========================================================================

2.  Installation Notes

2.1 Pre-requisites

This Fixpak requires that at least one Version 5.0.0 DB2 for NT/95 product
already be 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\<product name>\Current Version.
The values should be the following:

   Version           "0x00000005" (5)
   Release           "0x00000000" (0)
   Modification      "0x00000000" (0)
   Service Level     ""

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

You must stop all database activity before applying this FixPak.  Stop all
applications and issue the commands:

   db2stop
   db2admin stop


2.3 Installation Instructions

     1)  Copy and unzip 9044.zip to a temporary subdirectory
         (e.g. pkunzip -D -O 9044.zip X:\tempdir)

     2)  To start the FixPak, run X:\tempdir\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.  The following sample response
files are included in this FixPak:

    DB2CONPE.RSP    DB2 Connect Personal Edition
    DB2CONEE.RSP    DB2 Connect Enterprise Edition
    DB2UDBEE.RSP    DB2 Universal Database Enterprise Edition
    DB2UDBWE.RSP    DB2 Universal Database Workgroup Edition
    DB2UDBPE.RSP    DB2 Universal Database Personal Edition
    DB2UDEEE.RSP    DB2 Universal Database Extended Enterprise Edition
    DB2SDK.RSP      DB2 Software Developer's Kit
    DB2CAE.RSP      DB2 Client Application Enabler

**************** HOTFIX *******************
2.5 After Installation

2.5.0  Copy VisualAge TeamConnection interim fixes (HOTFIX)

    Copy 2 files -- 'db2dmgr.dll' and 'db2sqn.dll'
    from Z:\dbfilesw\fixes\hotfixtc to C:\SQLLIB\dll


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 <dbname>
       db2 BIND C:\SQLLIB\BND\@db2ubind.lst GRANT PUBLIC
       db2 BIND C:\SQLLIB\BND\@db2cli.lst GRANT PUBLIC
       db2 terminate

Where <dbname> 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 <dbname> 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 <bind_file> is the name of
the bind file, and <dbname> is the name of your database).

       db2 terminate
       db2 CONNECT TO <dbname>
       db2 BIND C:\SQLLIB\BND\<bind_file> 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 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.


---------------------------------------------------------------------------

*  are trademarks or registered trademarks of IBM Corporation.
** are trademarks or registered trademarks of their respective owners.

---------------------------------------------------------------------------

***************************************************************************
**
**  (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1998.
**                    ALL RIGHTS RESERVED.
**
***************************************************************************
