TMF Planning and Configuration Guide (H06.05+)

Concepts and Capabilities
HP NonStop TMF Planning and Configuration Guide—540136-002
1-3
Using the TMFCOM ALTER TMF Command
CONFVOL when creating TMF processes. You can store several TMF configurations
on a single node by specifying a different volume for each. Only one configuration,
however, can be active at one time.
The following topics describe how to specify the volume you want TMF to use for its
configuration information, how to move your current configuration from the $SYSTEM
volume to one that can be remotely mirrored, and how to determine which volume is
the current configuration volume.
Using the TMFCOM ALTER TMF Command
You specify which configuration volume you want TMF to use by issuing a TMFCOM
ALTER TMF, CONFIGVOL command while TMF is stopped.
After accepting the new configuration volume, TMF issues EMS event message 285,
specifying the new configuration volume:
The TMF configuration volume has been changed from volume1 to
volume2.
THE ALTER TMF, CONFIGVOL command causes the TMP to alter the configuration
volume and then stop itself. Although stopping the TMP is basically a TMF “crash,” it
does not affect running applications because TMF is in a stopped state. The TMP is
automatically recreated.
The next time TMF is started, it uses the information in the new configuration volume,
and generates EMS event message 120:
Starting TMF, using volume as the configuration volume.
Choosing the Configuration Volume
The chosen configuration volume should be mirrored; if you are using the Nomadic
Disk Subsystem, it must be remotely mirrored. The volume must also be attached to
the same processor as $SYSTEM; this will make the configuration volume immediately
available to TMF processes when the TMP is being created during a cold load.
Caution. You must ensure that the configuration volume is attached to the same processor as
$SYSTEM. If the configuration volume is unavailable because it is attached to a processor
that is not yet up:
•
A system RELOAD * operation might hang.
•
TMFMON2 will not be able to start the TMP and will generate EMS event message 287:
File-system error errornum occurred in accessing the
configuration volume volname.