CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

62 CICS Transaction Gateway V5
The CICS TG Client daemon trace is started with the CICSCLI /D command. If
you need to trace the client from startup, you can specify all the parameters
needed together on the command line, such as:
CICSCLI /S=SCSCPJA1 /D=9999 /M=ALL
For more information on Client daemon tracing, wrapping trace, and formatting
options, refer to CICS Transaction Gateway Windows Client Administration,
SC34-5940.
Example trace
To provide an example tracing scenario we disabled connection autoinstall on our
CICS region and tried to connect using TCP62 from our Windows workstation. To
disable autoinstall on CICS, we used the CICS command:
CEMT SET AUTOI PROGR(DFHZATDX)
To start the Client daemon and format the trace, we did the following from a
Windows command prompt:
1. We started the CICS TG connection to the CICS region using the command:
CICSCLI /S=SC62PJA1 /D=9999 /M=DRV.1,DRV.2
2. We stopped the CICS TG connection to the CICS region using the command:
CICSCLI /X
3. We formatted the trace with detailed formatting using the command:
CICSFTRC /D
The trace was output to the file CICSCLI.TRC in the CICS TG bin directory. As
shown in Example 3-17, the first network flow is an MPTN_Connect, from the
Client daemon with the node address USIBMSC.CCLI62LU. The destination
address is our CICS server, USIBMSC.SCSCPJA1.
Example 3-17 trace of connect
12:23:20.040 [00000780,000007f0] [5874] DRV:CCL5899 TCP62: connected
006c-SC62PJA1
12:23:20.050 [00000780,000007f0] [5879] DRV:CCL5894 TCP62: send ctl
006c-SC62PJA1 Length=254
...
________________________________________________MPTN Flow - Start_
00000004 Command Type = (0x80) MPTN_Connect
...
Destination User Address:
00000009 MPTN Qualifier = (0x0b) SNA network-qualified LU name
0000000a Address Mode = (0x01) individual address
0000000c Node Address = "USIBMSC.SCSCPJA1"
0000001c Local Address = (0x01) null