5.4 The Server Response Log File

When TMA TCP for IMS receives a client request from a remote system, the request is inserted into the IMS message queue for delivery to the specified IMS server transaction. The IMS server transaction processes the request and inserts the response (if required) into the IMS message queue for delivery to TMA TCP for IMS. When the response is received, it is returned to the requesting remote system.

Each IMS server request and the associated response contains a unique request/response ID, consisting of the date and time that TMA TCP for IMS was started, and a serial number. The TMA TCP for IMS gateway uses the request/response ID to correlate each response with a pending server request.

It is possible that TMA TCP for IMS may receive a response from an IMS server transaction for which no pending request exists. This can occur under any of the following conditions:

• The TMA TCP for IMS gateway was restarted after the request was sent to IMS but before the response was received. In this case, the response is usually received when TMA TCP for IMS is subsequently restarted.
• The TCP/IP connection with the remote gateway was lost after the request was sent to IMS but before the response was received.
• The request was sent to IMS, but timed out and was aborted before the response was received from IMS.
• The IMS server transaction returned a response to a request that did not require a response.

When a response cannot be correlated with a pending request (that is, a pending request with a matching request/response ID cannot be found), TMA TCP for IMS writes the response to a server response log file (DDNAME=SVRLOG). The information in the server response log file can be useful as part of a manual recovery procedure. Message BEA2033E is also issued, indicating that a server response has been logged and specifying the reason (“Server Request not found” or “No response was expected”).

Server responses are logged as two separate records: the BEA server request/response header (containing the unique request/response ID), and the response data.

Note:

The dataset attributes of the server response Log File are fixed by architecture. Refer to the Oracle Tuxedo Mainframe Adapter for TCP Installation Guide for additional information.