| {Sorry about the delayed response}
1. ZAP uses the DELPRC system service which is the same as using
the "$ STOP/ID=" command. Some applications do have problems
with this and should not be stopped by ZAP. Each application
should be checked.
2. Zap uses Direct I/Os, Buffered I/Os and CPU clock ticks to
determine how much work is performed. The ratio is
(3 * Direct I/O ) + ( 2 * Buffered I/O ) + CPU ticks
You can not change the formula, but you specify how many "units"
must be performed to be considered "active".
3. Zap uses UIC, Image name, Terminal class/name to determine
which "catagory" a user falls in to. Each "catagory" can have
its own time limit or be immune. An "mini" example is below
of the Zap data file:
!UIC Image Terminal Time limit Send Message
[1,*] * console * Nomessage
[200,150] monitor any 15 Message
[200,*] monitor any 30 Message
Etc.
In addition, you specify when the warning messages should be
send and what they should look like.
ZAP V3.8 can be obtained via the ASSETS program from VTX with
the $ VTX ASSETS_OFFICE command.
Thanks for your interest,
Keith Maconi
|