for details or if you wish to disable cookies.
Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See
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.
The global maximum CPU time can be defined in
MAXCPUTIME in the
SYS1.PARMLIB(BPXPRMxx) values can be easily displayed with the console command
The CPU time can be defined in the RACF OMVS segment with the
CPUTIMEMAX option as follows:
In JCL, the CPU time can be defined with the
TIME option. Defining
TIME=1440 sets unlimited CPU time.
[ Contents] [ Index] [ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]
Copyright © 2007 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved. Copyright Notice