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

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

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: All IMS V12 IMS Connect users                *
    ****************************************************************
    * PROBLEM DESCRIPTION: After response to PING IMS_CONNECT the  *
    *                      persistent socket disconnects after     *
    *                      configuration member timeout interval.  *
    *                                                              *
    *                      After response to PING IMS_CONNECT the  *
    *                      transaction socket does not disconnect  *
    *                      until after configuration member        *
    *                      timeout interval.                       *
    *                                                              *
    *                      Enhancement:                            *
    *                      Establish clientid with PING request    *
    *                      on persistent socket.                   *
    *                                                              *
    *                      Pre-condition PING IMS_CONNECT usage    *
    *                      for future IMS connect enhancements     *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    After the response to 'PING IMS_CONNECT' request is sent on a
    persistent socket the socket is expected to remain established
    however, the socket is disconnected after the execution timeout
    interval as defined on the TIMEOUT= value in the IMS Connect
    configuration member.
    
    After the response to 'PING IMS_CONNECT' request is sent on a
    transaction socket the socket is not disconnected until after
    the execution timeout interval as defined on the TIMEOUT= value
    the IMS Connect configuration member.
    
    An enhancement to the PING process allows for the clientid to be
    established during the 'PING IMS_CONNECT' request when the
    request is the first message received on a persistent socket.
    
    Forward-fit of PM27324
    

Problem conclusion

  • GEN: POSTREQ PM45956 PM57133
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    Logic has been corrected to insure that the socket remains
    connected after response to a successful PING request is sent
    when the socket type is persistent.
    
    Logic has been corrected to insure that the socket immediately
    disconnects after a response to a PING request is sent when the
    socket type is transaction.
    
    The PING process has been enhanced to:
      - Assign a client ID to the session.
    
           For HWSSMPL0, HWSSMPL1 and HWSSOAP1
      - The client ID is retrieved from the IRM_CLIENTID field of
        the IRM in message exits HWSSMPL0, HWSSMPL1 and HWSSOAP1.
    
      - If the client ID is not supplied in IRM_CLIENTID the message
        exits HWSSMPL0, HWSSMPL1 and HWSSOAP1 will generate a random
        client ID and assign it to the session.
    
      - If the client ID supplied in IRM_CLIENTID is the same as
        one already in use IMS Connect will return an error RSM with
        return code 8 and reason code 56 to report that a duplicate
        client ID had been detected. The session will be terminated
        and message HWSS0742W will be sent to the system console.
    
           For HWSJAVA0
      - For message exit HWSJAVA0 if the client ID is not supplied
        in the PING request mainline logic will generated a random
        client ID and assign it to the session.
    
      - If the client ID supplied in IRM_CLIENTID is the same as
        one already in use IMS Connect will return OMUSR_RETCODE = 8
        and OMUSR_RSNCODE = DUPECLNT to the client to report that a
        duplicate client ID had been detected. The session will be
        terminated and message HWSS0742W will be sent to the system
        console.
    
    To pre-condition PING IMS_CONNECT support to meet current and
    future enhancements the logic at label PING0010 is modified to
    build and return the ping response message to core IMS Connect
    in the OTMA header format.  This changes the existing logic that
    returns the ping response message in CSM format.  The ping
    response message will now flow through the XMIT routine of the
    user message exit before getting transmitted to the client.  For
    user exits HWSSMPL0, HWSSMPL1 and HWSSOAP1 the XMIT routine will
    convert the ping response from OTMA format to CSM format.
    
    The following parts have been modified:
     HWSEXPRM, HWSJAVA0, HWSSMPL0, HWSSMPL1, HWSSOAP1, HWSSDRCV
     HWSSREC0, HWSSRE40.
    
    HWSEXPRM:
     ADDED flag bit EXPREA_PINGRSP to EXPREA_FLAG2 flag byte:
    
      -EXPREA_PINGRSP x'80'- indicate PING response message.
    
     Set by user message exits HWSSMPL0, HWSSMPL1, HWSSOAP1
     and HWSJAVA0.
    
    HWSJAVA0:
     User message exit for TM Resource Adapter:
     Modified PING support logic
    
     - Copy client ID from TMRA header to EXPREA_CLID
    
     - Set EXPREA_PINGRSP in EXPREA_FLAG2 to trigger enhanced
       PING response logic in HWSSDRCV.
    
    HWSSMPL0, HWSSMPL1 and HWSSOAP1:
    
     - Set EXPREA_PINGRSP in EXPREA_FLAG2 to trigger enhanced
       PING logic in IMS Connect core
    
     - The PING support logic at label 'PING0010' has been
       redesigned to support the enhancement to establish the client
       ID and build the response in OTMA header format.
    
    
    HWSSDRCV (core logic):
     - After sending the response to a PING request on a persistent
       socket the socket is removed from the timer table.  This
       change prevents the socket from getting disconnected after
       the timeout interval.
    
     - After sending the response to a PING request on a transaction
       socket the socket is disconnect immediately.
    
    HWSSREC0:
     - Validate client ID.
         If ID is unique proceed with ping response.
         If ID is not unique setup return code 8, reason code 56 for
         client response, WTO HWSS0742 to system console, terminate
         session.
    
     - If message is a PING RESPONSE call HWSSRE40 to interface to
       issue transmit of the response message to the client.
    
     - If transaction socket, terminate socket after PING RESPONSE
       is sent to client.
    
    HWSSRE40:
     - Make interface call to process for transmit of PING RESPONSE
       message to client.
    

Temporary fix

Comments

  • REPINNED RP12/02/21 (ATXT) TO ADD POSTREQ PM57133 INFO.
     **** PE12/02/21 PTF IN ERROR. SEE APAR PM57133 FOR DESCRIPTION
    REPINNED RP11/08/24 (ATXT) TO ADD POSTREQ PM45956 INFO.
     **** PEyy/mm/dd PTF IN ERROR. SEE APAR PM45956 FOR DESCRIPTION
    
    ž**** PE11/08/24 FIX IN ERROR. SEE APAR PM45956  FOR DESCRIPTION
    ž**** PE12/02/21 FIX IN ERROR. SEE APAR PM57133  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PM29137

  • Reported component name

    IMS V12

  • Reported component ID

    5635A0300

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-16

  • Closed date

    2011-07-22

  • Last modified date

    2012-03-08

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

    PM27325

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

    UK70080

Modules/Macros

  •    HWSEXPRM HWSJAVA0 HWSSDRCV HWSSMPL0 HWSSMPL1
    HWSSOAP1 HWSSREC0 HWSSRE40
    

Fix information

  • Fixed component name

    IMS V12

  • Fixed component ID

    5635A0300

Applicable component levels

  • R200 PSY UK70080

       UP11/07/26 P F107

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

200

Operating system(s):

z/OS

Reference #:

PM29137

Modified date:

2012-03-08

Translate my page

Machine Translation

Content navigation