A fix is available
APAR status
Closed as program error.
Error description
During an XPI Inq_Application_Data request, an abend0C4 loop may occur in hte CICS trace module DFHTRPX. The program checks would be occurring on a MVCL instruction trying to move too much data and encountering protected storage. The tren_field_length contained x'140' that was the length of trace data of the DFHAPIQ parameter list. Yet the parameter list should only be x'40' bytes in length per the dsect. If the parameter list was not on the edge of a page boudary with the next page allocated to a protected area, the problem would be transparent. The data lengths that DFHAPIQ sends to DFHTRPX need to be reviewed.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All. * **************************************************************** * PROBLEM DESCRIPTION: Several * * "DFHAP0001 AN ABEND (CODE 0C4/AKEA) HAS * * OCCURRED AT OFFSET X'FFFF' * * IN MODULE DFHAPIQ." * * followed by * * "DFHAP0004 A POSSIBLE LOOP HAS BEEN * * DETECTED AT OFFSET X'FFFF' * * IN MODULE DFHAPIQ." * **************************************************************** * RECOMMENDATION: * **************************************************************** An application has a DFHAPIQX FUNCTION(INQ_APPLICATION_DATA) call. The ENTRY and EXIT trace entries for this call use a parameter list length of X'40' bytes but X'140' bytes are formatted. This may cause a loop of program checks (abend0C4 and abendAKEA) if protected storage is accessed and a runaway timeout (abendAKEC). DFHAPIQ has a DFHTRPTM FUNCTION(TRACE_PUT) call with data1(dfhapiq_ptr,length(dfhapiq_arg)). However, for a DFHAPIQX FUNCTION(INQ_APPLICATION_DATA) call, the parameter list only uses the first X'40' bytes of the DFHAPIQ_ARG DSECT, not the full length of X'140' bytes. Additional keywords: MSGDFHAP0001 MSGDFHAP0004 AP0001 AP0004 S0C4 abend0C4 AKEA AKEC
Problem conclusion
DFHAPIQ has been changed to use apiq_plistlen instead of length(dfhapiq_arg) in the ?dfhtrptm call for the ENTRY and EXIT trace entries for a DFHAPIQX FUNCTION(INQ_APPLICATION_DATA) call.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PK66404
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
400
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-05-20
Closed date
2008-07-22
Last modified date
2008-08-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK38326 UK38327
Modules/Macros
DESAPIQ DFHAPIQ
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
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":"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:
01 August 2008