TMF Reference Manual (G06.26+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-154
DUMP FILES
When the disk resides on a remote node:
•
The name specified for disk must be fully qualified.
•
volume must not exceed seven characters, counting the dollar sign ($).
•
You cannot specify ZT as the prefix.
When the disk resides on a local node:
•
node and prefix are optional.
•
If node is not specified, the default is the node on which your TMSERVE
process is running.
•
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. For more information, see the
file-set parameter description.
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 name
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.