STIMER= parameter for procedures

Use the STIMER= parameter in procedure to specify the processor time statistics to be gathered. Valid values are 0, 1 and 2. The default is 2.

Important: The following description applies to message-driven programs only.
0
No processor time statistics are to be gathered. No STIMER/TTIMER sequence is issued.
1
No DL/I processor time is to be included in the processor time statistics. An STIMER/TTIMER sequence is issued once for each program invocation and once for each DL/I call.

Specify this value for a BMP when you want to gather statistics. Specifying STIMER=1 for a BMP or IFP is like specifying STIMER=2 for an MPP. The overhead associated with it is a STIMER macro, a TTIMER macro, a load instruction, and a subtract register instruction per BMP execution.

2
If the LSO=S region startup parameter has been selected, processor time statistics include time durations for:
  • Application program time
  • DL/I processing time
  • CPU time for ESAF users such as Db2 for z/OS® that continue to process under the TCB of the dependent region. If Db2 for z/OS switches to another TCB, which is the case with parallelism, logging, and prefetch, this time is not included.

One STIMER/TTIMER sequence is issued for each program invocation. This is the default.

If you use the IMS timing services STIMER=1 or STIMER=2, you should ensure that your application programs do not use or invoke SVC2E or SVC2F (STIMER or TTIMER). Specifying STIMER=2 is invalid for an IFP region. If these services are invoked, they negate the function of controlling application programming loops, and invalid time statistics might be gathered. Additionally, ABENDU240 might occur. You should also be aware that the LSO option you select affects the meaning of the processor time statistics. If LSO= is specified, most DL/I processing time is not included in the statistics.