IBM Support

OY65199: VARY INACT,I ON AN INDEPENDENT LU HANGS IN PNFY1.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A VARY INACT,I is issued against an Independent LU (ILU).  A
    display shows the ILU in PNFY1.
    The trace shows a TERM-OTHER RU sent from config services
    to session services, but the RU does not have TMONOTFY on,
    which would indicate a NOTIFY is required.  After the BFCLEANUP
    RUs and BFSESSEND RUs are sent, a NOTIFY is never sent to
    config services, which would allow the ILU to be marked
    inactive. The SIBs are cleaned up, but the resource stays in
    PNFY1.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: An ILU (CDRSC) stays in PNFY1 state     *
    *                      after a Vary Inact immediate command is *
    *                      issued. The inactivation hangs because  *
    *                      the RCDINUSE bit is on.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A session set up request was routed to locate the DLU in the
    network. The DLU was not found in the adjacent SSCPs or CPs.
    Then before routing was exausted a last ditch effort was done
    to locate the DLU in this host. The last ditch effort was a
    success that the DLU was found and session became active. But
    route update (ROUTEUPD) was not performed causing the RCDINUSE
    bit remain turned on and other control block fields remain not
    updated.
    

Problem conclusion

  • ISTSSCUX has been changed to issue ROUTEUPD macro when a last
    ditch effort is performed and the DLU is found as a LEN owned
    by this host.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OY65199

  • Reported component name

    VTAM V4 MVS/ESA

  • Reported component ID

    569511701

  • Reported release

    101

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1993-06-23

  • Closed date

    1993-07-22

  • Last modified date

    1993-12-28

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

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

    UY96640

Modules/Macros

  • ISTSSCUX
    

Fix information

  • Fixed component name

    VTAM V4 MVS/ESA

  • Fixed component ID

    569511701

Applicable component levels

  • R101 PSY UY96640

       UP93/09/28 P F309

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

Document Information

Modified date:
28 December 1993