PICKDB2 command issuing DBG55092E Data Collector not active | DBG550I9I Db2 location not known to SYSVIEW for DB2
search cancel

PICKDB2 command issuing DBG55092E Data Collector not active | DBG550I9I Db2 location not known to SYSVIEW for DB2

book

Article ID: 277666

calendar_today

Updated On:

Products

SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

Issuing the PICKDB2 command (PF6) in Sysview for Db2 (IDB2) the defined remote data collectors when selected reflect the error:

DBG55092E Data Collector not active |  DBG550I9I Db2 location not known to SYSVIEW for DB2.   

All the necessary RAF VTAM jobs and parameters (as documented) have been successfully run and defined.   

For this particular customer environment the VTAM CDRM implementation is using TCPIP (via Enterprise Extender).  

Note: The respective IDB2 DC's are accessible from their corresponding LPARs, but not via remote access.

Environment

IDB2 r20, VTAM CDRM implementation using TCPIP (via Enterprise Extender) 

Cause

(Review of the provided GTF trace), the failure was due to BNDYN=NONE and no ADJCLUST table present for the DEFAULT NETID. 

Resolution

The GTF trace revealed the failure being due to BNDYN=NONE and no ADJCLUST table present for the DEFAULT NETID. 
This table is required because the CDRSC was coded without NETID parameter.   As indicated, the remote DB2 is pre-defined in CDRSC major node without NETID and with a CDRM instead of CPNAME so no directory entry is available that would map the ALIAS to a real name.  (If you had CPNAME= coded, then a directory entry would have been created for the real name.) 

Code an ADJCLUST table to allow for ALIAS searching over CP-CP sessions or restart VTAMs with BN=NO if there are no external networks to be connected.