IBM Support

OA42982: HUNG CP-CP SESSIONS AFTER AN ABEND0C4 OCCURS IN ISTLUCRP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Hung CP-CP sessions after an ABEND0C4 occurs.  Locates hang
    and CP-CP sessions are unable to be established.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of VTAM APPC (APPC=YES on the                      *
    * VTAM APPL statement) and/or VTAM APPN                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * CP-CP processes hung after ABEND                             *
    * in ISTLUCRP                                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply PTF                                                    *
    ****************************************************************
    The problem may be summarized as follows:
    1. CP-CP session initialization is started.
    2. While the Init_Other for the session is
    outstanding, an APPCB control block (NSSCB)
    is prematurely freed. (APAR OA42811 has been
    taken to address this issue.)
    3. When the Init_Other response returns, LUS references
    the freed control block.  ISTLUCSL ABENDs and then
    ISTLUCRP ABENDs.
    4. The ISTLUCRP ABEND is executing on the APPCB PAB and
    is not covered by a VTAM Recovery Routine (VRR),
    so the PAB is left undispatchable.
    5. As a result, CP-CP sessions hang and so do Locates.
    After this error occurs, no new CP-CP sessions may be
    established and no existing CP-CP sessions may be
    taken down. A D NET,CPCP display will show CP-CP
    sessions in various pending states.
    6. This APAR addresses the lack of recovery (VRR), rather
    than the issue leading up to the reported ABENDs.  The
    new recovery added by this APAR will allow VTAM to continue
    processing new CP-CP requests after these ABENDs.
    

Problem conclusion

  • ISTPSCR1 is updated to provide VRR coverage around
    the call to ISTOCCSM/ISTLUCRP.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    OA42982

  • Reported component name

    VTAM V4 MVS/ESA

  • Reported component ID

    569511701

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-07-31

  • Closed date

    2013-08-12

  • Last modified date

    2014-07-15

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

    OA42764

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

Modules/Macros

  • ISTPSCR1
    

Fix information

  • Fixed component name

    VTAM V4 MVS/ESA

  • Fixed component ID

    569511701

Applicable component levels

  • R210 PSY UA70316

       UP13/08/16 P F308

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 July 2014