A fix is available
APAR status
Closed as program error.
Error description
You are trying to run STAT, a COBOL application in a JAVA only CICS region. An ABEND0C1 is issued and the KERRD indicates that the failure is in DFH0STAT at offset 000065FA. The PSW points to a half word of zeros in what appears to be a COBOL module. The 0C1 is from within an LE-related bootstrap routine that is linked into the DFH0STAT load module. This routine is running before control has ever gotten to DFH0STAT. It is trying to establish the CAA for the new enclave. Normally this would use code in DFHGCAA to get to the TCA for the task and establish the CAA for the enclave. In this failure the pointer to the bootstrap code within the QR TCB (+X'144', TCBCELAP) is pointing to a BATCH method for getting a CAA. This is the routine that would be used with a JAVA application running on a J8 TCB, establishing an enclave. Earlier in the run of the CICS region, there was an LE ABENDU4087 that resulted in CICS issuing an abendu0999: --- ABEND ---/4087 ABEND ---/0999 ABEND ---/4093 PROGRAM CHECK 0C4/AKEA TRAN ABEND PERCOLATE ---/AEXZ --- During this recovery process TCBCELAP on the QR TCB was corrupted. Additional Symptom(s) Search Keyword(s): KIXREVACC CICS shutdown hangs because the SJ domain has not quiesced. SJ shutdown task is waiting on the SJVMPOOL lock. Owner of the lock has terminated (abended much earlier and went away without freeing the SJVMPOOL lock).
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS Users * **************************************************************** * PROBLEM DESCRIPTION: During a call to PIPI_CALL_SUB to * * Destroy JVM, the J8/J9 TCB has a * * runaway abend. CICS regains control on * * the QR TCB and attempts to destroy the * * PIPI enclave leading to unpredictable * * results. * **************************************************************** * RECOMMENDATION: * **************************************************************** A JVM is being destroyed and the J8/J9 TCB has a runaway abend after TCAJVMXT is turned ON. The abend leads to an ABTERM for the J8/J9 TCB and the task continues to run on the QR TCB. The abend is percolated with an OK response from DFHAPLJ. DFHSJIN then incorrectly attempts to destroy the enclave while running under the QR TCB. This can lead to a hang or a further abend. Additional keyword: TCZJVMXT
Problem conclusion
The DFHAPLJ recovery routine is changed to return a response of EXCEPTION with reason TRANSACTION_ABEND when processing a KERNEL_RUNAWAY_ERROR. NOTIFY_DELETE_TCB in DFHSJIN is updated to skip SJIN_DESTROY_ENCLAVE if SJIN_DESTROY_JVM does not return an OK response.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM36269
Reported component name
CICS TS Z/OS V4
Reported component ID
5655S9700
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-04-06
Closed date
2011-05-24
Last modified date
2011-11-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK68063 PM46923
Modules/Macros
DESLI1 DESSJIN DFHAPLI1 DFHAPLJ1 DFHAPLX1 DFHSJIN DFHSJINA DFHSJINM DFHSJINT
Fix information
Fixed component name
CICS TS Z/OS V4
Fixed component ID
5655S9700
Applicable component levels
R600 PSY UK68063
UP11/05/31 P F105
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":"4.1","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":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 November 2011