PI81486: AFDL ABENDAFDL AFTER SYNCPOINT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If a transaction issues an EXEC CICS SYNCPOINT after having
  updated one recoverable file and then after the SYNCPOINT
  attempts to update a second recoverable file it will receive
  AFDL abend. SYNCPOINT should forget about the first recoverable
  file update when replication logging.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A task has issued a syncpoint request   *
  *                      successfully and then issues a file     *
  *                      control update request against a        *
  *                      recoverable file. The task then abends  *
  *                      with code AFDL.                         *
  ****************************************************************
  * RECOMMENDATION: .                                            *
  ****************************************************************
  A task issues a file control update request against a
  recoverable file that has replication logging active.
  A syncpoint request is then issued within the same task and this
  is then followed by another file control update request against
  a different recoverable file that also has replication logging
  active against a different logstream. This update request abends
  with code AFDL as multiple replication logstreams can not be
  used within the same task. However the syncpoint request has
  resulted in the previous file control update request being
  committed and a new unit of work being attached so this abend is
  not necessary.
  

Problem conclusion

• DFHFCRC has been altered to ensure that frab_rep_log_token_p
  is reset during an intermediate syncpoint.
  
  The IBM Knowledge Center for CICS Transaction Server 5.1.0,
  5.2.0, 5.3.0 and 5.4.0 will all be updated in Reference >
  Diagnostics > Transaction abend codes > AFxx abend codes >AFDL
  so that the User response section is as follows:-
  
  Using multiple replication log streams for one transaction
  causes data integrity issues on the mirror site. This abend
  affects only transactions that update two different recoverable
  files in the same unit of work. Review your replication setup to
  ensure that data sets cannot be updated by different
  subscriptions. If the replication setup meets this requirement,
  update the LOGSTREAMID on the data set definition so that it
  uses the correct log stream. A system dump can be produced by
  adding the appropriate dump table entry using the CEMT SET
  TRDUMPCODE command.
  
  A description for transaction abend code AFDL can be found in
  the following pdf manuals.
  CICS Transaction Server for z/OS Version 5 Release 1, CICS
  Messages and Codes Vol 1, GC34-2861-00
  CICS Transaction Server for z/OS Version 5 Release 2, CICS
  Messages and Codes Vol 1, GC34-7283-00
  CICS Transaction Server for z/OS Version 5 Release 3, CICS
  Messages and Codes Vol 1, GC34-7418-00
  CICS Transaction Server for z/OS, CICS Codes, Version 5 Release
  4
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI49677 UI49678 UI49679 UI49680

Modules/Macros

• DFHFCRC
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R000 PSY UI49680

     UP17/08/23 P F708

• R100 PSY UI49678

     UP17/08/23 P F708

• R800 PSY UI49677

     UP17/08/23 P F708

• R900 PSY UI49679

     UP17/08/23 P F708

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.