Skip to main content

Support & downloads  >  

$DBDIR/tl_rules.err and $DBDIR/tl_rules.out grow in size
 Technote (FAQ)
 
Question
The rulesets ebusiness.rls, dependency.rls and netview.rls call tl_init() and if a call is made to this then output is put to the above files even if debug tracing is set to off.
 
Answer
The problem is in the wic file tracelog.pro and has been fixed at 3.9 FP08, the file is updated automatically as part of the upgrade.

If not able to upgrade to FP08 then a workaround is to comment out the tl_init() call in the rule that is causing the problem.

 
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Systems and Asset Management
 Event Management Automation
 IBM Tivoli Enterprise Console
 Operating system(s):
  AIX, HP-UX, Linux, Solaris, Windows
 Software version:
  3.9
 Reference #:
  1315619
 IBM Group:
 Software Group
 Modified date:
 2009-07-06

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.