BPXB003I OCS text

Explanation

Outboard Communication Server (OCS) encountered a kernel service failure.

In the message text:
text
One of the following:
SOCKET KERNEL SERVICE FAILED. RETURN CODE = return_code, REASON CODE = reason_code.
Indicates that a kernel SOCKET service failed.
BIND KERNEL SERVICE FAILED. RETURN CODE = return_code, REASON CODE = reason_code.
Indicates that a kernel BIND service failed.
LISTEN KERNEL SERVICE FAILED. RETURN CODE = return_code, REASON CODE = reason_code.
Indicates that a kernel LISTEN service failed.
ACCEPT KERNEL SERVICE FAILED. RETURN CODE = return_code, REASON CODE = reason_code.
Indicates that a kernel ACCEPT service failed.
READV KERNEL SERVICE FAILED. RETURN CODE = return_code, REASON CODE = reason_code.
Indicates that a kernel READV service failed.
WRITEV KERNEL SERVICE FAILED. RETURN CODE = return_code, REASON CODE = reason_code.
Indicates that a kernel WRITEV service failed.
SOCKOPT KERNEL SERVICE FAILED. RETURN CODE = return_code, REASON CODE = reason_code.
Indicates that a kernel SOCKOPT service failed.
return_code
The return code from the kernel service. For an explanation of the return code, see Return codes (errnos) in z/OS UNIX System Services Messages and Codes.
reason_code
The reason code from the kernel service. For an explanation of the reason code, see Reason codes in z/OS UNIX System Services Messages and Codes.

System action

OCS stops running.

Operator response

Notify the system programmer.

System programmer response

Correct the problem indicated by the return code and then have the system administrator reissue the ocsconfig command to start OCS. If the cause of the failure cannot be determined, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.

Problem determination

For differences among file systems, if the mount point cannot be resolved, the path is not displayed and the system displays the failing return and reason codes. If the path is not found for the BPXPRMxx value and the system displays only the final component for the system value, the mount point of the file system might be corrupted and therefore not accessible. This might happen if the mount point has been overlaid by another mount operation, if a directory in the path of the mount point is part of an unowned file system, or for other problems with the mount point. Investigate the mount point problem for the file system to determine why it is not accessible.

Module

BPXBOTBD

Source

z/OS UNIX kernel (BPX)

Routing Code

2

Descriptor Code

4