IBM Support

PK19465: APPLICATION TRACE TO MEMORY RESULTS IN INCORROUT. LOST DATA DUE TO VSAMTSK OR IFCARLC

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Invoking application trace to memory may result in incorrect
    data in many of the ATF displays. Statement number (STM#) may be
    incorrect. The number of SQL calls reported on high level panels
    may not agree with the detail.
    
    INCORROUT on panels ATVP,ATD1, ATD2, ATSI
    
    This will also effect the equivalent CUA screens
    
    
    Message
    O21152   NUMBER OF TRACE RECS LOST DUE TO IFCARLC:  00001252
    O21152   NUMBER OF TRACE RECS LOST DUE TO VSAMTSK:  00001252
    in the OMEGAMON DB2 address space
    DSNW133I in the DB2 address space
    
    due to volume of trace data generated.
    

Local fix

  • For lost data conditions consider refining the selection
    criteria of what is being traced.
    
    Consider usermod TKANSAM(KO2MOD04) to increase IFI buffer size
    for ATF
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of OMEGAMON XE for DB2 PE/DB2PM V310   *
    ****************************************************************
    * PROBLEM DESCRIPTION: After running ATF, the users see        *
    *                      messages 021152 NUMBER OF TRACE         *
    *                      RECS LOST DUE TO ICARLC                 *
    *                      O21152 NUMBER OF TRACE RECS             *
    *                      LOST DUE TO VSAMTSK                     *
    *                      with counts greater than zero.          *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF                                *
    ****************************************************************
    In a high-activity trace (ATF), DB2 may generate records
    faster than the ATF process is writing them out, resulting
    in non-zero value for IFCARLC and VSAMTSK.
    

Problem conclusion

  • Introduce code to write records when internal buffer begins
    to fill.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK19465

  • Reported component name

    OM XE DB2PE/PM/

  • Reported component ID

    5655OPE00

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-02-08

  • Closed date

    2006-04-10

  • Last modified date

    2006-05-01

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

    OA14303

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

Modules/Macros

  •    DUMM4KO2
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM/

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R310 PSN UK13407

       UP06/04/14 P F604

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 May 2006