IBM Support

PM19212: NEW HANDLING OF AN EXCEPTION TRANSACTION NEEDED WHEN IT SPANS TWO OR MORE ATF JOURNALS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • ATF journals are archived as they become full. Problem occurs
    when an exception transaction spans 2 or more ATF journals,
    resulting in an incomplete transaction being recorded in the
    extract file.
    
    Additional issues addressed in this APAR:
    1) Loop in IPIOPROC at about 7 instructions near x'16cc'
    to near x'171a' when using a large amount of ATF data
    coming from the OMEGAMON IF2 function.          Keyword: looping
    2) "Program name" field incorrectly displayed on the OMEGAMON
    ATF Trace Level 3 report of IMSPA. The field shows as:
    Program:   *  * **
    Although this is coming from the data, IMSPA should not be
    printing such asterisk garbage in the output.  The data is
    derived from the DB2 Program name field ATRSQLPN in the ATF
    records which contains Hex characters.
    3) ABEND0C4 IPI4PROC at x'EF8' trying to access R1 storage
    using ATF Extract facility.
    4) ABEND0C4 out of RECA05 in IPIOPROC which is in IPI4PROC.
    This issue can show up in various locations in IPI4PROC, so
    any ABENDS0C4 in this routine should have this maintenance on.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Performance Analyzer V4.2       *
    ****************************************************************
    * PROBLEM DESCRIPTION: ATF inflight support                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    ATF journals are archived as they become full. Problem occurs
    when an exception transaction spans 2 or more ATF journals,
    resulting in an incomplete transaction being recorded in the
    extract file.
    

Problem conclusion

Temporary fix

Comments

  • Implement Inflight transaction processing for ATF (as per
    Connect transaction processing).
    

APAR Information

  • APAR number

    PM19212

  • Reported component name

    IMS PERF ANALYZ

  • Reported component ID

    5655E1500

  • Reported release

    420

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2010-07-26

  • Closed date

    2010-08-17

  • Last modified date

    2010-12-16

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

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

Modules/Macros

  • H23K420J IPI#AGFL IPI#AGFP IPI#RSAG IPIATFIF
    IPIEVRS  IPIGGET  IPIML    IPIMSGT  IPIOCOMD IPIOINFL IPIOPROC
    IPIOTRAC IPIRSAG  IPIRSC   IPIRSDEC IPIRSJSK IPIRSSAV IPISAPAR
    IPI4PROC IPI4QMGR
    

Fix information

  • Fixed component name

    IMS PERF ANALYZ

  • Fixed component ID

    5655E1500

Applicable component levels

  • R420 PSY UK59742

       UP10/08/20 P F008

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

Document Information

Modified date:
16 December 2010