IBM Support

PI07401: CICS-IMS ISC LU6.1 SESSIONS REMAIN ALLOCATED LEADING TO SYSBUSY CONDITION.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After having upgraded CICS from PTF level UK74260 to UK90575
    (to RSU level is 1301) , CICS-IMS ISC connections remain busy
    after transactions are ended. In several identical CICS
    regions with 5 sessions to IMS, 4 remains SYSBUSY when
    allocated, only 1 session is available.
    A CEMT I NET command shows transactions in the Tra field but
    all these transactions have ended.
    The IMS system was at the same time upgraded from v.10
    to v.12. When the CICS regions are restarted on the earlier
    APAR PM93603 was previously opened for this problem.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS-IMS ISC LU6.1 sessions remain      *
    *                      allocated leading to SYSBUSY condition. *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A CICS front-end region is connected to an IMS back-end with an
    LU61 connection. A CICS transaction sends data to IMS and
    receives a reply carrying DR2 (definite response two) CONFIRM to
    request SYNCPOINT. Although CICS passes EIBSYNC back to the
    application it fails to take a SYNCPOINT, which it should have
    done in response to the EIBSYNC indicator. A further SEND to IMS
    also receives a reply carrying CONFIRM. A SYNCPOINT request is
    taken. As no SYNCPOINT was taken after the first receive the UOW
    (unit of work) contains two links to IMS, which both initiated
    SYNCPOINT and are therefore initiators. When CICS attempts to
    commit the links it expects to find only one initiator. The
    first initiator link found is not committed immediately, but a
    pointer to it is saved so that it can be committed last after
    all the other links. However when CICS finds the second
    initiator link it overwrites the pointer to the first initiator
    link with the new one, and the first initiator link is never
    committed. The link that is not committed does not get cleaned
    up properly, and the session TCTTE for the link is left pointing
    at the task that was running against it even after that task has
    ended. The link appears allocated and is unavailable to satisfy
    further allocates. If the problem is repeated with other links
    they can all become allocated leading to the reported SYSBUSY
    condition.
    
    Additional keywords: PM56243 PM93603
    

Problem conclusion

  • CICS commit processing has been changed to allow for a UOW
    with more than one initiator.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI07401

  • 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

  • Submitted date

    2013-12-04

  • Closed date

    2013-12-31

  • Last modified date

    2015-03-05

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

    PI07306

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

    UI13986

Modules/Macros

  • DFHRMLSO
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R800 PSY UI13986

       UP14/01/10 P F401

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

Document Information

Modified date:
05 March 2015