When using the Sysview -MVS monitor and selecting the DB2 option why am I limited to seeing metrics for only one of my subsystems?

book

Article ID: 6521

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

In the Sysview -MVS monitor option 6 (DB2 option) any selection to view a specific DB2 substem's metrics always reverts back to the first subsystem

defined.  After selecting a subsequent DB2 ssid from the DB2 list,  the information provided always reverts back to the first DB2 subsystem that was

selected.  The IDB2 DC job shows: (rc 204) Xnet request failed (rs 273) Xnet Duplicate Agent.  

Cause

The  (rc 204) Xnet request failed (rs 273) Xnet Duplicate Agent error condition was caused by the IDB2 ssidSYSP members having an erroneous

XNETID=0000 coded in them.  The default XNETID parameter in the ssidSYSP member(s) should be kept commented out (as shipped) to allow the

identification string to be uniquely built.  This will alleviate the (rs 273) Xnet Duplicate Agent error condition.

Environment

Sysview -MVS monitor DB2 Option (6), Sysview Performance Management Option for DB2 for z/OS (IDB2).

Resolution

The XNETID=0000 statement that was added by the customer in the IDB2 ssidSYSP member(s) was deleted, and the IDB2 data collectors were cycled.

The Sysview -MVS monitor option 6 (DB2 option) now provided metrics for all of the DB2 subsystems being monitored by the correlating IDB2

Data Collector.