TMF Reference Manual (G06.26+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-232
RECOVER FILES
<file-name>
identifies a file that contains one or more file-name patterns. These patterns, in
turn, designate files to be recovered. 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 RECOVER FILES 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,
the comment must begin with a hyphen in Column 1. However, if a line contains a
file-name pattern followed by a comment, the beginning hyphen is not required; all
characters that follow a file-name pattern are treated as a comment. The following
example illustrates the content of a <file-name> file:
$DATA01.SUBVOL1.FILE1
$*.ZSD*.*00 This is a comment: All SQL/MX data fork files.
- This is another comment: The next line is blank.
$DATA*.*0.FILE2
FILE3
.
.
.
In the <file-name> file, patterns that do not indicate fully-qualified file names are
expanded using the default node, volume, and subvolume names established in
TMFCOM. (For commands entered directly through SPI rather than TMFCOM,
however, you must specify the defaults to be used.)
If the <file-name> file contains very many patterns, you might need to increase
the extended segment size for the FILERECOVERY process by using the ALTER
PROCESS FILERECOVERY, EXTENDEDSEGSIZE command.
Note. You must include the angle-brackets (“<“ and “>”) exactly as shown in the <file-
name> syntax, embedding the file name within these. For example:
RECOVER FILES <$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
RECOVER FILES command.