IBM Support

PH63418: IMSPALOG TOTALTM FIELD INCORRECT AS IT SHOWS EXPONENTIAL TOTAL IMS TIME

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IMSPALOG LIST and SUMMARY reports for some transactions can
    display exponential Total IMS Time for field TOTALTM; for
    example, 7.79E+11.
    In some circumstances, messages are read by the MQ Trigger
    Monitor BMP which is put on the IMS message queue, but then
    there is no subsequent enqueue for a transaction and thus no
    Input Message Enqueue x35 log record is written. Next, the
    application for the triggered transaction issues a GU to the I/O
    PCB, causing an x'31' DLI GU log record to be written.
    
    This causes IMS PA to incorrectly calculate Total IMS Time
    because it expects a x'35' log record after the x'03' log record
    for the input message.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Performance Analyzer V4.5       *
    ****************************************************************
    * PROBLEM DESCRIPTION: IMSPALOG TOTALTM Field incorrect.       *
    *                      Shows exponential Total IMS Time.       *
    ****************************************************************
    IMSPALOG LIST and SUMMARY reports for some transactions can
    display exponential Total IMS Time for field TOTALTM,
    for example, 7.79E+11.
    
    In some circumstances, messages are read by the MQ Trigger
    Monitor BMP which puts on the IMS message queue, but then
    there is no subsequent enqueue for a transaction and thus no
    Input Message Enqueue x35 log record is written. Next, the
    application for the triggered transaction issues a GU to the
    I/O PCB, causing an x'31' DLI GU log record to be written.
    
    This causes IMS PA to incorrectly calculate Total IMS Time
    because it expects an x35 log record after the x03 log
    record for the input message.
    

Problem conclusion

  • IMS PA has been corrected to expect the x03 x31 log record
    sequence, with no intervening x35, thus making the correct
    calculation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH63418

  • Reported component name

    IMS PERF ANALYZ

  • Reported component ID

    5655E1500

  • Reported release

    450

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-09-26

  • Closed date

    2024-10-22

  • Last modified date

    2024-11-03

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

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

    UI98838

Modules/Macros

  • IPIIPROC IPISAPAR
    

Fix information

  • Fixed component name

    IMS PERF ANALYZ

  • Fixed component ID

    5655E1500

Applicable component levels

  • R450 PSY UI98838

       UP24/10/25 P F410

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":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A2","label":"IMS Tools"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"450"}]

Document Information

Modified date:
03 November 2024