The STNTRxx control statement provides granular control of CICS trace domains. This control statement provides similar functionality to the CICS STNTRxx system initialization parameter but allows you to dynamically override any component trace levels currently set in the trace.
To override a trace domain, replace the xx part of the STNTRxx control statement with the relevant CICS component. Refer to the IBM Knowledge Center topic STNTRxx system initialization parameter for a list of trace domains that can be controlled.
The STNTRxx control statement overrides any existing trace point settings in the CICS internal trace. Allowed values for the level parameter are 1, 2, 1-2 and OFF. The additional values allowed by CICS (3, 4 and ALL) are not supported.
To collect the additional trace information obtained by using an STNTRxx control statement, you must set your LEVEL control statement to 3. This can be useful when attempting to diagnose more complex problems and is generally not required for typical application profiling.
Example 1: Additional tracing for file control
The following example configuration file demonstrates the use of the STNTRxx control statement to increase the trace level of file control (FC) beyond what is captured when the ACTIVATETRACE control statement is set to 1.
RECORD FOR PROFILING LIMIT=10 MINUTES /* Profile for ten minutes and then stop CHECKPT=USR.CPROF.CHECKPT ARCHDSN=+USERID.CPROF.+CICS SUMMARY SPACE=(CYL,10,10) DETAIL SPACE=(CYL,50,20) LEVEL=3 /* Summary and detail - all trace events ACTIVATETRACE=1 /* Set minimum trace point levels RESETTRACE=1 /* Restore trace points when collector stops STNTRFC=1-2 /* Gather additional detail for file control CICS=PROD1
An example configuration file to collect additional tracing for file control
Adding STNTRFC=1-2 to the collector configuration file instructs C\Prof to set the level for file control tracing to 1-2. The LEVEL=3 control statement is used to ensure that all trace events are captured.
Example 2: Reduce trace collection overhead
The following example configuration file demonstrates the use of the STNTRxx and LEVEL control statements to reduce trace collection overhead. In this example:
The LEVEL=2 control statement is used to ensure that only important trace events are collected.
The ACTIVATETRACE=1 control statement sets the trace point levels required for C\Prof, including EXEC interface (EI) level 2.
The STNTREI=1 control statement is used to reduce the amount of detail reported in the CICS EXEC interface (EI) to 1.
RECORD FOR PROFILING LIMIT=2 MINUTES /* Collect for two minutes and then stop CHECKPT=USR.CPROF.CHECKPT ARCHDSN=+USERID.CPROF.+CICS SUMMARY SPACE=(CYL,10,10) DETAIL SPACE=(CYL,50,20) LEVEL=2 /* Summary and detail - important trace events only ACTIVATETRACE=1 /* Set minimum trace point levels (incl EI=2) RESETTRACE=1 /* Restore trace points when collector stops EXCLUDETRAN=(CICS) STNTREI=1 /* Reduce EXEC interface (EI) detail to level 1 CICS=PROD1
An example configuration file to reduce trace collection overhead
When using the ACTIVATETRACE=1 control statement, C\Prof will, by default, set the level for the EI domain to 2. EI level 2 provides more application call detail than EI level 1 but is more expensive to collect. The following application call demonstrates the difference between the two levels:
EI level 1:
EI level 2:
WRITEQ-TD QUEUE( CESE ) FROM ( HELLO WORLD ) LENGTH(11)
Use EI level 1 if you do not require the additional information provided by EI level 2 and you want to reduce the impact on your CICS regions.