A fix is available
APAR status
Closed as program error.
Error description
There is a Cobol program that links to a Java program (Liberty and OSGi). It happens from time to time that such task remains suspended for resource type JVMTHRED when the bundle was updated. This task can't be purged nor can the JVMServer be purged. The CICS region must be recycled in order to solve this problem. JVMTHRED usually means that the thread limit for the JVM server has been reached. The cause of the problem was identified as following: In dfhsjjs_disable_jvmserver the current thread limit is saved, then it is set to zero to clear the work out of the JVM. Once that's complete the thread limit value is restored in case the JVMSERVER is re-enabled. However dfhsjjs_disable_jvmserver resets the limit prior to the sjth_initialise_threadset call which initialises the thread limit to 0. A JVMSERVER should never be enabled with a thread limit of zero. There is a check in dfhsjjs_set_jvmserver, but that checks sj_jvmserver_threadlimit which is cataloged copy of the JVMSERVER rather than the actual value in the threadset.
Local fix
Not available.
Problem summary
**************************************************************** * USERS AFFECTED: All CICS Users. * **************************************************************** * PROBLEM DESCRIPTION: When a JVM server is disabled and * * re-enabled again, thread limit will * * be set to 0 which causes the JVM server * * to be unusable. * **************************************************************** When a JVM server is disabled, thread limit will be temporarily set to 0 to force work to drain out of the JVM. The original thread limit should be restored but DFHSJJS is incorrectly leaving the limit set to 0. When the JVM server is re-enabled the thread limit is 0 and it is unusable.
Problem conclusion
UI53821 UI54489 UI55925 DFHSJJS has been changed to reset thread limit correctly when the JVM server is disabled.
Temporary fix
Comments
APAR Information
APAR number
PH00162
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
900
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-07-09
Closed date
2018-08-27
Last modified date
2018-09-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI58116
Modules/Macros
DFHAMSJ DFHAPLJ1 DFHAPLJP DFHDSATT DFHDSATX DFHDSATY DFHDSDS4 DFHDSIT DFHEIQSY DFHKEDD DFHKEDS DFHKEIN DFHKESTX DFHKETA DFHKETCB DFHMNXM DFHSJBD DFHSJDM DFHSJDS DFHSJDST DFHSJDUF DFHSJIN DFHSJINT DFHSJIS DFHSJIT DFHSJJS DFHSJJST DFHSJL DFHSJPTI DFHSJRL DFHSJSA DFHSJST DFHSJTE DFHSJTH DFHSJTRI DFHSJXM DFHSODS DFHSTP
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R900 PSY UI58116
UP18/08/30 P F808
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 September 2018