PH71000: DFHFC0001 0C4 ABEND IN DFHFCLJ DURING KEYPOINT PROCESSING

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• During keypoint processing, CICS will browse the FCTEs in the
  region and decide whether to write a tie up record to the
  replication log if the file is eligible for replication and can
  be updated in some way. One of the checks which decides this is
  whether the DSNB associated with the FCTE has the flag on to
  indicate that replication logging is active. If the FCTE does
  not have a DSNB associated with it, then CICS may mistakenly
  check a low core address for this flag.
  
  
  
  If CICS determines that this flag is on, it starts processing
  to write a tie up record. However, when it attempts to obtain
  the log lock token for the DSNB, it takes an abend because the
  DSNB does not exist and does not have a valid lock token.
  Additional symptoms: KIXREVSCB
  FC001 DFHRM0002 Severe Error  0817 RM0002
  Abend0c4 DFHFCLJ abends0c4 s0c4
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Abend 0C4 in DFHFCLJ during keypoint    *
  *                      processing.                             *
  ****************************************************************
  During keypoint processing, CICS will browse the FCTEs in the
  region and decide whether to write a tie up record to the
  replication log if the file is eligible for replication and can
  be updated in some way. One of the checks which decides this is
  whether the DSNB associated with the FCTE has the flag on to
  indicate that replication logging is active. If the FCTE does
  not have a DSNB associated with it, then CICS may mistakenly
  check a low core address for this flag.
  If CICS determines that this flag is on, it starts processing
  to write a tie up record. However, when it attempts to obtain
  the log lock token for the DSNB, it takes an abend because the
  DSNB does not exist and does not have a valid lock token.
  

Problem conclusion

• DFHFCLJ has been changed to avoid writing a tie up record when
  an FCTE does not have a DSNB associated with it.
  

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:

  UO08272

Modules/Macros

• DFHFCLJ
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R600 PSY UO08272

     UP26/06/18 P F606 ¢

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.