

       IBM VisualAge TeamConnection Version 3.0.1 Fixpack - README.TXT
       --------------------------------------------------------------

Welcome to VisualAge TeamConnection Enterprise Server Version 3.0.1!
 
This file contains information you will need to install the V 3.0.1
Fixpack on both Unix and Intel Platforms.

 
The file is divided into the following sections:
   -  Important Fixpack Information
   -  Installing the Fixpack
   -  What was Fixed in the Fixpack
   -  Getting Help
   -  Service and Technical Support
   -  New Function in VisualAge TeamConnection Version 3.0.1
       -  XML Support
       -  Part Versions Support
   -  Known Problems in VisualAge TeamConnection Version 3.0.1
   -  Additional Information as of October 1998
   -  Sample Parser Files
   -  Trademarks
   -  Your Satisfaction

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

Important Fixpack Information
---------------------------------

If you are installing VisualAge TeamConnection fixpack over Version 3.0,
please read this ENTIRE section on backing up and updating your database.

Back Up Your Database
---------------------

Before installing the V3.0.1 fixpack over the V3.0 code,
you MUST 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.
 
Update your V3.0 Database
------------------------
The fixpack code installs a utility that
you need to run that updates the V3.0 database. The utility, called
FHCIRTUP.EXE, adds new tables, adds new columns to existing tables, and
populates the tables where necessary.

The syntax of FHCIRTUP.EXE is as follows:

fhcirtup databaselocation loadfiles

* Intel Platform

For example, on the Intel platform, to update the database on drive
f: to the family1 family name, set TC_FAMILY=family1 and issue the following
command (on a single line):

fhcirtup f:\teamc\nls\cfg\*.ddl f:\teamc\nls\cfg\*.ddv 
%TC_DBPATH%\cfgfield\*.ddv
f:\teamc\nls\cfg\*.ddx f:\teamc\nls\cfg\*.bnd

where TC_DBPATH is directory name that was set in your environment.

Note: The directory path \teamc\nls\cfg is the default installation path on
Intel for the TeamConnection DB2 files needed to create tables and views and
bind the family database. If you specify an installation path other than the
default, make sure the path you specify for the loadfiles parameter contains
the TeamConnection DB2 files.


* UNIX platform

In UNIX, to migrate data from a database to the family1 family name, set the
TC_FAMILY environment = family1 (using: export TC_FAMILY=family1) and then
issue the following command (on a single line):

fhcirtup $TC_HOME/nls/cfg/*.dd*
$TC_HOME/nls/cfg/*.bnd $TC_DBPATH/cfgField/*.ddv

where TC_HOME and TC_DBPATH are the directory names that were set in your
environment.

----------------------------------------------
UNIX and Intel Platforms - Database Reorg Script
------------------------------------------------

Running the Database Reorg Script after fhcirtup:

TeamConnection ships with a database reorg script that you should use after
making significant changes to a family.  A significant change might be
loading the family, adding lots of new parts, or making numerous part
changes. You should definitely run the reorg script after running the
fhcirtup command. This process should produce the optimal statistics and
performance. 

The procedure for running the reorg script differs
depending on whether you are in UNIX or on the Intel platform.

For UNIX servers, the reorg script you should run after running fhcirtup is
called: analyzeReorg
This file is located in ${TC-HOME}/samples/ksh

For Intel servers, the reorg command is called analyzeR.cmd. The
procedure for running this command is as follows:

1. Copy analyzeR.cmd from the fixpak\SPECIAL directory to your teamc\bin directory.

2. On NT, start a db2 command window (you don't have to do this for OS/2)

3. Backup the database. The syntax for doing this is:

      db2 backup database family_name to backup_directory

4. Run the following command:
      db2 connect to dbname      (where dbname is the family)

5. Run the following command:

      db2 reorgchk update statistics on table user > reorgchk.out

This will check all the tables that were created by this user and produce
an output file.

6. On OS/2, run the following command:

     analyzeR.cmd reorgchk.out

   On NT, run the following command:

     rexx analyzeR.cmd reorgchk.out

This will create a file with the necessary commands to reorg the
tables and indexes and to run the runstats command, which updates the
statistics in the DB2 catalogs.

7. Run the output of step 6.

   For example, if the output of step 6 is reOrg033.cmd, you would run
   the following command:  reOrg033 dbname.

8. Run fhcirt \teamc\nls\enu\*.bnd

This allows DB2 to recalculate the optimal access plans for the static sql
in the TeamConnection application.

Note: teamc report -view commands use dynamic sql so the rebind is not
necessary if you are having problems with views.

9. Backup the database.

This process should produce the optimal statistics and performance.

NOTES:
-  On NT you have to submit db2 commands from a db2 command window.
   You can run the db2cmd command from a dos command window to get one.

-  Sometimes, rather than running the reorg script, it is sufficient just to
do a runstat and rebind. In any event,  the reorg script will reorg any
tables or indexes that were flagged by db2 as needing a reorg.

Possible problem with fhcirtup can be ignored
--------------------------------------------

When upgrading to V3.0.1 you might encounter a problem in which duplicate
entries are found in the fhclevelmember table for a workarea. The
fhcirtup command is supposed to delete the duplicates and also add a unique
index to prevent this from happening, but under certain circumstances,
it may fail. If this process does fail, you can ignore the error message as
the duplicate entries will not effect the operation of the program or
the integrity of the database.

A fix for this annoyance is forthcoming.

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


Installing the Fixpack
----------------------

Important: Before installing the fixpack, make a backup copy of your
TEAMCV3.INI file. This file contains your GUI client settings.
After the installation is complete, you can replace
the newly installed TEAMCV3.INI file with your customized one.


** Installing the Fixpack in OS/2 **

To install the fixpack in OS/2, do the following:

   1. Download the fixpak image from the IBM service disk.

   2. Unzip the file c:/fixpakX.zipos2

      where     "c:" is the drive to which you have downloaded the fixpak
                "X" is the current fixpak number

   3. From the directory where you downloaded and unzipped the fixpak,
      type the following at the OS/2 command prompt:

                CD ENU
                install

   4. Press Enter.

   5. Follow the on-screen prompts.


** Installing the Fixpack in Windows **


To install the fixpack in Windows, do the following:

   1. Download the fixpak from the IBM service disk.

   2. Unzip the file c:/fixpakX.zipwin

      where     "c:" is the drive to which you have downloaded the fixpak
                "X" is the current fixpak number

   3. From the directory where you downloaded and unzipped the fixpak,
      type the following at the Windows command prompt:

                CD ENU
                setup

   4. Press Enter.

   5. Follow the on-screen prompts.

   ***********************************************************
   *  NOTE:
   *  The installation requires that you have double
   *  the space required for the product (80mg).  When the fixpak
   *  is installed, InstallShield will replace the existing
   *  product files, but will believe it needs enough free
   *  space to install the entire product.  When installation
   *  is complete, the product WILL only use the minimum amount
   *  required (40mg).
   ***********************************************************


** Installing the Fixpack in UNIX **

The instructions for installing the fixpack in UNIX are located in the root
directory of the CD in the file called readme.install.

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

What was Fixed in the Fixpack
-----------------------------

The following is a list of various defects that were fixed in V3.0.1.
The list was generated from our database and the descriptions do not
appear in complete sentences. We apologize for this inconvenience.

The categories of fixes are:

    Client Server
    Web Client
    Merge Tool
    Build
    GUI
    Install
    Lotus Notes
    SCC


The following are Client/Server related and miscellaneous defects that were
fixed in the fixpack:

 
30014   dbcreate hangs with low diskspace available
30048   Audit.log on AIX not adding StoreObjects tag after partadd/bui
30902   dynamic build fails
31179   Lock leak in report -view workAreaView -long
31613   fhcirt fails on drop if instance is empty SQLSTATE=58031
31732   release -extract doesn't support include/exclude lists
31091   Help for 'Select Preference File' does not work
31226   TcNotes fails when Notes installed on R/O Lan drive danjou
30691   Add back in unique flag for DriverMember
31306   FHCChange::ChangeGetListForFile sorts badly
31452   Add priority to PartView fields.
23384   ADSQLServer fails on large columns
24287   fhclcnfg causes access violation on Win/NT if TC_DBPATH not se
24441   fhcirt -c not graceful when database already active
24502   Change workarea -undo
24522   ResponseTime: report -view changeView
30071   reinstate Unique Index FHCConfgTypeName
30081   ResponseTime: vaTC: report -view defectView where name=nnn raw
30132   ResponseTime: verifyLogin
30148   Add index to ADLink_Target for build performance
30341   add UNIQUE to appropriate partView indexes
30428   Indexes to aid driver processing, views with drivers
30434   SQL error on bCompView -raw report
30476   ResponseTime: defect -modify
30505   Prioritized order for view joins
30544   allow makeall to run out of build dirs
30641   Startup: reduce LOGPRIMARY
30653   create index on fhcFile(osrelCollectorId,oid)
30933   SQL errors driverMember delete and driver commit.
30981   Scalability: part -create x -parent Many -none -builder xbldr
31426   PartView performance -- schema evolution
31441   fhcirt -c fails when *.ddl not included
31459   Drop dropped indexes in schema evolution
31487   Drop redundant index fhcWorkareaName
31579   add verbose option to fhcirtup
31581   new parsing in    fhcirt   poorly formatted
31583   Scalability: Reduce use of ADObject::_getClassLevel
31615   ResponseTime: driver -complete (add column to index)
31871   Obsolete index should be dropped in database upgrade
30165   tcwhat info for OS/2 has wrong driver
30323   tcadmin strings: add ellipsis ... to several entries in pull d
30101   tiv : teamcpak needs to pass return code 0 - 255 for build
30949   Solaris hangs on fhchdf
31015   Build Activities are not in audit.log
31023   When using Export/Import, dropDate changes from NULL to blank.
31064   tcbv or the gui returns recursive output is sibling outputs
31170   Scalability: workarea -integrate vs. rel cardinality
31368   tcbv should write error msgs to stderr
31394   Memory Leak in teamcbld
31444   UNIX: watch for single quotes in userexit.cpp
31483   teamcbld doens't erase empty output files
31504   tcbv should return a msg if the part specified is not found
31542   fixcrlf strips trailing spaces
31548   teamcbld messes with tabs/spaces
31556   build/regtest errors
31557   misc fhcirtup stuff
30112   Envy bridge query incorrect for configmaps - import/get
31074   Fix for the /LINKSEPARATE problem
21622   Short Circuit Already Current Refreshes
23552   Fix record created messages no longer in mail.
24668   ResponseTime: List % TCPart
24986   Driver commit fails - driverMember not integrated
25019   0010-498 has release name instead of workarea name.
25339   signal 2 on OS/2 teamcd if .tbl file has extra line
25408   typo in view name should not recycle daemon
30094   OS/2 - Build server fails with general protection fault.
30140   Parent of source not out_of_date when change to dependent undo
30141   HasChildren still yes after only child disconnected
30236   AIX: daemons recycling prematurely
30284   ResponseTime: teamc report (tx overhead)
30735   partview report not returning parameter data
30953   Scalability: workarea -integrate vs. growing build tree
31082   netXferFromNetFileStats doesn't do anything on non-OS2 platfor
31108   tcstop needs to break  DB2 connections on NT
31135   Deleting output part doesn't delete builder or change status
31152   Scalability: part -checkIn dependent vs. build tree complexity
31298   Build looping when parameter includes a part -connect command.
31360   do not default remarks string of initial version
31381   Part -overrideRestrict -cancel fails saying it doesn't exist
31432   No sibling output in bpartview when input deleted
31558   Common links lost after part deleted.
31651   DriverMember -delete fails with internal error 6021-139.
31833   userExits choke on \( and \)
30124   anybody can create a workarea no matter their authority
30873   user exit 1 failure gives unnecessary message
31268   Can create workarea with duplicate name of a driver
30199   Cannot grant access to components for new user

The following are Web Client related defects that were fixed in the fixpack:

30452   The words "Attribute", "* = required", and "Value" in the
30718   Can't query on nullness of an attribute
30987   cannot create part with -empty attribute (hello.exe, hello.obj
31011   Web Interface: Defect prefix value not updated
31014   v300 client not compatible with v310 server for checkout
31042   remarks for PartCheckIn should be a textarea.
31124   Nees part -extract now that we have create/checkin/checkout
31742   PartViewContents-extraneous data when viewing part contents
31764   required config. field for part not shown on PartCreate dialog
31853   Read all data from socket before sending anything.
31946   Add PartView enhancements to WebClient


The following are Merge Tool related defects that were fixed in the fixpack:

24828   Selecting merge session from file menu creates new entry
30369   Prime from the GUI does not work
31648   Color names are not translated properly
31403   tcMerge: compare of 2 binary files fail with a java exception


The following are Build related defects that were fixed in the fixpack:

23612   Parser output discard on OS/2
23665   daemon tries to delete non-existent file
30174   teamcbld on NT does not work if build dir contains blanks
30635   Java parser
30941   Variable $(BUILDERPARMS) not replaced in build parameters
30955   TSMC - parsing broken on V3
31294   disconnecting an output part from a build tree caused the
31595   build parser samples need attention
31654   rexx parsers can not handle extra params
31708   Sample parsers are not being built on OS/2
30896   EDCENV dd missing in RUNPGMT sample jcl
30928   MVS builder needs to be recycled to solve memory fragmentation
31010   MVS Builder runs out of memory for very large files
31047   STORAGE problems for MVS teamcbld
31326   temp dataset for cdf chunking runs out of space
31357   Log file takes up persistent space on MVS
31519   Some messages are not handled properly on MVS builder


The following are GUI related defects that were fixed in the fixpack:

20052   GUI-UNIX HP Phasefound field attached to defect window sizing
24765   ResponseTime: report -view config
25214   Preference file selection doesn't work on OS/2
25257   WIN:'Modified field label color' on GUI Settings not working
25294   partfullview icon view does not indicate deleted parts
25412   teamcgui dies if 'Field Type' dialog has values on 1st row.
25473   The footer in the Unix gui for tree-view windows doesn't displ
30007   'Required on Accept' config. field not shown as required in gu
30036   AIX: tcmerge: empty information window after exiting from show
30043   AIX: when using details view in the ini file, the windows are
30049   AIX Client / AIX server - GUI goes down durning part create, c
30115   in UNIX, do not use ctrl+D as hot key for Execute in Tasks lis
30116   part extract into Intel, ignores crlf conversion setting in Ex
30208   GUI-SOL: Core dump when editting a part
30312   NLV:Win/95-Jpn: Product Information Window has corrupts
30325   UNIX: Problem with Components -View dialog
30349   GUI-UNIX:Multitude of problems editting task list
30364   various problems with shortcuts & hotspots in Unix gui
30365   problem hotspots in N/T gui
30480   Remove tcg2 from the build
30541   Filter button in TaskList window doesn't work for PartsOutView
30620   GUI-UNIX:Action->Release->Modify->Name is not an option
30729   GUI-UNIX: Icon view for Change History looks like a tree view
30734   A strange dialog box comes up when you test the connection to
30739   When I try to select a large number of files for check-in from
30821   When I do a query component like %  I get the components but a
30847   GUI-HP: Remove duplicate symbol from combo boxes
30860   Solaris: cannot show help associated with a particula configur
30878   Select multiple workareas from workarea view and GUI only used
30888   GUI-UNIX: Fix the footer in v301
30891   Allow GUI to be rebuilt from build page
30983   UNIX -AIX: abrubt ending when selecting settings from window m
30985   choices for configurable fields not displayed on 'Open Defect'
31093   UNIX: Delete Components dialog does not come up
31094   Add a timestamp to entries in teamc.log file
31131   NT: V3, File -> Print -> Window List prints columns that are n
31149   Headings wrong on table format output.
31180   Solaris: coredumps exiting some views
31196   UNIX:Part Create/Release Create dialogs don't display correctl
31283   There are missing icons in the teamcgui panel.
31361   UNIX GUI:  does not display change history
31364   UNIX gui does not repaint the screen properly  on part selecti
31474   UNIX: The input fields are overlaped.
31563   NLV-JPN: Win/NT has corrupt messages in teamcgui
31718   JPN-Win/95: messages are corrupt in teamcgui
31766   Change the query used for show->parts->changed
25227   multiple selection problem on configurable fields for os2/aix
23512   Creating Family dialog disappears if user clicks on 'Stop'
30326   NLV: tcadmin not handling DBCS correctly
30459   NLV: different fonts in Family Server & Notification Server
30474   'Save as' dialog in tcadmin only saves to default directory
30697   In "Field Type" panel, can not see the whole vaules for the Fi
30756   Can not go to the 'Table' page after moving all the items of '
30795   tcadmin needs to call tcstop family@hostname@port
30814   Win/NT: Can bring up 2 families with same port number
31054   Once you press "stop" on Progress Dialog, it remains disabled
31117   UNIX: invalid message issued when updating configurable fields
31177   Stop button not working on 'Updating Family..' dialog
31276   TCADMIN dumps core when attempting to start a family
31434   Make the Family Servers window fully sizeable
31505   User Exit dialogs are missing environment variables
31546   KOR-OS/2: 'Preview' doesn't work for all the Object except Wor
31592   3 Actions not working on User Exit Settings dialog
31631   Update the swingall.jar file to the 1.0.3 level
31646   TCAdmin- missing column names
31873   Preview Button non-functional
30089   release filter dialog not sized corrrectly to fit all fields
30724   teamcgui crashes trying to invoke "find" from edit pulldown
30929   expand fully a component tree from the gui causes


The following are Install related defects that were fixed in the fixpack:

30202   NT - Start testfam not removed by uninstall
30216   WIN- change install default directory
30261   Client-only WinNT image needs Client Wizard copied
30511   FHCCMNC2.MVS not in install image.
30822   Can not bring up 'Register' program.
31007   WIN- disable 'F1' help during setup.
31310   Uninstalling server looses dlls needed by client.
31493   add db2UpdateChangeView.ksh to install C for Unix Platforms
30177   uninstall leaves some directories
31178   Delete tcserver.ok and tcclient.ok files from tc_home
30154   strange behavior when using symbolic link for target directory
30523   tcinst.ksh should recognize that DB2 UDB is installed, even wi
30701   tcstop stopped the daemons for current user even if input fami
31194   tcstop on UNIX (Solaris) doesn't work


The following are Lotus Notes related defects that were fixed in the fixpack:

30121   Feature Open missing Release field
30838   Setup Wizard problems
30840   Remove review documents from views
30876   History table out of alignment.
30890   Reconcile stops if user not authorized to delete docs
31113   Migration support for defect 30840
31128   Support Web publishing and browsing of tc notes db's
31172   Setup form Finish Button error from defect 30872
31192   Final update to Summary of changes document in base database
31600   Retain original remarks in  defect/feature in Notes document.
31762   Use release name 3.01 and change Setup reconcile default


The following are SCC related defects that were fixed in the fixpack:

21682   TeamConnection settings dialog box displays
25343   VB - Can't add parts to TC from Network drive. No way to acces
25400   Visual C++ - Can't access parts through SCC unless on local ma
30213   scc bridge from Java keeps asking me to login
30435   SccDiff API is not working
30447   SccProperties displays the TC GUI where input is allowed.
30481   SCC un-loads when SCCLOG is active
31429   Remove of parts through SCC does not always work.
31518   Port address limited to 4 digits (max value 9999).


===========================================================================
Getting Help
------------
 
   Available Documentation
   -----------------------
 
   The following is a list of the TeamConnection publications.  These
   publications are available in Adobe Acrobat (PDF) form.  To access
   the Acrobat softcopy files, either install the softcopy publications
   component during installation or go to one of the following directories
   on the product CD-ROM:

   softpubs/en_US          (for AIX and Solaris)
   softpubs/en_US.iso88591 (for hpux10)

               or

   nls\doc\<lang>  (for Intel)
 
   See the file called readme.pub in the directories above for instructions
   on how to obtain a free copy of the Acrobat Reader Version 3.0 or higher
   from the Adobe homepage.  The file also provides information about printing
   PDF files on a PostScript printer.
 
   IMPORTANT NOTE:  Due to the diversity of PostScript printer drivers and
                    configurations available, it may be necessary to print
                    segments (page ranges) of a document at a time to obtain
                    a complete printed document.

 
   Documents Available in Printed and PDF form:

     Getting Started with the TeamConnection Clients (SC34-4552):  getstart.pdf
     User's Guide (SC34-4499):  usrgde.pdf
     Administrator's Guide (SC34-4551):  admgde.pdf
     Commands Reference (SC34-4501):  cmdref.pdf

     These documents are installed as part of the VisualAge TeamConnection
     product.

   Hardcopy-only Documents:

     Quick Commands Reference (SC34-4500)
     Staying on track with VisualAge TeamConnection processes poster (SC34-4558)

   Softcopy-only (HTML, PDF, ASCII) Documents:

     Installation Guide (GC34-4742)  (install.pdf)

     Release Notes (relnotes.pdf, relnotes.htm)

     Note:  These documents are available on the product CD-ROM.  They are 
            located in the softpubs/<lang> (for UNIX) or nls\doc\<lang>  
            (for Intel) directory. 

   DB2 Quick Beginnings Documents (HTML):

     Go to the db2pubs\<lang> directories on the product CD-ROM.  The master
     files for each platform are as follows

        Windows NT      db2i6.htm (The Japanese version is: sqlr6mst.htm)
        OS/2            db2i2.htm (The Japanese version is: sqlr2mst.htm)
        UNIX            db2ix.htm (The Japanese version is: sqlrxmst.htm)


   Technical Reports and White Papers:

     See the IBM VisualAge TeamConnection Library home page for the most
     up-to-date list of technical reports.

     For important information regarding database tuning and configuration
     controls, refer to the VisualAge TeamConnection Software home page at:

        http://www.software.ibm.com/software/ad/teamcon  ("Library" item)


   Software dependencies:

   Please refer to the VisualAge TeamConnection Software home page at:

        http://www.software.ibm.com/software/ad/teamcon  ("Downloads" item)

   for pointers to the appropriate levels of Java, Adobe Acrobat, Netscape
   and operating system fixes required for VisualAge TeamConnection 
   Version 3.0.1.


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

Service and Technical Support
-----------------------------
  
VisualAge TeamConnection Services!

VisualAge TeamConnection services offerings will provide customers with the 
tools to quickly establish a more productive and efficient development 
environment. These services offerings focus on the LAN library component of 
VisualAge TeamConnection and on the Repository function of VisualAge 
TeamConnection.
 
If you are interested in the VisualAge TeamConnection Services, select the 
"Support" item at:  

        http://www.software.ibm.com/software/ad/teamcon

 
VisualAge TeamConnection Support!

If you have a question or a problem, please take a moment to review the 
Customer Support section from any of the manuals for the VisualAge 
TeamConnection product.
 
Your options for VisualAge TeamConnection support, as described in 
your License Information, include the following information (subject to 
availability).
 
 
IBM LOTUS PASSPORT ADVANTAGE PROGRAM

For more information on the IBM Lotus Passport Advantage volume licensing 
program which provides customers with a series of contract offerings under 
which they can acquire licenses, software subscriptions, and support, go to:

        http://www.lotus.com/passportadvantage
 

DB2 SERVICE MAINTENANCE AND TECHNICAL LIBRARY

To download the latest service maintenance for DB2, use the DB2 Service and 
Support on the World Wide Web at:

        http://www.software.ibm.com/data/db2/db2tech

Note: Even though DB2 is bundled with VisualAge TeamConnection you should 
contact VisualAge TeamConnection Support to report DB2 problems. The 
licensing for VisualAge TeamConnection does not entitle you to contact 
DB2 Support directly.  For a complete and up-to-date source of DB2 
information, use the DB2 Product and Service Technical Library, in English 
only, on the World Wide Web at:

	http://www.software.ibm.com/data/db2/library

 
FOR NORTH AMERICAN CUSTOMERS
 
ELECTRONIC FORUMS
 
You can access VisualAge TeamConnection technical information, exchange
messages with other users, and receive information regarding the
availability of FixPaks by logging on to the following news group: 

   news://news.software.ibm.com/ibm.software.teamcon
 

In the United States, call 1-800-547-1283.
 
 
Internet
 
Go to the IBM homepage, http://www.ibm.com. Use the search function with 
keyword TeamConnection to go to the VisualAge TeamConnection area.
Access the TeamConnection directory in our ftp site. Use ftp and
login as anonymous to ftp.software.ibm.com. In the directory
ps/products/teamconnection you can find fixes and information
related to VisualAge TeamConnection.
 

Telephone Support
-----------------
  
Direct customer support is provided by the Personal Systems Support Line and 
by the AIX Support Line. These fee services enhance customers' productivity 
by providing voice and electronic access to the IBM support organization. 
They will help answer questions pertaining to usage, "how to," and suspected 
software defects for eligible products.


The following are phone numbers for software support in the US:

United States:
Personal Systems Support Line:  1-800-237-5511
AIX Support Line: 1-800-CALL-AIX (1-800-225-5249)
Canada            1-800-IBM-SERV (1-800-426-7378)


Note: In the US, 1-800-237-5511 is the Software Support phone number for
all IBM software (390, OS/400, AIX, Personal Systems, etc.). You may call
this number and take the option for OS/2 - DOS support, which then
transfers you to 1-800-992-4777 for the Personal Systems (workstation)
products, or you may call 1-800-992-4777 directly.

 
Obtaining product information packages:
 
United States     1-800-IBM-CALL (1-800-426-2255)
Canada            1-800-IBM-CALL (1-800-426-2255)
 
Ordering TeamConnection products:
 
United States     1-800-IBM-CALL (1-800-426-2255)
Canada            1-800-IBM-CALL (1-800-426-2255)
 
TeamConnection education:
 
United States     1-800-IBM-TEACh (1-800-426-8322)
Canada  1-800-IBM-TEACh (1-800-426-8322)
 
While we may not be able to respond to or resolve all problems and questions, 
your satisfaction with our products and support is important to us. If you 
cannot access these forums, contact your IBM representative. There are 
several other support offerings available after purchasing IBM VisualAge 
TeamConnection.

If you live within the U.S.A., call any of the following numbers:

- 1-800-237-5511 to learn about available service options
- 1-800-IBM-CALL (1-800-426-2255) to order products or get general information
- 1-800-879-2755 to order publications.
  

SUPPORT FOR CUSTOMERS OUTSIDE NORTH AMERICA

For information on how to contact IBM outside of the United States, see 
Appendix A of the IBM Software Support Handbook, which can be located by 
selecting the "Service Offering" item at:

        http://www.ibm.com/support

Note: In some countries, IBM-authorized dealers should contact their dealer 
support structure instead of the IBM Support Center.

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

New function in TeamConnection Version 3.0.1:
-------------------------------------------
  
* DB/2 Universal Database Version 5 support.
* Java-based TCAdmin GUI
* Lotus Notes Integrated Databases
* Web Client for TeamConnection
* Microsoft Source Code Control API Integration
* New Build Server for MVS and MVS/OE 
* VisualAge TeamConnection Enterprise Server Bridge
* VisualAge TeamConnection VisualMerge Facility
* Solaris support
* Tivoli Software Distribution Packaging support
* Configurable Fields updates
* Shadowing capability
* Report -general command for customizing reports
* XML Support
* New Commands for Part Versions

With the exception of the last two items in the above list, the
VisualAge TeamConnection Release Notes contain detailed descriptions of
these Version 3.0.1 features. Information on XML Support and on New Commands
for Part Versions follows in the next section of this README file.

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

XML Support
----------

TeamConnection Version 3.0.1 now has limited XML support. Specifically, it
supports the following actions:
- get(retrieve)
- put(store)
- list
- query
- testServer

This initial implementation is the starting point for future
XML work.

Regarding the use of the above actions, we have made the following
assumptions:

- PUTs will contain the entire set of objects in the views.  TeamConnection
will perform a merge operation on the server and remove old objects.  Old
objects are those that appear in the original view (on the server) but are
not in the incoming XML stream. 

- There is currently no support for the explicit locking of objects as
a separate XML request.  We will, however, allow locking during a GET (see the
GET section below).

- Relationships/links between objects can be represented in different
ways in XML (ie. embedded objects vs. separate objects).  While TC will
handle both cases in the incoming XML stream, we will only generate XML
streams using one of these formats.  As of now we do not use embedded
objects.

- The get, put and list function can only be performed on versioned objects
while the query function can be performed on either versioned or unversioned
objects. 


Format of the incoming XML stream/request
-----------------------------------------
The XML request coming to XML needs to have a specific MIME header:
    verb url HTTP/1.1
    HOST: tc-hostname:tc-portnum
    Authorization: Basic encoded-password
    Content-Type: text/xml
    Context-Length: xxx (only on PUTs)

    incoming-xml-stream(only on PUTs)

Notice the 'Content-Type' tag.  The XML interface will only recognize
'text/xml' type of streams.

XML requests that support options expect the format of the URL to be:
      http://url?option1=value1&option2=value2...

(At the end of this section are some sample request/response XML streams.)

As previously mentioned, V3.0.1 only supports 7 verbs.
- get
 The URL should be in the form:
    release/workarea/view/part-name?option=value-pairs
 Workarea, view and part-name are optional and should be used to reduce the
 scope of the requested data.  For example, a request of 'r' will return
 an XML stream containing *all* of the parts in the release 'r'; 'r/w' will
 return all of the objects in workarea 'w' in release 'r'; 'r/w/BuildView' will
 return all of the objects contained in all of the BuildView's visible in 'r/w';
 and 'r/w/BuildView/foo.exe' will return just the objects in the BuildView rooted
 off of the part called 'foo.exe'.

Part names containing slashes '/' should not be treated any differently.  So
a URL request of 'r/w/BuildView/src/main/main.exe' will return all of the
objects in the BuildView for src/main/main.exe.

 Supported options:
     lock
       - type: Boolean
       - action: Will lock the TCPart's being retrieved if 'true'
     force
       - type: Boolean
       - action: Will break common links (if needed during a lock) if 'true'

Sample:

  getxml get http://dugnt:8765/r/w/buildviewonelevel/src/tcrs/deviant/exe

  HTTP/1.0 207 Multi-Status
  Server: VisualAge TeamConnection/3.1.0
  Content-Type: text/xml
  Content-Length: 1765

  <?xml version="1.0" ?>
  <?xml:namespace ns="DAV:" prefix="D" ?>
  <?xml:namespace ns="http://dugnt:8765/" prefix="E" ?>
  <?xml:namespace ns="http://dugnt:8765/TCPart" prefix="F" ?>
  <?xml:namespace ns="http://dugnt:8765/FHBGeneratesInfo" prefix="G" ?>
  <?xml:namespace ns="http://dugnt:8765/FHBuildEvent" prefix="H" ?>
  <?xml:namespace ns="http://dugnt:8765/FHBTransformedByInfo" prefix="I" ?>
  <D:multistatus>
   <D:response>
    <E:TCPart id="360262f1-4e47-000e-0000-000000000000">
     <F:adName>src/tcrs/deviant/exe</F:adName>
     <F:systemTimeStamp>1998/09/18 09:41:06</F:systemTimeStamp>
     <F:lastUpdateTimeStamp>1998/09/18 09:41:06</F:lastUpdateTimeStamp>
     <F:buildStatus>out_of_date</F:buildStatus>
     <F:type>text</F:type>
     <F:parser/>
     <F:lockedBy/>
     <F:generatedBy href="#360262f2-30a3-0015-0000-000000000000"/>
    </E:TCPart>
    <E:FHBGeneratesInfo id="360262f2-30a3-0015-0000-000000000000">
     <E:controller href="#360262f2-7d06-0012-0000-000000000000"/>
     <G:PartTimeStamp>1998/09/18 09:41:14</G:PartTimeStamp>
     <G:pBE href="#360262f2-7d06-0012-0000-000000000000"/>
    </E:FHBGeneratesInfo>
    <E:FHBuildEvent id="360262f2-7d06-0012-0000-000000000000">
     <H:adName>1339.0</H:adName>
     <H:systemTimeStamp>1998/09/18 09:41:06</H:systemTimeStamp>
     <H:beTS/>
     <H:builderRC>0</H:builderRC>
     <H:outputFileParms/>
     <H:builder>noop</H:builder>
     <H:buildParms/>
     <H:translates relPosn="0">360262fa-3ca0-0033-0000-000000000000</H:translates>
    </E:FHBuildEvent>
    <E:FHBTransformedByInfo id="360262fa-3ca0-0033-0000-000000000000">
     <E:controller href="#360262f2-7d06-0012-0000-000000000000"/>
     <I:PartTimeStamp/>
     <I:includeFlag>0</I:includeFlag>
    </E:FHBTransformedByInfo>
   </D:response>
  </D:multistatus>

- retrieve
    This is just like 'get' and might/should be removed.

- put
The URL should be in the form:
  release/workarea/view/part-name?option=value-pairs
The incoming XML stream must have an initial "multistore" element that contains
all of the objects that are to be stored.  The root object must the
part-name specified in the URL.  The 'view' specified in the URL is used to
determine which the list of 'old' objects to remove from TC.

When a new subclass of TCPart is created there are 2 attributes that must be
specified:
     adName
     component

When a new non-TCPart is created a controller attribute, referencing the
object's controller, must be specified:
    <F:controller href="controllers-guid">

In order to delete subclasses of TCPart (actually you can use this for plumbing
objects too) there is a special DELETE XML element:
    <E:DELETE id='object-guid'>

These delete elements should appear first in the XML stream (see the sample
below). 

Supported options:
 createComponents
   - type: Boolean
   - action: Will create components as needed if 'true'
 force
   - type: Boolean
   - action: Will break common links on checkin (if needed) if 'true'

 component
   - type: String
   - action: Specifies the default component to use if it's not specified
     as an attribute on the object.


Sample:

   getxml put http://dugnt:8765/r/w/TCPart/newpart inputFile

   where 'inputFile' contains:

   <?xml version="1.0" ?>
   <?xml:namespace ns="DAV:" prefix="D" ?>
   <?xml:namespace ns="http://dugnt:8765/" prefix="E" ?>
   <?xml:namespace ns="http://dugnt:8765/TCPart" prefix="F" ?>
   <D:multistore>
     <E:DELETE id='360262f3-5e88-0012-0000-000000000000">
     <E:TCPart id="360262f1-5e47-000e-0000-000000000000">
      <F:adName>newpart</F:adName>
      <F:component>c</F:component>
      <F:lastUpdateTimeStamp>1998/09/18 09:41:06</F:lastUpdateTimeStamp>
      <F:type>text</F:type>
      <F:parser/>
      <F:lockedBy/>
     </E:TCPart>
   </D:multistore>

- store
    This is just like 'put' and might be removed.

- list
  This is very similar to 'get' except only key pieces of information about
  the root object is returned.

Sample:

  getxml list http://dugnt:8765/r/w/buildview/%

  HTTP/1.0 207 Multi-Status
  Server: VisualAge TeamConnection/3.1.0
  Content-Type: text/xml
  Content-Length: 1008

  <?xml version="1.0" ?>
  <?xml:namespace ns="DAV:" prefix="D" ?>
  <?xml:namespace ns="http://dugnt:8765/" prefix="E" ?>
  <?xml:namespace ns="http://dugnt:8765/TCPart" prefix="F" ?>
  <?xml:namespace ns="http://dugnt:8765/FHBuildEvent" prefix="G" ?>
  <D:multistatus>
   <D:response>
    <E:TCPart id="360262f1-4e47-000e-0000-000000000000">
     <F:adName>src/tcrs/deviant/exe</F:adName>
    </E:TCPart>
    <E:FHBuildEvent id="360262f2-7d06-0012-0000-000000000000">
     <G:adName>1339.0</G:adName>
    </E:FHBuildEvent>
    <E:TCPart id="360262f9-3a77-002c-0000-000000000000">
     <F:adName>src/tcrs/deviant/obj</F:adName>
    </E:TCPart>
    <E:FHBuildEvent id="360262fa-744a-002f-0000-000000000000">
     <G:adName>1347.0</G:adName>
    </E:FHBuildEvent>
    <E:TCPart id="36026319-15ac-004a-0000-000000000000">
     <F:adName>src/tcrs/deviant/c</F:adName>
    </E:TCPart>
    <E:TCPart id="36026327-6718-0065-0000-000000000000">
     <F:adName>src/tcrs/deviant/h</F:adName>
    </E:TCPart>
   </D:response>
  </D:multistatus>

- query
The URL should be in the form:
   release/workarea?sql=query
The results of the query look like the following:

Sample:

 getxml query http://dugnt:8765/r/w?sql=select+name,buildstatus+from+buildviewonelevel

 query http://dugnt:8765/r/w:1?sql=select+name,buildstatus+from+buildviewonelevel
 HTTP/1.0 200 Ok
 Server: VisualAge TeamConnection/3.1.0
 Content-Type: text/xml
 Content-Length: 622

 <?xml version="1.0" ?>
 <?xml:namespace ns="DAV:" prefix="D" ?>
 <?xml:namespace ns="http://dugnt:8765/" prefix="E" ?>
 <resultSet query="select name,buildstatus from buildviewonelevel">
  <E:row>
   <E:NAME>src/tcrs/deviant/exe</E:NAME>
   <E:BUILDSTATUS>out_of_date</E:BUILDSTATUS>
  </E:row>
  <E:row>
   <E:NAME>src/tcrs/deviant/obj</E:NAME>
   <E:BUILDSTATUS>out_of_date</E:BUILDSTATUS>
  </E:row>
  <E:row>
   <E:NAME>src/tcrs/deviant/c</E:NAME>
   <E:BUILDSTATUS>success</E:BUILDSTATUS>
  </E:row>
  <E:row>
   <E:NAME>src/tcrs/deviant/h</E:NAME>
   <E:BUILDSTATUS>success</E:BUILDSTATUS>
  </E:row>
 </resultSet>

- testServer
    The URL should be in the form:    /

Sample:

 getxml testServer http://dugnt:8765/

 HTTP/1.0 200 Ok
 Server: VisualAge TeamConnection/3.1.0
 Content-Type: text/xml
 Content-Length: 292

 <?xml version="1.0" ?>
 <?xml:namespace ns="DAV:" prefix="D" ?>
 <?xml:namespace ns="http://dugnt:8765/" prefix="E" ?>
 <E:testServer>
  <E:family>vgtstest</E:family>
  <E:user>dug</E:user>
  <E:version>3.1.0</E:version>
  <E:os>NT</E:os>
  <E:language>English</E:language>
 </E:testServer>

****

New Commands for Part Versions
-----------------------------

Version 3.0.1 has new commands that enable you to maintain target and status
information for part versions.  This capability is necessary for situations
where multiple instances of the same executable are loaded at once.

To enable this new function, we have added:
- a new table which serves to contain the status information about each
  target and its  associated versions.
- views and a command-line interface for retrieving and updating status
  information for the desired targets and versions.
- configurable field information to part versions, which allows the user to
  maintain specific information about each unique part version as is required
  by the development process.

The syntax of the new commands are as follows:

1. teamc report -view TargetView [-table | -stanza | -raw]
2. teamc target -view -where "SQLCriteria" [-stanza | -table | -raw] [-verbose]
3. teamc target -create targetName -where "SQLcriteria" [-status statusName
     -time timeStamp-active activeValue-verbose]
4. teamc target -modify -where "SQLCriteria" [-status statusName -time
      timeStamp-active activeValue-verbose]
5. teamc target -delete -where "SQLCriteria" [-verbose]

For create, the SQL criteria will be applied to PartView, for all other
operations, the SQL criteria will be applied to TargetView. For add/delete/update operations, -verbose mode will display in raw format the list and number of rows changed. 

More detailed explanations about these commands will be provided with the next
release of the commands reference.


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

Known Problems in VisualAge TeamConnection Version 3.0.1
------------------------------------------------------

* Web Client
  The partview report command is not currently working on the web client.

* JAVA
  On Intel platforms, for TCAdmin and TCMerge to function correctly, users
  must manually add the BIN directory of their Java installation to
  their PATH statement, and CLASSES.ZIP to their CLASSPATH statement.

  On non-english versions of HP-UX 10.20 and AIX systems, there might be
  problems with certain font sizes; text characters may be truncated,
  hidden, or otherwise hard to read. This has been reported to the Java
  providers for these platforms, and may be fixed in either a future release
  of Java, or in a hotfix.


* Registration on Intel
  In some cases, multiple field specification is not supported, contrary to
  instructions in the registration form.


* Access List Checking
  Access list checking may not behave as expected in all cases.
  For example, a user whose user ID does not appear in a component's access 
  list may be able to view all TeamConnection objects for that component.


* TCMerge Help
  The TeamConnection merge tool requires the full path for its online help 
  to operate correctly.  Change the HELP environment variable in the 
  profile.family and profile.user samples profiles to the following:
      
        export HELP=$TC_HOME/www/http/$LANG
 

* TCAdmin GUI

  Documentation:
    Users should first complete the Help Settings dialog in the Family
    Administrator dialog to specify the locations of the Web Browser, 
    Acrobat Reader and the Softcopy Pubs.

  General:
  - Users may see intermittent Java exceptions when using the TeamConnection
    Family Administrator functions.  These are due to limitations of Java 
    (JFC) and can largely be ignored.

  - The minimum screen resolution required by TCAdmin is 800x600.
    640 x 480 is not a supported resolution.

  
  - Users may have some difficulty getting the context menu to display if they
    click mouse button 2 on the family icon on the TeamConnection Family 
    Administrator main dialog.  This is an intermittent problem.

  - Avoid modifying any fields in the SuperUser portion of the Required 
    Properties dialog after a family has been created.  If you wish to change 
    the Security Level of a family to "Password or Host", you can use the 
    Required Properties dialog to make this change, but do not enter a 
    password in the SuperUser section.  Use the TeamConnection client 
    Modify Password or TeamConnection Login dialog to specify a password 
    for the superuser.


  Configurable Fields:
  - Configurable fields for defects and features that were defined in TCAdmin 
    as "Required on Accept" may not display as required fields on the 
    Accept Defects and Accept Features dialogs.  This will be fixed in a 
    future release.

  - The Configurable Field Type dialog is missing the 'HelpText' column for 
    the configurable field types 'serial' and 'phone'.  They can still be used, 
    however, on all UNIX and OS/2 platforms.

  - When using TCAdmin to define a new configurable field type, do not insert 
    new values on the first row on the Field Type dialog.  Begin inserting 
    values after the first row that contains the Help Text.
 
  Family Monitor:
    For best results using the Family Monitor Window on the Family Server
    window, decrease the refresh interval down to 1 second. If the Monitor
    information is going to be ignored, increase the refresh interval to a
    large number.  These Java responsiveness issues will be addressed in a 
    future release.

  UNIX:
  
  - UNIX users may see the following message intermittently when invoking 
    tcadmin, even if the NLSPATH and TC_LANG environment variables are set 
    correctly:

    "Unable to identify the directory containing the files required by 
    TCADMIN.  Please verify your NLSPATH or user the -f parameter."

    If this occurs, just try invoking TCAdmin again.

  - UNIX users may see the following message on the TCAdmin Family Servers
    dialog when they stop their TeamConnection family server:

    "0010-495 The following error occurred: Invalid argument when the
    TeamConnection server processes the shared memory operation on the
    TeamConnection server. The TeamConnection server cannot obtain the control
    structure for shared memory. The TeamConnection server will operate  
    normally."

    This message can be ignored.

  - Driver and dependent configurable field types do not work correctly.
    This will be fixed in a future release.

  UNIX and OS/2:
  - The configurable field type 'list' does not work correctly on OS/2 and 
    UNIX platforms.  This will be fixed in future release.

  Solaris:
    On Solaris, you should not "background" (i.e., tcadmin &) the tcadmin
    script. If a user backgrounds the tcadmin script, any attempt to start
    a family within tcadmin will result in Java monopolizing all of the Motif
    resources.  In this case, no one will able to log in to the machine and it
    could possibly hang the session that it was started in, which may require 
    that your machine be rebooted. The tcadmin script already backgrounds the
    Java process that it starts by default, so backgrounding the script would
    be a redundancy.

  AIX:
    When using TCAdmin on AIX (in 1.1.2 and 1.1.4 levels of the JDK) with multiple families, 
    avoid using the context menu on the main panel due to the fact that the 
    wrong family may be chosen.  The selection area for each family overlaps 
    about 1/2 of the row below it.  This problem was fixed in Version 1.1.6 of 
	the Java Developer's Kit (JDK).

  OS/2:
    Occasionally, when TCAdmin is initialized, it will end abruptly after 
    displaying the following warning:
 
    "The settings file could not be found.  No settings were loaded."

    If this happens, retry running TCAdmin.  If the problem persists, run 
    tcadmin -log.  Once TCAdmin is run successfully, this problem should
    cease.

  Windows NT:
  - The 'Recycle Daemon' button on the Family Server dialog will stop the 
    family daemon instead of recycling it.

  - The IBM-supplied configurable field types 'serial' and 'phone' will
    not work on a Windows/NT server.  This is a permanent restriction.

  - On Windows/NT, an MS/DOS window with the teamcd daemon running in the
    foreground will display when the TeamConnection family is  started.  
    This window can be minimized.

  - Intermittently, connections to the database remain after a family is
    stopped.  As a result, users may see the following SQL message when 
    trying to drop, backup, or restore a database:

        SQL1035N The database is currently in use - SQLSTATE=57019

    The following DB2 commands can be used to force a reset:

        db2 force application all
        db2 disconect all

    The commands run asynchronously, so you must wait a sufficient amount of
    time to ensure they complete.

    The following DB2 command can be used to determine if all applications 
    have been disconnected from the database:

        db2 list active databases


* Configurable fields
  - If you have 20 configurable fields on parts,  you may get a DB2 error
    message -670, which states that the view is too large if you do a
    report -view partview -raw and specify a configurable field in the 
    'order by' clause.  Use the report -general command to limit the number 
    the columns shown.

  - When querying the config table, if you receive DB2 errors regarding 
    multiple rows returned on a scalar select, please check if the config 
    table has duplicate rows in it for the same configtype and name.  If 
    there is, correct the config.ld file and reload the config table.


* Authentication Resynchronization
  If a client logs into the Team Connection server and the server is
  recycled, sometimes the client and the server cannot resynchronize the
  authentication.  All client actions are rejected by the server.
 
  To solve the problem, terminate all of the client programs, including 
  any teamc commands, the GUI, and the login manager.  After the clients
  have been terminated, restart the client programs and log back into the
  server.  You may need to do this twice, because when a client has logged
  onto the server and attempts to log in again, the server automatically logs
  the client out; the client may not synchronize with the server correctly.
                                                                   
  Whenever the client logs into the server, a login manager is started
  automatically on the client.  This login manager runs in the background.
  To terminate this manager, issue the following command:
                                                                   
    teamc tclogin -KILL_TCLOGINMGR
 

* Windows NT 4.0 Installation Fails to Create Folders                                                                                                
  Before installing the current fullpak for Windows NT 4.0, determine
  whether your target system has IBM Anti-Virus 2.5.2 or higher 2.5.x level
  installed.  If it does, your TeamConnection installation may complete
  without errors, but fail to create folders.
 
  An interaction between the SHELL entry and InstallShield prevents
  folders from being created during installation.  This behavior occurs
  with ANY software installed on a Windows NT 4.0 system using InstallShield.
  IBM Anti-Virus 3.x fixes the problem by changing its append to SHELL.
                                                                                                                                                         
  SOLUTIONS:
        To resolve this problem, perform ONLY ONE of the following
        corrective actions:
                                                                                                                                                                      
        1. Upgrade to Anti-Virus 3.x, and then install TeamConnection.
                                                                                                                                                                      
        2. Remove IBM Anti-Virus, install TeamConnection, and then
           re-install IBM Anti-Virus.
                                                                                                                                                                      
        3. a. VERY CAREFULLY edit the SHELL registry entry located in:
 
     HKey_Local Machine/Software/MicroSoft/Windows NT/current version/winlogon
 
           b. You should see:  SHELL REG_SZ: explorer.exe,xxxxxx
              Record the portion of the string that reads ',xxxxx' (including
              comma and data), and then delete it from the entry, so that
              only 'explorer.exe' remains.
 
           c. Install TeamConnection.
 
           d. Edit the 'HKey_Local Machine/Software/MicroSoft/Windows NT
              /current version/winlogon' SHELL entry again, and restore
              the ',xxxxx' portion of the string.

 
* IPF_PATH32
  If you include IPF_PATH32 as a single pointer, and the product that
  sets that value is uninstalled and removes the variable, or a
  newly-installed product (such as VA TeamConnection) adds another 
  value that supersedes the single pointer, any products depending on 
  the single pointer (such as Workframe, PL/I, and Cobol) will no longer work.

  The solution is to change the value back to the original single pointer.  
  However, if you do this and then a product that removes this variable 
  instead of its entry (only) is uninstalled, the original problem will return.


* Files in the tmp Directory (UNIX)                                                              
  TeamConnection UNIX servers create files in the tmp directory of
  the form /tmp/TCSem_<number>.  UNIX servers also create a file called
  /tmp/TCSharedMem.<number>.  These files are entries for resources shared
  among the TeamConnection servers.  When the tcstop command is issued,
  these files are automatically cleaned up after the servers are terminated.
  If you do not use tcstop, these files will remain until you remove them.
  IT IS STRONGLY RECOMMENDED that you use tcstop to stop server daemons.
  Do NOT remove these files while the Team Connection servers are running;
  the results will be unpredictable and may jeopardize your data.  If you are
  absolutely sure that NO families are running, these files can be removed.
 
 
* Web Client
  - The PartBuild dialog does not issue any build status messages visible to 
    the user during a build.  Use the PartViewMsg dialog to view build 
    messages.

  - When using  the Netscape browser on Intel for the HTML Web client, users 
    may sometimes see page corruptions when using the frame separator bar 
    to resize dialogs.  A workaround is to click on the frame with mouse 
    button 2 and select Reload Frame to force a reload of the frame.

  - The Logout pushbutton on the VisualAge TeamConnection Common Tasks Web 
    client page will log the user off of the HTML server.  The user will  
    see the message "Authorization failed.  Retry?"  At this point, the user
    is logged out of the TeamConnection HTML server.  The user may then 
    either select Cancel, or select the OK pushbutton, at which point the 
    Login dialog is presented again.


* Lotus Notes Integrated Databases
  - For Unix environments, Lotus Notes 4.6 is recommended, although most 
    functions should work adequately on the latest version of 4.5.3 available.

  - There is no tclogin from Notes. You can either use the TeamConnection  
    command line or the client GUI. The client GUI can be opened from most 
    views in a TeamConnection Notes database.

  - If you receive the message, "Error in loading DLL", perform the 
    following steps:

        1. Edit your .profile in your home directory.
        2. Find the line containing the LIBPATH.
        3. Add :/usr/lib to the LIBPATH.
        4. Run you .profile.

  - The Release field of the Open Feature form is missing. This optional 
    field can be added using Feature Modify Properties from the VisualAge
    TeamConnection GUI or Web client.
 
  Access Control Issues:
  - The TeamConnection Notes support utilizes the hierarchical naming structure
    for Notes user IDs (for example, John Smith/Raleigh/IBM).  This means that
    individual users and users in groups should be specified in the Access 
    Control List (ACL) for your database with the hierarchical name.  Use of 
    flat names has not been fully tested and is not recommended.  The 
    documents are stored with the author's hierarchical name imbedded in 
    the document.

  - Users with special roles like Administrator and Project leader should be 
    defined as individuals and not as members of a group in the ACL.  An ACL 
    group can be defined for all the general users who will create documents.
    The group should be assigned the role of Author to permit creation of 
    numbered documents.

  Reconcile Function:
  The user running reconcile should be defined in the ACL with the authority 
  to delete documents.  Reconcile will  delete canceled defects or features if 
  the database has been setup with this option.  If this authority is not
  defined then reconcile will fail when an attempt is made to delete document 
  representing the canceled TeamConnection object.

  General Lotus Notes Issues:

 -  If you run the Notes client from a file server, the client will not
    communicate with TeamConnection correctly, and you will get a "File not
    found" message from Notes. This appears to be a Lotus Notes problem.
    Consequently, we recommend that you don't install Notes clients on file
    servers, but rather install the Notes clients locally on user
    workstations.
 
  - Lotus Notes Integrated databases inherit their document review and 
    document archiving functions from the document library template supplied
    by Lotus with Notes.  If there are problems with those functions, they 
    may be inherent in the original functionality supplied by Lotus.

  - The database archive function is inherited function from the Document 
    Library template supplied by Lotus. Testing has indicated that it will 
    archive main documents but not response documents. The archive database 
    is an empty copy of your source database.  To access archived documents,
    the Setup process must be run on the archive database.

  - The default access as defined in the TeamConnecton Notes database ACL is 
    Manager.  This allows administrators setting up databases for the first 
    time to be able to add themselves and others.  In the database an 
    administrator makes available to a user community, access should changed 
    to an appropriate level.  Author access may be appropriate, though you 
    might choose to be more restrictive.

  - Defects and features that are opened from a Notes database and
    subsequently renamed can no longer be found by the Notes database. 
    If a defect or feature is renamed you must do the following to allow
    access from Notes:
    1) Delete the Notes document representing the feature or defect.
    2) Use the "associate defect/feature" function to reestablish the 
       defect/feature in the Notes database.


* Microsoft Source Code Control Feature
  Due to certain architectural features of the Microsoft Source Code Control
  API, the TeamConnection integration with PowerBuilder, Visual Basic, and
  Visual C++ may exhibit differences in interface behavior.  The following is
  a listing of SCC feature limitations, on a by-IDE basis when appropriate.
 
  General Limitations:
  - If you modify a part path name under SCC feature control within
    TeamConnection, the part's pathname does not change name under SCC.
    Therefore, SCC operations on the newly renamed part are not reflected
    in TeamConnection.
  - TeamConnection settings dialog box may display twice when adding a project
    to SCC.  Clicking OK each time successfully adds the project to SCC.
  - If you check out a part through TeamConnection (rather than through SCC),
    you may not be able to check in the same part through SCC if you specify
    a destination directory in the Destination field.  If the Destination 
    field is left empty, SCC can check the part back in.
  - Advanced Check-in with breaking links does not work unless
    you specify the other (common) workareas that contain the part.
    It is advisable to use the TeamConnection GUI for this action.
 
  PowerBuilder
  - When PowerBuilder registers a new object with TeamConnection,
    it creates a temporary file that is stored in the TC database.  
    This file already has the "header" information (first 2 lines
    that appear during a PowerBuilder Export) before it is passed
    to TeamConnection.  These files CANNOT then be imported to
    another library; however, it does not affect normal checkin
    and checkout functionality.
  - SCC cannot be accessed by a Windows NT user who does not have 
    Windows NT Administrator authority.  The symptom for this problem
    is an error regarding registry keys that cannot be read.
  - If you have a pre-release version of the SCC feature, the configuration
    file used by PowerBuilder has an entry in the CFG file of:

                ProviderRegKey=SOFTWARE\IBM\TeamConnection

    that must be changed to:

                ProviderRegKey=SOFTWARE\IBM\VisualAge TeamConnection

  Visual Basic Limitations:
  - Under certain circumstances, the filename passed to the SCC is NOT 
    in the same case in which the part was created in TeamConnection, 
    so the SCC function call passed to TeamConnection may fail because 
    TeamConnection IS case sensitive.  This can be seen when asking for 
    a history of a part stored in TeamConnection (SccHistory call), and
    the results will indicate that the file does not exist.  It is HIGHLY
    recommended that project names be created in upper case.
  - There is no online help available.
  - For SCC running on Windows NT Version 4.0, the Add-Ins->Team Connection
    menu may have duplicate items.  All items are active.
  - Opening a project that has been added to source control before performing 
    any other task may cause Visual Basic to crash.  
  - Parts located on a network drive can not be added to TeamConnection 
    through the SCC because the path passed into the SCC contains "\\" 
    instead of a network drive letter assigned as the relative drive.
 
  Visual C++ Limitations:
  - If you are adding files to SCC and select the Select all option, all of
    the field text in the dialog is selected, but the check boxes
    associated with text are not checked.  Then, if you select ADD, you
    will receive an error message indicating that nothing is selected.
    However, if you select one of the check boxes, the other check boxes 
    are also selected.
  - After removing a part from SCC, you may not be able to add (re-register)
    it back into SCC, even though it is possible to recreate the part in
    TeamConnection.


* VisualAge Teamconnection Enterprise Server Bridge
  - To enable the VisualAge Teamconnection Enterprise Server Bridge, you must
    use the Envy/Manager-TeamConnection Bridge R1.02 configuration map for a 
    Version 3 server.  For a Version 2 server, use Envy/Manager-TeamConnection
    Bridge R1.01.

  - You must have a host list specified if you are using the 
    ENVY/Manager-TeamcConnection Bridge with a family server using HOST or 
    PASSWORD_OR_HOST security. The bridge does not support login passwords.

  - There is a known performance problem associated with the menu choice
    Tools->TeamConnection Bridge->Import Files when a large number of parts 
    exist in the database.  Until this is fixed, if you need to import files 
    from TeamConnection, it is suggested you use the TeamConnection GUI or 
    command line interface to import files.


* MVS Build Server
  A module called FHCCMNC2.MVS is packaged with VA TeamConnection Version 3.
  OS/390 Version 2 customers should rename this module to FHCCMNC.MVS before
  attempting to install an MVS build server.
 
  NOTE:  Build server installation instructions are located in the VisualAge
         TeamConnection User's Guide.

Additional Information for MVS Build Server

1. The MVS build server is built on OS/390 LE v2r4 and has been tested on
   OS/390 v2r4 and v2r5. To use it at your location, you must be at least at
   v2r4, and LE must be enabled for C++.

   If you are using OS/390 1.3, please obtain the MVS build server code for
   this version from the Visualage Teamconnection hot fix site.


 2. The following environment variables are introduced in this fixpack

- TC_BUILDER_RECYCLE_COUNT=n
  If this variable is set, then after n builds, the build server will terminate.

- TC_BUILDER_RESTART_CMD=command
  If this variable is set, then the specified command will be submitted. The
  intent is to restart the build server. For example,

   TC_BUILDER_RESTART_CMD=submit 'USERID.TEAMC.JCL(RUNPGMT)'

   This is supported only if the build server is started under IKJEFT01 as
   in RUNPGMT.

 3. @ symbol for non-English MVS environments
The @ symbols in TC_FAMILY (for example: testfam@myhost@9090) need to be in
US English, that is, x'7C'. In some non-English environments @ is at a
different codepoint. In such cases, edit the file containing TC_FAMILY, and
use x'7C' where @ is expected. 

4. The environment variable dataset (ddname EDCENV) may now be included
inline, that is: 

    //EDCENV DD *
    TC_FAMILY=..
    TC_BUILDPOOL=..
    ...
    /*


* Tivoli Software Distribution
  If you plan to the use Tivoli Software Distribution Bridge (teamcpak), you 
  must add the Tivoli "bin" directory in the PATH of the client invoking the 
  teamcpak command. This includes build servers that will invoke the softdist
  build script which uses the teamcpak command.  Also, for UNIX clients you 
  must include the Tivoli "lib" directories in the LIBPATH (AIX), 
  LD_LIBRARY_PATH (Solaris),  and SHLIB_PATH (HP-UX).  Your Tivoli 
  administrator can give you the full path name where your Tivoli managed 
  node installation is located.


* Editing Parts on UNIX Systems

  To edit parts on UNIX systems, the TMP environment variable must be set
  to a valid directory.  For example, export TMP=/tmp.


* UNIX GUI
  - Before using the UNIX GUI "teamcgui", add /usr/dt/lib to the end of your 
    LIBPATH (AIX), LD_LIBRARY_PATH (Solaris), or SHLIB_PATH (HPUX).

  - To use mnemonics, you must use the <Alt> key for the main menu item, 
    then the <Shift> key for the subsequent ones.  For instance, if you 
    want the Releases filter (Objects->Releases->Releases) you type:

        <Alt>o <Shift>r <Shift>r


* Loading Additional Models to the TeamConnection Server
  There are two methods to instruct the TeamConnection server to load  
  additional models, so that tools that are built on TeamConnection, such as
  DataAtlas, can be used.  These methods, currently undocumented, include:

  1) An environment variable, TC_MODELS.
  2) The -l option on the teamcd command.

  Refer to the tool-specific documentation (typically the product's readme.txt 
  file or User's Guide) for information on which models to load using either
  of these methods.

  VisualAge Teamconnection Enterprise Server Bridge users: The model name 
  for ENVY is _tcenvy.


* tcstop
  If more than one TeamConnection family has been created on an NT server,
  tcstop will only stop the first family created.  Users may have to use 
  the NT Task Manager to stop the second family (or enter CTRL-C).


* Workframe on NT
  There is a limitation on getting parts into a project.  The recommended
  workaround is to either extract or checkout the parts to the project 
  directory, and then select Refresh Now from the View menu.


* Version 2 Client Support
  There is limited support in Version 3 for Version 2 clients attached to a 
  Version 3 server.  This support is intended to aid current TeamConnection 
  customers in making the transition to the Version 3.0.1 product.  The
  following items are known, significant limitations of this configuration:
 
  - If you are using a Version 2 GUI client to view Defects, Features, Parts, 
    and PartFull windows with the view set to Details, any configurable 
    field data may be "off" by one or two fields in the configurable field
    columns.  Further, if you select Modify Properties from one of these 
    windows, configurable field data may or may not appear in the correct 
    fields.

  - Releases and Workareas support configurable fields in Version 3, but 
    these fields will not be recognized by a Version 2 GUI client.

  Support for Version 2 clients is intended as a short-term solution for
  customers during the migration from Version 2 to Version 3.

***

On UNIX platforms, if there are parts in the 2.0 database that do not have 
an fmode, they will be extracted during migration with the "sticky" bit set.
Migration will then fail while trying to run. To prevent this error, do the
following for each release to be migrated:

1. Run the following report on the 2.0 database (replacing yourRelease
with the name of the release):
  teamc report -view partview -release yourRelease -where "fmode is null"

2. For each part returned by this query, issue the following part -modify
command and replace partNamewith the name of each part and yourRelease
with the release it is located in:
  teamc part -modify partName -release  yourRelease -fmode 0644

***
Smart Guide for the Team Connection client install freeze

The Smart Guide for the Team Connection client install freezes 
on the Japanese Win95 operating system, requiring you to cold boot
the system. This occurs only when using the Japanese Win95
operating system.

Additonally, another WIN32 SDK function, GetStdHandle(STD_INPUT_HANDLE),
frequently returns a value of: INVALID_HANDLE_VALUE --- 0xFFFFFFFF.

Neither of these effects occur on the other platforms used by
Team Connection (including Japanese Windows NT) or in any other language.

***
HP JDK C.01.15.05 Write Bug

In either TCMerge or TCAdmin, using HP JDK C.01.15.05
and the Korean locale, Java deletes one character every
8K when writing out a file.

The most visible side effect of this occurs when
the creation of a family fails during the
"Updating the configurable types" step.

HP intends to fix its Java.  However, until then, a
hot fix will be available from IBM.

***
HP JDK DBCS character bug

In TCAdmin on HP, you cannot enter DBCS characters.
This problem has been reported to HP, and should be
fixed in a future release of HP's Java.

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

Additional Information as of October 1998
--------------------------------------
* part -delete Name command now renames files

When you delete a part, the part is renamed by adding a tilde (~) to the
begining of its original name.  For example, if you delete FOO.DOC, it is
renamed to: ~FOO.DOC. (If ~FOO.DOC already exists, it is renamed to
~~FOO.DOC, and so on.) If you want to re-create a part that was deleted, you
must re-create it using the renamed name. 

* LIBPATH environment variable for AIX CDE users

  In order to exploit the LIBPATH environment variable, you must set it in
  your .kshrc file.  If you do not export the variable in the .kshrc you will
  receive the following error messages when trying to use product:

   >> Could not load program teamc
   >> Could not load library libfhccmnc.a

  To use the .kshrc, please ensure that the following is in your .profile:

   export ENV=${HOME}/.kshrc
  An alternative is to re-source your .profile as in the following:
   . ${HOME}/.profile


* DB2 Configuration Parameters

  FHCIRT sets the following Database Configuration parameters to non-default 
  values to improve database performance and functionality:

  All platforms:

        logfilsiz  = 4000
        applheapsz = 1280
        logprimary = 5
        logsecond  = 30
        buffpage   = 12000
        dlchktime  = 1000

  Solaris:
                        
        dbheap     = 2400
        
  Intel:

        dbheap          = 600
        catalogcache_sz = 32
        maxappls        = 40
        locklist        = 50
        app_ctl_heap_sz = 128


* Samples
  There are several pieces of sample code in the samples directory.  The
  samples are not intended to be used as live code, but can be adapted to
  your site's purposes.  In particular, see files with the fhbh* naming 
  convention.

   For example, the current release includes sample COBOL parser code written
   in C.  This o code is provided so that users can modify the source
   code for the platform of their choice.  The samples directory includes the
   following COBOL parser source files:
 
        fhbcpp.c
        fhbcpp.h
        func.c


* Content Manager (Windows NT only)

  The Content Manager is an extension to VisualAge TeamConnection intended for
  use by content authors and web site developers to enable them to easily 
  access and use TeamConnection to manage their web site contents. The use of 
  Content Manager is independent of the source of the files under its control. 
  The contents can be created under any authoring or development tool.  
  The Content Manager code and readme file are available in the contentm 
  directory in the root of the product CD-ROM.


* Lotus Notes Integrated Databases
  Although Lotus Notes 4.5.3a for Intel platforms is the documented
  prerequisite, it is possible to use 4.5.1 with the following workarounds.

  - Full Screen Navigator:  The full screen Navigator does not allow you to
    Proceed to Database.  However, you can  select View->Documents->All, and 
    then select the Navigator button to see the proper navigators for the 
    database.

  - CR/LF bug in Rich Text Fields:  Pressing Enter in RTF fields generates a 
    new line, but does not move the cursor there.  The workaround is to use 
    the down arrow key.


  For detailed information regarding database tuning and configuration
  controls, refer to the VisualAge TeamConnection Software home page at:

        http://www.software.ibm.com/software/ad/teamcon  ("Library" item)
		

* Lotus Notes Changes and Upgrade Information for Version 3.0.1

1. A summary of changes is contained in a Notes document titled: Summary of
   Notes Database Changes for TeamConnection 3.0.1. This document is stored in
   the teamc.nsf database and can be seen from the "All documents" view.
 
  This document can be viewed from your Notes client, even if the database
  has not be set up, by performing the following steps:

  a) Add the teamc.nsf database file to your Notes Workspace page.
  b) Highlight the database icon and right mouse click. From the popup dialog
     select:  Go to ...
  c) From the list of displayed views select:  "All Documents". The is
     document will be listed. Open as a normal document.
 
2. Upgrading TeamConnection Notes databases from Version 3.0.0 to Version
   3.0.1

 a) To upgrade existing Notes databases to the latest version you must apply
 the 3.0.1 template fhcnotes.ntf using the Notes function "Design Replace".
 See the Chapter 8 of the User Guide for specific instructions.

 b) If your have been using the "Review Cycle function" in your Version
 3.0.0 databases it is recommended that you migrate those review documents
 using a migration agent supplied in Version 3.0.1. The agent is titled:
 Migration (3.0.1 fixpack). When you run it you will be prompted before
 proceeding.  A log of all changes will be created at the conclusion and
 stored in the database as a Notes document.


* TCAdmin now knows about families started outside of TCAdmin

If a family is started outside of TCAdmin (or by another copy of TCAdmin),
TCAdmin will not allow the family to be modified or deleted.

If this occurs, there will be a message in the Family Servers window stating:
"The family is already running outside of tcadmin."
There may also be a message in the Notification Server window stating:
"If the Notification Server was started outside of tcadmin, the output is
not available." 



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

Sample Parser Files
-------------------

The following sample parser files are shipped with TeamConnection and are
installed on the server in the SAMPLES directory

mvsasmp.c
mvsasmp.h
mvsasmp.exe (Intel only)

func.c
fhbcpp.h
fhbcpp.c
fhbcpp.exe (Intel only)

fhbwpars.c
fhbwpars.exe (Intel only)

fhbcpp1.dll (OS/2 only)
fhbcpp2.dll (OS/2 only)
fhbcpp3.dll (OS/2 only)
fhbcbp.exe  (OS/2 only)
fhbcbprs.cmd (OS/2 only)

fhbplprs.cmd (Intel only)


 
=====================================================================
 
Trademarks
----------
   The following terms are trademarks of IBM Corporation in the
   United States or other countries:
 
        AIX
        DB2
        DB2 Universal Database
        IBM
        Lotus Domino
        Lotus Notes
        OS/2
        TeamConnection
        Tivoli
        VisualAge
         
   The following terms are trademarks of other companies:
 
        Adobe                           Adobe Systems Incorporated
        Acrobat                         Adobe Systems Incorporated
        HP-UX                           Hewlett-Packard Company
        HotJava                         Sun Microsystems, Inc.
        Java                            Sun Microsystems, Inc.
        Netscape Navigator              Netscape Communications Corp.
        PowerBuilder                    Powersoft Corp.
        Microsoft Internet Explorer     Microsoft
        Solaris                         Sun Microsystems, Inc.
        VisualBasic                     Microsoft
        Visual C++                      Microsoft
        Windows NT                      Microsoft
        Windows 95                      Microsoft

 
Your Satisfaction
-----------------
Your satisfaction with IBM is important to us. If you are not totally
satisfied with this product, please contact us through one of the
Service and Technical support channels listed above.
 
Tell us what is not meeting your expectations and why you are
dissatisfied.  Provide your name, your organization's name, and
your telephone number so that we can contact you.  We will work with
you to resolve your concerns.
 
