Ping support for IMS Connect

To determine whether or not IMS Connect is available, you can send a ping request to IMS Connect. The ping support operates like a transaction and has the appearance of a transaction code and data. When you send the request PING IMS_CONNECT, the response is PING RESPONSE.

The user message exits, HWSJAVA, HWSSMPL1, HWSSMPL0, and HWSSOAP1 provide ping support. User message exits HWSCSLO0 and HWSCSLO1 do not support the ping function. If you write your own user message exit, you can choose to add the ping function support in your exit.

The communication sequence of the ping request consists of four steps. If you are using HWSSOAP1 user message exit, the third and the fourth steps, receive and disconnect, differ from the receive and disconnect steps for the HWSJAVA0, HWSSMPL0, and HWSSMPL1 user message exits.

For the HWSJAVA0, HWSSMPL0, and HWSSMPL1 user message exits, the communication sequence of the ping request is:

1. Connect.
2. Send PING IMS_CONNECT (must be sent in uppercase).
3. Receive:
   • If you are using HWSSMPL0 or HWSSMPL1, the user-written client application receives HWSC0030I *PING RESPONSE* *CSMOKY*.
   • If you are using HWSJAVA0, the IMS TM Resource Adapter application receives HWSC0030I *PING RESPONSE* in the application data portion of the OTMA header and return code of 48 and reason code ICONSUCC in the user data portion of the OTMA header.
4. Resolve socket connection.
   IMS Connect maintains the socket connection, except in the following circumstances:

   • If the socket is not persistent, IMS Connect disconnects the socket.
   • If IMS Connect expects an ACK or NAK response from the client application, IMS Connect disconnects the socket.
   • If the client application is in IMS conversational mode, IMS Connect disconnects the socket.

For the HWSSOAP1 user message exit, the communication sequence of the ping request is:

1. Connect.
2. Send PING IMS_CONNECT (must be sent in uppercase).
3. Receive PING_RESPONSE.
4. Disconnect.