IBM Support

JR62072: IDR CAUSES DB2 ON ZOS ABEND WHEN ZPARM CMTSTAT IS INACTIVE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • IDR sometimes causes Db2 to ABEND after upgrading to IDR
    11.4.0.2-5506.
    IDR reports error "IFI error code 8 reason code
    00E60863".
    Db2 reports error "RECEIVED ABEND=04E FOR
    REASON=00E50013".
    IDR 11.4.0.2-5506 depended on the Db2
    connection thread remaining ACTIVE; however, when CMTSTAT is
    INACTIVE this requirement was not always satisfied.
    Solution
    provides flexibility to operate properly regardless of the Db2
    ZPARM CMTSTAT setting.
    
    Workaround:
    Set Db2 ZPARM CMTSTAT =
    ACTIVE (requires database restart)
    Or
    Set IDR parameter
    mirror_log_read_commit_interval_seconds=0
    Note: This workaround
    setting requires all subscriptions to be stopped/restarted
    every hour of operation to ensure the replication process
    recycles the Db2 connection and COMMITS to database.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This issue may affect you if you use the CDC for Db2 for     *
    * z/OS remote source engine, and the Db2 for z/OS database has *
    * been upgraded from version 9.x.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Replication ends on error.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IDR 11.4.0.2-5543 or newer for Db2 for z/OS       *
    * remote source.                                               *
    ****************************************************************
    

Problem conclusion

  • Upgrading to IDR 11.4.0.2-5543 or newer for Db2 for z/OS remote
    source resolves the issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62072

  • Reported component name

    IDR DB2ZOS REMS

  • Reported component ID

    5737C30DR

  • Reported release

    B40

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-28

  • Closed date

    2020-04-15

  • Last modified date

    2020-04-15

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

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

Fix information

  • Fixed component name

    IDR DB2ZOS REMS

  • Fixed component ID

    5737C30DR

Applicable component levels

  • RB40 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
25 May 2020