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

318 CICS Transaction Gateway V5
Figure 11-26 on page 315, because the resource adapter hides details of the
CICS server and CICS TG protocol it uses.
11.4 Problem determination
In this section, we document useful information we learned while configuring this
scenario and further information on problem determination and tracing.
11.4.1 Tips and utilities
Important: We found that if no transactional attribute is specified on a session
bean deployed into WebSphere AE, then the WebSphere still makes the bean
transactional by default. If this bean makes a call to the CICS TG resource
adapter, this will be run under an extended LUW. If used with a remote CICS
TG on z/OS, the CICS TG must be configured with transactional EXCI support
enabled; otherwise a simple request would fail with the error CTG9631E. For
further details about enabling transactional EXCI, refer to page 152 in
Chapter 7.
In this section, you will find commands and utilities for debugging problems with
your configuration. You will also find some additional information about topics
discussed in this chapter.
Serious events
The Event Viewer is shown in the bottom part of the WebSphere administrative
console (see Figure 11-30). This Viewer displays records of the last several
serious events to occur since the administrative server was started, as well as
warning and audit messages.
Figure 11-30 Event Viewer window on the administrative console
Use the Options window to specify Event Viewer properties, such as how many
event records to keep at one time and how often to update the messages on the
administrative console with data from the administrative server. The Log Limit
property specifies how many serious event records to keep. They are stored in
the administrative database. If the administrative database is getting too full, set
the Log Limit to the minimum value that is reasonable for your environment.