PI09581: BATCH ACCOUNTING SUPPORTS IFCID 380, 381 ALTERNATIVELY TO IFCID 233 WHEN REPORTING A STORED PROCEDURE OR UDF.

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• 1. ORDERING BY ACTIVIY NAME in batch Accounting accounts for
  subprograms of a STORED PROCEDURE and UDF by using ifcid 380,
  381. Ifcid 233 is no longer needed but is tolerated.
  2. Improvement of PACKAGE filtering.
  3. Correct reported class 10 data.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component                           *
  *                 - Batch Reporting                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Batch Accounting's STORED PROCEDURE     *
  *                      and UDF reporting will be able to       *
  *                      process IFCIDs 380, 381 alternatively   *
  *                      to IFCID 233 when reporting             *
  *                      by activity name.                       *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  Batch Accounting's STORED PROCEDURE and UDF reporting will be
  able to process IFCIDs 380, 381 alternatively to IFCID 233
  when reporting by activity name.
  
  PROBLEM CONCLUSION:
  Batch Accounting offers a new function by this PTF.
  If available, IFCIDs 380 for STORED PROCEDUREs (SP)
  and 381 for USER DEFINED FUNCTIONs (UDF) are being processed
  when REPORT ORDER(ACTNAME) was requested. These IFCIDs can be
  used now for identifying SP and UDF parent routines.
  These IFCIDs are an alternative and are cheaper than IFCID 233
  when collecting a DB2 trace.
  If no IFCIDs 380, 381 were found in DB2 trace data the
  Accounting process still tries to find and use IFCIDs 233 for
  identifying main SP and UDF routines.
  The new function completes the original Accounting Activity
  Name processing which is without IFCIDs 380, 381, and 233.
  In that case nesting subroutines cannot be identified and
  each package marked as SP or UDF is treated as an independent
  routine.
  
  KEYWORDS:
  ACCOUNTING REPORT ORDER ACTNAME STORED PROCEDURE
  USER DEFINED FUNCTION UDF IFCID 380 381 233 SUBROUTINE
  

Problem conclusion

Temporary fix

Comments

• PROBLEM SUMMARY:
  Batch Accounting's STORED PROCEDURE and UDF reporting will be
  able to process IFCIDs 380, 381 alternatively to IFCID 233
  when reporting by activity name.
  
  PROBLEM CONCLUSION:
  Batch Accounting offers a new function by this PTF.
  If available, IFCIDs 380 for STORED PROCEDUREs (SP)
  and 381 for USER DEFINED FUNCTIONs (UDF) are being processed
  when REPORT ORDER(ACTNAME) was requested. These IFCIDs can be
  used now for identifying SP and UDF parent routines.
  These IFCIDs are an alternative and are cheaper than IFCID 233
  when collecting a DB2 trace.
  If no IFCIDs 380, 381 were found in DB2 trace data the
  Accounting process still tries to find and use IFCIDs 233 for
  identifying main SP and UDF routines.
  The new function completes the original Accounting Activity
  Name processing which is without IFCIDs 380, 381, and 233.
  In that case nesting subroutines cannot be identified and
  each package marked as SP or UDF is treated as an independent
  routine.
  
  KEYWORDS:
  ACCOUNTING REPORT ORDER ACTNAME STORED PROCEDURE
  USER DEFINED FUNCTION UDF IFCID 380 381 233 SUBROUTINE
  
  CIRCUMVENTION:
  Using a DB2 trace that is including IFCID 233
  in addition to IFCID 3 and 239.
  

APAR Information

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

  PM97652

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

  UI17285

Modules/Macros

• DGOAACUM DGOACALC DGOACMER DGOACOMP DGOACREC
  DGOACREP DGOADIST DGOAIREC DGOAIREP DGOAMSGS DGOAMTRC DGOARCAL
  DGOAREDB DGOAREDC DGOAREDD DGOAREDG DGOAREDI DGOAREDM DGOAREDP
  DGOAREDR DGOAREDX DGOASAVE DGOATRAC DGOATREC DGOAZMER DGOAZREC
  DGOAZREP DGOEINIT DGOFPRIC DGONCREP DGONIREC DGORAEXT DGORCREP
  DGORCRE2 DGORIREP DGORPACC DGORUACC DGORZREP FPECHECO FPECHE15
  FPECHE35 FPECHFLT FPECHNMP FPECKECO FPECKE15 FPECKE35 FPECMDAT
  FPECQECO FPECQE15 FPECQE35 FPECVCRS FPECVVCD FPEUFFER FPEUFFE2
  FPEUFIOI FPEUFIO2 FPEUFOCR FPEUFOC2 FPEUFTDS FPEUFTS2 FPEUFUIS
  FPEUFUIT FPEUFUNI FPEUFUN2 FPEUFWMG FPEUFWMX FPEUFYDY FPEUFYD2
  FPEUFYLD FPEUFYST FPEUFYS2 FPEUIFCI FPEUIFC2 FPEUMSGS
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R520 PSY UI17285

     UP14/04/25 P F404

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.