IBM VisualAge TeamConnection 3.0.7 FixPak - systeminfo.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.txtMain Index ----------
- Where to get the most recent version of this file - Objective - Gathering System Info - Directions - For the Platform - For the Version of TeamConnection - For the Version of DB2 - Additional Directions for FixPak v3.0.2 and lower Back to Main IndexWhere 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/ Back to Main IndexObjective: ---------
The objective of this file is to collect information about your system and the levels of TeamConnection you have installed in order to help Customer Support diagnose your problem. See "Getting Help" in the Release Notes for information contacting Customer Support. For your ease, we suggest you view the HTML version of this document in a web browser. Back to Main IndexGathering System Info ---------------------
Please fill in the table and then contact Customer Support for Visual Age TeamConnection. ==================================================================== PLATFORM: OS LEVEL FIXPAK PATCH (example WINNT 4.0 sp5.0 ???) SERVER ??? ??? ??? ??? CLIENT ??? ??? ??? ??? BUILD_SERVER ??? ??? ??? ??? VERSION OF TC: (example v303HF1 v304) SERVER ??? ??? ??? CLIENT ??? ??? ??? BUILD_SERVER ??? ??? ??? DB2: (example 5.2 fp11) ??? ??? ??? PROBLEM: (detailed steps to reproduce the problem) ==================================================================== Back to Main IndexDirections: ----------
For the PLATFORM: 1) SERVER OS/LEVEL/FIXPAK: determine the level of the operating system the TeamConnection server (teamcd) is running on. For AIX do "oslevel". For Solaris and HP, do "uname -a". For NT do "winver" on the server machine. 2) CLIENT OS/LEVEL/FIXPAK: determine the level of the operating system the TeamConnection client (teamcgui) is running on. For AIX do "oslevel". For Solaris and HP, do "uname -a". For NT do "winver" on the client machine. 3) BUILD_SERVER OS/LEVEL/FIXPAK: determine the level of the operating system the TeamConnection server (teamcbld) is running on. For AIX do "oslevel". For Solaris and HP, do "uname -a". For NT do "winver" on the build machine. Back to Main Index For VERSION of TeamConnection: 4) SERVER LEVEL/FIXPAK: determine the level of the TeamConnection server (teamcd) by running the "tclevel" command on the server machine. On UNIX, verify these results by using "what `which teamcd`". On NT, verify using "tcwhat %TC_HOME%\bin\teamcd.exe". As a last resort, verify with "teamc report -testServer". 5) CLIENT LEVEL/FIXPAK: determine the level of the TeamConnection client (teamcgui) by running the "tclevel" command on the client machine. On UNIX, verify these results by using "what `which teamcgui`". On NT, verify by using "tcwhat %TC_HOME%\bin\teamcgui.exe". Or as a last resort, verify with "teamc report -testClient". 6) BUILD_SERVER LEVEL/FIXPAK: determine the level of the TeamConnection build server (teamcbld) by running the "tclevel" command on the build machine. If this does not work, for UNIX use "what `which teamcbld`" and for NT use "tcwhat %TC_HOME%\bin\teamcbld.exe" Back to Main Index For the Version of DB2: 7) DB2 LEVEL/FIXPAK: determine the level of DB2 by running "db2level" on the server. Provide the informational token with the version, eg v5.2.0.33. Back to Main IndexAdditional Directions for FixPak v3.0.2 and lower. -------------------------------------------------
##################################################################### You don't need the following if your level of TeamC is v303 or higher ##################################################################### NOTE: tclevel was added to TeamConnection with v3.0.2 Hotfix 3. If your level of TeamConnection is earlier than FixPak v3.0.3, you can take these additional steps to help determine your level of TeamConnection A) cd to to the directory where TeamConnection is installed, INTEL: cd %TC_HOME% UNIX: cd $TC_HOME B) Search for any files of the type *.hf?, INTEL: dir /s/b *.hf? UNIX: find . -name *.hf? -print 2>/dev/null The last character of the extension should be the Hotfix number, for example, readme.hf2 would be a readme file from Hotfix 2. C) Search for any files of the type, *.1*, *.2*, *.3* INTEL: dir /s/b *.1* UNIX: find . -name *.1* -print 2>/dev/null These are files that were backed up as the Hotfix was applied. The first character of the extension identifies the Hotfix number, for example monitor.2xe would indicate that Hotfix 2 was applied. D) As a final check to verify that no Hotfix has been applied, do a long listing of the contents of the "lib" and "bin" and "nls/cfg" directories and and compare the file sizes and timestamps with the original files on the Installation CD. INTEL: dir /o-d %TC_HOME%\lib > lib.out dir /o-d %TC_HOME%\nls\cfg > cfg.out dir /o-d %TC_HOME%\bin > bin.out UNIX: ls -al $TC_HOME/lib > lib.out ls -al $TC_HOME/nls/cfg > cfg.out ls -al $TC_HOME/bin >bin.out