A fix is available
APAR status
Closed as program error.
Error description
When CICS is writing security discovery data to the DFHSECD journal, it's possible that a write will fail if the amount of data is too large for the log stream. This results in a DFHXS1605 message (and perhaps a DFHLG0742 message): DFHLG0742 05/14/2025 04:06:06 xxxxxxxx Log record too long for block. Record size 32,450 bytes. Block size 32,000 bytes. MVS log stream DFHSECD.STREAM.NAME. DFHXS1605 05/14/2025 04:06:06 xxxxxxxx Failed to write the Security Discovery Data to the DFHSECD logstream. Reason: Journal DFHSECD log stream length error. . After one write fails, CICS should stop attempting to write out the security discovery data. However, there's a section of the code where the failure may not be immediately recognized. This may result in multiple DFHLG0742 and DFHXS1605 messages. Additional Keywords: SECD, SECDISCOVERY KIXREVACC
Local fix
Increase MAXBUFSIZE within your log stream.
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: Multiple DFHXS1605 & DFHLG0742 messages * * occur in the joblog when writing * * security discovery data. * **************************************************************** When writing security discovery data with a MAXBUFSIZE defined in the log stream which is smaller than the size of the data attempting to be written, the following messages may occur multiple times in the CICS joblog: DFHLG0742 05/14/2025 04:06:06 xxxxxxxx Log record too long for block. Record size 32,450 bytes. Block size 32,000 bytes. MVS log stream DFHSECD.STREAM.NAME. DFHXS1605 05/14/2025 04:06:06 xxxxxxxx Failed to write the Security Discovery Data to the DFHSECD logstream. Reason: Journal DFHSECD log stream length error. This occurs because the log stream data is larger than the defined MAXBUFSIZE and so CICS cannot write the data correctly into the logstream. As a result, further attempts are incorrectly made to attempt to write the security discovery data instead of clearing the buffer and stopping further action.
Problem conclusion
CICS has been updated to prevent further DFHLG0742 & DFHXS1605 messages occurring after an initial failure.
Temporary fix
Comments
APAR Information
APAR number
PH66730
Reported component name
CICS TS Z/OS V6
Reported component ID
5655YA100
Reported release
500
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2025-05-27
Closed date
2025-06-24
Last modified date
2025-07-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO03786
Modules/Macros
DFHXSDC
Fix information
Fixed component name
CICS TS Z/OS V6
Fixed component ID
5655YA100
Applicable component levels
R500 PSY UO03786
UP25/06/25 P F506
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":"6.2","Line of Business":{"code":"LOB70","label":"Z TPS"}}]
Document Information
Modified date:
02 July 2025