Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.

SSH

Exceeding Maximum CPU Time

In some environments it is possible that CPU time is restricted per user process. This can cause the transfer of large files or long-running terminal sessions to fail.

The problem can manifest itself as the signal 29 (SIGXCPU) error, which means that the allocated CPU time per process was exceeded.

Global

The global maximum CPU time can be defined in MAXCPUTIME in the SYS1.PARMLIB(BPXPRMxx) file.

MAXMMAPAREA(40960)
MAXCORESIZE(4194304)
MAXASSIZE(2147483647)
MAXCPUTIME(2147483647)

The defined SYS1.PARMLIB(BPXPRMxx) values can be easily displayed with the console command D OMVS,O.

OMVS

The CPU time can be defined in the RACF OMVS segment with the CPUTIMEMAX option as follows:

OMVS INFORMATION
----------------
UID= 0000000000
HOME= /
PROGRAM= /bin/sh
CPUTIMEMAX= NONE
ASSIZEMAX= 0268435456
FILEPROCMAX= NONE
PROCUSERMAX= NONE
THREADSMAX= NONE
MMAPAREAMAX= NONE

JCL

In JCL, the CPU time can be defined with the TIME option. Defining TIME=1440 sets unlimited CPU time.

===AUTO_SCHEMA_MARKUP===