IBM Support

PI36058: DFHIS1023 CICS1234 CONVERSATION ERROR (CODE X'61D') OCCURRED ON IPIC SESSION /AAN IN IPCONN CON1.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The customer upgraded CICS Transaction Server to V5.1, on z/OS
    1.13. Since the upgrade, a CICS to CICS connection over IPIC
    receives error message :
    
    DFHIS1023 10/11/2014 13:46:56 CICS1234 Conversation error (code
    X'061D') occurred on IPIC session /AAN in IPCONN 5678.
    .
    DFHIS4000 01/13/2015 10:03:57CICS5678 CONVERSATION FAILURE ON
    IPCONN 1234.  SENSE CODE (X'1008600B'). MESSAGE (DFHIS1023
    13/01/2015 10:04:37 CICS1234 CONVERSATION ERROR (CODE X'061D')
    OCCURRED ON IPIC SESSION /AAN IN IPCONN 5678.)
    CICS trace shows :
    task 58 CISR does
    IS 0800 ISAL  ENTRY ALLOCATE_RECEIVE
    .
    IS 0801 ISAL  EXIT  ALLOCATE_RECEIVE/EXCEPTION
                        NO_FREE_RECEIVE_SESSION
    and after about 30 retries :
    
    IS 061D ISRR  *EXC* - NO_ISSB_AVAILABLE - IPCONN(5678    )
    MSG_TYPE(DATA) CONVID8(CE5944ECFAD0F069) CONV_ID(00004B97)
    CONV_STATE(B)
    REQ_TYPE(LN) MSG_SEQ(000001) LIC CHAIN_SEQ(000001) TRAN(CSMI)
    
    The Server CICS ISSS.1 154230F0 IS DOMAIN CLIENT SESSION SET
    has all of the R.1 RECEIVE ISSBs showing as Active.
    All of the IPCONN RECEIVE ISSBs are showing as ACTIVE when they
    don't have ant task attached.
    Each of the ISSB has ISSB_SFP ( implicit forget pending)
    and a value set in ISSB_PREV_CONV_ID8. ( CONVID)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFHIS1023 Conversation error            *
    *                      (CODE X'61D') occurred on IPIC session  *
    *                      /xxx in IPCONN xxxx.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    CICS systems connected via MRO connection and IPIC connection.
    SYSB sends a DPL request over IPIC connection to SYSA and does
    a function shipping over MRO connection. After the task
    terminates, on SYSB there is a UOW left in COMMITTED state
    waiting FORGET flow sent by SYSA. On SYSA there is an ISSB
    left on he active chain. After some interval, SYSB sends a PING
    command to SYSA and allocates a send ISSB which happens to be
    the same as the ISSB used in DPL request. After the PING reply
    is received from SYSA, the UOW waiting FORGET flow is resolved
    and the ISSB is put on the free chain. However, on SYSA, when
    it receives the PING request, it does not allocate a receive
    ISSB. Instead it calls a subroutine to send the PING response
    directly and leaves an orphan receive ISSB on the active chain.
    When this happens repeatedly, they are left in this state on
    the active chain eventually resulting in message dfhis1023
    with error code x'061D' being issued.
    

Problem conclusion

  • A new flag has been introduced in DFHISDCC to indicate that the
    SEND ISSB is being used by a PING command.  The new flag will
    prevent the outstanding UOW waiting implicit forget flow to be
    resolved when the PING response is received.  The outstanding
    UOW will be resolved when the SEND ISSB is used to send a user
    request or during IPCONN RELEASED processing, ensuring that the
    receive ISSB in the partner region is moved from the active to
    the free chain.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI36058

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-02

  • Closed date

    2015-09-28

  • Last modified date

    2015-11-03

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

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

    UI26934 UI26935

Modules/Macros

  • DFHCIS4  DFHISAL  DFHISCO  DFHISCOP DFHISCU  DFHISDM  DFHISDUF
    DFHISEM  DFHISEMP DFHISFS  DFHISIC  DFHISIF  DFHISIS  DFHISJU
    DFHISLQ  DFHISLQP DFHISPH  DFHISPHP DFHISPRP DFHISRE  DFHISRR
    DFHISRRP DFHISRS  DFHISRSP DFHISSR  DFHISST  DFHISTRI DFHISUE
    DFHISXF  DFHISXM  DFHISXS  DFHISZA  DFHMIRS
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R800 PSY UI26934

       UP15/10/08 P F510

  • R900 PSY UI26935

       UP15/10/08 P F510

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.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
29 July 2020