IBM Support

PI55657: MULTIPLE ISSUES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1. 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.
    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 result in several errors but is most noticable when it
       results in routing errors and/or the HWSS0742W message.
    
    Summary of changes:
    1. Add exception code to handle the PING case.
    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.4         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Multiple issues.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1. 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.
    2. If sending of a SendOnly transaction to OTMA is delayed for
       any reason, it an 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
       result in several errors but is most noticable when it
       results in routing errors and/or the HWSS0742W message.
    

Problem conclusion

  • 1. Add exception code to handle the PING case.
    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.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI55657

  • Reported component name

    IMS CONNECT EXT

  • Reported component ID

    5655K4800

  • Reported release

    240

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-19

  • Closed date

    2016-02-26

  • Last modified date

    2016-04-05

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

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

    UI35720

Modules/Macros

  • CEXEXRTR CEXTECL1
    

Fix information

  • Fixed component name

    IMS CONNECT EXT

  • Fixed component ID

    5655K4800

Applicable component levels

  • R240 PSY UI35720

       UP16/03/02 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.

[{"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":"2.4.0"}]

Document Information

Modified date:
22 October 2020