Your browser does not allow storing cookies. We recommend enabling them.

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.


 

 
PrivX
 

 

 
What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.



    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH



    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now