TMF Reference Manual (G06.24+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-002
3-128
DUMP FILES
•
Any value for prefix can be specified.
•
If prefix is not specified, the local node default ZT is automatically assigned
as the prefix.
Optical disks are not supported for dump to disk operations.
If you specify DISKMEDIA, you must omit the following options: BLOCKSIZE,
COPIES, SYSTEM, TAPEMEDIA, and VERIFYTAPE.
NOT file-set
identifies one or more files that 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 earlier in the
discussion of the file-set option for this command. 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
indicates the file at which the online dump begins in the specified volume and
subvolume. TMF dumps this file and all subsequent ones (based on alphabetical
ordering) in this volume and subvolume. Enter start-file in the following
format:
{[[volume.]subvolume.]{file-id | *}}
{[volume.]*.*}
You can use an asterisk (*) in the file-id or subvolume field of start-file,
but not in the volume field. If you specify an asterisk in the file-id field, the
dump starts at the beginning of the subvolume. If you specify an asterisk in the
subvolume field, the dump starts at the beginning of the volume. To avoid
dumping the entire database, you should specify start-file as a fully qualified
file name.
If you do not specify the volume and subvolume in start-file, the current
default volume and subvolume are used. If the resulting file cannot be found, the
START parameter is ignored and TMF dumps the entire file set.
Note. If you plan to refer to SQL/MX objects in a file-set list or 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 file-
set list or 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.