AIOps: Monitoring and Observability

AIOps: Monitoring and Observability

AIOps: Monitoring and Observability

Comprehensive performance monitoring and observability of your IBM Z environment. Solutions include OMEGAMON, Service Management Suite for z/OS, and IBM Z Application Performance Management Connect

 View Only

Compatibility Check Utility for OMEGAMON AI for Db2 6.1.0 Performance Database users (by Vytautas Ambrasas and Matthias Tschaffler)

By Matthias Tschaffler posted 05/18/26 11:07 AM

  

The OMEGAMON AI for Db2 Performance Database (short PDB) allows you to store Db2 performance data for your Db2 subsystem as well as your applications for an extended period of time, thus allowing users to do capacity planning and resource consumption projections.

The PDB is delivered as a set of Db2 DDL artifacts in the tHilev.TKO2SAMP library.

Loading Db2 performance data into the PDB relies on TKO2SAMP load statements matching the binary format of your FILE or SAVE-CONVERT data sets. 

When the rollout for new maintenance updates one side (TKANMOD) but not the other (TKO2SAMP), you get errors during the load process or even worse - potentially silent data corruption - leading to wrong numbers in your PDB tables with no obvious error in sight.

IBM Z OMEGAMON AI for Db2 6.1.0 introduces the Peformance Database Compatibility Check Utility, a simple utility that catches this mismatch before it becomes a problem.

During report generation, the Batch reporter stamps each FILE or SAVE-CONVERT data set with the TKO2SAMP members it used. The new program FPEPDBCH takes your current TKO2SAMP members and compares them to the timestamp as captured in the TKO2SAMP module. If anything drifts, it tells you which members are out of date and which APAR to apply.

Example:

//TSXXXXC JOB (ACCT#),' OMPE PDB DML',CLASS=A,                    
//      REGION=0M,MSGCLASS=X,NOTIFY=&SYSUID                       
//STEP1    EXEC PGM=FPEPDBCH,PARM='TDDB2T.V610.TKO2SAMP'          
//STEPLIB  DD  DSN=TDDB2T.V610.TKANMODP,DISP=SHR                  
//INPF     DD  DSN=OMDB2.SACC.FILE,DISP=SHR             
//SYSPRINT DD  SYSOUT=*                                           
//SYSOUT   DD  SYSOUT=*                                           
//STEP2    EXEC PGM=DSNUTILB,COND=(8,EQ,STEP1),                   
//          PARM='OC1A,LOADB2PE,'                                 
//STEPLIB  DD DISP=SHR,DSN=OC1A.SDSNEXIT                          
//         DD DISP=SHR,DSN=DSN.VD10.SDSNLOAD                      
//SYSUDUMP DD DUMMY                                               
//UTPRINT  DD SYSOUT=*                                            
//SYSPRINT DD SYSOUT=*                                            
//SYSREC   DD DISP=SHR,DSN=OMDB2.SACC.FILE              
//SYSIN DD DISP=SHR,DSN=OLD.TKO2SAMP($REPDML)   
//      DD DISP=SHR,DSN=OLD.TKO2SAMP(DGOALFGE)  
//      DD DISP=SHR,DSN=OLD.TKO2SAMP($REPDML)   

Could return:

FPED1005E  Error: 1 load member is not compatible with provided FILE dataset.                                                     
     //'TDDB2T.V610.TKO2SAMP(DGOALFGE)'                                                                                           
FPED1005E  Error: Update your TKO2SAMP to APAR PH69153 and run update statements located in DGOAUPDB against respective PDB tables

RC=0 means you're good to load. RC=8 means stop and update your TKO2SAMP first.

One extra JCL step - zero corrupted tables!

#IBMZ #IBMChampion #AIOpsonZ #OMEGAMON

0 comments
28 views

Permalink