IBM Support

PI54504: TRACKING IS NOT SELECTING TYPE X'67D0', X'3F' OR X'4040' IMS LOG RECORDS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Tracking is not selecting queue manager diagnostics type x'67D0'
    IMS log records when they can be correlated by the transaction's
    message tracking UOW token.
    Also, tracking is not selecting x'3F' or x'4040' UOWE IMS log
    records which contain multiple message tracking tokens.
    
    Keywords: function TU TX track
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Problem Investigator V2.4       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Tracking is not selecting type x'67D0', *
    *                      x'3F' or x'4040' IMS log records        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1.Tracking is not selecting queue manager diagnostics type
      x'67D0' IMS log records when they can be correlated by the
      transaction's message tracking UOW token
    2.Tracking is not selecting x'3F' or x'4040' UOWE IMS log
      records  which contain multiple message tracking tokens
    

Problem conclusion

  • 1.The ORGUOWID token will be set for queue manager diagnostics
      type x'67D0' IMS log records. This will trigger tracking to
      include them in the tracking result set.
    2.The x'3F' and x'4040' IMS multi-token records do not register
      global fields but are explicitly handled in the tracking
      engines. Each token in the record is checked against the list
      of tokens already registered to the tracking engine, a
      resulting token match will include the record in the result
      set.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI54504

  • Reported component name

    IMS PROBLEM INV

  • Reported component ID

    5655K5000

  • Reported release

    240

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-12-21

  • Closed date

    2016-02-09

  • Last modified date

    2016-03-02

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

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

Modules/Macros

  • ALZTRACK ALZTUTRK ALZ67D0A ALZ67D0B ALZ67D0C
    ALZ67D0D ALZ67D0E
    

Fix information

  • Fixed component name

    IMS PROBLEM INV

  • Fixed component ID

    5655K5000

Applicable component levels

  • R240 PSY UI35216

       UP16/02/11 P F602

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.4.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A4","label":"IMS Problem Investigator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.4.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 March 2016