DB2 Connect Server
Select this main menu option for information about DB2 Connect Servers that serve as DB2 Connect gateways and are connected to the selected Db2 subsystem.
Other DB2 Connect Server information is displayed in panels that are documented in Thread Activity and Resource Managers.
No DB2 Connect Server connections
is displayed.
________________ ZDB2C VTM O2 V540./C SZ91 07/31/13 17:06:16 2
> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11
> G.
===============================================================================
> DB2 CONNECT SERVER
DB2C DB2C Master: SZ91
+
+ Name IP Address Node Name Status Server Name
+ --------------- --------------- ---------- --------------- ---------------
+ IBM-590C1A11DE1 9.76.24.33 N/P ACTIVE DB2
+ IBM-590C1A11... 9.65.68.52 N/P INACTIVE N/P
+ IBM-3B8F56F0... 9.76.6.137 N/P INACTIVE N/P
===============================================================================
Navigation
You can scroll through the list using F7 and F8, or select a particular list item and press F11 (Zoom). For more information, see the description of panel Db2 Connect/Gateway Statistics.
Fields
- DB2C Master
- Shows the name of the member of the data sharing group that controls DB2 Connect monitoring for
the group. If
N/A
is shown, the DB2C Master is currently being changed. For more information, see the description of panel Redirect Monitoring to Another Db2. - Name
- Shows the name in the database manager configuration file at the client node. It identifies the client node that is running the application.
- IP Address
- Shows the current IP address.
- Node Name
- Shows the name of the node being monitored by the database system monitor. It identifies the database server node being monitored.
- Status
- Shows whether the server is active or inactive.
- Server Name
- Shows the name of the
database manager instance for which the snapshot was taken.
If the system contains more than one instance of the database manager, this name is used to uniquely identify the instance for which the snapshot call was issued. Along with configuration NNAME at monitoring (server) node, this information can be useful if you are saving your monitor output in a file or database for later analysis, and you need to differentiate the data from different instances of the database manager.