IBM Support

PK78320: IMS PA APPEARS TO GO INTO A LOOP, BUT IT IS ACTUALLY NOT A LOOP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An IMS PA job appears to go into a loop, but the job does run to
    completion after a few hours processing.
    It is a very large Pgm-switch chain of some 184K+ transactions
    which we keep and process sequentially when adding, updating and
    terminating transactions.  Because we don't actually get to a
    point where the transaction sequence is complete our CPU
    utilization just keeps growing (almost exponentially) each time
    we add a record to the chain.  Because we are using so much CPU
    traversing the chain and so few I/O in between times it looks
    like a loop.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS Performance Analyzer V4.1 users.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: IMS PA job appears to go into a loop,   *
    *                      but is actually not a loop.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An IMS PA job appears to go into a loop, but the job does
    run to completion after a few hours processing.
    It is a very large Pgm-switch chain of some 184K+
    transactions which are kept and processed sequentially when
    adding, updating and terminating transactions.
    Because IMSPA doesn't actually get to a point where the
    transaction sequence is complete the CPU utilization just
    keeps growing (almost exponentially) each time a record
    is added to the chain.  Because the job is using so much CPU
    traversing the chain and so few I/O in between times
    it looks like a loop.
    

Problem conclusion

  • Flush program switch entries from internal queue when
    queue exceeds 256 entries, and process later entries as
    new program switch sets tied to the originating transaction.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK78320

  • Reported component name

    IMS PERF ANALYZ

  • Reported component ID

    5655E1500

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-01-08

  • Closed date

    2009-02-02

  • Last modified date

    2009-03-03

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

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

    UK43708

Modules/Macros

  • IPICPROC IPICXCPT IPIFPROC IPIGGET  IPIIPROC
    IPITDMGR IPITPROC IPI4DMGR IPI4PROC IPI4QMGR
    

Fix information

  • Fixed component name

    IMS PERF ANALYZ

  • Fixed component ID

    5655E1500

Applicable component levels

  • R410 PSY UK43708

       UP09/02/06 P F902

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":"410","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":"410","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 March 2009