A fix is available
APAR status
Closed as program error.
Error description
A Liberty JVM server is running in a CICS region that has TRANISO=YES coded in the SIT. If a Liberty application links to a non-Liberty program and that linked to program abends, code added by PH00938 sets a flag (SJKE_RECOVERY) in the SJKE block associated with the tasks T8 TCB. This flag is used to detect recursive or repeated abends within the same task. The flag should get reset at task termination but, due to the use of TRANISO=YES, DFHSJXM runs on the QR TCB instead of the expected T8 TCB. This leaves the flag set on because the SJKE block was not located. When a subsequent Liberty application runs and encounters the same abend, CICS checks the SJKE_RECOVERY flag. The flag is already set on so CICS incorrectly believes it is processing a recursive abend. This causes message DFHSJ1007 to be issued and the JVM server is recycled. ADDITIONAL KEYWORDS: DFHSJ1007 DFHSJ0918 DFHXMAT TRANISO T8 QR KIXREVSCB
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All * **************************************************************** * PROBLEM DESCRIPTION: A Liberty JVM server may terminate * * unexpectedly with a msgDFHSJ1007. * **************************************************************** A path exists in Liberty Java code where a T8 TCB control block can contain a flag (sjke_recovery) indicating a previous Liberty task had abended. If another Liberty task uses the same TCB but is running ISOLATE=YES and it also abends then it can be deemed as being in a repetitive abend condition and the JVM server is terminated with message DFHSJ1007. If transaction isolation is inactive, then a different code path is driven. The flag is cleared and the problem does not arise.
Problem conclusion
CICS Liberty code has been amended to clear the sjke_recovery flag, thus preventing the aforementioned scenario.
Temporary fix
Comments
×**** PE19/11/04 FIX IN ERROR. SEE APAR PH18794 FOR DESCRIPTION
APAR Information
APAR number
PH13146
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-06-10
Closed date
2019-10-24
Last modified date
2019-11-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI66041 UI66042 UI66043 UI66044 UI66045 UI66046 UI66047
Modules/Macros
DFHAPJVM DFHAXIS2 DFHCDJNI DFHSJBD DFHSJDM DFHSJDS DFHSJDUF DFHSJIN DFHSJIS DFHSJIX DFHSJJS DFHSJL DFHSJNA DFHSJNR DFHSJNT DFHSJRE DFHSJRL DFHSJRM DFHSJRT DFHSJSC DFHSJSM DFHSJST DFHSJTH DFHSJTRI DFHSJXM DFJ@H317 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 UI66045
UP19/10/30 P F910
R003 PSY UI66047
UP19/10/31 P F910
R00D PSY UI66046
UP19/10/31 P F910
R100 PSY UI66042
UP19/10/25 P F910
R103 PSY UI66044
UP19/10/26 P F910
R10D PSY UI66043
UP19/10/26 P F910
R200 PSY UI66041
UP19/10/25 P F910
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.4","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.4","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
13 November 2019