TMF Reference Manual (G06.24+)

Using TMFCOM
HP NonStop TMF Reference Manual—522418-002
2-9
Using Partially Qualified File Names
•
If you omit \node,volume, or subvolume, the default is your current node,
volume, or subvolume, respectively.
If you omit the OUT option, the device from which you enter the TMFCOM command
receives the output.
As an illustration of the OUT option, to direct the output from a STATUS TMF
command to a disk file named $OPS.STATUS.TMF, you enter the following command:
TMF 25> STATUS /OUT $OPS.STATUS.TMF/ TMF
Using Partially Qualified File Names
For convenience and brevity, you can use partially qualified file names in TMFCOM
commands. These names, for example, often specify the file but not the node
(system), volume, or subvolume on which the file resides. The system then
determines, by context, the node, disk volume, and subvolume where the file is stored.
Specifically, partially qualified file names are expanded according to the default node,
volume, and subvolume names in effect when TACL is started, or by default names
established by TMFCOM commands as follows:
•
For file names of command files, the defaults established by the TMFCOM
commands OBEYVOL and VOLUME are used.
•
For file names of output files, the defaults established by the TMFCOM command
VOLUME are used.
•
For file names of other files used in TMFCOM commands, the defaults established
by the CMDVOL and VOLUME commands are used.
The default names established by TMFCOM override those established in TACL.
Suppose, for instance, that you use the following VOLUME command to set your
TMFCOM command context to the default volume $OPS and the default subvolume
TMFLOC:
TMF 33> VOLUME $OPS.TMFLOC
Thereafter, when you enter a command to access any file in the current subvolume,
you can omit the node, volume, and subvolume names from this command, and use
only the file name:
TMF 34> DUMP FILES DFILE1
In this context, this command would be equivalent to entering:
TMF 35> DUMP FILES $OPS.TMFLOC.DFILE1