IBM Support

PM86451: SUPPRESS REPLICATION LOGGING FOR NON-LOGGING TRANSACTIONS WHEN REQUESTS ARE FUNCTION SHIPPED TO A FOR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • There is a need for additional functionality from CICS to
    suppress replication logging for non-logging transactions
    when their file control requests are function shipped to a FOR.
    
    Additional Symptom(s) Search Keyword(s): KIXREVNDB
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * 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 for
    the transaction to not be CFC1 before writing replication log
    data for the file control requests. However, for function
    shipped requests, the transaction will be CSMI and not CFC1, so
    this check fails and replication data is written.
    KEYWORDS: fclj active standby
    

Problem conclusion

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

  • DFHFCLJ has been changed to check for the original transid that
    led to the CSMI task being attached. If it was CFC1 then
    replication logging is avoided in this case.
    

APAR Information

  • APAR number

    PM86451

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    800

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-05

  • Closed date

    2013-08-28

  • Last modified date

    2015-03-04

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

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

    UK97129

Modules/Macros

  • DFHFCLJ
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R800 PSY UK97129

       UP13/09/06 P F309

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 March 2015