IBM Support

PM34994: MIGRATION OF DB2 V8/V9 TRACE DATA DOES NOT WORK CORRECTLY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 V8/V9 Trace Data are always migrated to the last valid trace
    data format. This migration logic is not correct in some cases.
    
    Additional symptom when batch report was run:
    ICE185A 0 AN S0C4  ABEND WAS ISSUED BY DFSORT, ANOTHER PROGRAM
    OR AN EXIT (PHASE C 3)
    SYSTEM COMPLETION CODE=0C4  REASON CODE=00000004
     TIME=01.32.25  SEQ=20263  CPU=0000  ASID=002D
     PSW AT TIME OF ERROR  078D0000   8000A19C  ILC 2  INTC 04
       ACTIVE LOAD MODULE           ADDRESS=000076F8
    OFFSET=00002AA4
       NAME=FPEUFUD2
       DATA AT PSW  0000A196 - 58F051C1  0E6819EF  A7D40003
       AR/GR 0: 96CC148A/00000007   1: 00000000/000356EC
             2: 00000000/00000000   3: 00000000/00000001
             4: 00000000/00000000   5: 00000000/0000C23B
             6: 00000000/182D31EE   7: 00000000/00000080
             8: 00000000/0019E274   9: 00000000/00000007
             A: 00000000/0000B23C   B: 00000000/0000A23D
             C: 00000000/8000923E   D: 00000000/0000C0FC
             E: 00000000/00000007   F: 01000002/00000080
     END OF SYMPTOM DUMP
    IEF237I JES2 ALLOCATED TO SORTSNAP
    IEF472I SJCHANGI DB2PEP - COMPLETION CODE - SYSTEM=0C4 USER=0000
    REASON=00000080
    

Local fix

  • Please run the report with EXCLUDE(IFCID(343)) to eliminate the
    ABEND0C4-4, before the PTF is ready.
    
    e.g.
    GLOBAL
         TIMEZONE(+05:00)
         FROM (,00:00)
         TO   (,23:59)
         PRESORTED(ACCEPT)
         EXCLUDE(IFCID(343))      <========
         INCLUDE(GROUP(DSNDB0P))
    *
    ACCOUNTING
         REPORT LAYOUT(PCKSUM) DDNAME(ACRPTDL)
         ORDER(PLANNAME)
         SCOPE(GROUP)
    EXEC
    //*
    ..............................................
    This also could be caused by the invalid data from
    IFCID145 processing.
    EXCLUDE(IFCID(145)) can be used as the workaround.
    .
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - Batch Reporting                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Processing of DB2 V8 or V9 Trace        *
    *                      data was not correct in current         *
    *                      OMPE version 510.                       *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    Processing of DB2 V8 or V9 Trace data incorrect
    in batch reporting.
    
    PROBLEM CONCLUSION:
    DB2 V8 or V9 trace data is processed correctly in OMPE V510.
    
    KEYWORDS:
    IFCID 145, IFCID 239, IFCID 337, IFCID 342, IFCID 343
    

Problem conclusion

  • PROBLEM CONCLUSION:
    DB2 V8 or V9 trace data is processed correctly in OMPE V510.
    
    KEYWORDS:
    IFCID 145, IFCID 239, IFCID 337, IFCID 342, IFCID 343
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM34994

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-03-17

  • Closed date

    2011-06-07

  • Last modified date

    2017-02-04

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

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

    UK68528

Modules/Macros

  •    DGOAACUM DGOABORD DGOABORE DGOACALC DGOACMER
    DGOACOMP DGOACREC DGOADIST DGOADNOR DGOAEXIT DGOAEX20 DGOAFLAT
    DGOAFORM DGOAFPCK DGOAIREC DGOALUMP DGOAMPAC DGOAMTRC DGOAQKEY
    DGOARCAL DGOAREDB DGOAREDC DGOAREDD DGOAREDG DGOAREDM DGOAREDP
    DGOAREDR DGOAREDX DGOARXIT DGOASAVE DGOATOPR DGOATPRC DGOATRAC
    DGOATREC DGOAZMER DGOAZREC DGOBARDD DGOBARLK DGOBARLO DGOBARPK
    DGOBARPO DGOBARPT DGOBARRI DGOBARRL DGOBARSH DGOBARSP DGOBARSQ
    DGOBARTE DGOBARTM DGOBATDD DGOBATLK DGOBATLO DGOBATPK DGOBATPO
    DGOBATPT DGOBATRI DGOBATRL DGOBATSH DGOBATSP DGOBATSQ DGOBATTM
    DGOBGENL DGOER000 DGOFECAL DGOFEDAT DGOFEPKG DGOFPDAT DGOFPRIC
    DGOMTLST DGOMTPKG DGONFPAC DGONFWP9 DGONF320 DGOPACNV DGOPA830
    DGOPA840 DGOPA920 DGORAEXT DGORIREP DGORPACC DGORUACC DGORZREP
    DGOVSADK DGOVSAGG FPECMDAT FPEUCBPR FPEUFTDS FPEUFTS2 FPEUIFCI
    FPEUIFC2 FPEUNIDT FPEVRDS1
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R510 PSY UK68528

       UP11/06/08 P F106

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":"5.1.0","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":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 February 2017