IBM Support

PH01640: IPIC CONNECTION IS INSERVICE AND ACQUIRED BUT RECIEVES SYSIDERR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You have an IPIC connection that displays as INService and
    ACQuired when you do an INQUIRE on it.
    
    However when trying to exectute a SEND_REQUEST using that
    connection the trace entry shows a Session Error:
    
    IS 0701 ISSR  EXIT  - FUNCTION(SEND_REQUEST) RESPONSE(PURGED)
    REASON(SESSION_ERROR)  ISSB(/XXX) ISSS(2DADE2D0) CONV_ID8
                       (XXXXXXXXXXXXXX) CONV_ID(XXXXXXXX)
    CONV_STATE_IS(NONE) CONV_STATE_WB(NONE)
    PREV_CONV_ID8(0000000000000000)
     PREV_CONV(XXXXXXXX) TRANNO(XXXXX) TASK_WAITING(NO)
    MSG_AVAILABLE(NO) PACING_RECEIVED(NO) RECV_CHAINING(NO)
                       LAST_RECEIVED(NO)
    
    Looking in the IS domain at the control blocks for this
    connection you see that it displays the following symptoms:
    
    isss_conn_error = yes
    isss_sess_error = yes
    isss_on_error_q = no
    isss_error_code = 609
    
    The problem is involving the CIST and CISE transactions while
    it is working with IPCONN ABCD.  When CISE got control, it
    detached the error queue, got an isss and processed the
    connection error. The connection error process was suspended
    waiting for the exclusive lock.
    
    CIST continue to run. After terminated the 1st server session,
    it continued to terminate the 2nd serer session, which is the
    isss that CISE obtained. The isss_on_error_q=yes, the flags
    mentioned above was not cleared.
    
    CIST and CISE alternately run. Flag isss_on_error_q was set off
    at the end of connection error process in CISE. But the other 3
    flags kept the wrong value after IPCONN ABCD was released. If
    this IPCONN got acquired again, any ISSB on the server isss
    being allocated to send a request will cause the SESSION_ERROR
    seen in the trace.
    
    Additional Symptom(s) Search Keyword(s): KIXREVxxx
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Some ISSS flags can not be cleared if   *
    *                      it is in error queue while in the       *
    *                      middle of IPIC connection termination.  *
    ****************************************************************
    CICS is connected with remote system by IPIC connection. A
    session error arrived and CIST is attached to terminate this
    IPIC connection. Then another server session error is notified.
    This server session is added to the error queue with
    isss_on_error_q setting on and other flags (isss_error_code,
    isss_sess_error and isss_conn_error) to record the session
    error. CISE is resumed to handle it. Before CISE can run, CIST
    locks the server ISSS chain and starts to release the server
    sessions. When CISE starts to run, it is suspended waiting for
    the exclusive lock (owned by CIST). CIST continues to run. For
    the server session which has isss_on_error_q set on, the flags
    that record the session error (mentioned above) are not
    cleared. These flags keep the residual values after IPIC
    connection released.  If this IPIC connection is acquired
    again, any ISSB on this server ISSS being allocated to send a
    request will cause a problem.
    

Problem conclusion

  • DFHISEM has been changed to make sure the flags in server ISSS
    get properly cleared after IPCONN released.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH01640

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-13

  • Closed date

    2018-10-15

  • Last modified date

    2018-11-01

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

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

    UI59118 UI59119

Modules/Macros

  • DFHISEM
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI59119

       UP18/10/17 P F810

  • R100 PSY UI59118

       UP18/10/17 P F810

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":"5.3","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":"5.3","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 November 2018