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.

For further details on tracing J2EE resources in <strong>CICS</strong>, refer to Chapter 4 in<br />

<strong>WebSphere</strong> Application Server V4.0.1 for z/OS and OS/390, Messages and<br />

Diagnosis, GA22-7837.<br />

Java client trace<br />

<strong>CICS</strong> TG Java client tracing can be set programmatically within the servlet by<br />

adding the following statements to the Java application:<br />

com.ibm.ctg.client.T.setDebugOn(true);<br />

com.ibm.ctg.client.T.setTimingOn(true);<br />

In our CTGTesterECI Web application the Trace option on the index.jsp welcome<br />

page controls this tracing. Output from this trace will go to the SYSPRINT log of<br />

the J2EE Server, since this is what we set up for the TRACEBUFLOC, as shown<br />

on page 286.<br />

Note: Enabling <strong>CICS</strong> TG Java client tracing in an application will enable it for<br />

all applications running in the application server, as a consequence of the<br />

static nature of the T class.<br />

<strong>CICS</strong> TG JNI trace<br />

<strong>CICS</strong> TG JNI trace is output from the <strong>Gateway</strong> JNI module (libCTGJNI.so) that<br />

acts as the interface between the <strong>Gateway</strong> and the underlying native transport<br />

(EXCI). We found it to be a very useful means of problem determination.<br />

It is controlled with the Java system property gateway.T.setJNITFile. <strong>The</strong><br />

property value specifies the file name where the JNI trace is output. This must be<br />

set in the JVM properties file for the J2EE Server. To do this, we performed the<br />

following steps:<br />

1. Edited our J2EE Server instance’s jvm.properties file, located in the directory<br />

/<strong>WebSphere</strong>C1/CB390/controlinfo/envfile/WTSCPLX1/C1OASR2A.<br />

2. Added the following Java property:<br />

gateway.T.setJNITFile=/tmp/wasctgjni.trc<br />

3. Restarted our J2EE Server instance using the Operations application.<br />

You can see the output in our JNI trace file (/tmp/wasctgjni.trc) for a simple<br />

request to our CTGTesterCCI Web application in Example 10-9.<br />

Example 10-9 <strong>CICS</strong> TG JNI trace output from <strong>WebSphere</strong><br />

<strong>CICS</strong> <strong>Transaction</strong> <strong>Gateway</strong> JNI Trace file for z/OS Version 5.0, Build Level<br />

c000-20020621<br />

20:13:59.451 [020e008c,10e616a0,WS007208 ] : CCL6813I CcicsInit: Running<br />

under Websphere z/OS.<br />

Chapter 10. <strong>CICS</strong> TG and <strong>WebSphere</strong> Application Server for z/OS 285

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

Saved successfully!

Ooh no, something went wrong!