ARS0188E ARSMSG Unable to create thread. The return code is 112

[hbusk]

Hi

Running OnDemand for z/OS V8R5M0L6 on a z/OS v2.1 system

We got ARS0188E msg followed by an abend with a SYSTEM COMPLETION CODE=A03 three times shortly after each other:   

ARS0188E ARSMSG Unable to create thread. The return code is 112 
ARS0188E ARSMSG Unable to create thread. The return code is 6   
IEF450I ARSSP ARSSP ARSSP - ABEND=SA03 U0000 REASON=00000000
        TIME=13.08.32                                       

ARS0188E ARSMSG Unable to create thread. The return code is 6   
IEF450I ARSSP ARSSP ARSSP - ABEND=SA03 U0000 REASON=00000000     
        TIME=13.21.32                                           

ARS0188E ARSMSG Unable to create thread. The return code is 6   
IEF450I ARSSP ARSSP ARSSP - ABEND=SA03 U0000 REASON=00000000
        TIME=13.28.10                                       

This happened about two hours ago and since last restart of the OnDemand task there has been no errors.


The manual says:

ARS0188E
The thread cannot be created. The return code is rc=returnCode

Explanation
There might not be enough memory for each process.

User response
Ensure that the maximum amount of memory per process is unlimited. Then try the command again. If the problem persists, contact IBM� Software Support.


I can only find a tip for what to do when running OnD on a Unix system.

Any ideas of what I shall look for on z/OS?


Regards
Hans 

[Justin Derrick]

On UNIX/Linux, you can normally look up error codes in a file called error.h or errno.h.  Do you have a similar file on your system that provides a list of OS-level return codes?

On AIX, 112 is 'Host is down', and 6 is 'no such device or address'.

[Ed_Arnold]

JBNC's analysis is correct.

An SA03 is 99 times out of 100 due to ARSSOCKD losing TCP/IP connectivity to something.  If ARSSOCKD goes too long - and I don't know what too long is - without being able to talk to who it wants to talk to it gets very unhappy.

Usually an SA03 is some sort of network burp and ARSSOCKD is a victim, not a cause.

Ed

[2ma2]

As I think it a dractic act that OnDemand ABENDs because there are delays from TCPIP, I am about curious what solved the problem?

/Marthin

[2ma2]

We had the same  problem.
After issuing SETOMVS LIMMSG=ALL we received this message:

BPXI040I PROCESS LIMIT MAXTHREADS HAS REACHED 100% OF ITS CURRENT CAPACITY OF 200 FOR PID=2611 IN JOB ARSSP RUNNING IN
ADDRESS SPACE 00DD
ARS0188E ARSMSG Unable to create thread. The return code is 6             
ARS0352I The ARSSOCKD instance ARCHIVE is terminating                     

We set OMVS(THREADSMAX(1000), and after this we do not see the error again