IBM Support

PK53653: IMS CONNECT DOES NOT GENERATE EVENT 72 IF A COMMIT MODE 1 TRANSACTION TIMES OUT ON A PERSISTENT SOCKET.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a Commit Mode 1 transaction on a Persistent Socket times
    out IMS Connect returns a timeout message to the ICON client but
    it keeps the socket open and issues a read for the next message.
     However in this case IMS Connect is not generating the Prepare
    Read event (Event 72).  IMS Connect Extensions uses this event
    when deciding how to route messages.  If this event is missing
    IMS Connect Extensions may not route the message correctly, or
    it may be routed even if the transaction is not eligible for
    routing.
    

Local fix

  • IMS Connect Extensions has temporary fix code if needed by the
    customer.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V9 IMS Connect users with IMS        *
    *                 Connect Extensions.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: With IMS transaction routing            *
    *                      implemented in IMS Connect Extensions   *
    *                      (CEX) transactions are incorrectly      *
    *                      routed when the transaction request     *
    *                      follows a commit mode 1 transaction     *
    *                      that has timed out.                     *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    IMS Connect does not generate event 72 when a commit mode 1
    transaction times out on a persistent socket.  The event 72
    (Trigger event) is required by IMS Connect Extensions (CEX) as
    a framing event to delineate the timed out transaction.  As a
    result of not receiving the event 72, CEX associated the new
    transaction with the previous and maintains the routing option
    of the previous transaction.
    

Problem conclusion

  • AIDS: RIDS/DCS RIDS/LMGR DCS LMGR
      GEN:
    
    *** END IMS KEYWORDS ***
    IMS Connect logic in part HWSSCVC0 has been corrected to ensure
    that event recording record 'EVENT 72' (trigger event) is
    produced for Commit mode 1 transactions that have timed out on
    persistent sockets.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK53653

  • Reported component name

    IMS V9

  • Reported component ID

    5655J3800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-09-27

  • Closed date

    2007-11-16

  • Last modified date

    2008-04-30

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

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

    PK55928 UK31347

Modules/Macros

  • HWSSCVC0
    

Fix information

  • Fixed component name

    IMS V9

  • Fixed component ID

    5655J3800

Applicable component levels

  • R900 PSY UK31347

       UP07/11/22 P F711

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 April 2008