MAXPROCSYS reached Max Defined processes
Article ID: 255426
Updated On:
Products
SYSVIEW Performance Management
Issue/Introduction
In production, they found a lot of processes remained open and that caused the MAXPROCSYS to reach the maximum defined (they set this parameter to 500). They had to stop/restart SYSVIEW to reset the parameter.
Environment
Release : 16.0
Resolution
SYSVIEW PTF LU02316
PROBLEM DESCRIPTION:
The JVM component of SYSVIEW automatically discovers JVMs running
on a system. Once a JVM is recognized, the JVMDATA subtask that
runs in the SYSVIEW main address space is responsible for determining
the Java version being used by the JVM. In order to determine the
version, JVMDATA will attempt to execute the Java executable file
that lives in the bin directory under the Java home directory used
by the JVM. To do this, a new OMVS session in a new address space
will be spawned to execute the "java -version" command.
The user id that runs the SYSVIEW main address space must have execute
permissions to the Java executable file in order to resolve the Java
version. If the SYSVIEW user id does not have execute permissions to
the Java executable file, the spawned OMVS session will fail to close.
This leads to the address space and OMVS session running under it to be
stuck indefinitely in a waiting state.
The JVM component of SYSVIEW automatically discovers JVMs running
on a system. Once a JVM is recognized, the JVMDATA subtask that
runs in the SYSVIEW main address space is responsible for determining
the Java version being used by the JVM. In order to determine the
version, JVMDATA will attempt to execute the Java executable file
that lives in the bin directory under the Java home directory used
by the JVM. To do this, a new OMVS session in a new address space
will be spawned to execute the "java -version" command.
The user id that runs the SYSVIEW main address space must have execute
permissions to the Java executable file in order to resolve the Java
version. If the SYSVIEW user id does not have execute permissions to
the Java executable file, the spawned OMVS session will fail to close.
This leads to the address space and OMVS session running under it to be
stuck indefinitely in a waiting state.
SYMPTOMS:
One symptom of this bug is seeing several address spaces of type
OTX being created with the same name as the SYSVIEW main address
space. In the case where the SYSVIEW main address space's jobname
is less than 8 characters, an increasing numeric will be appended
to the end of the SYSVIEW main address space jobname. For example,
if the SYSVIEW jobname is SYSVIEW, the OTX address spaces will get
created with names SYSVIEW1, SYSVIEW2, SYSVIEW3, etc.
One symptom of this bug is seeing several address spaces of type
OTX being created with the same name as the SYSVIEW main address
space. In the case where the SYSVIEW main address space's jobname
is less than 8 characters, an increasing numeric will be appended
to the end of the SYSVIEW main address space jobname. For example,
if the SYSVIEW jobname is SYSVIEW, the OTX address spaces will get
created with names SYSVIEW1, SYSVIEW2, SYSVIEW3, etc.
Additional Information
Feedback
Yes
No
Powered by
