01.01.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3.5.2 Tracing<br />

SNA sense data can be entered in the Sense Data field and a detailed sense<br />

code description displayed by clicking Lookup.<br />

In this section, we provide information on how to use the trace facilities provided<br />

with the Client daemon to debug a simple TCP62 communications problem.<br />

Client daemon<br />

<strong>The</strong> first place to look for error messages when using the <strong>CICS</strong> TG on the<br />

Windows system is the log file. This is specified in the Client configuration<br />

parameters in the <strong>CICS</strong> TG Configuration Tool. We used the default name<br />

<strong>CICS</strong>CLI.LOG, which can be found in the <strong>CICS</strong> TG \bin subdirectory.<br />

<strong>The</strong> first step to useful tracing with the Client daemon is identifying which<br />

components should be traced. A full list is shown in Example 3-16 and can be<br />

viewed using the command <strong>CICS</strong>CLI /M. If in doubt, you should trace with the<br />

default selected components, since these have been selected to be sufficient to<br />

diagnose most problems. <strong>The</strong> default components have an X in front of them in<br />

the following example. To turn on all the parameters, you can use the /M=ALL<br />

option.<br />

Example 3-16 <strong>CICS</strong> TG client trace options<br />

C:\>cicscli /m<br />

CCL8001I <strong>CICS</strong>CLI - <strong>CICS</strong> Client Control Program<br />

CCL0002I (C) Copyright <strong>IBM</strong> Corporation 1994,2001. All rights reserved.<br />

CCL1120I Trace has not been started<br />

CCL1100I <strong>The</strong> following list shows what components can be traced<br />

CCL1101I An 'X' indicates which components are enabled<br />

CCL1102I <strong>CICS</strong>CLI Command Process [CLI]<br />

CCL1103I Interprocess Communication [TRN]<br />

CCL1104I X Protocol Drivers (Level 1) [DRV.1]<br />

CCL1105I Protocol Drivers (Level 2) [DRV.2]<br />

CCL1106I X API (Level 1) [API.1]<br />

CCL1107I API (Level 2) [API.2]<br />

CCL1108I X Client Daemon [CCL]<br />

CCL1109I Terminal Emulators [EMU]<br />

CCL1111I C++ Class Libraries [CPP]<br />

CCL1112I Workload Manager [LMG]<br />

CCL1113I <strong>CICS</strong> Client Service for NT [SER]<br />

Trace is written to a binary file called, by default, <strong>CICS</strong>CLI.BIN. To read the trace,<br />

you must format the binary file into a text file by using the <strong>CICS</strong>FTRC /D<br />

command. This will produce a viewable file called <strong>CICS</strong>CLI.TRC. Both<br />

<strong>CICS</strong>CLI.BIN and <strong>CICS</strong>CLI.TRC are found, by default, in the \BIN subdirectory.<br />

Chapter 3. TCP62 connections to <strong>CICS</strong> 61

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!