This Natural profile and session parameter determines the maximum amount of CPU time which can be used by a Natural program.
Important:
In server environments where the server itself runs without any operating system
controlled CPU time limit, it is strongly recommended to set the profile parameter
MT
to a non-zero value to prevent the formation of endless loops
caused e.g. by application errors. This recommendation applies to Natural RPC and Natural
Development Server servers.
Possible settings | 1 - 9999999 |
Maximum amount of CPU time in seconds.
Notes:
|
|
---|---|---|---|
0 |
MT=0 defines that no Natural CPU time
limit is to be in effect.
|
||
Default setting | 60 |
||
Dynamic specification | yes | ||
Specification within session | yes | ||
Applicable statements | SET
GLOBALS |
||
Applicable command | GLOBALS |
||
Application programming interface | USR1005N |
See SYSEXT - Natural Application Programming Interfaces in the Utilities documentation. |
Notes:
NEXT
mode or by means of a FETCH
statement, that is, on program level 1. In non-batch mode (Natural Development Server,
Natural for TSO), CPU time measurement is restarted at every terminal I/O.
MT
profile parameter can be
overridden by the session parameter MT
.
MT
profile parameter
applies separately to both TCB (except under CICS) and SRB (zIIP) processing modes. If
MT=0
is set in SRB mode, Natural uses the existing z/OS TCB time limit to
avoid endless loops because there is no z/OS CPU time limit (for example, the JCL TIME
parameter) for SRBs.
MT
parameter is supported under CICS SRBs (zIIP), but not
under CICS TCBs. If MT=0
is set, Natural uses the CICS runaway time as CPU
time limit in SRB mode. A CPU timeout abend that occurs when a CICS open TCB is used
cannot be recovered. It causes an immediate AICA abend of the CICS task and the Natural
session is aborted.