PI22636: IPCONN REMAINS IN AN OBTAINING STATE

Obtain the fix for this APAR.

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 5 Release 1
  Data Areas, GC34-2849-00, will be updated to add the following
  in Table 670 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        *
  
  
  The CICS Transaction Server for z/OS Version 5 Release 2
  Data Areas, GC34-7271-00, will be updated to add the following
  in Table 679 WBCLB Web client session :-
  
  Offset Hex  Type       Len      Name                 Description
  (1A9)       BIT(8)     1        WBO_PEEK_FLAGS2
              1... ....           WBO_CAPEX_PENDING
              .1.. ....           WBO_RECEIVE_DEFERRED
  (1AA)       CHARACTER  2        *
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PI16866

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

  UI20706 UI20707 UI20708 UI20709

Modules/Macros

• DFJ@H360
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R80D PSY UI20707

     UP14/08/30 P F408

• R800 PSY UI20706

     UP14/08/30 P F408

• R90D PSY UI20709

     UP14/08/30 P F408

• R900 PSY UI20708

     UP14/08/30 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.