IBM Support

PI16866: IPCONN REMAINS IN AN OBTAINING STATE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If an expedited timeout message arrives in the CAPEX flow, it
    can cause the IPICONN remains in OBTaining state.
    
    The IPIC code is not expecting additional messages to arrive
    until the CAPEX response has been sent back.
    .
    The presence of this extra message caused the ISRR notify
    processing to get driven immediately by CSOL.  Because this was
    not driven as part of an async receive the saved token held in
    the socket object is null.
    The null token causes the DFHISRR notify processing to just
    ignore the data.  No further async receives are issued so CICS
    will not receive any more data for this socket or even detect
    that the socket has been closed.
    .
    This situation leave the IPCONN in an OBTaining state.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: IPCONN for CICS Transaction Gateway     *
    *                      stuck in partially initialized state.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A request to activate an IPCONN is sent from CICS Transaction
    Gateway. The response is not forthcoming and the gateway
    times out the request. The timeout causes a second message to
    be sent from CICS TG (a FORCEPURGE command). The socket is then
    closed by CICS TG.
    Eventually, the initial request from CICS TG ( the CAPEX ) is
    received by CICS. The transport layer code detects excess data
    has been received (the FORCEPURGE command) so it uses an
    internal CICS mechanism to nudge the sockets listener task so
    that the excess data can be processed.
    CICS doesn't expect this excess data and it is too early in the
    activation of the IPCONN to process this data. This leads to an
    error when DFHISRR NOTIFY is called to process the data. An
    error of INVALID_USER_TOKEN is returned as the socket has not
    been 'bound' to the IPCONN which CICS TG is trying to activate.
    This error leaves the socket without an active RECEIVE.
    The FORCEPURGE never gets processed by CICS and CICS fails to
    detect that the socket has been closed by CICS TG.
    CICS is left with a partially initialized IPCONN.
    When CICS TG tries to activate the IPCONN for a second time,
    CICS rejects the request with message DFHIS1015 error code 0515.
    
    ADDITIONAL KEYWORDS :- MSGDFHIS1015 IS1015 0515
    

Problem conclusion

  • CICS has been changed to defer the processing of excess data
    when a CAPEX ( capability exchange ) is in progress for an
    IPCONN socket.
    The excess data will be processed only when the IPCONN has been
    'bound' to the socket object
    
    The CICS Transaction Server for z/OS Version 4 Release 2
    Data Areas, GC34-7163-01, will be updated to add the following
    in Table 751 WBCLB Web client session :-
    
    Offset Hex  Type       Len      Name                 Description
    (1A1)       BIT(8)     1        WBO_PEEK_FLAGS2
                1... ....           WBO_CAPEX_PENDING
                .1.. ....           WBO_RECEIVE_DEFERRED
    (1A2)       CHARACTER  2        *
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI16866

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-28

  • Closed date

    2014-07-31

  • Last modified date

    2014-09-03

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

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

    PI22636 UI20140

Modules/Macros

  • DFHIEIE  DFHIIRR  DFHIIXM  DFHRZDM  DFHRZIX  DFHRZLN  DFHRZNR2
    DFHRZRG2 DFHRZRM  DFHRZRS1 DFHRZSO  DFHRZSO1 DFHRZTA  DFHRZTCX
    DFHRZTRI DFHRZTR1 DFHRZXM  DFHSOCK  DFHSOCKT DFHSODM  DFHSOIS
    DFHSOLI  DFHSOLS  DFHSOM01 DFHSOM02 DFHSOM03 DFHSOPL  DFHSORD
    DFHSOSE  DFHSOSES DFHSOST  DFHSOS00 DFHSOS01 DFHSOS02 DFHSOS03
    DFHSOS04 DFHSOS05 DFHSOS06 DFHSOS07 DFHSOS08 DFHSOS09 DFHSOS10
    DFHSOS11 DFHSOS12 DFHSOS13 DFHSOS14 DFHSOS15 DFHSOS16 DFHSOS17
    DFHSOS18 DFHSOS19 DFHSOS20 DFHSOS21 DFHSOS22 DFHSOS23 DFHSOTI
    DFHSOXM  DFHWBA   DFHWBAP  DFHWBAPF DFHWBBLI DFHWBCL  DFHWBCLI
    DFHWBDM  DFHWBDUF DFHWBSO  DFHWBSR  DFHWBSV  DFHWBXM  DFHWBXN
    

Publications Referenced
GC34716301    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R700 PSY UI20140

       UP14/08/07 P F408

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 September 2014