TMF Planning and Configuration Guide (H06.06+, J06.03+)

Reconfiguring TMF Processes
HP NonStop TMF Planning and Configuration Guide—540136-005
6-9
Changing Home Terminals
The DEBUG option, if present, specifies that you want debug mode to be on as soon
as the process is created and started (omitting the option designates that you want
debug mode enabled only if the process terminates abnormally).
The MAKESAVEABEND option, if present, specifies that you want a saveabend file
created (preserving the context) if the process terminates abnormally. This option
requires use of the Inspect program; it is ignored if you omit the INSPECT option.
Changing Home Terminals
You can change the home terminal for particular TMF processes by using the TERM
option in an ALTER PROCESS command. By default, TMF processes use the system
console as their home terminal. Someone using a debug program in conjunction with a
TMF process, however, might want to temporarily change the home terminal for that
process to a terminal that is easier to use than the system console.
You should change home terminals for TMF processes only under special
circumstances, at the direction of your service provider.
Changing Program File Names
The program file for a TMF process is the file containing the code that, when executed,
constitutes that particular kind of process.
You can change the program file name for any of the TMF processes except TMFMON
by using the PROGRAMFILE option in the ALTER PROCESS command. (Because the
TMFMON code is contained within the operating system image, and therefore does not
have its own file on the $SYSTEM disk, you cannot use the PROGRAMFILE option for
that process.) However, you should change the program file for a TMF process only
under special circumstances, at the direction of your service provider.
The default program file names for the TMF processes are as shown in Table 6-2 .
Caution. If the SWAP, TERM, or PROGRAMFILE attribute for the TMFMON2 process is
modified so that the swap volume, terminal, or program file is inaccessible when a processor is
reloaded, the attempt to create the TMFMON2 process in that processor fails. Then TMF tries
again to create TMFMON2 in this processor, this time ignoring the configured value of the
attribute causing the problem and using that attribute’s default value instead. Although TMF
starts this TMFMON2 process with one or more default values, the configuration attributes are
not permanently modified. Thus, if the attribute values no longer cause errors when future
TMFMON2 processes are created, these new processes run with the configured values rather
than the defaults.
Until successful, TMF attempts to start the TMFMON2 process every 60 seconds. For each
failed attempt, TMF issues an EMS event message 184 to explain the problem.