A fix is available
APAR status
Closed as program error.
Error description
The problem is caused by PI92770. DFHAPLJP saves the original T8 TCB token to ensure that it can change back to this TCB when recovery is driven. The field to hold the TCB token is incorrectly defined as 4 bytes. It should be 8 bytes. That didn't used to be a problem because the next 4 bytes were never used. PI92770 introduced a new flag to try and detect recursive error handling taking place. This flag ends up being the top byte of the instance count part of the T8 TCB token. In this case task 388 is using T8007. It gets the -904 abend, drives DFHAPLJP recovery and sets the new bit on. An exception is returned to the Java application, which completes. Liberty retains the thread and uses it for task 394. Task 394 also gets the -904 abend. This drives DFHAPLJP recovery routine. That issues a CHANGE_MODE to the saved T8 token. The token is corrupted due to the new bit being set on. That causes DFHAPLJP to percolate the abend to DFHSJIN and terminate the JVM instead of returning to the Java application with an exception.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: An abend in non Liberty program that * * has been linked to using JCICS causes * * the Liberty JVM server to be recycled. * **************************************************************** A Java program in Liberty links to a non-Java program. This non-Java program abends causing that transaction to fail. The thread within Liberty is reused by a subsequent program. The thread is in a compromised state and leads a DFHSJ0001 error and causes the JVMSERVER to restart. Additional Keywords: msgDFHSJ001 SJ001
Problem conclusion
The abend is now correctly handled.
Temporary fix
Comments
APAR Information
APAR number
PH00938
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
000
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-07-30
Closed date
2019-02-12
Last modified date
2019-03-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI61247 UI61248 UI61249 UI61250 UI61251 UI61252 UI61253
Modules/Macros
DFHAMSJ DFHAPJVM DFHAPLJ1 DFHAPLJP DFHAXIS2 DFHCAL64 DFHCDJNI DFHCDK64 DFHDSATT DFHDSATX DFHDSATY DFHDSDS4 DFHDSIT DFHEIQSY DFHKEDD DFHKEDS DFHKEIN DFHKESTX DFHKETA DFHKETCB DFHKETIX DFHMNXM DFHSJBD DFHSJDM DFHSJDS DFHSJDST DFHSJDUF DFHSJIN DFHSJINT DFHSJIS DFHSJIT DFHSJJS DFHSJJST DFHSJL DFHSJNT DFHSJPTI DFHSJRE DFHSJRL DFHSJRM DFHSJSA DFHSJSC DFHSJSM DFHSJSR DFHSJST DFHSJTE DFHSJTH DFHSJTRI DFHSJWL DFHSJXM DFHSODS DFHSTP DFJ@H356 DFJ@H360 DFJ@H427 DFJ@H467 DFJ@H468 DFJDTCOE DFJOUTRE DFJWLPBP DFJWLPPL
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R000 PSY UI61247
UP19/02/22 P F902
R003 PSY UI61249
UP19/02/23 P F902
R00D PSY UI61248
UP19/02/22 P F902
R100 PSY UI61250
UP19/02/15 P F902
R103 PSY UI61252
UP19/02/15 P F902
R10D PSY UI61251
UP19/02/15 P F902
R200 PSY UI61253
UP19/02/15 P F902
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.3","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.3","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 March 2019