VTAM buffer traces
The VTAM® buffer trace shows the contents of the message buffers as messages flow inbound and outbound from VTAM.
To start a VTAM buffer trace, the user must first start the z/OS® generalized trace facility (GTF) with option=USR. Then, an z/OS modify command is used to start and stop the trace.
To start the trace:
F VTAMDDF,TRACE,TYPE=BUF,ID=LUDBD2
To stop the trace:
F VTAMDDF,NOTRACE,TYPE=BUF,ID=LUDBD2
(F is the z/OS modify command
VTAMDDF is the name of the VTAM startup procedure
TRACE indicates that the trace is being turned
on
NOTRACE indicates that the trace is being turned
off
TYPE=BUF indicates that this command affects the
buffer trace
ID=LUDBD2 indicates which node is to be traced,
or is to no longer be trace.)
The 'ID=' parameter on the command causes the messages to and from this resource to be traced. When you trace session setup attempts, selection of the resource to be traced is important.
After the trace is started, re-create the problem situation that needs diagnosing. After you trace the problem, stop the trace to avoid writing unnecessary records to the GTF data set.
Now, the programs available to format the VTAM buffer trace are ACFTAP and IPCS.
The VTAM buffer trace is primarily used to determine the cause of session and network-related problems. The trace contains the transmission header (TH), the request/response header (RH), and up to 256 bytes of request unit (RU) data. Because the distributed data facility uses a RUSIZE of 4 KB, the buffer trace is of limited use when trying to capture the data that is sent from the session. The data can be traced by using the Db2 trace that specifies IFCIDs 160 and 161.
USRFD FEF ASCB 00F9D980 JOBN DBD2DIST
BUFF LUDBD2 /LUDBD1 LRC(000,000) INBOUND
VTAM TH=40000000 20000010 0000000F 0000000E 1C00006E 006B0006 030D RH=039020
030AEFFE 41550010 D4C2C840 0000030A 41080060 *........MBH .......-*
D4C9C240 000002FA 00000000 48000000 00030001 *MIB ................*
A0EFCF14 37DA5B01 A0EFCF14 45E83700 4D000000 *......x......Y..(...*
0003561E 4D000000 0002F9F6 00000000 00000000 *....(.....96........*
00000000 00000000 00000000 00000000 00000000 *....................*
00000000 00000000 00000000 E2D8D3C3 C1404040 *............SQLCA *
00000088 00000000 00004040 40404040 40404040 *...h...... *
40404040 40404040 40404040 40404040 40404040 * *
40404040 40404040 40404040 40404040 40404040 * *
40404040 40404040 40404040 404040 * *
TIME 48910.070212
USRFD FF1 ASCB 00F9D980 JOBN DBD2DIST
BUFF LUDBD2 /LUDBD1 LRC(000,000) INBOUND
USER 030AEFFE 41550010 D4C2C840 0000030A 41080060 *........MBH .......-*
D4C9C240 000002FA 00000000 48000000 00030001 *MIB ................*
A0EFCF14 37DA5B01 A0EFCF14 45E83700 4D000000 *......x......Y..(...*
0003561E 4D000000 0002F9F6 00000000 00000000 *....(.....96........*
00000000 00000000 00000000 00000000 00000000 *....................*
00000000 00000000 00000000 E2D8D3C3 C1404040 *............SQLCA *
00000088 00000000 00004040 40404040 40404040 *...h...... *
40404040 40404040 40404040 40404040 40404040 * *
40404040 40404040 40404040 40404040 40404040 * *
40404040 40404040 40404040 40404040 40404040 * *
C4E2D540 40404040 00000000 00000000 00000000 *DSN ............*
436F24F0 *.?.0 *
TIME 48910.070577
0000001 RNIO TRACE OUT ORIGIN(0000000F) DESTINATION(0000000E) TIME(10.08.48.174531) DATE(09.26.89)
TH 40000000000000000000000E0000000F1C00006B006E00070350 OSAF OEF(0000000F 006E) DSAF DEF(0000000E 006B)
ERN(0) VRN(0) TP PRI(0) VR SEQ(000) TG SEQ(000) SEQ(0007) COUNT(00848)
RH 0B90A0 FM DR1 EXC BB CD FMT REQ UNKNOWN
RU 270502FF0003D0
0000002 RNIO TRACE IN ORIGIN(0000000E) DESTINATION(0000000F) TIME(10.08.48.371635) DATE(09.26.89)
TH 40000000200000100000000F0000000E1C00006E006B0006030D OSAF OEF(0000000E 006B) DSAF DEF(0000000F 006E)
ERN(0) VRN(0) TP PRI(0) VR SEQ(010) TG SEQ(000) SEQ(0006) COUNT(00781)
RH 039020 FM DR1 EXC CD REQ
RU 030AEFFE415500