A fix is available
APAR status
Closed as program error.
Error description
Customer received ABEND0C4 in DFHFCRR at x'398E' ( Actually at X'398A' since it was a PIC4 ABEND ). We are attempting to store into a FLLB ( File control locks locator block ) which has not been initialized. Because it is 00000000, CICS abends. CICS issues a getmain in DFHFCRR for an FLLB control block. But, we are coming straight into Lost Locks Recovery and assume we have already issued the getmain. The IFGINQRC + x'14' indicates there is 1 dataset in lostlocks. Additional Symptom(s) Search Keyword(s): KIXREVBDB TS003029567
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS Users. * **************************************************************** * PROBLEM DESCRIPTION: While CICS is processing RLS lost locks * * recovery, message 'DFHFC0001 An abend * * (code 0C4/AKEA) has occurred at offset * * X'398E' in module DFHFCRR' will be * * issued. * **************************************************************** After CICS has detected that the SMSVSAM server has failed and restarted, it will begin RLS dynamic restart. In this scenario, during the restart process it is detected that CICS also needs to run lost locks recovery. This can be due to the IGWLOCK00 lock structure having been deleted. When processing lost locks recovery CICS will need to access or recreate file control locks locator blocks (FLLBs). During the processing of lost locks the FLLB_pointer is used to write to a FLLB that has not yet been addressed, and so CICS abends with an 0C4 and issues message DFHFC0001. Additional Keywords: AbendAKEA Abend0C4 FC0001 398E FCRR DFHFC0555 msgDFHFC0555 FC0555
Problem conclusion
DFHFCRR has been altered to ensure that FLLB_POINTER is not used to write to a FLLB when it is not necessary.
Temporary fix
Comments
APAR Information
APAR number
PH20409
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-12-17
Closed date
2020-02-12
Last modified date
2020-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI67846
Modules/Macros
DFHFCRR
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R200 PSY UI67846
UP20/02/14 P F002 ¢
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.5","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.5","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 March 2020