The CICSPlex® SM Web User Interface provides a trace service to help diagnose any problems encountered while using the interface.
You should ensure that you have specified the USERTR, SYSTR, and AUXTR CICS® system initialization parameters in your Web User Interface server start-up job.
Trace records are written to the local AUXTRACE only and are not sent to the CMAS. These trace records can be formatted by the standard CICSPlex SM trace formatter, EYU9XZUT.
You can control the amount of trace information produced by the Web User Interface by setting appropriate trace flags. Thirty one independent trace flags are provided and these can be enabled by:
For more information about using trace and the EYU9XZUT utility, see theCICSPlex SM Problem Determination.
You specify the WUITRACE parameter as described in CICSPlex System Manager Web User Interface Guide. For example, to activate trace levels 13,15, and 31 when the Web User Interface is started, specify the WUITRACE parameter as follows:
WUITRACE(13,15,31)
If you run the COVC transaction and select Trace Flags, you are presented with Figure 11.
COVC CICSPlex SM Web User Interface Control EYUVCTT Trace Flags Overtype the trace, enter to update. 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 Trace Flags : Y Y N N N N Y N N N Y N Y N Y N N N N N N N N N N N N N N N Y Aux. Trace Status : Started Current Status : Ready Time : 14:24:36 Applid : IYCQCTA5 Date : 02/27/2001 PF 1 Help 3 Exit 12 Return
Figure 11 shows that trace levels 1,2, 7, 11, 13,15, and 31 are active. You can overtype any of the trace flags with Y or N to change the default settings.
Table 3 shows a list of some of the available trace levels and their usage.
Level | Usage |
1 | Method entry and exit (summary) |
2 | Method entry and exit (detail) |
3 | Method entry and exit (special) |
7 | Stack management |
8 | Storage management |
9 | Service queue processing |
10 | Service event processing |
11 | View Editor |
12 | Resource catalogue |
13 | Stub management |
14 | View cache |
15 | HTTP requests and responses |
18 | API command |
31 | Soft exceptions |
Exception tracing is always performed by the Web User Interface server when it detects an exceptional condition. The goal of this type of trace is first failure data capture, to capture data that might be relevant to the exception as soon as possible after it has been detected.
Exception tracing cannot be disabled and all exception trace points are always active.
First-failure data capture is provided in two ways, as follows: