This document provides trace information for the following components:
To switch on tracing
Set the attribute TRACE-LEVEL in the broker attribute file
for minimal trace output to "1"
for detailed trace output to "2"
for full trace output to "3"
Example:
TRACE-LEVEL=2
To switch off tracing
Set the attribute TRACE-LEVEL in the broker attribute file to 0:
TRACE-LEVEL=0
Or:
Omit the TRACE-LEVEL attribute.
The broker stubs provide an option for writing trace files. Trace output is only available for transport method TCP.
To switch on tracing for the broker stub
Before starting the client application, set the environment variable STUBLOG in your application job control or CICS startup:
| Trace Value |
Trace Level | Description |
|---|---|---|
| 0 | NONE |
No tracing. |
| 1 | STANDARD |
Traces initialization, errors, and all ACI request/reply strings. |
| 2 | ADVANCED |
Used primarily by system engineers, traces everything from level 1 and provides additional information - for example the Broker ACI control block - as well as transport information. |
| 3 | SUPPORT |
This is full tracing through the stub, including detailed traces of control blocks, message information, etc. |
Example:
//SETPARM STUBLOG=2
If the trace level is greater than 1, unencrypted contents of the send/receive buffers may be exposed in the trace.
Trace output is written to SYSOUT.
Remember to switch off tracing to prevent trace files from filling up your disk.
To switch off tracing for the broker stub
Set the environment variable STUBLOG to NONE or remove the SETPARM statement.
To switch on tracing for the RPC server
Set the parameter TRACELEVEL in the configuration file RPCPARM in sublibrary EXP960. Example:
TRACELEVEL=SUPPORT
To evaluate the return codes, see Error Messages and Codes.