KOBCM0045W RC = return code in DRA = Data_Retrieval_Agent_name IP = IP_address, Hub = hub_monitoring_server_name (application_name .table_name)

Edit online

Explanation

Message KOBCM0045W indicates that the Data Retrieval Agent (KOBAGENT) was contacted from the Tivoli® OMEGAMON® Manager, but an error was detected in the Data Retrieval Agent. This error indicates that a repeat attempt might be successful.

The following return codes are possible:
RC=5
The Hub or Remote Tivoli Enterprise Monitoring Server is not yet available.
RC=79
When attempting to delete a table row, the row was not found.
RC=80
When attempting to insert a table row, a duplicate row was found.
RC=155
A hub or remote monitoring server could not be contacted.
RC=202
A TEMS does not contain application support for a particular column.
RC=209
A monitoring server does not contain application support for a particular application and table.
RC=3000
Historical data does not exist for the requested table.
RC=9036
The hub monitoring server is not yet available.
RC=9037
SQL SELECT string is too long, rejected by the DRA
RC=9038
SQL query contains invalid column name, rejected by the DRA
RC=9999
The hub monitoring server is not yet available.
RC=67109015
A hub or remote monitoring server could not be contacted.
RC=67109019
A Hub or Remote TEMS could not be contacted.
RC=67109066
A TEMS does not contain application support for a particular column.
RC=67109073
A monitoring server does not contain application support for a particular application and table.

If this message occurs frequently, check the RKLVLOG for the Data Retrieval Agent that is listed, which might contain more details. If the message indicates that a remote or hub monitoring server is not yet available, confirm that the monitoring server is running and is not out of storage or abending.

System action

The query, insertion or deletion fails and any enhanced 3270 user interface workspace that needs the results might be missing data.

System programmer response

Check the message details for the particular return code (RC) and take the appropriate action. For example, if the message return code indicates that the monitoring server is not available, check the system to confirm that the monitoring server is running correctly. If the return codes indicate that application support files are missing, apply application support (also known as seeding) to the necessary remote and hub monitoring servers.