Version 4.2.6 for Mainframes (Update)
 —  Parameter Reference  —

MT - Maximum CPU Time

This Natural profile and session parameter only applies to programs executed in batch mode, under Natural Development Server (SPoD) or under Natural for TSO.

It determines the maximum amount of CPU time which can be used by a Natural program.

CPU time measurement starts when a Natural program is started from 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.

Within a Natural session, the profile parameter MT can be overridden by the session parameter MT.

Possible settings 1 - 9999999

Maximum amount of CPU time in seconds.

If Natural Security is installed, the profile parameter MT can be overridden within Natural Security. With Natural Security, the maximum value for the profile parameter MT is 32767. To use a higher value as specified with the MT profile or session parameter, specify MT=0 within Natural Security.

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:

  1. The limit for programs operating in interactive mode is controlled by the TP monitor in use.
  2. The maximum value that can be used is determined by the operating system environment. Any setting in excess of the maximum is reduced to the maximum supported by the operating system.
  3. In system environments which do not support CPU time measurement, the limit is interpreted as elapsed time. The CPU time limit is ignored for systems without timer support.

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 (NDV) servers.

Top of page