IBM Support

PK53787: EXCLUDED TRANSACTIONS ARE ROUTED INCORRECTLY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This problem is due to the failure of IMS Connect to provide a
    framing event after a transaction times out on a persistent
    socket.  As a result of this missing event, IMS Connect
    Extensions fails to delineate two transactions and may route the
    second one incorrectly.  This APAR will provide toleration for
    this problem until IMS Connect APAR PK53653 is closed.
    This APAR will also fix the following:
    Command destined for an IMSPLEX is routed incorrectly if the
    IMSPLEX Tmember name matches a CEX Datastore group name.  The
    command request is sent to one of the datastores in the
    datastore group instead of the IMSPLEX.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Users of IMS Connect Extensions V1.2.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Excluded transactions are routed        *
    *                      incorrectly.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR provides: Toleration for an issue in IMS Connect
    (PMR86205) that causes problems in routing.
    Prevents messages from the IMS component of DB2 Control
    Center from being routed (PMR40852).
    

Problem conclusion

  • The problem identified by PMR86205 is due to the failure of
    IMS Connect to provide a framing event after a transaction
    times out on a persistent socket. As a result of this
    missing event, IMS Connect Extensions fails to delineate
    two transactions and potentially routes the second
    transaction incorrectly.
    The problem identified by PMR40852 is due to commands destined
    for an IMSPLEX being routed incorrectly if the IMSPLEX
    TMEMBER name matches an IMS Connect Extensions Datastore
    group name. The command request is sent to one of the
    datastores in the datastore group instead of the IMSPLEX.
    After applying this fix, Restart your IMS Connect Extensions
    system.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK53787

  • Reported component name

    IMS CONNECT EXT

  • Reported component ID

    5655K4800

  • Reported release

    120

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-09-28

  • Closed date

    2007-11-06

  • Last modified date

    2007-12-03

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

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

    UK30967

Modules/Macros

  • CEXEXRTR
    

Fix information

  • Fixed component name

    IMS CONNECT EXT

  • Fixed component ID

    5655K4800

Applicable component levels

  • R120 PSY UK30967

       UP07/11/10 P F711

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.

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88S","label":"IMS Connect Extensions"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"120"}]

Document Information

Modified date:
22 October 2020