Using same OBID data set in Sysview for Db2 Data Collector monitoring members of a DB2 Data Sharing group see message DBG48006E

Products

• SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

See message DBG48006E OBID TABLE FILE IS INVALID in Sysview for Db2 for z/OS (IDB2) Data Collector started task DBGPRINT output when
use the same OBID data set in the IDB2 Data Collectors that are monitoring all members of a DB2 Data Sharing group.

Requirement to add the JCL parameter =GROUP=db2group in the JCL that initializes the OBID data set.

Resolution

Each IDB2 Data Collector that is monitoring a member of a Db2 Data Sharing group can use a single OBID file.
This OBID data set is created and populated by the utility coded in the IDB2OBI JCL member of the product SOURCE data set.
You would only need to run it against one member of the DS group.

In order for a single OBID file to be used by all IDB2 Data Collectors monitoring members of a DB2 DS group, modify the IDB2OBI JCL member as follows:

1. Code the =GROUP parameter in the PARM entry for the EXEC card in the JCL.
   
   e.g.
   Assume DB2T is a member of the DS group DSNGET0.
   To create a single OBID file that can be used for all members of the DSNGET0 group, code the IDB2OBI JCL as follows:
   ...
   //IDOBLOAD EXEC PGM=IDB2OBI,REGION=0M,COND=(0,LT),
   // PARM='=UPPER=NO =PLAN=IDBOxxxx =SSID=DB2T =GROUP=DSNGET0'
   ...
   Plan IDBOxxxx would have been bound as part of the product post install process, where xxxx can be any 4 characters.