NonStop SPAM User Guide

NonStop SPAM – Version 1.2 – T0814
Page 43 of 44
 INTERVAL <process timeline interval>
The "New Process Creation Timeline" and "Process Existence Timeline" reports show the user new
process creations and process existence, respectively, during intervals within the overall measurement
"window". These reports show 16 equal-sized intervals within the window.
Use this parameter, in conjunction with the BEGIN parameter, to "zoom in" on a shorter time period
within the measurement window.
Use this parameter to specify the interval size, in minutes. Values range from 0 to 999 minutes; the
default value is 0, which causes these reports to compute the interval size such that the entire
Window (or BEGIN time to end of window) is shown.
Example: INTERVAL 5, BEGIN 08:30
 IOFACTOR <physIO:cache hit CPU cost ratio>
Some reports attempt to apportion Disc Process CPU time to the files/partitions accessed, or to the
programs accessing the files/partitions.
This parameter specifies how much more CPU-costly a Physical I/O (Driver Call minus Cache Hit) is than a
Cache Hit. Values range from 0.0 to 99.9; the default value is 2.0 - the same default value as is used by
the Tandem Capacity Model (TCM).
Example: IOFACTOR 2.5
 MINMSGS <minimum messages received>
The "Program Overview" chart and the "Application Program Profiles" report show program resource
consumptions and wait times per "unit of measurement". One MESSAGE RECEIVED is often a good unit
of measurement for "server" processes.
Other processes (e.g. batch processes), however, may receive only process-creation messages such as
the STARTUP message, a PARAM message and one or more ASSIGN messages. A MESSAGE RECEIVED is
not usually an appropriate unit of measurement for such processes.
MINMSGS allows the user to specify the minimum number of messages a process must receive in order
for "Program Overview" and "Application Program Profiles" to show program resource consumptions
and wait times PER MESSAGE RECEIVED. If the average number of messages received by processes run
from a given program file is below MINMSGS, "Program Overview" and "Application Program Profiles"
will instead show program resource consumptions and wait times PER SECOND of the average "lifetime"
of one of these processes.
NOTE: Values range from 1 to 9999; the default value is 10.
Example: MINMSGS 15