Subject: Hot fixes for VisualAge TeamConnection Version 3 Fixpak 1
Date: November 16, 1998


Hot Fixes
---------
  Hot fixes are interim fixes shipped by the VisualAge TeamConnection
  development team that do not follow the normal (planned) fixpak schedule.
  These fixes are tested, but not through our normal regression test cycle.
  They are available to customers to use at their own risk.
  THEY SHOULD ONLY BE APPLIED TO INSTALLATIONS AT VERSION 3, FIXPAK 1 LEVEL.

Hot Fixes Shipped
-----------------
    Hot Fix #1 - 11/12/1998  (as I301hotfix1os2.zip for Intel/os2 and
                                           I301hotfix1win.zip for Intel/win )

<<HotFix1 Begin >>
****************************************************************
This is a server only update, no client parts are included

31928, 31946   Have the web client and repository use the optimized PartView views.
                 This is a significant performance fix.
31651           DriverMember -delete fails with internal error 6021-139.
31965           Builder Modify fails with a constraint violation

           fhmkrnl.dll   (NT)
           FHMhttpd.dll  (NT)
           fhmbuild.dll  (NT)
           fhckrnl.dll   (OS2)
           FHChttpd.dll  (OS2)
           fhbbuild.dll  (OS2)
           _tcbuild.bnd
           tccollc.bnd
           fhcfgfld.bnd
           _tcbase.bnd
           admerge.bnd
           adobject.bnd
           adlink.bnd
           fhcversn.bnd
           tctrans.bnd
           advroot.bnd
           fixup.bnd
           fhccntxt.bnd
           session.bnd
*****************************************************************

In addition, for Windows five files, 'readme.tc' for each language, are included.
These are replacement readme.tc files for those on the V301 CD.
'readme.tc' explains how to apply the DB2 service and patches to WIN
systems.  They are not installed or copied from the CD.

<HotFix1 end >>

--------------------
INTEL Installation
--------------------
    Unzip the appropriate file.
    Note: In order to unzip the hot fix zip file, some versions of unzip
            may require the file I301hotfix1.zipos2 or I301hotfix1.zipwin
            be renamed to *.zip .

    Please apply the changes for server installs.
    No TeamConnection process should be running.
    Make backups of the existing dlls in the 'teamc'\dll directory,
    and replace with the three updated dlls.
    Backup the '*.bnd' files in the 'teamc'\nls\cfg directory,
    and copy the 13 bnd files.

    Before installing the V3.0.1 hotfix over the V3.0.1 code,
    it is HIGHLY recommended that you back up your TeamConnection database
    using the DB2 Backup command. The syntax of the DB2 backup command is:

    'db2 backup database family_name to backup_directory'

    Substitute your family name for family_name and a directory path for your
    backed up database for backup_directory. The DB2 backup utility will place a
    compressed version of the database in the backup directory path. Be sure to
    set file permissions for the backup directory such that the compressed backup
    file is accessible.

    Note: For details on backing up DB2 databases, see the DB2 Universal
    Database Administration Guide. Also refer to the TeamConnection
    Installation Guide for information on using the backup command.

    After backing up your family database, you must rebind using the new
    bnd files.  Syntax is :
        fhcirt  loadfiles (TC_FAMILY must be set to the family
                                            name being processed)
    for example, with TC_FAMILY set to 'family1'  and TeamConnection installed
    in 'f:\teamc',
        fhcirt f:\teamc\nls\cfg\*.bnd
    will rebind family1.

 A Rexx command file, HOTAPPLY.CMD, has been provided to  automate this task.
 DB2 database backup should be run before using HOTAPPLY.  Original parts
 will be renamed with .hf1 filetypes before HOTAPPLY copies the hotfix parts.
 Windows users should use 'rexx hotapply' from a command prompt.
 (DB2 for WinNT includes a version REXX ).


** end of file **