HP 3000 Manuals HP 3000 Manuals
THRESHOLD
[CPU=percent ]
[DISC=rate ]
[RESPONSE=seconds ]
[FIRST=seconds ]
THRESHOLD [TRANSACTIONS=count]
[NONEW ]
[NOKILLED ]
[NOSHORT[=seconds] ]
[MINTHINK=seconds ]
[MAXTHINK=seconds ]
The parameters for THRESHOLD can be entered on the same line (separated
by commas) or on separate THRESHOLD lines.
The default for THRESHOLD is the following:
THRESHOLD CPU=10.0, DISC=10.0, RESPONSE=5.0, FIRST=1.0
THRESHOLD TRANSACTIONS=100
THRESHOLD MINTHINK=0.2, MAXTHINK=3600
NOTE The default status for NONEW, NOKILLED, and NOSHORT parameters is
OFF (not enabled)--that is, NEW, KILLED, and SHORT processes will
be logged.
CPU=percent
This parameter sets the amount of CPU utilization that a process must
exceed to become interesting and be logged. It is only used if process
logging is enabled.
Percent (1.0-100.0) indicates overall CPU usage. For example, CPU=7.5
indicates a process will be logged if it exceeds 7.5 percent CPU
utilization in a 1-minute sample interval.
DISC=rate
Rate (1-32767) signifies the disc I/O rate in transfers per second.
The DISC parameter sets the rate of physical disc I/Os that a process
must exceed to become interesting and be logged.
For example, DISC=8.0 indicates a process will be logged if it exceeds an
average of 8 disc I/Os per second in a 1-minute sample interval.
RESPONSE=seconds
Seconds (0.1-32767) signifies terminal response time.
The RESPONSE parameter sets the average terminal response time that a
process must exceed to become interesting and be logged. Terminal
response time is the number of seconds between pressing Return or Enter
and the next prompt.
This parameter also sets the default value for an application's
service-level response time.
For example, RESPONSE=4.0 indicates a process will be logged if its
response time exceeds an average of 4 seconds in a 1-minute sample
interval.
FIRST=seconds
Seconds (0.1-32767) signifies time-to-first response.
The FIRST parameter sets the average time-to-first response that a
process must exceed to become interesting and be logged. Time-to-first
response is the number of seconds between pressing Return or Enter and
the first data are written to the terminal.
This parameter also sets the default value for an application's
service-level response time.
For example, FIRST=1.5 indicates a process will be logged if its first
response time exceeds an average of 1.5 seconds in a 1-minute sample
interval.
TRANSACTIONS=count
Count (0-32767) signifies the number of terminal transactions.
The TRANSACTIONS parameter causes any process that completed more than
the specified number of terminal transactions during a 1-minute sample to
become interesting and be logged.
For example, TRANSACTIONS=85 indicates a process will be logged if it
exceeds 85 transactions in a 1-minute sample interval.
NONEW
The NONEW parameter prevents the logging of any process that would have
been considered interesting only because it was a new process and the
process was not interesting for any other reason during the sample
interval.
You can use the NONEW parameter to reduce the amount of disc space
required to hold process information when processes are being created
rapidly.
NOKILLED
The NOKILLED parameter prevents the logging of any process that would
have been considered interesting only because it was a terminating
process and the process was not interesting for any other reason during
the sample interval.
You can use the NOKILLED parameter to reduce the amount of disc space
required to hold process information when processes are terminating
frequently.
NOSHORT[=seconds]
Seconds (1-32767) signifies the minimum time a process must run to be
logged. The default is 30 seconds.
The NOSHORT parameter prevents the logging of any process that would have
been considered interesting only because it was created or terminated and
has a run time less than or equal to the specified number of seconds.
The process will be logged normally if it was interesting for any reason
other than being new or killed, or if it ran for longer than the
specified time.
Use the NOSHORT parameter to reduce the amount of disc space required to
hold process information when many short-duration processes are executed.
If you use NOSHORT instead of NONEW and NOKILLED, you can eliminate short
processes from the log file while still logging the start and stop of
longer-running processes.
MINTHINK=seconds
The range for the MINTHINK value is 0.001-60.000 seconds.
The MINTHINK parameter sets a filter used in calculating terminal
response times. Any terminal transaction having a think time less than
the MINTHINK setting is assumed to be a hardware-generated transaction,
such as a terminal status read.
Since the user at a terminal does not see or respond to this read to the
terminal, the user does not consider it to delimit a real terminal
transaction. Terminal reads that complete in less than the minimum think
time are therefore not used to delimit terminal transactions, and they
are treated the same as if they were a terminal write.
The following factors affect the MINTHINK parameter setting:
* Increasing the number of seconds in the MINTHINK parameter reduces
the number of terminal transactions and increases the average
response times.
* Setting MINTHINK too high can eliminate actual user-entered
terminal transactions and can report response times that are too
high.
* Setting MINTHINK too low can cause hardware-satisfied terminal
reads--such as terminal status requests used often in block mode
protocols like VPLUS--to be counted as terminal transactions.
This can result in a higher transaction count than is perceived by
the user and a shorter average response time.
* Setting MINTHINK to 0.0 defeats the minimum transaction think-time
filtering mechanism, and every terminal read will count as a
transaction. You may need to increase MINTHINK to account for
delays caused by data communications to terminals.
MAXTHINK=seconds
The range for the MAXTHINK value is 0-86400 seconds (24 hours).
The MAXTHINK parameter sets a filter used in calculating terminal
response times. Any terminal transaction having a think time greater
than the MAXTHINK setting is ignored. All times involved with this
transaction (think time, time-to-first response, and response time) are
discarded and a new transaction is begun.
You can use the MAXTHINK directive to eliminate start-up transactions at
a terminal after a long absence. If a terminal application is left idle
for a long time, MPE may reallocate the memory resources of that
application to other users on the system. When the next transaction is
completed all those memory resources must be re-acquired, often resulting
in an abnormally long response time.
To ignore the first transaction following a long absence, you can set the
MAXTHINK parameter to the number of seconds you want to consider a long
absence.