A fix is available
APAR status
Closed as program error.
Error description
In a situation where both regions were CICS TS 1.3, the FOR would receive an abend AFCY and the AOR would receive an AZI6. In a situation where both regions are CICS TS 2.2, the FOR would receive an AZI6 and the AOR would receive an AFCY. The problem is that you cannot diagnose an AFCY abend due to the dumpcode now being set on the AOR.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All. * **************************************************************** * PROBLEM DESCRIPTION: When a file control request is purged * * or timed out, the AFCY transaction dump * * is taken too late to contain useful * * diagnostic information. * **************************************************************** * RECOMMENDATION: * **************************************************************** DFHEIFC will abend the transaction with an AFCY transaction dump following a file control request which has been purged or timed out. Much of the diagnostic information may be lost by the time this dump is produced, particularly in the case of a file control request which has been shipped to a remote system. Additional keyword: SERVAID
Problem conclusion
DFHFCFR will produce a transaction dump with a new abend code, AFCI, when it detects a purged response for a file control request. The production of AFCI dumps can be controlled by setting options in the transaction dump table using CEMT SET TRDUMPCODE. In the case of a local file control request which has been purged the default will be to get an AFCI transaction dump followed by an AFCY transaction dump. Either or both of these may be suppressed. In the case of a remote file control request which has been purged the default will be to get an AFCI transaction dump on both the local and remote systems, followed by an AFCY transaction dump on the AOR (local system). The CICS Transaction Server for z/OS CICS Messages and Codes, Version 3 Release 1, GC34-6442-01, will have the following abend code added: . AFCI Explanation: The transaction issued a file request resulting in a call to the main file control program (DFHFCFR). During the processing of the request the transaction was purged. That is, the transaction was the subject of an explicit PURGE or FORCEPURGE request, was timed out, or was selected by CICS for termination in an attempt to alleviate an SOS condition. . System Action: A CICS transaction dump is issued with abend code AFCI. A "purged" response is returned from DFHFCFR to its caller. The transaction issuing the file control request will eventually issue an AFCY abend with a further transaction dump. . User Response: In some instances, for example if the transaction was explicitly purged, no further action is necessary. Otherwise examine the exception trace and the transaction dump to identify the point at which the purge occurred. . Module: DFHFCFR . Also change the AFCY abend code entry as follows: . AFCY Explanation: The transaction issued a file request resulting in a call to the main file control program (DFHFCFR). During the processing of the request the transaction was purged (that is, was the subject of an explicit PURGE or FORCEPURGE request, was timed out, or was selected by CICS for termination in an attempt to alleviate an SOS condition). A "purged" response was returned from DFHFCFR to its caller. . System Action: The task is abnormally terminated with a CICS transaction dump. . Exception trace entries are made between the point at which the purge is detected and the issuing of the abend. . If a task times out while waiting for a lock on a record in a coupling facility data table, CICS will issue message DFHFC7130 identifying the key of the locked record and the system and unit of work that owns the lock. . A transaction dump with abend code AFCI is taken when the purged response is detected by DFHFCFR. . User Response: In some instances, for example if the transaction was explicitly purged, no further action is necessary. . If using a coupling facility data table, look for any relevant DFHFC7130 messages. . Otherwise examine the exception trace and the AFCI/AFCY transaction dumps to identify the point at which the purge occurred. . Modules: DFHDMPCA, DFHEIFC
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PK04926
Reported component name
CICSTS 3.1 Z/OS
Reported component ID
5655M1500
Reported release
400
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2005-04-28
Closed date
2005-06-06
Last modified date
2005-07-01
APAR is sysrouted FROM one or more of the following:
PK01842
APAR is sysrouted TO one or more of the following:
UK04255
Modules/Macros
CHAPT023 DFHFCFR DFH04926
GC34644201 |
Fix information
Fixed component name
CICSTS 3.1 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R400 PSY UK04255
UP05/06/14 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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
22 July 2020