Validate a requested hub Tivoli Enterprise Monitoring Server

Edit online

While you are interacting with the OMEGAMON enhanced 3270 user interface, a hub Tivoli Enterprise Monitoring Server data source is needed to handle SQL queries that are issued by the user interface workspaces that you want to display.

During the installation of the enhanced 3270 user interface, part of the configuration process is to specify the hub monitoring server, which includes the name of the monitoring server, the IP address, and port number that the SQL queries are sent. For example, as shown in the following screen capture:

Figure 1. CUADATA profile definition shown during the configuration process at installation time

When you log on to the user interface, the hub monitoring server specifications are retrieved from your profile, and an attempt is made to connect to that hub. If the connection attempt is successful, the initial workspace panel for your profile is displayed, for example, the Enterprise Summary (KOBSTART) workspace.

If the hub monitoring server connection attempt fails, the Hub Connectivity Administration workspace is displayed, as shown in Figure 1. This workspace notifies you that a failure occurred and the possible reason for the connection failure.

These are some of the reasons for failed connections to a requested hub monitoring server:

The name of the hub monitoring server is incorrect (names are case-sensitive).
The hub monitoring server IP address is incorrect.
The hub monitoring server TCP/IP port number is incorrect.
The hub monitoring server is not operational (not started or is having communications problems).
TCP/IP or z/OS® UNIX® System Services on the z/OS system that is running the user interface address space is not configured to allow TCP/IP communications between the interface and the hub monitoring server.
A TCP/IP firewall is preventing successful communications between the interface and the hub monitoring server.