IV60992: ITNM CORE (E.G. NCP_MOEL) AND ITNM GUI SET THE TIMESTAMPS INCONSISTENTLY RESULTING 0 NODES IN NETWORKVIEWS

4.1.1-TIV-ITNMIP-Linux-FP0002
4.1.1_README_NLS_FP0002
4.1.1_README_FP0002
3.9.0-TIV-ITNMIP-Solaris-FP0005
3.9.0_INSTALL_NLS_FP0005
3.9.0_INSTALL_FP0005
3.9.0-TIV-ITNMIP-Windows-FP0005
3.9.0-TIV-ITNMIP-zLinux-FP0005
3.9.0-TIV-ITNMIP-Linux-FP0005
3.9.0-TIV-ITNMIP-AIX-FP0005
4.1.1_README_NLS_FP0001
4.1.1_README_FP0001
4.1.1-TIV-ITNMIP-Linux-FP0001
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-Windows-IF0001
3.9.0.4-TIV-ITNMIP-GUI-Windows-IF0001
3.9.0.4-TIV-ITNMIP-GUI-Window-IF0001
3.9.0.4-TIV-ITNMIP-GUI-Unix-IF0001
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-zLinux-IF0001
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-Solaris-IF0001
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-Linux-IF0001
3.9.0.4-TIV-ITNMIP-CORE-OpenSSL-AIX-IF0001
3.9.0.4-TIV-ITNMIP-zLinux-CORE-IF0001
3.9.0.4-TIV-ITNMIP-Windows-CORE-IF0001
3.9.0.4-TIV-ITNMIP-Solaris-CORE-IF0001
3.9.0.4-TIV-ITNMIP-Linux-CORE-IF0001
3.9.0.4-TIV-ITNMIP-AIX-CORE-IF0001
3.9.0.4_README_NLS_IF0001
3.9.0.4_README_GUI_IF0001
3.9.0.4_README_CORE_OpenSSL_IF0001
3.9.0.4_README_CORE_IF0001
IBM Tivoli Network Manager IP 3.9.0.4 Interim Fix 1, 3.9.0.4-TIV-ITNMIP-IF0001
IBM Tivoli Network Manager IP Edition 3.9.0 Fix Pack 5, 3.9.0-TIV-ITNMIP-FP0005
IBM Tivoli Network Manager IP Edition 4.1.1 Fix Pack 2, 4.1.1-TIV-ITNMIP-FP0002

APAR status

• Closed as program error.

Error description

• v3.9-FP3 - applicable for other FixPacks too (FP1 to FP4).
  
  The ITNM components use different methods of setting the
  timestamp in the NCIM database (ncim.domainMgr - column name is
  'lastUpdated') - some use the system timestamp, others use the
  database to set the timestamp. This causes problems when the
  timestamps are compared for various operations. All timestamps
  recorded in NCIM database should be set at a database level to
  be consistent.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users have ITNM and database servers installed separately    *
  * and located in different time zone.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Network Views show zero nodes on the graph after discovery   *
  * completes. The reason is that the Core server is in a        *
  * different time zone than the TIP and the Database servers.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * The following fixpacks will contain the fix:                 *
  * | fix pack | 3.9.0-ITNMIP-FP0005                             *
  * | fix pack | 4.1.1-ITNMIP-FP0001                             *
  * | fix pack | 3.9.4-ITNMIP-IF0001                             *
  ****************************************************************
  

Problem conclusion

• The root cause is that the Core and the GUI use different
  methods to set/read the timestamps to/from the database. Some
  places in the code use the system timestamp, others the database
  timestamp. The inconsistency in setting and using the lastUpdate
  timestamp tricks the Network Views that the discovery hasn't
  happened yet (the lastUpdate timestamp is in the future), hence
  zero nodes are shown on the screen.
  
  Modify the following timetamp parameters to be set at the
  database level and not using the system time:
  NCIM_FN_CREATIONTIME
  NCIM_FN_LASTUPDATED
  NCIM_FN_CREATE_TIME
  NCIM_FN_CHANGE_TIME
  PATH_LASTTRACED
  

Temporary fix

Comments

APAR Information

• 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

• R390 PSN

     UP

• R390 PSY

     UP

• R411 PSN

     UP

• R411 PSY

     UP