TMF Planning and Configuration Guide (H06.05+)

Reconfiguring TMF Processes
HP NonStop TMF Planning and Configuration Guide540136-002
6-5
Online Restore
Online Restore
The TMP automatically creates an online restore process whenever a file recovery
process requires that one or more online dumps be restored. The online restore
process copies online dump files from the archive media to disk. When it is finished,
the online restore process is terminated.
If the online restore process stops or abends while TMF is running, the TMP
automatically restarts it. When it is finished, the online restore process is terminated.
The $CMON Process
There is an optional system communications monitor process, called $CMON, that, if
present, participates in determining where new processes are started and the priority
at which they will run. If $CMON exists, the TMP sends a message to it, soliciting
agreement on which processor and priority to use (although it does not usually do so,
$CMON can override the configured attribute values). If $CMON does not exist, the
TMP uses the applicable attribute values from its configuration file.
Changing Process Attributes
You change the attributes of TMF processes by using the TMFCOM ALTER PROCESS
command.
For most TMF processes, you can change the processors in which they run. (The only
exceptions are the TMFMON and TMFMON2 processes, because they run in all
processors in the system.) This is the most commonly recommended way to
reconfigure processes for load balancing.
For all TMF processes, you can also change the following attributes:
The priority at which the process executes
The extended and process file segment sizes
The swap volume used by the process
The debug mode (INSPECT or DEBUG)
The home terminal
The program file name (except for the TMFMON and TMFMON2 processes)
To display and change the currently saved process configurations, use the ALTER
PROCESS command.
You can view or change process configurations only when TMF is started or stopped.
If it is stopped, the TMP must be running. New configuration values for a process do
not take effect until the next time the process is started.