TMF Operations and Recovery Guide (G06.24+)

Online Dumps
HP NonStop TMF Operations and Recovery Guide522417-002
5-4
Selecting Dump Options
The file-name pattern syntax is:
[[$pattern.]pattern.]pattern
In this syntax, pattern consists of one or more characters. Allowable characters
are letters, digits, asterisks (*), and question marks (?). The maximum length of a
pattern is 8 characters, including wild-card characters. Wild-card characters can
appear in any portion of a name, for as many times as there can be characters in
that portion.
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.
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.
The attributes for online dumps, which are set with the DUMP FILES command, are
similar to those for audit dumps, which are set with the ALTER AUDITDUMP
command, with the following exceptions:
The COPIES option specifies the number of parallel copies to be made of each
dump; online dumps cannot be made serially. To make two copies of an online
dump, therefore, requires two tape drives. Make two copies of each dump, if you
have two available tape drives, in case one online dump tape cannot be read.
COPIES 1 is the default.
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.