IV21442: MAKE DISCOVERY PROCESS LOG THE TIME TAKEN AND NUMBER OF EXECUTIONS FOR EACH STITCHER

IBM Tivoli Network Manager IP 3.9.0 Fix Pack 3, 3.9.0-TIV-ITNMIP-FP0003
IBM Tivoli Network Manager IP 3.9.0 Fix Pack 4, 3.9.0-TIV-ITNMIP-FP0004
IBM Tivoli Network Manager IP Edition 3.9.0 Fix Pack 5, 3.9.0-TIV-ITNMIP-FP0005

APAR status

• Closed as program error.

Error description

• When diagnosing slow discoveries there is often a delay of a
  serveral days during which time L2 will send the customer a perl
  script to add timing infomration to the discovery stitchers and
  ask them to run a new discovery and send back the resutls.
  
  This ticket has been raised to cover some changes to the
  discovery process that will allow it to log the time taken and
  number of executions for each stitcher on every discovery. This
  would significantly reduce the time taken to diagnose when a
  discovery is slow due to a specific stitcher.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All ITNM 3.9 users.                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When diagnosing slow discoveries there is often a delay of a *
  * serveral days during which time L2 will send the customer a  *
  * perl                                                         *
  * script to add timing infomration to the discovery stitchers  *
  * and                                                          *
  * ask them to run a new discovery and send back the resutls.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * | fix pack | 3.9.0-ITNMIP-FP0002                             *
  ****************************************************************
  

Problem conclusion

• StitcherProfiling rule implemented .
  The call to get the new profiling logged is at the end of the
  ProfilingEndFinal.stch stitcher.
         // The first of the following two lines will log the
  number of executions
          // and the total execution time of each stitcher that
  had been executed. And
          // the second will reset this data ready for a
  subsequent discovery.
          //
          StitcherProfiling('LOG');
          StitcherProfiling('RESET'
  

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

  NC/PREC DISCOVY

• Fixed component ID

  5724O52DS

Applicable component levels

• R390 PSN

     UP

• R390 PSY

     UP