IBM Support

PI34089: ABEND0C4 IN IPIGVQMD NEAR X'D6C' USING INTERVAL REPORTING

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABENDS0C4 in IPIGVQMD+D6C when processing both IMS PA
    Statistics and Management Exception reports using Interval
    reporting.                                            S0C4
    
    An ABEND0C4 was received at IPIGVQMD + x'C72' (a new offset)
    with another customer.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Performance Analyzer V4.3       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend S0C4 in IPIGVQMD+D6C when         *
    *                      processing both IMS PA Statistics       *
    *                      and Management Exception reports        *
    *                      using Internal reporting.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The IPIGVQMD routine manages dictionary storage and indices
    used by the IMSPA Statistics report processor (IPIPSTAT)
    using a number of fixed subpools dedicated to individual
    queues. After IMS PA finishes reporting at EOF these indices
    may be released individually or by subpool. In this instance
    there are two error conditions which result in the S0C4 abend
    when the VQMD routine attempts to access a top-level Index.
    Index entry when reporting restarts:
     1. When EOF is signalled to the IMS PA Statistics report
        processor it frees all current dictionary storage but due
        to an incorrect flag setting several dictionary queues
        may be omitted.
     2. The Management Exception report incorrectly uses storage
        from a subpool(93) that is also used by the dictionary
        queues above, when this report finishes processing at EOF
        it release all storage from the specified subpool,
        including the dictionary queues above.
     3. In the above situation, when IMS PA is producing reports
        at intervals rather than at EOJ, then an attempt by the
        VQMD routine to use Index pointers retained in its
        internal tables, but actually released by the MGRX
        routine, will result in S0C4 abend.
    

Problem conclusion

  • Resolution is to isolate storage subpools used by the VQMD
    and MGRX outines and to correctly release dictionary entries
    after reporting in the Statistics report processor.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI34089

  • Reported component name

    IMS PERF ANALYZ

  • Reported component ID

    5655E1500

  • Reported release

    430

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-03

  • Closed date

    2015-02-09

  • Last modified date

    2015-09-03

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

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

    UI25033

Modules/Macros

  •    IPIGGET  IPIGVQMD IPISAPAR IPISPARM
    

Fix information

  • Fixed component name

    IMS PERF ANALYZ

  • Fixed component ID

    5655E1500

Applicable component levels

  • R430 PSY UI25033

       UP15/02/14 P F502

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":"SSCX8A2","label":"IMS Performance Analyzer"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"430"}]

Document Information

Modified date:
03 October 2020