Error message and return code problems

Table 1 lists problems related to error responses.

Table 1. Error message and return code problems
Problem	Cause	Resolution
The client program is receiving a request status message (RSM)	The Listener sends this message to the client program when it detects an error condition.	Use the return and reason codes from the message to look up the explanation. See Where to find return code documentation.
The implicit IMS™ transaction is receiving return codes in the I/O program communication block (PCB) that are not defined in the section on status codes in	The IMS assist module performs several socket-related functions on behalf of the implicit IMS transaction in response to IMS transaction manager requests. When errors are detected that are not related to the IMS transaction manager request, the IMS assist module sets special return codes in the PCB.	Look up the meaning of the special return codes. See Where to find return code documentation.
The Listener error messages are written to the MVS™ system console instead of the SYSPRINT data set	If the Listener experiences data set I/O errors, it redirects the error messages to the MVS system console.	Check the MVS system console log for I/O errors on the data set to identify the problem. The SYSPRINT DD statement in the JCL procedure to start the Listener specifies the destination data set for the error messages.