TMF Reference Manual (G06.24+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-002
3-166
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.
BRIEF | DETAIL | OBEYFORM
specifies the size and content of the report to be produced, and its destination:
BRIEF
produces a short form of the report and is normally used when directing output
to devices that handle 80 columns or fewer per line (terminals, for example).
The report includes the name of the dumped file, the tape volume identifier, the
serial number of the dump, the date and time of the dump (to the minute), and
the type of the dump. If you omit both BRIEF and DETAIL, BRIEF is assigned
by default.
DETAIL
produces a long form of the report and is normally used when directing output
to devices that handle up to 132 columns per line (printers, for example). In
addition to the items listed with the BRIEF option, the detailed report includes
the master audit trail sequence number, the part number of the dump, the copy
number of the dump, and the date and time (to the second) that the dump was
taken.
OBEYFORM
formats the INFO DUMPS output as command file text that can be executed by
TMFCOM. TMF saves this output in the file designated by the OUT option
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.