A fix is available
APAR status
Closed as program error.
Error description
A File Close record is sometimes not written to the replication logstream when an RLS file is closed. This problem begins after application of the PTF for APAR PH45117 or PH50400 CICS/TS 5.4 UI83428 (PH45117) CICS/TS 5.5 UI83427 (PH45117) CICS/TS 5.6 UI83426 (PH45117) CICS/TS 6.1 UI83429 (PH50400) The problem happens for RLS files that specify LOGREPLICATE and a LOGSTREAMID, and do *not* specify LOG(ALL). Defined that way, the file is setup to do replication logging, and is not setup to do Forward Recovery logging. When such a file is closed in a CICS Region, the CICS region should always write a File Close record to the replication logstream. But with the PTF applied, the CICS region sometimes does not write a File Close record to the replication logstream. The logstream specified in LOGSTREAMID in the IDCAMS DEFINE CLUSTER definition of an RLS file serves as the name of either (or both) the replication logstream and/or the forward recovery logstream. Prior to the PTF, this logstream was always closed by the CICS region that is closing the RLS file. The closing of the logstream flushes out the FILE_CLOSE record that was written to the logstream buffer. After the PTF, the CICS region only closes the logstream if Forward Recovery is active. If Forward Recovery is not active but replication logging is active, CICS no longer closes the replication logstream. This means that the FILE_CLOSE record written to the logstream buffer might not be flushed out to the logstream. Whether or not it is flushed out depends on if there are other writes to that logstream that fill up the buffer which forces an I/O to the logstream. When the FILE_CLOSE record is never written to the logstream, it can cause any product using the replication logstream ( such as IIDR ) to be inefficient and do unnecessary work.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users with UI83427 or UI83426 * * applied. * **************************************************************** * PROBLEM DESCRIPTION: Missing file close log record when a * * file that uses replication logging is * * closed. * **************************************************************** PH45117 changed DFHFCRO to only log a file close log record if the file being closed had FCTBCFR specified in its DSNB. This means forward recovery is specified for that file. A file can also be defined to use replication logging, and may not also use forward recovery. This means such a file will no longer cause a close record to be logged when the file is closed.
Problem conclusion
UI83427 UI83426 UI96599 UI94940 DFHFCRO has been changed to write a file close record if either forward recovery or replication logging is specified in a file's DSNB.
Temporary fix
Comments
APAR Information
APAR number
PH67035
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
200
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2025-06-19
Closed date
2025-10-23
Last modified date
2025-11-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO05493 UO05494
Modules/Macros
DFHAMFC DFHAMPFI DFHAPTR5 DFHBRNS DFHDMPCA DFHEDFX DFHEIQDS DFHEJOB DFHEJOS DFHESP01 DFHFCBU DFHFCL DFHFCMT DFHFCMTT DFHFCN DFHFCRL DFHFCRO DFHRLRO DFHRSSR DFHSHRQ1 DFHSTFC DFHW2FI DFHW2FR
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
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":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.5","Line of Business":{"code":"LOB70","label":"Z TPS"}}]
Document Information
Modified date:
08 November 2025