IBM Support

PI52919: IN COMBINED MQ/IMS TRACKING, IF THE TX COMMAND IS ISSUED AGAINSTAN MQ RECORD, THE RESULT SET MAY NOT BE COMPLETE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In combined MQ / IMS tracking, if the TX command is issued
    against an MQ record, the result set may not be complete if
    only a LOGTOKEN is available for tracking. This combined MQ/IMS
    tracking issue will be corrected.
    
    Additional changes included:
    Knowledge module updates required as a result of IMS service
    changes.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Problem Investigator V2.4       *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. Address an issue in combined MQ/IMS  *
    *                         tracking.                            *
    *                      2. Knowledge module updates for IMS     *
    *                         service changes.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1. In combined MQ/IMS tracking, if the TX tracking command is
       issued against an MQ log record the result set may be
       incomplete.
    
    2. Knowledge module updates required as a result of IMS
       service changes.
    

Problem conclusion

  • 1. In combined MQ/IMS tracking, if the TX command is issued
       against an MQ record, the result set may not be complete if
       only a LOGTOKEN is available for tracking. In this case the
       bounds checking for determining related IMS transactions was
       not being correctly performed.
    
    2. Update IMS Knowledge modules to cater for changes as a result
       of IMS service changes.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI52919

  • 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-11-20

  • Closed date

    2015-11-25

  • Last modified date

    2015-12-03

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

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

    UI33324

Modules/Macros

  • ALZBRAPI ALZCA01A ALZLCAT  ALZTRACK ALZTUTRK
    ALZ1DZ   ALZ22A   ALZ22B   ALZ22C   ALZ22D   ALZ22E   ALZ6701A
    ALZ6701B ALZ6701C ALZ6701D ALZ6701E ALZ6705A ALZ6705B ALZ6705C
    ALZ6705D ALZ6705E
    

Fix information

  • Fixed component name

    IMS PROBLEM INV

  • Fixed component ID

    5655K5000

Applicable component levels

  • R240 PSY UI33324

       UP15/12/01 P F511

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:
03 December 2015