HI Karin,
Your mail comes like manna from heaven :)
I have a customer who has asked me about a setting ( which apparently set in 
.vnmrc ) for MAIL_Q_SIZE, but I can't find anything on that : wants to know 
what is the default setting and which factors to take into account when 
increasing or lowering it ?

Can you help me out ?

Regards
Arnold Jeffrey
Software Support Engineer
Dimension Data
South Africa


From: Karen Kedda [mailto:[email protected]]
Sent: Thursday, October 28, 2010 5:17 PM
To: spectrum
Subject: [spectrum] VNMRC entries


After looking back at backups from years ago, I found some .vnmrc entries that 
I used to use at different customers.  I'm curious if anyone is still using 
them.  I have a ticket open with CA to see if they're still viable, but thought 
I'd query the Spectrum community to see if anyone still uses them:

always_randomize_first_poll=1
mdl_act_dist_factor=1800

These entries were used to randomize polling and I believe the 
mdl_act_dist_factor was a timer used in setting up randomizing the polling.  
Anyone remember more information?


Some other entries I currently user in my .vnmrc file are as follows:
ctrace=true                                        <==  Turns on Communication 
Tracing (for troubleshooting - will add lots of entries to the VNM.OUT)
strace=true                                        <==  Turns on Security 
Tracing (for troubleshooting - will add lots of entries to the VNM.OUT)
CORBATRACE=true                                <==  Turns on Corba Tracing (for 
troubleshooting - will add lots of entries to the VNM.OUT)
MDLACT_DEBUG=true                                <==  Turns on Tracks models as 
they activate (for troubleshooting - will add lots of entries to the VNM.OUT)
debug=true                                        <==  Turns on General 
debugging (for troubleshooting - will add lots of entries to the VNM.OUT)
procedure_error_file=procedure_error.txt        <==  New in 9.x for tracking 
issues with Event Procedures.  Haven't seen anything in our file, so our Event 
Procedures must work correctly!
event_disp_error_file=eventdisp.txt                <== Tracks issues with 
EventDisp files.  Very helpful in finding issues with new Event handling.

Anyone else want to share undocumented .vnmrc entries?

The following can also be added to the .locrc file.
ctrace=true                                        <==  Communication Tracing 
(for troubleshooting - will add lots of entries to the LOCSERV.OUT)
strace=true                                        <==  Security Tracing (for 
troubleshooting - will add lots of entries to the LOCSERV.OUT)
CORBATRACE=true                                <==  Corba Tracing (for 
troubleshooting - will add lots of entries to the LOCSERV.OUT)


Karen Kedda
Enterprise Monitoring Solutions
Berkley Technology Services LLC
405 Silverside Rd., Suite 205
Wilmington, DE 19809
302.746.2113
[email protected]


*************
CONFIDENTIALITY NOTICE: This e-mail and the transmitted documents contain 
private, privileged and confidential information belonging to the sender. The 
information therein is solely for the use of the addressee. If your receipt of 
this transmission has occurred as the result of an error, please immediately 
notify us so we can arrange for the return of the documents. In such 
circumstances, you are advised that you may not disclose, copy, distribute or 
take any other action in reliance on the information transmitted.

 *   --To unsubscribe from spectrum, send email to 
[email protected]<mailto:[email protected]> with the body: unsubscribe spectrum 
[email protected]

This email and all contents are subject to the following disclaimer:

"http://www.dimensiondata.com/emaildisclaimer";

---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to