TMF Reference Manual (G06.24+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-002
3-90
ALTER PROCESS
Cold Loading and Reloading Considerations
All settings established by the ALTER PROCESS command persist across subsequent
cold-load operations.
Altering the program file for the TMFMON2 process type does not require cold loading
all processors. However, the ALTER PROCESS command does not take effect for a
particular processor until that processor is reloaded. There is no way to stop an
individual TMFMON2 process without stopping its processor. To avoid possible
incompatibilities, you might wish to cold load the system after altering the TMFMON2
program file name.
If the TMFMON2 process type’s SWAP, TERM, or PROGRAMFILE attributes are
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. Now, TMF tries again to create TMFMON2 in this processor, this time ignoring
the configured value of the attribute causing the problem and using instead that
attribute’s default value. 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.
TMF fails if the SYSTEM_TERMINAL option was not used in the system generation
operation. When this failure occurs:
•
The TMFMON2 process in the cold-load processor (named $ZTMnn) may repeat
the following EMS event message every 10 seconds:
TMF *0182* TMP Process #0: The TMF process TMP could not be
started or it failed. Completion Code: 4. Completion Info:
8 PROCESS_CREATE_error 8, 14 on file TMFTMP
•
Attempts to reload any other processor will fail, and the target processor will halt
with halt code %1002.
AUDITDUMP
AUDITRESTORE
COPYAUDITOVFLOW
FILERECOVERY
FILERECOVLIST
ONLINEDUMP
ONLINERESTORE
VOLUMERECOVERY
Processes of these types are transient in the system; they are
started automatically as they are needed, and terminate
automatically when they are no longer needed.
Table 3-2. Stopping and Restarting TMF Processes
Process Type How Stopped and Restarted