IBM Support

OW30833: CROSS NETWORK RNAA FAILS WITH 089D0006.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Cross network RNAA fails with sense 089D0006.  VTAM requesta a
    RNAA from a gateway NCP.  The NCP returns a positive response
    to the RNAA.  VTAM then tries to SRTA the network addresses
    which fails because the network address is already in use in
    VTAM.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All VTAMs that are GW SSCPs.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:   Cross network session fails with      *
    *                      089D0006 or 089D0001 after an RNAA      *
    *                      returns a network address that is       *
    *                      already in use by VTAM.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
      During cross network LU to LU session setup, a gateway SSCP
    sent an RNAA to the GateWay NCP.  The GW NCP returned a network
    address that was already in use by VTAM.  Because this could be
    a timing problem, VTAM is designed to send a NOTIFY, followed by
    another RNAA.  If the second RNAA returns a network address
    which is also in use, VTAM sets sense 089D0006 and tries to find
    a different path to the other SSCP.
      This could result in the session failing with sense 089D0006
    or 089D0001 for the other SSCP.
    

Problem conclusion

  • ISTSSCKA has been enhanced to issue a new message group
    starting with IST1693I when the 089D0006 is set for the second
    RNAA.  This message group is intended to document what resource
    is trying to use the duplicate network address and what
    resource is already using it.  This information can be used
    to determine why VTAM and NCP are out of sync on their
    network address assignment.
      MSG1650, ISTINCNO, ISTCFCML, ISTCFCMM, and ISTVTMEU were
    modified to define the new MSGIST1693I.  ISTMSFLD and ISTMSFLI
    were modified to suppress the message group if the data in the
    IST1421I message is the same.
    
      The following update will be made to the VTAM Messages manual,
    GC31-8368-00 page 5-558 in V4R4:
    
    IST1693I  NETWORK ADDRESS RECEIVED FOR resourcename IN USE
    
    EXPLANATION:  This message is the first in a group of messages.
    A complete description of the message group follows.
    
       IST1693I NETWORK ADDRESS RECEIVED FOR resourcename IN USE
       IST1421I nodetype dupresource HAS DUPLICATE ADDRESS
       IST314I END
    
    IST1693I
    
        This message is issued during cross network LU-to-LU
        session setup when the network address for the specified
        resourcename could not be defined.  VTAM detected another
        resource was using the network address return by the
        gateway NCP for resourcename. The form of resourcename
        is netid.name.
    IST1421I
        nodetype is the node type of dupresource.  See Chapter 11,
        'Node and ID Types in VTAM Messages' on page 11-1 for a
        description of nodetype.
        dupresource is the name of the resource that is currently
        defined to the address in question.  The form of dupresource
        is netid.name.
    SYSTEM ACTION:  Processing continues.
    OPERATOR RESPONSE:  Issue the DISPLAY ID=dupresource,E command
    to display information about the duplicate resource.  Save the
    system log for problem determination.
    PROGRAMMER RESPONSE:  Check your network address assignments.
    See the section on non-VTAM problems, in the VTAM Diagnosis for
    additional problem determination actions.).
    

Temporary fix

Comments

APAR Information

  • APAR number

    OW30833

  • Reported component name

    VTAM V4 MVS/ESA

  • Reported component ID

    569511701

  • Reported release

    301

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1997-12-08

  • Closed date

    1998-01-27

  • Last modified date

    1998-05-01

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

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

    UW45453 UW45454 UW45455

Modules/Macros

  • ISTCFCML ISTCFCMM ISTINCNO ISTMSFLD ISTMSFLI
    ISTVTMEU MSG1650  ISTSSCKA
    

Publications Referenced
GC31836800    

Fix information

  • Fixed component name

    VTAM V4 MVS/ESA

  • Fixed component ID

    569511701

Applicable component levels

  • R301 PSY UW45455

       UP98/03/27 P F803

  • R401 PSY UW45453

       UP98/03/27 P F803

  • R411 PSY UW45454

       UP98/03/10 P F803

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

Document Information

Modified date:
01 May 1998