During the process of SNA problem determination, it often becomes necessary to submit trace information to IBM SNA technical support. IBM Communications Server for AIX includes a getsnapd script which facilitates the collection of many traces and logs into a single compressed tar file. This file is referred to as a testcase. The purpose of this document is to provide the basic steps involved in collecting an SNA testcase. Specific steps included in this document are for IBM Communications Server for AIX Version 4.2.
Be aware that this version of Communications Server is no longer supported. Support ended on November 30, 1998. New defects discovered in this version will not be corrected.
This document applies to IBM SNA Server/6000 V3.1, IBM Communications Server V4, and AIX levels 4.1.5 and above.
Related documentation
For additional information about IBM Communciations Server, see the IBM Communications Server V4R2 manuals:
http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/Shelves/ASY0BK01
The AIX 4.3 and hardware product documentation library is also available:
http://www.rs6000.ibm.com/resource/aix_resource/Pubs/index.html
Whenever possible, stop SNA and delete old SNA logs and traces. This produces cleaner traces, making troubleshooting much easier. If SNA must not be stopped, skip the first five steps below, to begin with the first sna -setlogs command. Be aware, however, that this could make isolating the problem more difficult.
Before starting SNA, reconfigure the logs and start new traces. This process will require space in both the /tmp and /var file systems. Make sure there is plenty of free space (more than 30MB) in both file systems. Use the following commands to stop SNA and prepare for tracing:
sna -t off
trcstop
sna -stop sna
rm /var/sna/*
verifysna -U
sna -setlogs -i /var/sna/snatrace -zi 0
sna -setlogs -f /var/sna/snafailure -zf 0
sna -setlogs -s /var/sna/snaservice -zs 10000000 -w 3
sna -t on -l MYLS -a on -c on -e 'tpcreate opint session pc_trace'
NOTE: The word MYLS in the above command should be replaced with the name of your linkstation. If needed, multiple linkstation names may be given (separated by spaces).
If IBM technical support has not requested an API or CPI-C trace,
the words following the -a flag and -c flag in the preceding
command should be changed from on to off.
Tracing the problem
In the preceding step, the SNA logs were reconfigured and several SNA traces were started while SNA was inoperative. Now, start SNA and make sure the traces are active. Use the following commands to accomplish these tasks:
sna -start sna sna -s l -p MYLS sna -d l sna -d trace
NOTE: For MYLS above, use the name of your linkstation.
At this point, reproduce the problem. Once the problem has recurred, continue
with the following step.
Collecting getsnapd
Once you have reproduced the problem, run the following command:
/usr/lpp/sna/bin/getsnapd
The file pd.tar.Z will be created in the current directory. Rename the file to NNNNN.bBBB.tar.Z (where NNNNN is your PMR number and BBB is the branch number of the problem record opened with IBM SNA Support).
Refer to the instructions in the next section, "How to submit a testcase to IBM".
Instructions on file naming conventions, file format, and delivering your
testcase to IBM via the Internet are available at the following URL:
http://techsupport.services.ibm.com/cgi-bin/support/rs6000.support/assistance
Instructions are also available from IBM Fax Service:
[ Doc Ref: 96419825519116 Publish Date: Jan. 19, 2001 4FAX Ref: 8790 ]