MSN not found message displays for the enhanced 3270 user interface

If panels in the Enhanced 3270 User Interface display a MSN not found message, the managed system you are attempting to view is not known at this time.

In this case, the managed system may have recently gone offline, or if your monitoring environment was recently started, the monitoring agents might not have registered with the hub monitoring server and might not have been discovered by the enhanced 3270 user interface.

See Problem 1: Monitoring agent is offline for information about how to determine when an agent is offline.

Also check the status of the data retrieval agent (DRA). Search the RKLVLOG for instances of KOBDR. If you see a message similar to the following messages:

KOBDRAG not found

Check the E3270 load libraries are in the RKANMODL load library concatenations for the monitoring agent and that the KDSLLIST member in RKANPAR (not RKANPARU) to ensure that these load libraries have an entry for KOBAGENT.

The MSN not found message may also be displayed when the monitoring agent has recently started and the enhanced 3270 user interface has not discovered the newly started monitoring agent. Look in the RKLVLOG if your hub or remote monitoring server is running on z/OS®, or the MS log if your hub monitoring server is running on a distributed platform, for following message:

Remote node <stcname:sysid:KN3AGENT> is ON-LINE.

If any instances of this message are written after the last registry refresh occurs (message KOBCM0058I in the SYSPRINT log of the enhanced 3270 user interface started task), you must refresh the DRA Registry. The database resource adapter (DRA) registry tracks the connections and disconnections from database control, telling the enhanced 3270 user interface when a shutdown of DBCTL has been requested or if DBCTL has failed. This facility manages threads, establishing contact with the DBCTL address space and loading the DRA startup parameter table.

The DRA registry is refreshed when the enhanced OMEGAMON® 3270 user interface (CANSTOM) is started. A refresh is also done internally every five minutes, by default (see message KOBCM0054I for your registry refresh interval).

To refresh this registry, either restart your enhanced OMEGAMON 3270 user interface started task, wait for the default refresh, or issue the following command:

/F canstom,REGREFRESH

You can also refresh the registry by opening the Enhanced OMEGAMON 3270 User Interface Tools pull-down and selecting Option 3. Registry Refresh. The following messages found in the SYSPRINT log indicate that registry refresh has completed:

KOBCM0058I: Registry Refresh statistics:
+           Refresh completed in      = 162 millisec
+           Hubs Currently active     = 1
+           Hubs No longer active     = 0
+           Hubs Just added           = 1
+           DRAs Currently active     = 1
+           DRAs Newly discovered     = 1
+           DRAs Removed              = 0
+           DRAs Registration errors  = 0
+           MSNs Currently registered = 26
+           MSNs Newly discovered     = 26
+           MSNs Removed              = 0
+           MSNs With TEMS errors     = 0
+           MSNs Registration errors  = 0
+           MSLs Currently registered = 26
+           MSLs Newly discovered     = 26
+           MSLs Removed              = 0
+           MSLs With TEMS errors     = 0
+           MSLs Registration errors  = 0