MVS uprocs abort with owls_api_zos_obj_get_response returns -1

Products

• CA Automic Dollar Universe

Issue/Introduction

MVS uprocs abort with failed connection error message

Error Message in Manager for MVS 3.0.02 log:

|WARN |X|ZOS|pid=p.t|o_zos_srv_impl_api_callba|Server is saturated, please try again later. (Current Threads=11 over 11, Pending Threads=8) 

In the Job Log:

Failed to connect to NODENAME... Attempt #1... Try to reconnect... 
Connection to z/OS node NODENAME was lost. Trying to reconnect... 
JES job (JOBNAME) started with JobID 
Connection to z/OS node NODENAME was lost. Trying to reconnect... 

JES job ended with error: 1

Failed to connect to NODENAME... Attempt #1... Try to reconnect... 
Connection to z/OS node NODENAME was lost. Trying to reconnect... 

====================== INTERNAL ERROR ====================== 
Error recovering results for JCL JOBNAME : owls_api_zos_obj_get_response returns -1. 
============================================================ 
Abort.

Environment

OS: MVS
Component:Manager for MVS 3.0.02
Product Version: Dollar.Universe 6.x

Cause

Cause type: Configuration
Root Cause: Maximum number of threads allocated to the manager for MVS has been reached

Resolution

Increase the values of the following variables:
Node settings -> Manager for z/OS -> Number of threads in the request management thread pool, Minimum number of threads in the thread pool and Maximum number of threads in the thread pool.

ZOS_POOL_QUEUE_SIZE
Number of threads in the request management
thread pool
ZOS_POOL_MIN_THREADS
Minimum number of threads in the thread pool
ZOS_POOL_MAX_THREADS
Maximum number of threads in the thread pool