You configure tracing for CICS services by setting the
Generated trace level,
Runtime trace level, and
Trace queue name properties for your service interface.
You set trace levels for two phases.
Set the
Generated trace level property to specifiy the level of information you want to generate into your deployed service. This determines the level of trace information available at run time. The options are:
- None - No trace information is generated into the deployed service
- Low - Generate trace code showing the execution of service interface operations, input and output interface fields, and screen records
- High - Generate trace code showing record names and paragraph names as they execute, in addition to the information generated by the Low setting
Set the
Runtime trace level property to specifiy the level of information you want to to have written to the trace queue at run time. The options are:
- RUN_LEVEL_1 - No information is written to the trace queue
- RUN_LEVEL_2 - Writes trace records showing the execution of operations and the accessing of screen input and output records
- RUN_LEVEL_3 - Writes trace records showing the names of paragraphs as they execute, input and output interface data, and screen records
- RUN_LEVEL_4 - Writes low-level trace messages from bridge support modules
- RUN_LEVEL_5 - Writes medium-level trace messages from bridge support modules
Note:
- Because the
Generated trace level setting determines the type of information generated into the deployed service, the runtime can only generate messages based on that stored information even if the
Runtime trace level is set to write out higher-level messages.
- The reporting for each trace level builds on the lower level or levels, meaning that the higher trace levels also include all trace messages associated with lower levels.
- The file sizes for your deployed service grow in proportion with the level of reporting you specify. Larger files could slightly degrade run-time performance.
We provide a trace viewer you can run using a TN3270 emulator. You must have your service deployed to an enterprise server configured with a TN3270 listener. You can retrieve information about transactions and render screens.
Note:
Before redeploying your service for production, set the
Generated trace level to
None.
