[Contents] [Index]

About This Document >>     Installing SSH Tectia Server for IBM z/OS >>     Getting Started with SSH Tectia Server for IBM z/OS >>     Configuring the Server >>     Authentication >>     System Administration >>     File Transfer Using SFTP >>     Secure File Transfer Using Transparent FTP Security >>     Tunneling >>     Troubleshooting SSH Tectia Server for IBM z/OS >>         Debugging SSH Tectia Server for IBM z/OS>>         Solving Problem Situations>>             Using the OMVS Shell             Common MVS Error Messages             Common SSH Tectia Server for IBM z/OS Error Messages             Exceeding Maximum CPU Time             Auxiliary Storage Shortage             SSHD2 Cannot Be Started as a Started Task             File Transfer Server Log Messages with Wrong Timestamps     Man Pages and Default Configuration Files >>     Log Messages >>

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.