Starting and stopping the measure subsystem – HP NonStop G-Series User Manual
Page 34
![background image](/manuals/397027/34/background.png)
Measure Command Interface (MEASCOM)
Measure User’s Guide — 520560-003
2 -6
Starting and Stopping the Measure Subsystem
Starting and Stopping the Measure Subsystem
The Measure subsystem must be installed and operating before you can use the
Measure command interpreter or callable procedures to configure and run
measurements and display measurement data in active data files or counter space. To
display only data in inactive data files, you do not need to start the subsystem. Only a
super-group user (255,
n
) can start or stop the Measure subsystem.
Starting the subsystem creates the monitoring process (MEASMON) and its backup
process. MEASMON then immediately creates a counter-record control process
(MEASCTL) in each CPU of the local system.
To start the subsystem:
35> MEASCOM
MEASURE Performance Monitor - T9086G10 - (16DEC03) - \HATI
(C)1986 Tandem (C)2003 Hewlett Packard Development Company, L.P.
1+ START MEASSUBSYS
You can also start the subsystem from the command interpreter prompt without starting
MEASCOM interactively:
36> MEASCOM START MEASSUBSYS
If a CPU fails while the subsystem is running, MEASMON automatically re-creates and
restarts a MEASCTL control process in that CPU after the CPU is reloaded. The
re-created control process receives information on all currently active measurements
and starts data collection.
The data file for any measurement that spans the CPU’s failure and reload contains at
least one record for each measured entity in that CPU: the one from the CPU restart to
the end of the measurement. If a collection interval was specified for the measurement,
the data file contains records at each specified interval up to the time of CPU failure
(except for records lost from the write buffer) and at each interval after the CPU reload.
To stop the Measure subsystem:
6+ STOP MEASSUBSYS
Stopping the Measure subsystem aborts all currently active measurements. Closing
records are not issued, so data files might be incomplete.
Note.
If you start the subsystem from a Multilan window session, the Multilan Resource
Manager (MLRM) stops the MEASMON process when the window session terminates. The
MEASCTL processes continue to run. To stop them, reissue a START MEASSUBSYS
command from a Multilan session, then issue a STOP MEASSUBSYS command.
WARNING.
Do not bring down MEASCTL’s swap volume while Measure is still running. Doing
so could cause all CPUs to halt.