Subject: Hot fixes for VisualAge TeamConnection Version 3 Fixpak 1 Date: December 17, 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 ) Hot Fix #2 - 12/16/1998 (as I301hotfix2os2.zip for Intel/os2 and I301hotfix2win.zip for Intel/win ) Note: Hot Fix #2 includes all changed parts from Hot Fix #1. <> This is a server and client update, please see Installation section. ******Server****** 31995 workarea -integrate/driver -commit can overlay part changes with an older version. 32091 PMR81427 DriverMember create works when we there should be a Collision 32346 Removes a bottleneck for concurrent access to the family. This fix will improve the concurrency of read-only commands when update commands are running. 32319 cdf processing blows up on large values in workarea -export/-import 32330 Teamcbld dies when trying to remove a timed out job from the build queue. Server Parts (new) fhccmns.dll (OS2) fhcmodel.dll (OS2) fhcmystc.dll (OS2) fhmcmns.dll (NT) fhmmodel.dll (NT) fhmmystc.dll (NT) _tcmod.bnd fhcaccss.bnd fhclevel.bnd fhcpath.bnd fhcuser.bnd (per Hotfix1) fhbbuild.dll (OS2) fhckrnl.dll (OS2) fhchttpd.dll (OS2) fhmbuild.dll (NT) fhmkrnl.dll (NT) fhmhttpd.dll (NT) _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 *******Client****** 32305 allows migration of workarea versions, (like WA:1 that have colons in the name ). This is needed for V2->V3 migration of fine-grained data. 32319 cdf processing blows up on large values for workarea -export/-import 32331 PMR 82434 Expand Build tree fails with memory errors in tcbv. Client Parts fhcclint.dll (both) fhccmnc.dll (both) fhcrscli.dll (both) fhmclint.dll (WIN) fhmcmnc.dll (WIN) fhmrscli.dll (WIN) <> <> **************************************************************** 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. > -------------------- INTEL Installation -------------------- Unzip the appropriate file. Note: Unzip the hot fix zip file, with the option to create directories! The Server parts are in the SERVER directory, client parts in the CLIENT directory. The hotapply.cmd will copy/rename the appropriate files from either/both directories. >> SERVER Apply Please apply the changes for server installs from the SERVER directory. No TeamConnection process should be running. Make backups of the existing dlls in the 'teamc'\dll directory, and replace with the six updated dlls. Backup the '*.bnd' files in the 'teamc'\nls\cfg directory, and copy the 18 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 .hf2 filetypes before HOTAPPLY copies the hotfix parts. Windows users should use 'rexx hotapply' from a command prompt. (DB2 for WinNT includes a version REXX ). >> CLIENT apply No TeamConnection process should be running. Make backups of the existing dlls in the 'teamc'\dll directory, and replace with the six (WIN) or three (OS2) updated dlls. A Rexx command file, HOTAPPLY.CMD, has been provided to automate this task. Original parts will be renamed with .hf2 filetypes before HOTAPPLY copies the hotfix parts. Windows users should use 'rexx hotapply' from a command prompt. Note that while a version of REXX is always installed on the VATC server (ships with DB2), REXX may not be present on VATC clients. ** end of file **