IBM Support

OA39554: GATEWAY AUTOTASK RESTARTING LOOP ON DUPLICATE SDFROOT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An incorrect update to the SDFROOT value on a Netview in
    a system which runs two NetViews was made.  This resulted
    in both NetViews having the same SDFROOT value, and the
    gateway autotask failing on the SDF focal point.
    This resulted in a message:
    AOF776I CONNECTION FROM DOMAIN xxxxx xxxx REJECTED AT DOMAIN
    xxxx SDFROOT NAME IS THE SAME AS DOMAIN xxxxx.
    SA immediately restarted the gateway autotask which failed
    and restarted in a loop.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All SA z/OS V3R2, V3R3 and V3R4 customers.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When msgAOF776I is issued indicating a  *
    *                      rejected connection, the connecting     *
    *                      task is logged off. This in turn can    *
    *                      cause AOFR1ILL to be issued from the AT *
    *                      to log this task back on and therefore  *
    *                      creating a loop. One of the causes of   *
    *                      this can be a wrongly defined SDF root. *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A loop caused by a wrongly defined SDF root should not cause a
    logon/logoff loop for the task in question, normally the gateway
    task for the remote system.
    

Problem conclusion

  • Rexx routines INGRVXMT and AOFR1ILL have been changed to avoid a
    logon/logoff loop when a SDF root has been defined incorrectly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA39554

  • Reported component name

    SYSTEM AUTO Z/O

  • Reported component ID

    5698SA300

  • Reported release

    330

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-05-10

  • Closed date

    2012-05-22

  • Last modified date

    2012-06-03

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

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

    UA65417 UA65418 UA65419

Modules/Macros

  • AOFR1ILL INGRVXMT
    

Fix information

  • Fixed component name

    SYSTEM AUTO Z/O

  • Fixed component ID

    5698SA300

Applicable component levels

  • R320 PSY UA65417

       UP12/05/26 P F205

  • R330 PSY UA65418

       UP12/05/26 P F205

  • R340 PSY UA65419

       UP12/05/26 P F205

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":"SSWRCJ","label":"IBM Tivoli System Automation for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"330","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
03 June 2012