KOBCM0010E Conduit manager Recv Error, rc = return_code, retry = n, microseconds = y+extended diagnostics error and context
Explanation
An IP socket recv() function call ended badly. The return code is return_code, the elapsed duration of the receive attempt is y. The errno and errno2 values in the extended data can help clarify what receive error occurred. If the errno is retry-able, like EINTR, EWOULDBLOCK, or EAGAIN, then retry = n gives the count of retries done. Many of the conduit manager error messages are followed by extended diagnostic information. This information is intended to help users determine the context of the failing query, where:- errno and errno2
- Are further error codes beyond the return code from many system services. When present, the additional codes can help isolate the exact nature of the problem. Since the conduit manager (CM) can be in simultaneous conversation with several data retrieval agents (DRAs) associated with several different hub environments, the following data will help identify just which query to which DRA has encountered a problem.
- Target Hub
- Is the hub environment of the DRA involved in this query.
- DRA IP
- Is the IP address of the LPAR where the DRA is running.
- DRA jobname
- Is the name of the address space where the DRA used is running.
- DRA Port
- Is the port number this DRA is listening to.
- Sequence #
- Is a unique identifier for this query transaction.
- Query
- Is the text string of the query in question.
System action
No further results are processed for this query.User response
Verify that the partner data retrieval agent (DRA) is okay by inspecting its RKLVLOG messages. If the errno value is EWOULDBLOCK, it is likely that the query timed out. Compare the microseconds value to the value found in the most recent log message KOBCM0066I, KOBCM0068I, KOBCM0081I, or KOBCM0083I. If the microseconds in this message are slightly longer than the timeout value, in seconds, found in the most recent preceding message, then the query took too long to process.If the microseconds values are similar to that found in the most recent KOBCM0066I or KOBCM0068I message, you can try increasing the timeout value using command "/F tom,SO_TIMEOUT x" to change the timeout value, where x is the timeout in seconds and tom is the name of the enhanced 3270 address space. You can try increasing the timeout value to see if that resolves the problem.
If the microseconds values are similar to that found in the most recent KOBCM0081I or KOBCM0083I, you can try increasing the timeout value using command "/F tom,DIS_TIMEOUT x" to change the timeout value, where x is the timeout in seconds, tom is the name of the enhanced 3270 address space. Retry the query.
If the problem persists, restarting either the enhanced 3270 user interface or the DRA address space might help.