IBM Support

OA46259: INCORRECT RELATIONSHIPS BROUGHT IN WHEN APLS SHARE THE SAME SUBSYSTEM NAME

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Created two APLs with different entry names but same
    Subsystem name. Add different relationships (but all of them
    should be valid on test system) to each APL. Create an APG.
    'Automatically link Application-Resources in APG' is set to NO.
    Link both APLs to this one APG. Link the APG to a valid system.
    Build ACF & load it. Select ONE of the APLs on the systemand
    relationships from BOTH APLs show up!
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All SA z/OS V3R4 and V3R5 customers using    *
    *                 the Customization Dialog.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: An incorrect relationship can be built  *
    *                      when multiple APLs have the same        *
    *                      subsystem name.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Relationships originating from other APLs should not be created.
    

Problem conclusion

  • Macro AOFIAMC2 has been modified to correct the problem.
    Modules AOFFAMCT, AOFFBAM0, AOFFBAM1, AOFFBAM2, AOFFBAM3,
    AOFFBAM4 and AOFFBCHK have been shipped due to the macro
    change.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA46259

  • Reported component name

    SYSTEM AUTO Z/O

  • Reported component ID

    5698SA300

  • Reported release

    340

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-13

  • Closed date

    2014-10-29

  • Last modified date

    2014-11-04

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

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

    UA75314 UA75315

Modules/Macros

  • AOFFAMCT AOFFBAM0 AOFFBAM1 AOFFBAM2 AOFFBAM3 AOFFBAM4 AOFFBCHK
    

Fix information

  • Fixed component name

    SYSTEM AUTO Z/O

  • Fixed component ID

    5698SA300

Applicable component levels

  • R340 PSY UA75314

       UP14/10/31 P F410

  • R350 PSY UA75315

       UP14/10/31 P F410

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

Document Information

Modified date:
04 November 2014