IBM Support

PH46288: ENSURE THAT THE IPCONN IS RELEASED AFTER AN AIPK ABEND

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The IPCONN is stuck in FREEing state due to an ISSB being owned
    by a task that is no longer in the system.  The kernel error
    data shows that this task abended AIPK.  When this happens, the
    ISSB is still in receive state.  That causes the error
    processing to bypass attempting to send an IS7 back to the
    client.  The call to free the ISSB is also bypassed,
    incorrectly.  That leaves the ISSB allocated and the IPCONN
    stuck.
    

Local fix

  • kixrevrjl
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: An IPCONN remains stuck in a FREEing    *
    *                      state after a mirror task abends AIPJ   *
    *                      or AIPK, or it abended AKC3 while       *
    *                      purged in a TCLASS wait.                *
    ****************************************************************
    A request arrives in CICS over an IPCONN and a mirror task is
    attached.  During initialization of the mirror task it abends
    AIPJ or AIPK, or it may abend AKC3 if purged while in a TCLASS
    wait.  The IPIC connection will have been lost.
    
    The mirror task is terminated but the ISSB is not freed.  The
    IPCONN is left 'Inservice' with a connection state of 'Freeing'.
    A dump will show the ISSB for the terminated task is 'Active'
    and the session state is 'Receive'.  The IPCONN remains in this
    state until CICS is recycled. You may see one or more of the
    following messages:-
    
    DFHIS1003 mm/dd/yyyy hh:mm:ss applid Unable to release IPCONN
    xxxxxx. IPCONN state INSERVICE,FREEING is invalid.
    
    DFHSO1000 mm/dd/yyyy hh:mm:ss applid A request for TCP/IP
    communication failed (code X'nnnn') for IPCONN xxxxxx using
    applid xxxxxx.  z/OS UNIX system services supplied
    bpx_return_value( -1) bpx_return_code( n,nnn ), and
    bpx_reason_code( X'nnnnnnnn' ).
    
    DFHIS1015 mm/dd/yyyy hh:mm:ss applid Unable to accept connection
    for IPCONN xxxxxx. IPCONN client session state is invalid. Error
    code is (code X'nnnn').
    

Problem conclusion

  • The dfhisis_send_error routine is changed to free an ISSB if its
    state is IS_RECEIVE and the abend code is AIPJ, AIPK or AKC3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH46288

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-05-10

  • Closed date

    2022-07-14

  • Last modified date

    2022-09-28

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

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

    PH47777 UI81466 UI81467 UI81468

Modules/Macros

  • DFHISIS
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R100 PSY UI81466

       UP22/07/16 P F207 ¢

  • R200 PSY UI81467

       UP22/07/15 P F207 ¢

  • R300 PSY UI81468

       UP22/07/15 P F207 ¢

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
28 September 2022