CPUTIME= parameter for procedures
Use the CPUTIME= parameter in procedure to specify the task timing option for either BMP or Fast Path.
The possible values are:
- 0
- No task timing is performed for this BMP or Fast Path region. A default value is placed in the 07 accounting log record to indicate that no timing was done. This is the default.
- N
- A 1- to 4-digit number that specifies the maximum task time in minutes to be allowed for the execution of this BMP or Fast Path region. The values can range from 1 - 1440 minutes. If a value of 1440 or greater is specified, a time of 24 hours is used. When N is nonzero, the STIMER=1 option is in effect.
For BMP task-timing, the measured time includes the DL/I processing that occurs in the dependent region. This includes CPU time for External Subsystem Attach Facility (ESAF) users such as Db2 for z/OS® that continue to process under the TCB of the dependent region. When the dependent region exceeds the specified time, a U0240 abend occurs after the current DL/I call completes. To control the execution time of a BMP, use CPUTIME=N instead of the TIME= of the operating system. If the operating system time limit is included with a job that specifies CPUTIME=N, ensure that the former is a sufficiently higher value to allow for initialization and one completed DL/I call beyond the CPUTIME value. When the CPUTIME=N option is used, the application program must not use the STIMER or TTIMER CANCEL.
For Fast Path programs, the timer is set at the beginning of program invocation. However, message-driven programs are not allowed to exceed the amount of time that is defined for the program to process a single transaction. In this case, CPUTIME=n is ignored.