A fix is available
APAR status
Closed as unreproducible.
Error description
This is a problem of freeing FREE_32K_BUFFER after a remote abend. This is not the 32k buffer obtained from the buffer pool, but is SET storage obtained as user storage. pool, but is true set storage obtained as user storage. Because the initial read set abended, FRT_DATA_BUFFER was never cleared. Reg2 contains this address.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DFHFCFR when an application * * issues a read_set with a handle_abend, * * that is activated, followed by a * * read_into against a remote file. * **************************************************************** * RECOMMENDATION: * **************************************************************** An application issues a read_set to a remote file. This request abends on the FOR and is passed back to the AOR where it is handled by a handle_abend command. This is immediately followed by a read_into request. This request also abends and is handled. When the application comes to an end during clean up of the task, DFHFCFR abends with an 0C4. During the read_set some set storage is allocated and is pointed at via the FLAB and FRT_DATA_BUFFER off the FRTE. During the first abend, the intention is to set FRT_DATA_BUFFER to zero. However, the register being used for FRTE addressability has been corrupted via the abend. This means FRT_DATA_BUFFER is not set to zero, instead the uninitialized pointer to the FRTE leads to random storage being cleared with unpredictable results. During the read_into the set storage is released updating the FLAB. When the second abend occurs the same FRT_DATA_BUFFER problem occurs. During the clean up of the task, the FRTE needs to be released and so the system also attempts to free the FRT_DATA_BUFFER. As the set storage has already been released the system believe that the FRT_DATA_BUFFER storage comes from FCPH and program checks as it cannot find an index for zero length. Additional Keywords: DFHFC0001 FC0001 AKEA 56B6 FCFR FCFRREC MSGDFHFC0001 ABENDS0C4 S0C4
Problem conclusion
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
DFHFCFR has been altered so that in the recovery routine, FRTE_POINTER is restored before FRT_DATA_BUFFER is used.
APAR Information
APAR number
PK61254
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
400
Status
CLOSED UR3
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-02-18
Closed date
2008-04-28
Last modified date
2008-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK35922
Modules/Macros
DFHFCFR
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R400 PSY UK35922
UP08/04/30 P F804
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":"3.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":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 May 2008