Specifying trace defaults

The data extractor must be active to perform summary or detail tracing.

A detail trace will use the CICS global user exits XEIIN and XEIOUT to trace all EXEC CICS API and SPI calls that are issued by a transaction. A detail trace will trace only transactions that started after the trace unless it is an in-flight trace. A summary trace will trace all of the transaction history records that were written after the trace is started, even if the transaction was started before the summary trace.

Keywords that are specified in member CMRBEX00 of the BBPARM data set define the default values of MainView for CICS trace requests. These values appear in the fields of the online trace request data entry dialogs as the option defaults.

Note

CMRBEX00 is the default member unless the BBCFG facility is used. For more information about BBCFG, see Failed to execute the [excerpt-include] macro.
.

This section describes CMRBEX00 keywords and CMRSOPT keywords that define trace option defaults for:

  • all trace requests
  • detail trace request
  • trace logging

The following CMRSOPT option affects only summary tracing:

  • STRACSIZ=nnn determines the size of the trace data space reserved for summary trace.

The following CMRSOPT options also affect detail tracing:

  • DB2=YES must be specified to trace DB2 SQL calls
  • MQFILE=YES must be specified to trace WebSphere MQ calls
  • PSB=YES must be specified to trace of DLI calls
  • DLOGPROC=TRSIZE determines the size of the detail trace buffers
  • DTRACSIZ=nnn determines the size of the trace data space reserved for detail trace.

For more information about CMRSOPT, see Setting-monitoring-conditions-CMRSOPT. 

This section contains the following topics:

Related topic

Customizing the application trace facility

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*