TMF Planning and Configuration Guide (G06.26+)

Reconfiguring TMF Processes

HP NonStop TMF Planning and Configuration Guide—522416-005

6-6

Returning to Default Process Configurations

If you have changed process configurations for TMF processes and you are

experiencing problems, you can use the RESET options for most configuration

parameters to reset the parameters to their default values. By using the wild-card

feature (*), you can reset all parameters for all processes in a single ALTER

PROCESS command. For details, refer to the description of the TMFCOM ALTER

PROCESS command in the TMF Reference Manual.

Changing Processor Residency

You can move TMF processes (except the TMFMON and TMFMON2 processes) from

one processor to another by using the CPUS option in an ALTER PROCESS

command. You might want to do this for load balancing.

If no CPUS list is defined for a recovery process (backout, file recovery, or volume

recovery) and $CMON is not running, the new process is created in the first processor,

from all available processors that are up, with the fewest instances of that particular

process type.

Unless overridden by the $CMON process, the default processor for all other TMF

processes (besides recovery, TMFMON, and TMFMON2) is the processor in which the

primary TMP is running.

TMFMON and TMFMON2 processes always run in all processors, and therefore

cannot be moved.

Changing Process Priorities

You can change the priority at which TMF processes run by using the PRI option in an

ALTER PROCESS command.

Unless overridden by the $CMON process, the default priority is 205 for TMFMON, 180

for TMFMON2, 204 for the TMP, and 140 for all others.

Changing Extended Segment Sizes

You can change the extended segment size for particular TMF processes by using the

EXTENDEDSEGSIZE option in an ALTER PROCESS command. You should do this

only in the following cases:

•

If a TMF process fails and generates an event message stating that it ran out of

memory space

Caution. Consider the operations and values described in the following discussion very

carefully, because the basis for them is subject to ongoing change. If such changes were

implemented in TMF since this manual was published with RVU G06.26, they will be described

in TMF Supplement for Limits and Defaults Changed After RVU G06.26. If that Supplement

currently exists, please read it for new information about this topic.