This Natural profile and session parameter determines the maximum amount of CPU time which can be used by a Natural program.
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
|| Maximum amount of CPU time in
|Specification within session||yes|
|Application programming interface||
||See SYSEXT - Natural Application Programming Interfaces in the Utilities documentation.|
NEXTmode or by means of a
FETCHstatement, 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.
MTprofile parameter can be overridden by the session parameter
MTprofile parameter applies separately to both TCB (except under CICS) and SRB (zIIP) processing modes. If
MT=0is 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.
MTparameter is supported under CICS SRBs (zIIP), but not under CICS TCBs. If
MT=0is 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.