Micro Focus Enterprise Developer 3.0 for Visual Studio 2017 > Programming > Mainframe Programming > Interface Mapping Toolkit (IMTK) > Tracing Service Execution > Tracing CICS Service Execution

Tracing CICS Service Execution

You configure tracing for a CICS service interface by setting its Generated trace level, Runtime trace level, and Trace queue name properties.

To view trace information, you can use a TN3270 emulator such as Micro Focus Rumba, which is available as an Enterprise Developer installation option. See Installing and Licensing Micro Focus Rumba for details.

To enable a TN3270 emulator in your enterprise server region you must define a TN3270 listener. For more information, see To specify a listener for TN3270 terminals.

Micro Focus Rumba

The Generated trace level property dictates how much trace information is generated for the service interface at run time. The options are:

None: No trace information is generated for the service.
Low: Generates trace code that shows the execution of service interface operations, input and output interface fields, and screen records.
High: In addition to the trace code generated by the Low option, High also generates trace code that shows record names and paragraph names as they execute.

The Runtime trace level property dictates how much of the generated trace information is 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.

Note: Before redeploying a service interface for production, set the Generated trace level back to None.