PI51396: REPLICATION LOGGING IS GENERATED WHEN IT SHOULD NOT BE WHICH CAN CAUSE DUPLICATE KEY ERRORS IN VSAM DATA REPLICATION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You are running CICS TS 5.1  and find replication logging is
  generated- that is, log records contain the replication logging
  bit on, when they should not.   Because this bit is on,
  replication logging records are generated when they should not
  be.  This can cause Replication for VSAM to fail with duplicate
  key, data mismatch or key not found problems.
    The problem is seen when an EXEC CICS START command is
  used to start the CFC1 task on CICSA. The logic in DFHFCLJ
  in CICSB sees the original transid in the origin data for
  the CSMI task is set to the tranid of the task that issued
  the START, rather than the CFC1 task itself. This causes
  the logic in DFHFCLJ to incorrectly write out the file
  operations generated by CFC1 to the replication log for
  CICSB.
  Additional Symptom(s) Search Keyword(s): KIXREVEPH
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unnecessary replication logging when    *
  *                      file control requests are function      *
  *                      shipped to an FOR.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If CICS is responding to replication log data by applying file
  control changes from the replication log, transaction CFC1
  issues the file control requests. If the target file is remote,
  then these are function shipped to the FOR. DFHFCLJ has code to
  prevent further replication logging for such work, as it is
  being driven as the result of replication logging. It checks
  the transaction is not CFC1 before writing replication log
  data for the file control requests. In the case of function
  shipped requests, the transaction will be CSMI. This means
  DFHFCLJ has to check whether CSMI tasks were initiated from
  CFC1 tasks. It does this by inquiring on the association data
  for the first transid. Normally this would be CFC1; however in
  this case CFC1 was EXEC CICS STARTed by a front end
  listener task. This meant the DFHMNADM call did not return
  CFC1 and so DFHFCLJ did not avoid the logging to the replication
  log.
  KEYWORDS: fclj active standby PM86451
  

Problem conclusion

• DFHFCLJ has been changed to inquire on the transid from the
  previous hop rather than the first transid in order to determine
  whether CSMI was invoked by CFC1.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

• ×**** PE16/01/07 FIX IN ERROR. SEE APAR PI54769  FOR DESCRIPTION
  

APAR Information

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

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

Modules/Macros

• DFHFCLJ
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R800 PSY UI33889

     UP16/01/06 P F601

• R900 PSY UI33890

     UP16/01/06 P F601

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.