Data retrieval delays/timeouts causing no data conditions

OMEGAMON enhanced 3270 user interface logs are written to the address space SYSPRINT DD statement.

By default, the OMEGAMON enhanced 3270 user interface is configured with the request timeout parameters shown in the following table:
Table 1. OMEGAMON enhanced 3270UI request timeout parameters
Parameter name Description Defaults and overrides
QUERYTIMEOUT User interface workspace query timeout 10 seconds
Note: Some workspace queries are delivered with a timeout override; where the composition of data requests anticipates an elongated response.
PNG_TIMEOUT DRA ping health check (endpoint ping) timeout One second
SO_TIMEOUT DRA data request (socket) timeout 15 seconds
DIS_TIMEOUT Registry refresh (discovery data request timeout Two seconds
CON_TIMEOUT Conduit manager connect to a DRA socket timeout If parameter PNG_TIMEOUT is specified, the CON_TIMEOUT parameter defaults to the value specified in PNG_TIMEOUT.

If parameter PNG_TIMEOUT is not specified, the default value is one second.

These parameter defaults have been established for reasonable or normal operational conditions. There might be unique operational conditions in your environment where the defaults are not optimal. In that case, you can modify the defaults by creating customized OMEGAMON Enhanced 3270 user interface workspaces or specifying parameter overrides in the OMEGAMON Enhanced 3270 user interface environment parameters file (rte.RKANPARU(KOBENV) that is referenced by the address space RKANPAR DD statement. It is recommended that you use embed members so that your override settings persist. For more information, see Enhanced 3270 user interface (KOB) parameters .

Elongated response times when interacting with the OMEGAMON Enhanced 3270 user interface might be a symptom of timeout conditions. For example, during log on, the initial Enterprise Summary (KOBSTART) workspace might take a significant amount of time (more than a few seconds) to render and or the workspace is rendered with partial or no data.
Note: The following message is written to the SYSPRINT log files when request timeouts occur:
KOBCM0010E: conduit manager Recv Error, rc = -1, microseconds = nnnnnnnn
The following items identify the common causes for delay and or timeout conditions. Investigation of these conditions might be complex, this information provides you with some hints for further investigation:
  • The hub monitoring server is running under degraded system conditions (heavy system workload or an under-capacity system) and is being delayed when attempting to service OMEGAMON Enhanced 3270 user interface data requests. In this example, examine the availability and priority of the system resources provided to the hub monitoring server.
  • The OMEGAMON agent is running under degraded system conditions (heavy system workload or an under-capacity system) and is being delayed when attempting to service OMEGAMON Enhanced 3270 user interface data requests. In this example, examine the availability and priority of the system resources provided to the OMEGAMON agent.
  • Data requests submitted from the OMEGAMON Enhanced 3270 user interface to a given Data Retrieval Agent, thorough a TCP/IP conduit, are being impacted by degraded network conditions. In this case, the availability, priority, and configuration of network resources and paths associated with communications between the OMEGAMON Enhanced 3270 user interface and the hub monitoring server and OMEGAMON agents should be examined.
  • An OMEGAMON component (monitoring server or agent) that played a role in a given data request path has gone off-line; the LPAR was terminated, or the address space was terminated. In this case, The OMEGAMON Enhanced 3270 user interface local registry does not contain required agent information to investigate the status of OMEGAMON components, (Managed Systems: on line or off line).
  • The hub and or a remote monitoring server is experiencing operational issues and is being delayed when attempting to service OMEGAMON Enhanced 3270 user interface data requests. A misconfiguration or a special site or environmental configuration requirements might lead to operational issues.
    For example:
    • Operational issues might arise if a monitoring server running on a z/OS operating system is experiencing problems writing to its’ Historical Persistent Datastore files.
    • Operational issues might occur if a monitoring server is unable to bind to its configured TCP/IP port number.
  • The IP domain name resolution is not fully configured on the z/OS operating system where the OMEGAMON Enhanced 3270 user interface, Tivoli Enterprise Monitoring Server and or agent address spaces are running. Also, there might be more than one TCP/IP task running on the z/OS operating system; for these cases, the OMEGAMON address spaces, the OMEGAMON Enhanced 3270 user interface, Tivoli Enterprise Monitoring Server and or agent started task JCL procedures must specify the IP name resolution configuration data set to be specified through the SYSTCPD DDNAME statement.
  • The hub Tivoli Enterprise Monitoring Server is running on a system that has multiple network interfaces and perhaps the preferred and or universally known interface is not being employed; this results in IP connection issues that manifest on the interface as a possible sporadic, no data condition. For more information related to this type of configuration, including the use of the KDEB_INTERFACELIST parameter, see technote KDEB_INTERFACELIST and it variants ("*" and "!*") are misunderstood .