IBM Support

IJ10143: PHYSICAL FRAME INSIDE ANOTHER PHYSICAL FRAME ARE NOT SHOWN IN TADDM UI.

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 discovery of a device through Network sensors, if a Physical
    Frame is contained in another physical frame, this is
    information is not showing in the Data Management Portal screen.
    When we open the Physical Package Tab of a Switch/Bridge , then
    all it's physical frame are visible in a dropdown. If one of
    that Physical Frame contains another Physical Frame, and then we
    select that physical frame from dropdown, the child physical
    frame is not shown in the opened window.
    
    Solution is to show the physical frame in that window.
    

Local fix

  • User can add a tag in the file:
    dist/etc/detail/screencontent.xml. This file has many variants
    for different languages. For English language steps are:
    
    Open file dist/etc/detail/screencontent.xml
    Under this tag: <tableContent
    className="com.collation.platform.model.topology.phys.physpkg.Ph
    ysicalFrame" name="PhysicalFrame.Components">
    Add following tag:
        <field>
    
          <nested
    className="com.collation.platform.model.topology.phys.physpkg.Ph
    ysicalFrame" fieldName="physicalFrames">
    
            <plain displayName="Physical Frames"
    fieldName="displayName"/>
    
          </nested>
    
        </field>
    
    
    
    3. Save the file and restart TADDM
    
    4. For other languages , user can follow similar steps on their
    corresponding files available in same directory. For the new tag
    added, except of displayName value , other content has to be
    kept same as mentioned above. This file is updated by fix packs
    and releases, so any changes made here manually must be merged
    back in after a fix pack update.
    

Problem summary

  • In discovery of a device through snmp sensors, if a Physical
    Frame is contained inside another physical frame, this
    information is not showing in the Data Management Portal screen.
    When we open the Physical Package Tab of a Switch/Bridge,
    all it's physical frame are visible in a dropdown. If one of
    those Physical Frames contains another Physical Frame, and then
    we select that physical frame from dropdown, the child physical
    frame is not shown in the opened window.
    This APAR will show the child physical frame in that window.
    

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

    IJ10143

  • 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

    2018-10-09

  • Closed date

    2019-01-18

  • Last modified date

    2019-01-18

  • 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:
18 January 2019