A fix is available
APAR status
Closed as program error.
Error description
A DFHTR0112 Bad data passed for tracing to module DFHTRPT dump is received followed by multiple DFHIS0002 A severe error (code X'0206') has occurred in module DFHISIS dumps. The trace in the DFHTR0112 dump shows IS 0200 ISIS ENTRY - FUNCTION(BIND_RECEIVER) SESSION(xxxxxxxx) followed later by - IS 0206 ISIS *EXC* - INVALID_DATA_RECEIVED - FUNCTION(BIND_RECEIVER) SESSION(xxxxxxxx) In this situation the session has been terminated while this mirror task was waiting for its initial data to arrive. This situation was detected and DFHISIS INITIALIZE_RECEIVER returned a PURGED response. That led to an AIPK deferred abend to be set. Importantly the DFHISIS call has not received the actual request into an ISSB related buffer. The issb_purged flag is also not set, because this isn't really a direct purge of the task. DFHISXM gets to BIND_XM_CLIENT. It checks for issb_purged being set, which it is not. Processing continues and DFHISIS is called for BIND_RECEIVER. This expects to process the received FMH5. The request wasn't actually received so this call works on residual buffer data. The residual data causes the exception trace to be issued and then also the bad length to be passed to trace domain. Code will changed to avoid calling BIND_RECEIVER when we know that the earlier INITIALIZE_RECEIVER call has failed. Additional Symptom(s) Search Keyword(s): ABENDAPIK bind dfhisis dfhisxm KIXREVRJL
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All. * **************************************************************** * PROBLEM DESCRIPTION: DFHTR0112 followed by DFHIS0002 for an * * IPIC mirror task. * **************************************************************** A request arrives in CICS over an IPCONN and a mirror task is attached. During initialization of the mirror task the IPIC connection is lost. This causes DFHISIS INITIALIZE_RECEIVER to return a PURGED response and for a deferred AIPK abend to be set. The mirror task has not received all of the inbound request. DFHISIS BIND_RECEIVER gets called to process the request even though it hasn't been received properly. DFHISIS processes residual data. This leads to an exception trace entry being made with an invalid length. This results in a DFHTR0112 message followed by a DFHIS0002 message and dump.
Problem conclusion
DFHISXM has been changed to no longer call DFHISIS BIND_RECEIVER when the task is abending AIPJ or AIPK.
Temporary fix
Comments
APAR Information
APAR number
PH41406
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-10-18
Closed date
2022-01-14
Last modified date
2022-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI78915 UI78916 UI78917
Modules/Macros
DFHISXM
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R100 PSY UI78917
UP22/01/15 P F201
R200 PSY UI78916
UP22/01/15 P F201
R300 PSY UI78915
UP22/01/15 P F201
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.
[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4"}]
Document Information
Modified date:
02 February 2022