A fix is available
APAR status
Closed as program error.
Error description
You are running CTS 4.2 RSU1206. We have a AOR region that connects to 3 FOR's (files split amongst the three regions) not using RLS. Your region was going in and out of SOS and a XXXX task was purged. That resulted in this first abend: +DFHAP0001 An abend (code ---/AZI9) has occurred at offset X'0996' in module DFHCRIU. This resulted in a loop of the following abend: DFHAP0001 An abend (code 0C4/AKEA) has occurred at offset X'031A' in module DFHCRIU. Additional Symptom(s) Search Keyword(s): KIXREVBDB
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: The DFHCRIU recovery routine is called * * repeatedly in a loop after the user * * task has been FORCEPURGEd during * * dfhcriu_Perform_Prepare producing * * message DFHAP0001. * **************************************************************** * RECOMMENDATION: * **************************************************************** An application running in a CICS AOR function ships requests to multiple FOR regions connected by IRC links. The remote files on the FOR regions are defined as recoverable. The application issues an EXEC CICS SYNCPOINT request and DFHCRIU sends a PERFORM_PREPARE to the first region. The associated task is suspended on IRLINK while it awaits a response to the SYNCPOINT. During the suspend the task is FORCEPURGEd resulting in an ABEND AZI9, dfhcriu_Recovery_Routine is driven and issues an exception trace entry, AP X'0D82', criu_module_recovery, followed by message DFHAP0001. The recovery routine obtains the TCA pointer for the task but does not set R12 to address the TCA before returning to mainline code. Mainline code expects R12 to address the TCA, and the first attempt to process an operation involving the TCA causes a program exception, and the recovery routine to be driven again. The recovery routine is called repeatedly in a loop, each time it runs writing exception trace and issuing message DFHAP0001. Additional keywords: MSGDFHAP0001
Problem conclusion
The DFHCRIU recovery routine has been changed to set R12 to the TCA address.
Temporary fix
********* * HIPER * ********* FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM84103
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2013-03-05
Closed date
2013-03-28
Last modified date
2015-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK93404
Modules/Macros
DFHCRIU
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R800 PSY UK93404
UP13/04/20 P F304
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.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":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 March 2015