IBM Support

IJ13272: FP5(7305) IS DEPLOYING ANCHOR SENSORS EVEN THOUGH THE ANCHOR IS NOT IN SCOPE WHEN RUNNING SUBNET DISCOVERY.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In taddm 7.3.0.5, when discovery is launched on a subnet
    scope which does not have any anchor in the scope set but there
    are some anchors on anchor list, still the anchor sensor
    launches which should not happen.
    
    A previous apar IJ05795 delivered to fix an issue "PORT SENSORS
    ARE NOT INVOKING INCASE OF SUBNET MASK IS /23 OR BELOW"
    caused this issue during subnet discovery.
    

Local fix

  • Do not use subnet based discovery, or request an efix to remove
    IJ05795.
    

Problem summary

  • In taddm 7.3.0.5, when discovery is launched on a subnet
    scope which does not have any anchor in the scope set but there
    are some anchors on anchor list, still the anchor sensor
    launches which should not happen.
    A previous apar IJ05795 delivered to fix an issue "PORT SENSORS
    ARE NOT INVOKING INCASE OF SUBNET MASK IS /23 OR BELOW"
    caused this issue during subnet discovery.
    This APAR reverts back changes done for APAR IJ05795.
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    packages:
    | Fix Pack | 7.3.0-TIV-ITADDM-FP0006
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ13272

  • Reported component name

    APP DEPENDENCY

  • Reported component ID

    5724N5500

  • Reported release

    730

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-06

  • Closed date

    2019-02-11

  • Last modified date

    2019-02-11

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

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

Modules/Macros

  • 999
    

Fix information

  • Fixed component name

    APP DEPENDENCY

  • Fixed component ID

    5724N5500

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 February 2019