PM06363: IMS CONNECT PING DISCONNECTS A PERSISTENT SOCKET AND IS NOT RECOGNIZED AS A FIRST MESSAGE AFTER A TCP/IP CONNECT.

APAR status

• Closed as fixed if next.

Error description

• There are 3 problems with IMS Connect PING:
  
  1) A PING received on a Persistent Socket disconnects the socket
  when it sends the PING reply.
  
  2) If the PING is received as the first message after a Connect
  the Client ID is not established.
  
  3) If the PING is received as the first message after a Connect
  the "first message received" message timer is not turned off.
  
  This affects the ability to use PING as a mechanism to keep a
  firewall timer from timing out.
  

Local fix

• There is no local fix or workaround for these problems.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IMS V9 IMS Connect users                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Enhance IMS Connect PING function.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Request to enhance IMS Connect TCP/IP PING IMS_CONNECT function.
  After a PING request is processed as the first message received
  after the session is connected:
  
     1) Maintain persistent socket connection.
  
     2) Establish the clientid.
  

Problem conclusion

Temporary fix

Comments

• The proposed enhancements to the IMS Connect PING function
  will be addressed in V10 via apar PM27324.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM27324 PM27325

Fix information

• Fixed component name

  IMS V9

• Fixed component ID

  5655J3800

Applicable component levels

• R900 PSN

     UP