Metrics for SMF 101 (DB2) Package Level Records Not Produced for MOI Ingestion

Products

• Mainframe Operational Intelligence

Issue/Introduction

After upgrading MOI to 2.0.5 and ensuring CCS Message Service was at the required level (15.0 with PTF SO10574)  we are successfully receiving 'plan-level' metrics for SMF 101 (DB2).    However we are not receiving 'package-level' metrics.  


LPAR:  MSTRSVW   (MSTRSVW.lvn.broadcom.net)

CCS Message Services:  STC  ZMSCAW2
    - INSTANCE Dir:  /u/users/cai/ccsdeploy/cfgb/instance/zmscaw2

CCS Data Mover: STC ZDMVPROC 

MOI Instance:  https://oi-n-plex-dmo01.lvn.broadcom.net:61443/MPM/#/view/Analytics   (demo/demo)

 
See attachments for logs, sysout, and screen prints

 

    

Environment

Release : 2.0    MOI 2.0.05 and higher

Component : CCS MESSAGE SERVICE

Resolution

It was determined that the SMF DB2 101.1 records that were added to MOI in release 2.0.05 are not automatically produced for each LPAR.   These SMF record collections have to be turned on for each LPAR where these records need to be generated. 

Here are the instructions for turning on the DB2 plan/package information for inclusion in the SMF 101.1 records being produced:

 

DB2

For DB2, trace class 1 is needed for plan level metrics (subtype 0), and 7 and 8 are needed for package level metrics (subtype 1).  

Issue the DISPLAY TRACE command to validate:

DSNW127I  !D121 CURRENT TRACE ACTIVITY IS -         
TNO TYPE   CLASS        DEST QUAL IFCID             
01  STAT   01,03,04,05, SMF  NO                     
01         06                                       
02  ACCTG  01,02,07,08, SMF  NO                     
02         10                                       
*********END OF DISPLAY TRACE SUMMARY DATA*********

To permanently change the class setting, the SMFACT parameter on the DSN6SYSP macro must be changed,  must be assembled and linked into module DSNZPARM, and the subsystem must be restarted.  The DB2 standard installation has the JCL to perform this update in  SDSNSAMP(DSNTIJUZ).