IBM Support

PI80466: IMS VRM CHANGE NOT RETAINED ACROSS MULTIPLE LOGS AND IRUR TCB STATISTICS INVALID IN SOME CASES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A few issues found internally, are being addressed as follows:
    1) IMS PA can detect and correct an invalid IMS VRM parm
    (Message IPI0331W issued on change), however, the updated VRM is
    not maintained across subsequent input logs for the same system.
    2) IRUR TCB statistics may contain values in excess of the
    elapsed checkpoint interval (i.e >100% of time), usually in
    'Total Real Time for this TCB' or 'IMS Busy Time/TCB'.
    3) If a time-only (i.e. no date) IMS PA global time range is
    specified (e.g. IMSPALOG START(,14:30:00:00),STOP(,14:44:59:99))
    the expected results may not be reported if input messages have
    been queued for a number of hours/days, causing records to
    appear out of expected date/time sequence.
    4) If there is a gap in the input log time sequence an
    incomplete Schedule may be invalidly continued with subsequent
    records for the same PST id.
    5) Some program switch transactions may be missing "Parent"
    related data.
    
    Keywords: MSGIPI0331W Internal Resource Usage Report
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Performance Analyzer V4.4       *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. IMS VRM change not retained across   *
    *                          multiple logs                       *
    *                      2. IRUR TCB statistics invalid in some  *
    *                          cases                               *
    *                      3. Additional minor updates             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1. IMS PA can detect and correct an invalid IMS VRM parm
       (Message IPI0331W issued on change), however, the updated
       VRM is not maintained across subsequent input logs for
       the same system.
    
    2. IRUR TCB statistics may contain values in excess of the
       elapsed checkpoint interval (i.e >100% of time), usually in
       'Total Real Time for this TCB' or 'IMS Busy Time/TCB'.
    
    3. If a time-only (i.e. no date) IMS PA global time range is
       specified (e.g. IMSPALOG START(,14:30:00:00),
       STOP(,14:44:59:99)) IMSPALOG START(,14:30:00:00),
       STOP(,14:44:59:99)) the expected results may not be
       reported if input messages have been queued for a number of
       hours/days, causing records to appear out of expected
       date/time sequence.
    
    4. If there is a gap in the input log time sequence an
       incomplete Schedule may be invalidly continued with
       subsequent records for the same PST id.
    
    5. Some program-switch transactions may be missing "Parent"
       related data.
    

Problem conclusion

  • 1. When a change of IMS VRM is detected the change is applied
       to all subsequent input logs belonging to the same system.
    
    2. Log records containing TCB dispatcher statistics may show
       unexpected decreases in values due to a reduced TCB count.
       Where such unexplained changes in value occur these records
       are ignored as they may invalidly skew or corrupt the
       reported results.
    
    3. Code is added to accommodate the case where a time-only IMS
       PA global time range is specified and input log data spanning
       multiple days is given as input.
    
    4. Code is added to validate the active Recovery Token matches
       existing Schedule data for a transaction. If they do not
       match the Region entry for the PST id is re-initialized to
       ensure the correct Schedule data is reported.
    
    5. Improved reporting of some program-switch transactions where
       the "Parent" transaction data is missing/incomplete.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI80466

  • Reported component name

    IMS PERF ANALYZ

  • Reported component ID

    5655E1500

  • Reported release

    440

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-24

  • Closed date

    2017-05-17

  • Last modified date

    2017-06-02

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

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

    UI47309

Modules/Macros

  • IPIIPROC IPISAPAR IPISCOMD IPISIRUR IPISMCOP
    IPISMERG IPISPSCN IPI4DMGR IPI4PROC
    

Fix information

  • Fixed component name

    IMS PERF ANALYZ

  • Fixed component ID

    5655E1500

Applicable component levels

  • R440 PSY UI47309

       UP17/05/20 P F705

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":"4.4.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A2","label":"IMS Performance Analyzer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.4.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 June 2017