TMF Operations and Recovery Guide (G06.26+)

Online Dumps
HP NonStop TMF Operations and Recovery Guide—522417-003
5-5
Selecting Dump Options
In the <file-name> file, patterns that do not indicate fully-qualified file names are
expanded using the default node, volume, and subvolume names established in
TMFCOM. (For commands entered directly through SPI rather than TMFCOM,
however, you must specify the defaults to be used.)
NOT fileset
The NOT option specifies which files in the file set list are not to be dumped. If you
specify the same file in this option and in file-set, the file is not dumped. The
NOT file-set list allows the same pattern-matching (wild-card) characters
described in the file-set discussion. The NOT file-set information cannot
exceed the size of the SPI message buffer that supports communication between
TMFCOM and TMFSERVE, which is 28 KB. If this limit is exceeded, TMFCOM
displays Error Message 1050.
NOT <file-name>
identifies a file that contains one or more file-name patterns. These patterns, in
turn, designate files that are not to be dumped. If you specify the same file in NOT
<file-name> and in <file-name>, the file is not dumped. For more
information, see the <file-name> parameter description.
START start-file
The START option allows you to start the online dump in the middle of the file set
list. This option is most commonly used when a previous dump was stopped
prematurely, and you want to restart the dump at the specified starting point. Enter
start-file in the following format:
{[[volume.]subvolume.]{file-id | *}}
{[volume.]*.*}
You should create the dump commands in a command (OBEY) file so that the same
command is repeated each time.
Note. If you plan to refer to SQL/MX objects in a NOT file-set list, you must use the
Guardian names of the underlying files in all TMFCOM commands. You can run the
MXGNAMES utility to convert one or more objects’ ANSI names to their underlying
Guardian file names. You can then use the Guardian file names in the NOT file-set
list. For convenience, MXGNAMES provides an option that generates names formatted as
TMF file-sets for direct use in TMFCOM commands. For information about using
MXGNAMES, see the SQL/MX Reference Manual.
Note. You must include the angle-brackets (“<“ and “>”) exactly as shown in the <file-
name> syntax, embedding the file name within these. For example:
DUMP FILES <$BOULDER.SNOW.NPFILE>, NOT <$DENVER.RAIN.NPX>
You cannot specify both the NOT file-set and the NOT <file-name> formats within
the same DUMP FILES command.