The All Known Hubs workspace
You can use the All Known Hubs workspace to view status information about each of the available hub Tivoli Enterprise Monitoring Servers in your Sysplex.
Use the All Known Hubs workspace to select and connect to an available hub monitoring server. The connection procedure is detailed in other topics. For more information about the connection procedure, see Changing a hub server connection, Correcting a failed hub server connection, and Logon administration and customization.
You can use the All Known Hubs workspace to view valuable status information about each hub monitoring server that can help you decide the hub to use for your monitoring activities.
The workspace can be scrolled vertically and horizontally to view all of the available hubs and their status information. You can use PF10 and PF11 keys to scroll horizontally and PF7 and PF8 keys to scroll vertically. The workspace also contains vertical and horizontal arrow keys that you can use for scrolling. Select an arrow and press Enter to scroll in this way.

Hub status information
The following fields are displayed for every hub in the All Known Hubs workspace- Hub Name
- The name that is given to a hub monitoring server during IBM Tivoli Monitoring configuration of a runtime environment (RTE).
- Hub Connect Status
- A text value that indicates whether a TCP connection can be established
between the enhanced 3270 user interface address space and the specific
hub monitoring server and whether an SQL query can be issued to the
hub monitoring server. This TCP connection is attempted and then immediately
closed. The TCP port number that is used is the port number that is
assigned to this hub monitoring server during Tivoli Monitoring configuration
of an RTE (typically port number 1918). Check the user interface REXX
log (RKANRXLG DD name) for more details if the status is not Success.
The text values in the Hub Connect Status field can be as follows:
- Success
- The TCP connect and a query completed at the Hub.
- Data Failure
- A TCP send or receive failed with the Hub.
- Timed Out
- A TCP connect cannot complete in the allotted time.
- Connect Fail
- The TCP connect cannot complete.
- TCP Failure
- TCP cannot connect because of a failure with a TCP socket or select call.
- Query Failed
- A TCP connect was successful, but an SQL query to the Hub did not complete.
- CannotAccess
- The TCP port number to access the Hub cannot be determined.
- SAF Denied
- The status cannot be determined because the user does not have security authorization to connect to the specified Hub.
- ITM Service Index Status
- A text value that indicates whether a TCP connection can be established
between the enhanced 3270 user interface address space and the IBM
Tivoli Monitoring Service Index component that is running at the specific
hub monitoring server and whether the Tivoli Monitoring Service Index
data can be retrieved. The TCP port number that is used is the HTTP
port number that is assigned to this hub monitoring server during
Tivoli Monitoring configuration of an RTE (typically port number 1920).
Check the user interface REXX log (RKANRXLG DD name) for further details
if the status is not Success.
The text values in the ITM Service Index Status field can be as follows:
- Success
- The TCP connect and Service Index retrieval completed at the Hub.
- Data Failure
- A TCP send or receive failed with the Hub.
- Timed Out
- A TCP connect and data retrieval did not complete in the allotted time.
- Connect Fail
- The TCP connect cannot complete.
- TCP Failure
- TCP cannot connect because of a failure with a TCP socket or select call.
- No HTTP Port
- The TCP port number that is needed to access the HTTP Server at the Hub cannot be determined.
- Did Not Try
- Because of previous connectivity failures an attempt is not made to find the value.
- SAF Denied
- The status cannot be determined because the user does not have security authorization to connect to the specified Hub.
- SOAP Status
- A text value that indicates whether a TCP connection can be established
between the enhanced 3270 user interface address space and the IBM
Tivoli Monitoring SOAP server component that is running at the specific
hub monitoring server and whether sample SQL query data can be retrieved.
The TCP port number that is used is the HTTP port number that is assigned
to this hub monitoring server during Tivoli Monitoring configuration
of an RTE (typically port number 1920). Check the user interface REXX
log (RKANRXLG DD name) for further details if the status is not Success.
The text values in the SOAP Status field can be as follows:
- Success
- The TCP connect and SOAP query completed at the Hub.
- Data Failure
- A TCP send or receive failed with the Hub.
- Timed Out
- A TCP connect and data retrieval did not complete in the allotted time.
- Connect Fail
- The TCP connect cannot complete.
- TCP Failure
- TCP cannot connect because a failure with a TCP socket or select call.
- No HTTP Port
- The TCP port number that is needed to access the HTTP Server at the Hub cannot be determined.
- Did Not Try
- Because of previous connectivity failures an attempt is not made to find the value.
- SAF Denied
- The status cannot be determined because the user does not have security authorization to connect to the specified Hub.
- Hub Connect Time
- The number of seconds it took to complete the TCP connection to
the hub monitoring server. A value of
n/aindicates the TCP connect cannot be attempted. - Hub Time (bar graph)
- A small horizontal bar graph that shows the Hub Connect Time. This field is highlighted by colors that depend on the threshold settings for the KOBHUBS table, which you can adjust.
- ITM Service Index Time
- The number of seconds it took to retrieve the IBM Tivoli Monitoring
Service Index from the hub monitoring server. A value of
n/aindicates the TCP connect cannot be attempted. - Srvc Time (bar graph)
- A small horizontal bar graph that shows the Tivoli Monitoring Service Index Time. This field is highlighted by colors that depend on the threshold settings for the KOBHUBS table, which you can adjust.
- SOAP Time
- The number of seconds it took to run a simple SOAP SQL query at
the hub monitoring server. A value of
n/aindicates the TCP connect cannot be attempted. - SOAP Time (bar graph)
- A small horizontal bar graph that shows the SOAP Time. This field is highlighted by colors that depend on the threshold settings for the KOBHUBS table, which you can adjust.
- HTTP Port
- The TCP port number that is used with HTTP to access the IBM Tivoli
Monitoring Service Index and the SOAP server. If there is no port
number configured, the text value
Missingis shown. - HTTPS Port
- The TCP port number that is used with HTTPS to access the Tivoli
Monitoring Service Index and the SOAP server. If there is no port
number configured, the text value
Missingis shown. HTTPS is a version of HTTP that supports authentication and encryption. - Hub DRA Count
- The number of Data Retrieval Agents (DRAs) used by the enhanced 3270 user interface for this particular hub monitoring server.
- Hub TCP/IP Host Name
- The host name of the TCP/IP interface in use by the hub monitoring server.
- Hub IP Address
- The IP address in use by the hub monitoring server to which all user interface requests are directed.
- Hub Port
- The TCP port number in use by the hub monitoring server to which all user interface requests are directed. The port number is typically 1918.
- Hub Start Date
- The date that the hub monitoring server job was started.
- Hub Start Time
- The time of day that the hub monitoring server job was started.
- Hub Job Name
- The job name (z/OS system) or task name (Windows, UNIX, or Linux systems) under which the hub monitoring server is running.
- Hub System Name
- The operating system name under which the hub monitoring server is running.
- Hub System Type
- The operating system type under which the hub monitoring server is running. Typical values: z/OS;01.13.00, Linux;2.6.9-67.EL or Win2008;6.0-SP2.