IBM VisualAge TeamConnection 3.0.7 FixPak -
trace.txt (13-MAR-2001)
------------------------------------------
Documents
---------
backup_db.txt, fix302.ddl, fixdb.ddl, readme.txt, relnotes.txt,
restore_db.txt, systeminfo.txt, trace.txt, upgrading_to_v303HF1.txt
Main Index
----------
- Where to get the most recent version of this file
- Objective: (setting up a local or remote trace for TeamC)
- Step 1A) Set up a local trace of the family server (teamcd)
- Step 1B) Set up a remote trace of the family server (teamcd)
- Step 2) Provide an exact description of the steps
- Step 3) Zip the log files and trace
- Step 4) Send the trace to Customer Support
Where to get the most recent version of this file
-------------------------------------------------
The most recent version of this file can be found at:
ftp://ftp.software.ibm.com/ps/products/teamconnection/fixes/
Objective: (Setting up a local or remote trace for TeamC)
--------------------------------------------------------
Follow these steps to set up a trace and contact TeamConnection
Customer Support. You may choose to set up either a local trace
or a remote trace. For your ease, we suggest you view
the HTML version of this document in a web browser.
Step 1A) Set up a local trace of the family server (teamcd)
----------------------------------------------------------
You may set up a local trace (this step) or remote trace (step 1B).
Set up a local trace on the server if you are not too
concerned about the performance impact of doing the
trace and you have sufficient disk space available.
The following example sets up a 10 MEG trace.
1. Log in as the family administrator and then set up the
environment:
UNIX:
export TC_TRACE=*
export TC_TRACESIZE=10000000
WINDOWS:
set TC_TRACE=*
set TC_TRACESIZE=10000000
NOTE: you may also set TC_TRACEFILE to the absolute
path of the trace output file if you wish to
control its location. Otherwise, the output
file will be called tctrace and wll be located
in the directory where you started the family
daemon.
2. Recycle the family
tcstop [familyName]
teamcd [familyName] [numberOfDaemons] &
3. After you reproduce the problem, save the trace
UNIX
mv tctrace tctrace.1
WINDOWS
move tctrace tctrace.1
4. Stop the family and unset TC_TRACE
Step 1B) Set up a remote trace of the family server (teamcd)
-----------------------------------------------------------
Set up a remote trace of the family server if the performance impact
of doing a trace is a concern. A remote trace will be sent from the
family server (teamcd) to the remote machine running the tcrtrc
utility. (A TeamC client needs to be installed on the remote
machine.)
1. On the TeamC family server do
tcstop [familyName]
2. On the remote TeamC client machine run the
tcrtrc executable like this:
tcrtrc -p[portNumber] [traceFileName]
For example, you would type,
tcrtrc -p1234 trace.out
(WARNING: you must issue the tcrtrc command while the TeamC
family is down!)
Issue the command "tail -f [traceFileName]" to view the
end of the trace output. Once you start the family server
you will see additions being made to the trace output file.
In this way you will know the family server is communicating
correctly with the tcrtrc utility.
3. On the TeamC family server, set up the remote trace:
UNIX:
export TC_TRACE=*
export TC_TRACEOPTS=-h[remoteMachine]@[portNumber]
WINDOWS:
set TC_TRACE=*
set TC_TRACEOPTS=-h[remoteMachine]@[portNumber]
eg. assuming that jupiter is the client machine,
you would type:
export TC_TRACEOPTS=-hjupiter@1234
(WARNING: Do not stop the tcrtrc utility on the client machine
or you will break the communication between the
remote client and the family server, meaning you
will need to stop both the family server
and the tcrtrc utility in order to reestablish
communication.)
4. Start the family and then reproduce the problem.
teamcd [familyName] [numberOfDaemons] &
5. After you reproduce the problem, save the trace
UNIX
mv tctrace tctrace.1
WINDOWS
move tctrace tctrace.1
(WARNING: This step may also break communication betweeen
the family server and the tcrtrc utility.)
Step 2) Provide an exact description of the steps
--------------------------------------------------
Provide an exact description of the steps you took to
reproduce the problem, including teamc commands. Collect
the syslog.log, the audit.log, and the db2diag.log
INTEL:
syslog.log
%TC_FAMILY%\audit.log
c:\sqllib\db2\db2diag.log
UNIX:
see /etc/syslog.conf for the location of the syslog
$TC_FAMILY/audit.log
$DB2INSTANCE_HOME/sqllib/db2dump/db2diag.log.
Step 3) Zip the log files and trace
------------------------------------
Zip the log files and trace using the info-zip utilities
"zip" and "unzip" which you can download for each platform at:
ftp://ftp.uu.net:/pub/archiving/zip/
Step 4) Send the trace to Customer Support
If 3 MEG or less, send the data and the steps to
reproduce the problem to TeamConnection Support via email.
If greater than 3 Meg, ftp the data to "testcase.boulder.ibm.com"
using login "anonymous".
ftp testcase.boulder.ibm.com
NOTE: cd into the directory /ps/toibm/teamconnection
and make a directory with the name of the pmr number
to hold your files. Don't forget to use "bin" mode
to "put" the files. You will not be able to view files
you place in the "teamconnection" directory.