TRANSFER Installation and Management Guide

Sample Monitor Configuration
TMANAGER
10–26 13198 Tandem Computers Incorporated
Database Threshold: 80%
The database threshold depends on how full you want any part of the database to
grow before raising an alarm.
Queue Thresholds:
Queue Work MaxValue
1120
1 10 1000
3110
411
431
451
Tandem recommends monitoring the READY and HELD queues; normally you do
not need to monitor the TIME file. Monitoring the NET queue can alert you to
potential network problems.
Monitoring the READY queue (Queue 1)
You can ensure that message delivery is proceeding satisfactorily by
monitoring the number of Submit Pkg (work type 1) requests waiting to be
processed on the READY file. The value shown in the preceding example is
dependent on the concurrent numbers of users submitting packages.
If the alarm is activated, it might be no problem if 20 users submit packages at
the same time. The alarm merely warns you that message delivery might be
backing up. You can then monitor the queues more closely.
Monitoring the NET queue (Queue 3)
By monitoring Submit Pkg (work type 1) requests on the NET queue, you can
detect potential problems with remote message delivery. A remote
TRANSFER system might be down, the node itself might be off the network,
someone might have tried to send a message to a nonexistent TRANSFER
system, your own node might be off the network, or you might be having
problems with EXPAND.
Monitoring the HELD queue (Queue 4)
By monitoring the HELD file, you can detect problems with message transport
and message delivery that cannot be resolved by TRANSFER.