TMF Reference Manual (G06.26+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-194
INFO DUMPS
For both online dumps and audit dumps, in the file-set list, file names are
expanded with default volume and subvolume names, and the space required for
them is impacted by other overhead as well. All 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.
You can specify a file-set as a file-name pattern, using the asterisk (*) and
question mark (?) as wild-cards in pattern-matching. For full information about
specifying a file-name pattern, see the file-set parameter discussion in the
DUMP FILES command description.
If the file-set parameter is omitted, all dumped files are selected, subject to the
additional filtering criteria specified in the other INFO DUMPS parameters.
<file-name>
identifies a file that contains one or more file-name patterns. These patterns, in
turn, designate files for which information is to be retrieved. The <file-name>
file can be an EDIT format file (file code 101) or a C data file (file code 180).
Typically, the <file-name> file is generated by an automated process such as
the MXGNAMES utility that converts ANSI names to Guardian file names for
SQL/MX, or by a TACL macro. The <file-name> option lets the process or user
specify many more files within a single INFO DUMPS command than is possible
with the file-set option.
Within the <file-name> file, each non-blank line contains a file-name pattern that
identifies a volume, subvolume, and file, using the syntax and rules described
earlier under the file-set description. The pattern must begin in Column 1.
Blank lines are permitted, and so are comments. If a line contains a comment only,
Note. If you plan to refer to SQL/MX objects in a 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. 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:
INFO DUMPS <$BOULDER.SNOW.NPFILE>
Wild-card characters (such as * and ?) are not allowed in the file name bounded by the
angle-brackets.
You cannot specify both the file-set
and the <file-name> formats within the same
INFO DUMPS command.