A fix is available
APAR status
Closed as program error.
Error description
When an EXEC CICS LINK request is dynamically routed to a remote region over an IPIC connection, and the task issuing the DPL request is then the subject of a PURGE or FORCEPURGE, the dynamic routing program can be redriven in the originating region. This APAR will avoid the routing program being called a subsequent time in the originating region after a task has been purged.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS Users. * **************************************************************** * PROBLEM DESCRIPTION: The dynamic routing program can be * * called for a second time after a PURGE * * or FORCEPURGE command has been * * performed against a task that has * * issued a DPL request to a remote region * * over an IPIC connection. * **************************************************************** When a DPL request is routed to a remote region over an IPIC connection, the dynamic routing program can be called again after the task has been PURGED or FORCEPURGED. When a program that is defined as DYNAMIC(YES) is the target of a DPL request, the request can be routed to a remote region by the dynamic routing program specified on the DTRPGM SIT parameter. If a PURGE or FORCEPURGE is issued against the task in the originating region (the region that issued the DPL request), the dynamic routing program can be called again and the request may be routed to another region to run.
Problem conclusion
DFHEPC has been changed so the the dynamic routing program is not called again in these cases. The task that has been purged will abend with new abend code AITQ. The CICS TS 5.6 "What's new?" section will be updated with the new abend code. The CICS TS 5.6 and CICS TS 6.1 documentation will be updated with the following: AITQ Explanation: The transaction was processing a request which involved waiting for a response from a connected subsystem over an IPIC connection. During the wait, the transaction was purged. SystemAction: The task is abnormally terminated. UserResponse: Investigate the reason the transaction was purged.
Temporary fix
Comments
APAR Information
APAR number
PH52991
Reported component name
CICS TS Z/OS V6
Reported component ID
5655YA100
Reported release
400
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-03-03
Closed date
2023-03-17
Last modified date
2023-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI91015
Modules/Macros
DFHEPC
Fix information
Fixed component name
CICS TS Z/OS V6
Fixed component ID
5655YA100
Applicable component levels
R400 PSY UI91015
UP23/03/21 P F303
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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
03 April 2023