IBM Support

PI57235: COMBINED IMS AND IMS CONNECT TRACKING DOES NOT INCLUDE IMS CONNECT RECORDS FOR ASYNCHRONOUS OUTPUT PROCESSING

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • When merging IMS and IMS Connect logs, if the IMS transaction
    did not originate from IMS Connect, tracking does not include
    IMS Connect records for asynchronous output processing.
    Tracking is being changed to include IMS Connect records for
    asynchronous output processing in the result set of an IMS
    transaction when the IMS message is retrieved by IMS Connect
    Resume-Tpipe processing.
    
    This was opened as a result of requirement RFE 52855.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Problem Investigator V2.4       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Combined IMS and IMS Connect tracking   *
    *                      does not include IMS Connect records    *
    *                      for asynchronous output processing.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When merging IMS and IMS Connect logs, if the IMS transaction
    did not originate from IMS Connect, tracking will not include
    IMS Connect records for asynchronous output processing.
    

Problem conclusion

Temporary fix

Comments

  • Tracking is changed to include IMS Connect records for
    asynchronous output processing in the result set of an IMS
    transaction when the IMS message is retrieved by IMS Connect
    Resume-Tpipe processing. The OTMA correlator token is used to
    associate the IMS log to the IMS Connect log when an IMS log
    record is used to start tracking. The result is that only the
    IMS Connect log records directly related to the transaction's
    output message are included in the tracking result set.
    

APAR Information

  • APAR number

    PI57235

  • Reported component name

    IMS PROBLEM INV

  • Reported component ID

    5655K5000

  • Reported release

    240

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2016-02-15

  • Closed date

    2016-03-24

  • Last modified date

    2016-05-23

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

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

    UI36491

Modules/Macros

  •    ALZA0419 ALZA0429 ALZTRACK ALZTUTRK ALZ0B01S
    ALZ01A   ALZ01B   ALZ01C   ALZ01D   ALZ01E   ALZ0701S ALZ0702S
    ALZ31A   ALZ31B   ALZ31C   ALZ31D   ALZ31E   ALZ32A   ALZ32B
    ALZ32C   ALZ32D   ALZ32E   ALZ35A   ALZ35B   ALZ35C   ALZ35D
    ALZ35E   ALZ36A   ALZ36B   ALZ36C   ALZ36D   ALZ36E   ALZ37A
    ALZ37B   ALZ37C   ALZ37D   ALZ37E   ALZ38A   ALZ38B   ALZ38C
    ALZ38D   ALZ38E
    

Fix information

  • Fixed component name

    IMS PROBLEM INV

  • Fixed component ID

    5655K5000

Applicable component levels

  • R240 PSY UI36491

       UP16/03/30 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":"SSCX8A4","label":"IMS Problem Investigator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.4.0"}]

Document Information

Modified date:
14 December 2020