APAR status
INTRAN
Error description
OMEGAMON XE for DB2 Performance Expert on z/OS ( OMPE ) Batch Reporting Tips: - When running batch reports for OMPE, the INPUTDD can be either SMF, GTF, DPMOUT, CRD data or NTH stored data in sequential dataset. This sequential dataset of NTH is created when VSAMSEQ option is used in ICAT for NTH (Near Term History) panel, for example: KD261PX OMEGAMON XE for DB2 PE - Near-Term History - PROFID: Start Near-Term History ==> Y (Y, N, C) Specify whether to store trace data to VSAM datasets only (VSAM) Storage type ==> VSAMSEQ (VSAM, VSAMSEQ). - Reporter Migration from OMEGAMON for DB2 V540 to OMPE Former Omegamon/DB2 reporting engine was replaced by Performance Expert (PE) reporting engine beginning from OMPE V310. Details regarding the old Historical reporter that correlates with the current OMPE Batch reports can be found in the OMPE v410 Configuration and Customization guide ( GC18-9979-02 ). http://publib.boulder.ibm.com/epubs/pdf/ko2ccb12.pdf PART 4 , Chapter 17 and Appendix B, a mapping of former Candle reports to the OM DB2 PE reports. - Batch Reporting JCLs Please see OMPE manual - Reporting User's Guide for various reports sample JCL examples, for example Accounting, Statistics, SQL Activity, Explain, Locking Activity, IO Activity, Utility Activity, Record Trace, Audit and SYSPARMS reports from chapters of "Using OMEGAMON XE for DB2 PE Reports" and "Other OMEGAMON XE for DB2 PE Reports". The Interactive Report Selection (option 1 - Create and execute reporting commands) in TSO/ISPF FPEJINIT EXEC allows you to create your own JCL in a dialog. - DB2PM Performance database Sample sources can be found in RKO2SAMP members, for example: create tablespaces/tables, load tables, SQL queries on File and Save data, convert Save files for accounting, statistics, Exception Processing, Locking, Record trace and Audit types of reports. Refer to Report User's Guide Chapter 5 - "The Performance Database and the Performance Warehouse" for more details. - Negative SQL Report Reporting manuals detail the SQLACTIVITY report where you can specify the reporting commands to produce a report of negative SQLCODEs, such as: SQLACTIVITY TRACE INCLUDE(SQLCODE(LT(0))) REPORT EXEC You need to start the PERFM trace of IFCID 58 and its related START SQL traces (59-66) by turning it on via DB2 or by selecting NEGSQL (YES) in the RKD2PAR(COPTssss) member(s), where ssss denotes the DB2 ssid. In addition, the VSAMSEQ option must also be specified in ICAT in order to get these SMF records for reporting on the negative SQL statements. If you turn on this NTH trace for negative SQL statements and do not have VSAMSEQ set, then it is somewhat of a waste, ie. the IFCIDs will be written, but there is no reporting on negative SQL statements. DB2 Trace example: -STA TRACE(PERFM) CLASS(3) or -STA TRACE(PERFM) CLASS(30) IFCID(58,59,60,61,62,63,64,65,66) If you wish to report on failed SQL text only, you would code: INCLUDE(SQLCODE(LT(0)) IFCID(58,59,60,61,62,63,64,65,66)) - Debugging Aid: Batch report abends with S0C4 while sort. Collect the dump: //SYSMDUMP DD DISP=(NEW,CATLG),UNIT=SYSALLDA, // SPACE=(CYL,(300,100),RLSE), // DSN=XXXX.XXXXX.XXXXX (this will allocate the dataset) //SORTDIAG DD DUMMY (produces sort diagnostic messages) //DFSPARM DD * DEBUG ABEND (in column 2) The SYSMDUMP DD will capture a dump when the 0C4 is occurred. The SORTDIAG DD adds extra diagnostic messages into JOBLOG to DFSORT. We would need the dump with corresponding JOBLOG and a JOBLOG from a good run with the diagnostic JCL in place for analysis on the abend situation. - B37 at SORT - The ACWORK dataset keeps abending on SB37 There are several possibilities which can also be combined, of course: 1) Add more //SORTWK* files in the JCL and/or try to divide the input file into parts if it is possible. 2) You can use new option "CALCULATE" to get the size of ACWORK that requires to process the reports. Please see OMPE V510, Reporting User's Guide Chapter 6 - "Using Accounting REDUCE subcommand option to balance performance and dataset space" section. The new options are "OPTIMIZE" and "CALCULATE". New option "OPTIMIZE" allows the customer to balance between the CPU and the amount of ACWORK space. . New option "CALCULATE" is specified along with the normal report requests, the requested report is not produced, but instead the batch job terminates early with the joblog containing an entry stating the size of ACWORK that would be required to process the reports. 3) Use INCLUDE/EXCLUDE to run dedicated selected reports, e.g. for Batch or DRDA only. 4) Reduce manifoldness of generated report data. e.g. ORDER(PLANNAME-PRIMAUTH) creates more report data compared to ORDER(PLANNAME) 5) Use GROUP ... REDUCE INCLUDE ... to reduce manifoldness data groups generated (refer to Report User's Guide Chapter 5 - "Streamlining OMEGAMON XE for DB2 PE processing" section). - Documentation request for problem recreate We would need the batch report job output, INPUT dataset such as SMF trace dataset, INPUT JCL DD stmt, DB2 version info and OMPE STC joblog for problem recreate and analysis. Please terse the datasets and FTP to Ecurep file server ( II11945 for FTP info ). - References - Report Command Reference, Reporting User's Guide, Report Reference. . https://www-304.ibm.com/support/docview.wss?uid=swg27020910 /* DB2 Tools Product Page */ https://www-304.ibm.com/support/docview.wss?uid=swg27020910#omeg a-lib /* OMPE library section of the DB2 Tools Product */ http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.js p /* Information Center for all OMEGAMON Products */ http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.js p?topic=%2Fcom.ibm.omegamon.xe_db2.doc%2Fko2welcome_pe.htm /* Information Center for all OMEGAMON for DB2 products */ ================================================================ Known issues in OMPE Batch Reporting (compid= 5655ope00 ) APARs/PTFs for OMPE V410 deleted ================================================================ APARs/PTFs for OMPE V420 from 2010 onwards: PM50567 / UK75377 F201 PM49833 / UK76747 F203 / UK76748 PM56515 / UK77221 F203 PM55509 / UK77221 F203 PM57461 / UK79190 F205 PM71881 / UK82078 F209 PM82179 / UK94474 F305 PM93767 / UI12264 F311 N/A' IN SOME UTILITY TRACE REPORT FEILDS PI21156 / UI21630 F409 STATISTICS REPORT INCORRECT, REPORTS 4K PI25281 / UI21628 F409 ABEND0C4 IN DGORPHVA ON SQLACTIVITY TRACE PI43273 / UI28657 EXPLAIN DISPLAYS DUPLICATE ROWS ================================================================ APARs/PTFs for OMPE V510 Batch Reporting, 2013 onwards PM75430 = PM73547 / UK90576 F301 Missing data from Acctg report PM75714 / UK90886 F301 DB2 V10 ROLLUP THREAD ACCOUNTING PACK PM74713 / UK90972 F301 EDMPOOL COLUMN IN INF00.DB2PMSYSPAR_10 PM73071 / UK91158 F301 Various Acctg/stats table issues PM77817 <= PM74888 / UK90705 (F301) =a10 SECP CPU VALUE IN ACCT PM78041 / UK91867 F302 RECTRACE RPT NEEDS TYPE OF INCOMPA PM76016 / UK90672 F301 SAVE of report failed FPEA0700S PM82259 / UK93341 F304 Incorrout Stats values for Group BP PM85113 / UK94595 F305 Perfm degrade w/GROUP command PM85128 UK94848 F306 MISSING PACKAGES WHEN RUNNING ACCOUNTI PM85942 UK96243 F307 GROUP BUFFER POOL NAME NOT SHOWN PM88571 / UK95707 F307 AUDIT REPORT TYPE AUTHCNTL HAS INCORRECT PM90613 / UK95036 F306 % PAGES IN USE FOR SKELETON AND DBD PAGES PM93606 / UK98326 F310 INCORRECT HUGE VALUE IN #CP/X PARALLEL PM93767 / UI12265 F311 N/A' IN SOME UTILITY TRACE REPORT FEILDS PM95135 / UI14703 F401 INCORRECT BPX VALUES IN EXCEPTION LOG PM96290 / UI12023 F310 IMPROVEMENTS CORRECTIONS FOR SPREADSHEET PM96398 / UI13709 F312 IFCID316 not valid data PM97502 / UI13308 F312 DISCREPANCY IN ACCOUNTING TRACES OUTPUT PI06091 / UI15504 F402 DIFFERENT QWACAWTL VALUES IN OMPE BATCH PI07326 / UI15811 F403 BATCH REPORTING 0C4-011 FPEUFUD2 OFFSET=0 PI25583 / UI22472 F410 BATCH REPORTER BUFFER POOL ADJUSTMENTS PI25914 / UI23803 F412 IFCID 366 RECORD TRACE SHOWS BLANKS PI26193 / UI23615 F412 ABEND 0CC WHILE RUNNING BATCH REPORT PI29410 / UI25141 F502 EXCEPTION LOG SHOWS INCORRECT DSG =============================================================== APARs/PTFs for OMPE V511 Batch Reporting: PM75430 = PM73547 / UK90577 F301 Missing data and abend0c1 PM75714 / UK90887 F301 DB2 V10 ROLLUP THREAD ACCOUNTING PACKAGE PM73071 / UK91159 F301 VARIOUS ACCT & STATISTICS TABLES PM78041 / UK91868 F302 RECTRACE RPT NEEDS TYPE OF INCOMPA PM82817 / UK92380 F303 SAVE of report failed w/ FPEA0700S PM82259 / UK93342 F304 Incorrout Stats values for Group BP PM84155 / UK94042 F305 FPEU0101S OBGLCN for exception report PM85113 / UK94596 F305 Perfm degrade w/GROUP commanPM85660d PM85660 / UK95377 F306 Enhance RID LIST monitoring in ACC RPT PM85128 / UK94849 F306 MISSING PACKAGES WHEN RUNNING ACCOUNTI PM85942 / UK96244 F307 GROUP BUFFER POOL NAME NOT SHOWN PM86840 / UK95921 F307 SPECIAL HANDLING FOR IDAA QLAC SECTIONS PM87384 / UK94985 F306 IMPROVE HANDLING OF PACKAGE WAIT TIMES PM88571 / UK95708 F307 AUDIT REPORT TYPE AUTHCNTL HAS INCORRECT PM96398 / UI13710 F312 IFCID316 not valid data PM93767 / UI12266 F311 N/A' IN SOME UTILITY TRACE REPORT FEILDS PM94202 / UI11962 F310 QWAC SECTION INSTRUMENTATION ENHANCEMENTS PM95135 / UI14704 F401 INCORRECT BPX VALUES IN EXCEPTION LOG PM95251 / UK98328 F310 OMPE ABEND 0C4-004 DB2PM OFFSET 00225300 PM96290 / UI12024 F310 IMPROVEMENTS CORRECTIONS FOR SPREADSHEET PM96506 / UI15013 F402 Serviceability Enhancements PM97502 / UI13309 F312 DISCREPANCY IN ACCOUNTING TRACES OUTPUT PM98585 / UI13576 F312 CORRUPTED DATA FROM BATCH REPORTING USING PM98699 / UI14452 F401 INCORRECT VALUE IN #CP/X PARALLEL FIELD PM99308 / UI14830 F402 IFCID 360 SUPPORT IN BATCH RECORD TRACE PM99691 / UI13072 F311 ACCELERATOR INSTRUMENTATION ENHANCEMENTS PI06091 / UI15505 F402 DIFFERENT QWACAWTL VALUES IN OMPE BATCH PI06838 / UI13387 F312 TIME FIELDS SET TO N/P IN STATEMENT CACHE PI07326 / UI15812 F403 BATCH REPORTING 0C4-011 FPEUFUD2 OFFSET=0 PI07668 / UI15722 F403 URLGWTH VALUE IN OMPE SYSTEM PARAMETTERS PI09449 / UI16177 F403 AFTER A B37-04 ABEND ON THE LOWORK FILE. PI10530 / UI17820 F405 FPEU0101S INTERNAL ERROR IN MOD FPEMEXA0, PI10732 / UI17268 F404 ABEND 0C4-004 IN FPECMAIN OFFSET 000BD714 PI11775 / UI17327 F404 CORRUPTED PLANNAME FIELD IN OMPE REPORT PI12525 / UI17919 F405 ORDERING BY ACTNAME CAN RESULT N/C FEILDS PI25427 / UI22304 F410 ADD NEW FIELD IN BUFFER POOL REPORT PI23577 / UI22393 F410 HIGH SYNC READ I/O VALUES PI25427 / UI22304 F410 BATCH REPORTER BUFFER POOL ADJUSTMENTS PI25171 / UI23223 F411 FPEU0101S INTERNAL ERROR IN DGOFEDPM PI25914 / UI23804 F412 IFCID 366 RECORD TRACE SHOWS BLANKS PI26193 / UI23615 F412 ABEND 0CC WHILE RUNNING BATCH REPORT PI28631 / UI23719 F412 FPEU0101S FPEUFLN2 CODE=1, DATA=0000001 PI29410 / UI25142 F502 EXCEPTION LOG SHOWS INCORRECT DSG PI30452 / UI24733 F501 OMPE JOB ABENDS VSAM DUPLICATE KEY ERROR PI38236 / UI27801 F505 ABEND0C4 IN DGOAREDB BATCH PROCESSING PI43273 / UI28658 EXPLAIN DISPLAYS DUPLICATE ROWS =============================================================== APARs/PTFs for OMPE V520 Batch Reporting: PM95135 / UI14705 F401 INCORRECT BPX VALUES IN EXCEPTION LOG PM96398 / UI13711 F312 IFCID 316 DATA NOT VALID WHEN PROCESSED PM98092 / UI13658 F312 Support DB2 IFI enhancements for IBM DB2 PM98585 / UI13577 F312 CORRUPTED DATA FROM BATCH REPORTING USING PM99040 / UI12456 F311 AUTONOMOUS SQL PM99280 / UI13091 F312 DISCREPANCY IN ACCT TRACES OUTPUT PM99308 / UI14831 F402 IFCID 360 SUPPORT IN BATCH RECORD TRACE PI05051 / UI14521 F401 N/A' IN SOME UTILITY TRACE REPORT FIELDS PI06838 / UI13388 F312 TIME FIELDS SET TO N/P IN STATEMENT CACHE PI06883 / UI17605 F405 BATCH REQUESTER FIELD DOES NOT SHOW LONG PI07326 / UI15813 F403 BATCH REPORTING 0C4-011 FPEUFUD2 OFFSET=0 PI07668 / UI15723 F403 URLGWTH VALUE IN OMPE SYSTEM PARAMETTERS PI08288 / UI15982 F403 SUPPORT INSTRUMENTATION ENHANCEMENTS FOR PI09449 / UI16178 F403 AFTER A B37-04 ABEND ON THE LOWORK FILE. PI09581 / UI17285 F404 BATCH ACCOUNTING SUPPORTS IFCID 380, 381 PI10530 / UI17821 F405 FPEU0101S INTERNAL ERROR IN MOD FPEMEXA0, PI10732 / UI17269 F404 ABEND 0C4-004 IN FPECMAIN OFFSET 000BD714 PI11775 / UI17328 F404 CORRUPTED PLANNAME FIELD IN OMPE REPORT PI12525 / UI17920 F405 ORDERING BY ACTNAME CAN RESULT N/C FEILDS PI12538 / UI17260 F404 ENHANCEMENTS IN STORAGE REPORTING PI12870 / UI18439 F405 DIFFERENT QWACAWTL VALUES IN OMPE BATCH PI13644 / UI16647 F404 ABEND0C4 PROCESSING IFCID204 QW0204UR PI15377 / UI17338 F404 INCORRECT VALUES RECORD TRACE REPORT PI16762 / UI18047 F405 ENHANCEMENTS IN BATCH REPORTING PI18458 / UI19559 F407 SUPPORT OF IFCID 365 IN RECORD TRACE. PI22243 / UI20466 F408 INCORROUT STATISTICS REPORTS PI25427 / UI22305 F410 ADD NEW FIELD IN BUFFER POOL REPORT PI23577 / UI22394 F410 HIGH SYNC READ I/O VALUES PI25427 / UI22305 F410 BATCH REPORTER BUFFER POOL ADJUSTMENTS PI25171 / UI23224 F411 FPEU0101S INTERNAL ERROR IN DGOFEDPM PI26193 / UI23617 F412 ABEND 0CC WHILE RUNNING BATCH REPORT PI28211 / UI24153 F412 0C1 IN DB2PM FPEDB2PM ACCOUNTING REPORT PI28338 / UI24269 F501 SUPPORT FOR DB2 11 SIMULATED BUFFER POOLS PI29410 / UI25143 F502 EXCEPTION LOG SHOWS INCORRECT DSG PI32621 / UI24444 F501 INCORROUT AFTER UI24269/PI28338, STATS PI30452 / UI24734 F501 OMPE JOB ABENDS VSAM DUPLICATE KEY ERROR PI31784 / UI24995 F502 A LOOP IN FPECMAIN PI33401 / UI25623 F503 FIX SOME ISSUES AND DOCUMENTATION PI34961 / UI27740 F505 FPEC2202E - FILE SUBCOMMAND LIMITATION 5 PI38236 / UI27802 F505 ABEND0C4 IN DGOAREDB BATCH PROCESSING PI43273 / UI28659 EXPLAIN DISPLAYS DUPLICATE ROWS ====================================================== APARs/PTFs for OMPE V530 Batch Reporting: PI43273 / UI28660 EXPLAIN DISPLAYS DUPLICATE ROWS =============================================================== IBM Tivoli OMEGAMON XE for DB2 Performance Expert 5655OPE00 IBM Tivoli OMEGAMON XE for DB2 Performance Monitor 5655OPE00 PID 5655W35 COMPID 5655OPE00 R511
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II14642
Reported component name
PA LIB INFO ITE
Reported component ID
INFOPALIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-08-23
Closed date
Last modified date
2015-06-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
18 June 2015