IBM Support

OW06024: SENSE 08900037 OR SENSE 08970007 ON SESSIONS TO DLUS-SERVED LUS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • -Sense code 08900037 on PLU-initiated sessions to an LU who is
    served by VTAM's Dependent LU Server (DLUS) function, or
    -Sense code 08970007 on a BIND to a DLUS-served LU, the PLU
     of the BIND is not a VTAM, and the DLUS host is an intermediate
     node on the BIND path
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All using the Dependent LU Server (DLUS)     *
    *                 function of VTAM V4R2                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. Sense code 08900037 on               *
    *                         PLU-initiated sessions to LUs        *
    *                         served by VTAM's Dependent LU        *
    *                         server function.  The Dependent      *
    *                         LU requester (DLUR) node is a        *
    *                         network node in the same             *
    *                         subnetwork as the PLU node, and      *
    *                         the DLUS node is in a different      *
    *                         APPN subnetwork.                     *
    *                      2. Sense code 08970007 on BIND to       *
    *                         an LU served by DLUS.  The DLUS      *
    *                         node is also an intermediate node    *
    *                         on the BIND path, and the BIND was   *
    *                         sent by a node, like AS/400, which   *
    *                         does not do LU2 type sessions.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1.  The PLU and the DLUR node are in the same subnetwork and the
        DLUS node is in a different subnetwork.  When a PLU-init
        request is done for the DLUR node, the search initially
        goes to the cross-subnet DLUS node.  When the reply is
        received from the DLUS node, the border node in the
        subnetwork of the PLU and DLUS node initiates a search to
        obtain DLUR TGVs in the border node FSM (ISTSLPXR).  Since
        the DLUR node is a network node, no TGVs are returned.
        Then the mainline PLU-init FSM (ISTSLPND) gets control and,
        since no SLU TGVs are present, attempts to get them again.
    
    2.  A node which does not reserve resources was trying to start
        a session to a DLS-served SLU by sending a BIND with an
        RSCV.  The DLS node was along the BIND path.  When the
        BFINIT was received, ISTSSCEB called ISTSSCUR, which had
        code to push an LU RDTE into shadow if this node is
        intermediate on the BIND path.  The theory behind this was
        that some other node must actually own the LU, and our
        node's definition is incorrect.
    
        However, in this case the LU was DLS served and this node
        was the DLS.  Therefore, even though this node was
        intermediate on the BIND path, the LU RDTE in this node for
        the SLU is correct and should not be pushed into shadow.
    
        Normally this would not be a problem because if the PLU were
        a node that reserves resources, there would have already
        been a SIB in this node, so ISTSSCUR would not have been
        called on the BFINIT.
    

Problem conclusion

  • 1. ISTSLPND has been updated to not check the CVs list in the
    TGS_PROVIDED condition if the SLU is non-native.  (P114762)
    
    2.Code was added to ISTSSCUR to not push an LU RDTE into shadow
    when it is DLUS served and this node is intermediate on a BIND
    path. (P114833)
    

Temporary fix

Comments

APAR Information

  • APAR number

    OW06024

  • Reported component name

    VTAM V4 MVS/ESA

  • Reported component ID

    569511701

  • Reported release

    201

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1994-06-15

  • Closed date

    1994-07-06

  • Last modified date

    1994-11-04

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

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

    UW08642

Modules/Macros

  • ISTSLPND ISTSSCUR
    

Fix information

  • Fixed component name

    VTAM V4 MVS/ESA

  • Fixed component ID

    569511701

Applicable component levels

  • R201 PSY UW08642

       UP94/08/04 P F408

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

Document Information

Modified date:
04 November 1994