HP NonStop G-Series - Manual (Page 37)

Measure Command Interface (MEASCOM)
Measure User’s Guide — 520560-003
2 -9
Creating a Custom Startup File
Creating a Custom Startup File
You can create a file of MEASCOM commands to be executed similarly to a command
(OBEY) file each time MEASCOM is invoked. The file must be an EDIT file named
MEASCSTM that contains only MEASCOM commands.
You can set up multiple MEASCSTM files to perform different measurements. Each
MEASCSTM file must be in a different subvolume. MEASCOM first looks for the
MEASCSTM file in the current subvolume. If the file is not found, MEASCOM looks in
your default subvolume.
This example shows a MEASCSTM file:
COMMENTS SUPPRESS 2000
WARNINGS SUPPRESS 3014
SETPROMPT VOLUME
SET REPORT RATE OFF
SET REPORT LOADID TEST
Accessing Online Help
During an interactive MEASCOM session, you can access online help text for the
various MEASCOM elements. Enter the HELP command to display help text.
The help text for some topics is more than one screen long. For these topics,
MEASCOM uses a double prompt (++) at the end of the first screenful of text to
indicate more information. To view additional help text, press RETURN. To return to
command entry, press CTRL Y or type the word BREAK at the double prompt.
For a list of all MEASCOM keywords (commands, objects, and attributes) as well as
guidance to more specific help topics, enter HELP ALL.
•
To display the cause, result, and recovery action to be taken for any error
message, enter HELP and the error number. For example:
31+ HELP 3055
Cause: The parser encountered a syntax error
Result: The requested operation is ignored
Recovery: Correct the syntax according to HELP or the MEASURE
Reference Manual
•
To get information about how to use a Measure command keyword, enter HELP
and the command. For example:
32+ HELP ADD
The ADD command can operate on three objects: 1) entities
(such as CPU, Process, etc.), 2) a measurement datafile, and
3) the plot list.
Before a measurement can be taken, the measurement
configuration must be built. To do this, one or more ADD
entity commands are executed. For example, ADD CPU *; ADD
PROCESS $SYSTEM.SYSTEM.*, would cause all CPUs and any