IBM Support

IV01669: THE SAVED NETWORK VEIW LAYOUT CHANGED TO ORIGINAL AFTER DOMAIN RESTART WHERE DISPLAY LABELS CONTAIN MUITI-BYTE CHARATERS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The saved network veiw layout changed to original after domain
    restart where devices' display labels contain muiti-byte
    charaters.
    
    And got the following errors
    in $TIPHOME/profiles/TIPProfile/logs/server1/SystemOut.log
    'SavedMap.getGraph: Unable to construct graph'
    
    and the Fatal Error in
    $TIPHOME/profiles/TIPProfile/logs/server1/SystemErr.log
    'XML document structures must start and end within the same
    entity'
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users saving Topology Maps with multi-byte characters (e.g.  *
    * multi-byte Japanese characters) may experience this issue    *
    * - across all supported hardware and software                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * While saving Topology Maps with multi-byte characters (e.g.  *
    * multi-byte Japanese characters) the                          *
    * topology map may be truncated when it is saved to the        *
    * database. The topology map can subsequently not be           *
    * loaded from the database. This may manifest as the GUI       *
    * reverting to the previous version of the topology.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * | fix pack | 3.8.0-ITNMIP-FP0007                             *
    * | fix pack | 3.9.0-ITNMIP-FP0001                             *
    ****************************************************************
    

Problem conclusion

  • Although then issue was initially identified on 3.8 , it is also
    prevalent on other releases.
    Hence, the fix is being applied to each of 3.8 3.9 and 3.9.1
    
    New behavior with fix in place:
    The Topology map is not truncated when it is saved to the
    database.
    It can subsequently not be loaded from the database
    successfully.
    

Temporary fix

Comments

  • The occurrence of this issue is dependent on both
    - the number of multi-byte characters in the topology map
    and
    - the compressibility of the map using ZLIB compression
    (as implemented by java.util.zip.Deflator and
    java.util.zip.Inflator)
    Both of these factors affect the size of the working buffer
    required to store the bytes prior to deflation/inflation.
    The code issue is that the working buffer is not set to be large
    enough to cater for all multi-byte scenarios.
    

APAR Information

  • APAR number

    IV01669

  • Reported component name

    TIV NETWK MGR I

  • Reported component ID

    5724S4500

  • Reported release

    380

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-13

  • Closed date

    2011-06-29

  • Last modified date

    2011-07-15

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

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

Fix information

  • Fixed component name

    TIV NETWK MGR I

  • Fixed component ID

    5724S4500

Applicable component levels

  • R380 PSN

       UP

  • R380 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSHRK","label":"Tivoli Network Manager IP Edition"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"380"}]

Document Information

Modified date:
28 September 2021