Okay, my VAR responded and said that syschk is usually setup to stop in
the user-coldstart macro with the command "syschk stop". He said it is
the most common thing he's seen.

Why is that? Is there no value in syschk?

He told me where the thresholds can be changed. So for those that use
syschk, what are your settings?

Sampling Period
Maximum CPU%
Maximum CPU% per process
Maximum % of swap
Maximum % of overflow
Maximum % of basic
Max % of txlog queue
Log message (0=no, 1=yes)


Regards,
Danny

I use syschk as an excuse to keep the clients from trying to use the
console as a workstation. I explain that syschk messages are system
diagnostic messages and *no one* should use the console as these
are necessary for proper diagnostics in the event of a problem.
They are not to touch the console unless I am on the other end
of the phone. It creates FUD to the benefit of system stability.

My 2, Patrick <;=)

ddspell-m3 wrote:

An excellent suggestion.
You are an evil genius.

/Scott Ballinger

(latimerp) wrote:

"ddspell-m3" wrote: Is there no value in syschk? ...

A number of prior discussions have good info on syschk. Here is
another tool in your kit:
http://groups.google.com/groups
From there use syntax like "group:comp.databases.pick syschk".
I have my browser set so all I need to do is type "cdp syschk" and it
shows me all CDP references to this or other keywords. Great for
research.

HTH