PI53698: Pre-routing exit not called after a PING request in same sessionNo destination found errors for SendOnly transactions

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• 1. The pre-routing exit is not called following a PING request
  in the same persistent session. The Target Datastore name in
  event x'3E' for the transaction that is not routed might show a
  value of PING_IMS in some cases. The root cause of the problem
  is that IMS Connect does not produce the expected TRIGGER event
  TYPE=MESSAGE (EVENT ID=X'48') following the PING response. This
  results in residual information being retained about the session
  and the PING request, causing CEXEXRTR not to call the
  pre-routing exit.
  2. If sending of a SendOnly transaction to OTMA is delayed for
  any reason, it can result in the trigger event for a SendOnly
  transaction being issued while the next SendOnly transaction on
  the same ICON session is being processed by the message exit.
  This can cause the CEX SVT control block to be cleared for the
  first transaction after the SVT has been updated with the
  results of message exit processing for the second SendOnly
  transaction. This corruption of the CEX SVT can results in
  several errors but is most noticable when it results in routing
  errors and/or the HWSS0742W message.
  
  Summary of changes:
  1. A circumvention is provided in module CEXEXRTR that detects
  the missing trigger event x'48' and clears the residual
  information from the PING request.
  
  2. A change in SVT maintenance for SendOnly transaction is made
  to delay cleanup of the CEX SVT so that it is not impacted by a
  delayed trigger event.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IMS Connect Extensions V2.3         *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. The pre-routing exit is not called   *
  *                      following a PING request in the same    *
  *                      persistent session.                     *
  *                      2. Routing errors resulting in message  *
  *                      HWS0742I NFNDDST or RSM indicating no   *
  *                      destination found for SendOnly          *
  *                      transaction.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1. The pre-routing exit is not called following a PING request
     in the same persistent session. The Target Datastore name in
     event x'3E' for the transaction that is not routed may show
     a value of PING_IMS in some cases. The root cause of the
     problem is that IMS Connect does not produce the expected
     TRIGGER event TYPE=MESSAGE (EVENT ID=X'48') following the
     PING response. This results in residual information being
     retained about the session and the PING request, causing
     CEXEXRTR not to call the pre-routing exit.
  2. If sending of a SendOnly transaction to OTMA is delayed for
     any reason, it can result in the trigger event for a SendOnly
     transaction being issued while the next SendOnly transaction
     on the same ICON session is being processed by the message
     exit. This can cause the CEX SVT control block to be cleared
     for the first transaction after the SVT has been updated with
     the results of message exit processing for the second
     SendOnly transaction. This corruption of the CEX SVT can
     results in several error but is most noticable when it
     results in routing errors and/or the HWS0742I message.
  3. A PING request shows incorrect information in event x'3E',
     the origin DS name of PING_IMS is incorrectly propagated
     to the target DS name field.
  

Problem conclusion

• 1. A circumvention is provided in module CEXEXRTR that detects
     the missing trigger event x'48' and clears the residual
     information from the PING request.
  2. A change in SVT maintenance for SendOnly transaction
     is made to delay cleanup of the CEX SVT so that it is not
     impacted by a delayed trigger event.
  3. Add exception code to handle the PING case.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UI35721

Modules/Macros

• CEXEXRTR CEXTECL1
  

Fix information

• Fixed component name

  IMS CONNECT EXT

• Fixed component ID

  5655K4800

Applicable component levels

• R230 PSY UI35721

     UP16/03/04 P F603 Ž

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.