HP 3000 Manuals HP 3000 Manuals
Chapter 7
Performance Collection SoftwarePerformance Alarms
Performance Collection Software performance alarms may be used to
identify periods in the logged data when performance met user-specified
criteria. You can specify up to 50 independent alarms. Each alarm
definition may contain the following:
* An alarm identifier (up to 40 characters).
* One or more CONDITIONS that must be satisfied.
* An ACTION to be performed when the alarm is initiated.
* An ACTION to be performed when the alarm has ended.
* A minimum time between repetitions of the same alarm.
The alarm identifier determines which alarm is being acted upon. The
40-character ID string is optional and may be any user-specified value.
A condition specifies two items, a comparison between those items, and a
duration for which the comparison must be true. Items can be selected
from a list of performance metrics provided by the SCOPE(XL) collector,
constants, or user-defined variables. A user can define up to 26 user
variables which are combinations of two items (metric, constant, or
previously-defined user variables). These two items may be added,
subtracted, multiplied, or divided to arrive at the new user-variable
value.
You can specify actions to take when (1) the alarm is first satisfied
because all conditions for the alarm were true for their specified
durations and/or at the end of an alarm because one or more of the
conditions ceases to be true after the alarm was satisfied. An action
can be an MPE command (including :RUN commands), a command to the
SCOPE(XL) collector, or the name of an ASCII file that may itself contain
commands. The commands can include codes to force the substitution of
metric or user variables before they are executed.
You can specify a minimum time between repetitions to prevent alarms from
acting more than once within a given period. If you specify an alarm
action such as the streaming of a detailed data collection job, you might
want not want the job to be streamed more then once a day, even if the
alarm condition continues through the day or is satisfied then becomes
active again during the same day.
NOTE Alarm actions will not be performed while logged data is being
examined. They can be listed with substituted performance metrics
if desired.
Performance Collection Software alarms are specified in the SCOPE(XL)
collector's PARM file. The syntax for specifying these alarms is:
ALARM=alarmid [TYPE=typeid] [SEVERITY=severitynumber]
IF item1 [>, <, >=, <=] item2 FOR duration [MINUTES]
[:MPECOMMAND ]
THEN [$SCOPE scopecommand]
[^COMMANDFILENAME ]
[:MPECOMMAND ]
FINISH [$SCOPE scopecommand]
[^COMMANDFILENAME ]
REPEAT=nnn
VAR [A - Z] = item1 [+, -, *, /] item2
where:
ALARM=
alarmid is a string of up to 40 characters that identifies this alarm.
The default is all blanks.
typeid is a string of up to 8 characters that identifies the general
category for this alarm. Any combination of 8 characters is acceptable,
but certain products might recognize specific strings. The default is
all blanks.
severity number is an integer number indicating the relative severity of
this alarm. Any value between 0 and 32767 is acceptable although certain
products might place special significance on values in certain ranges.
The default is zero.
IF
item1 is the first item in the comparison. An item can be one of the
following:
* A positive number specifying a literal constant [real numbers are
allowed].
* A metric name chosen from the Performance Items tables shown later
in this chapter.
* The upper case characters A through Z signifying a
previously-defined user variable. VAR followed by upper case A
though Z may also be used to reference a user variable. For
example, A and VAR A are equivalent.
condition is one of the following codes that indicate how to compare
item1 and item2.
> true if item1 is greater than item2
< true if item1 is less than item2
>= true if item1 is greater than or equal to
item2
<= true if item1 is less than or equal to
item2
duration is the number of continuous minutes that the condition must be
true before the alarm is satisfied. Performance metrics are updated
every five minutes and most are averages of the values for the last
five-minutes. If at the end of a sample, the condition is true then five
minutes is added to the accumulated time.
If the condition is false for more than one-half the duration time, the
accumulated true time is reset to zero. The condition is considered
satisfied only when its accumulated true time exceeds its duration time.
The duration time prevents false alarms from transitory events or
multiple alarms from events which are mostly continuous.
You can specify multiple conditions for an alarm. Each condition applies
against the last ALARM command entered, and all such conditions must be
satisfied at the same time before the alarm can begin.
THEN
This is an optional parameter, but if entered it specifies the action to
be taken when the alarm is first satisfied. It will be repeated also if
the alarm remains satisfied for a period longer than the specified REPEAT
period.
If the first character of the action string is a colon (:), the action is
interpreted as a single MPE command. Most MPE commands are allowed,
including the :RUN command to run programs. The following commands are
specifically not allowed:
ABORT DO HELLO SETCATALOG
BYE EOD JOB SHOWCATALOG
CHGROUP EOJ LISTREDO REDO
DATA EXIT OPTION RESUME
On MPE/iX, user-defined commands (UDCs) and user COMMAND-file commands
may be entered. On MPE V, UDC and COMMAND-file commands are not allowed
using this syntax.
If the first character of the action string is a dollar sign ($), the
SCOPE data-collection program interprets the action as a command. Valid
SCOPE commands are:
$SCOPE NOTE Logs a message to the GLOBAL log file. These messages
message can be retrieved using the UTILITY SCAN command.
$SCOPE NEW Forces the SCOPE collector to process its PARM file again
and act on any changes.
If the first character in the action is a caret (^), it is interpreted as
the name of an ASCII file. This file will be opened, and the commands in
it will be executed (subject to the restrictions listed above). This
feature works on MPE V as well as on MPE/iX. See the discussion of
Variable Substitutions in "Commands", later in this chapter.
NOTE Alarm actions will not be performed while logged data is being
examined. They can be listed with substituted performance metrics
if desired.
FINISH
This is an optional parameter, but if entered it specifies the action to
be taken when an alarm is started and then ends (it is no longer
satisfied). The options for this action are the same as those for the
THEN parameter, above.
REPEAT=
[MINUTES] specifies the minimum time between repetitions of an alarm
before it is allowed to be satisfied again. If the alarm is satisfied
and remains satisfied for this time, it will REPEAT (it will process the
THEN action again without performing the FINISH action). If the alarm is
satisfied, finishes, and is satisfied again, no second THEN action will
be taken until after the time specified by REPEAT=nnn following the
initial satisfaction of the alarm. Alarm conditions continue to be
processed during the REPEAT interval, but no THEN action is taken until
the REPEAT interval passes and the alarm is again satisfied (no
intermediate alarms are remembered during the repeat period).
NOTE The REPEAT time will always be greater than or equal to the longest
DURATION time for any condition in the alarm. If you try to set a
lower REPEAT time, it will be overridden. If you do not specify a
REPEAT time, the default will be the time of the longest DURATION
in the alarm.
VAR
The VAR command creates a user variable. You can have up to 26 user
variables (named A through Z). Each variable definition consists of two
items (see item1 and item2 definitions above) plus an arithmetic
operation that is to be performed on them. The operations are:
+ User variable = item1 added to item 2
- User variable = item1 minus item 2
* User variable = item1 multiplied by item2
/ User variable = item1 divided by item 2
NOTE A user variable may include another user variable in its definition
but variables are processed in alphabetical sequence from A through
Z. For proper operation you should not reference a user variable
unless it precedes the current one, alphabetically.
Table 7-1. Global Performance Items
Item Name Description
TOTAL CPU Total percentage of CPU busy.
SYSTEM CPU CPU usage by system processes (percentage of
total).
SESSION CPU CPU usage by interactive session processes
(percentage of total).
BATCH CPU CPU usage by batch job processes (percentage of
total)
MEM MGR CPU CPU usage for memory management (percentage of
total)
DISPATCH CPU CPU usage for dispatching processes (percentage
of total, MPE/iX only).
CACHING CPU CPU usage for disc caching (percentage of total,
MPE V only).
OTHER CPU CPU usage for other activities such as ICS
(percentage of total).
CPU PAUSED Time CPU was idle and disc IO occurred
(percentage of total).
IDLE CPU Time CPU was idle and disc IO did not occur
(percentage of total).
PHYS DISC Physical disc IO rate (IOs/second), overall not
counting MEM MGR.
SYSTEM DISC Physical disc IO rate for system processes
(IOs/second).
SESSION DISC Physical disc IO rate for session processes
(IOs/second).
BATCH DISC Physical disc IO rate for batch processes
(IOs/second).
MEM MGR DISC Physical disc IO rate for memory management
(IOs/second).
LOGICAL DISC Total logical disc IO rate (IOs/second).
DISC UTIL Average percentage disc utilization.
TRANSACT/MIN Terminal transactions completed
(transactions/minute).
FIRST RESP Average first-response time for terminal
transactions.
RESPONSE Average response-to-prompt time for terminal
transactions.
ANY LOGL IO Highest logical disc IO rate on any disc drive
(IOs/second; MPE V only).
ANY PHYS IO Highest physical disc IO rate on any disc drive
(IOs/second).
ANY MEM IO Highest memory management IO rate on any drive
(IOs/second).
ANY UTIL Highest percentage utilization on any disc
drive.
CPU QUEUE Average number of processes waiting for or using
the CPU.
DISC QUEUE Average number of processes waiting for DISC
transfers.
MEMORY QUEUE Average number of processes waiting for MEMORY
resources.
IMPEDE QUEUE Average number of processes waiting for locks,
etc..
NUM JOBS Average number of batch jobs logged on.
NUM SESSIONS Average number of sessions logged on.
ACTIVE JOBS Average number of active batch jobs.
ACTIVE SESS Average number of active sessions.
Performance metrics may be selected for a single application as defined
in the PARM file. The syntax for specifying an application performance
item is
application name:application item
where application name exactly matches one of the APPLICATION= strings
defined earlier in the PARM file (including upper/lower case), and an
application item is chosen from the list below.
Table 7-2. Application Performance Items
Item Name Description
TOTAL CPU CPU usage by this application's processes
(percentage of total).
PHYS DISC Physical disc IO rate for the application
(IOs/second).
TRANSACT/MIN Terminal transactions completed
(transactions/minute).
FIRST RESP Average first-response time for terminal
transactions.
RESPONSE Average response-to-prompt for terminal
transactions.
SERVICE LEVL Terminal transactions meeting service levels
(percentage of total).
CPU QUEUE Average number of processes waiting for or
using the CPU.
DISC QUEUE Average number of processes waiting for DISC
transfers.
MEMORY QUEUE Average number of processes waiting for
MEMORY resources.
IMPEDE QUEUE Average number of processes waiting for
locks etc..
CPU WAIT Time spent waiting for CPU resources
(percentage of total).
DISC WAIT Time spent waiting for disc data transfers
(percentage of total).
MEMORY WAIT Time spent waiting for main memory resources
(percentage of total).
LOCK WAIT Time spent waiting for software locks &
impedes (percentage of total).
IO WAIT Time spent waiting for IO other than disc
and terminal input (percentage of total).