Specifying Files in a STORE Command

Filesets

A fileset specifies a group of files to be stored. It can also include an exclusion set, which is a group of files to be excluded from the STORE operation.

The syntax for a fileset is:

Where filestore represents a fileset and filestoexclude represents an exclusion fileset.

The filestostore and filestoexclude are specified using the same syntax. Any file that matches filestostore will be stored, unless the file also matches a filestoexclude. An unlimited number of filestoexclude may be specified. However, if the TRANSPORT option is also being used, only one filestoexclude may be specified.

	NOTE: Since the hyphen (-) is a valid character for HFS syntax filenames, a blank character must separate it from HFS filesets to obtain the special negative fileset meaning.

Specifying A Fileset

Filesets and exclusion sets are specified using the same format. They can be specified two different ways:

   /dir_lev_1/dir_lev_2/.../dir_lev_i/.../filedesig

   ./dir_lev_i/dir_lev_j/.../dir_lev_k/.../filedesig

Using Wildcard Characters

Use wildcard characters to select multiple files to store. The wildcard character is expanded to include all files that match.

Both MPE and HFS name components use the at sign (@), pound sign (#), and question mark (?) as wildcard characters. These wildcard characters have the following meaning:

The characters can be used as follows:

Also, character sets may be specified in the following syntax:

Examples of using character sets are:

You specify up to a maximum of sixteen characters for each character set, and you cannot nest brackets. Do not use character sets with the TRANSPORT option.

A character set specifies a range for only one ASCII character. The range [a-d]@ gets all files that begin with the letter "a" through the letter "d". The range [ad-de] will cause unpredictable results.

	NOTE: Since the hyphen (-) is a valid character for HFS syntax filenames, it is allowed inside a character set, immediately following a left bracket ([) or preceding a right bracket (]). When specified between two characters, the hyphen implies a range of characters.

MPE and HFS Naming Equivalences

When an MPE name component is a single @ wildcard, the @ includes all MPE and MPE-named files at that level and below. To specify only MPE-named files, use ?@ instead. The ? forces the first character of the filename to be an alphanumeric character, which only matches MPE-named files.

MPE wildcards are not expanded in exclusion filesets. This means that @.@.@-@.@.@ is NOT an empty fileset. @.@.@ is the same as /. -@.@.@ does not have an HFS equivalent. -@.@.@ specifies all HFS-named files on the system, the resulting fileset is all of the HFS named files on the system.

You can enter a fileset in any of the following formats and may use wildcard characters. Equivalent MPE and HFS formats are grouped together.

Examples:

	NOTE: All of the following examples assume that a file equation for T was previously set up, by issuing the FILE command: :FILE T;DEV=TAPE

Using Indirect Files

If you back up the same information regularly, you might keep the STORE parameters and options you use in an indirect file. An indirect file is a text file containing filesets, exclusion sets, and parameters for a STORE command. Instead of listing the files you want to store and the options you want to use in a STORE command, enter them in a text file and name the text file in the STORE command.

An indirect file must:

The following is an example of using an indirect file:

Suppose you regularly back up all the files on your system, including the system directory and a nonsystem volume set's files and directory. The usual STORE command, as illustrated in the previous section, might be:

   :STORE @.@.@;*T;DIRECTORY;ONVS=MPEXL_SYSTEM_VOLUME_SET,NV1

Using an indirect file can save time, especially if your STORE command is long or contains information that is difficult to remember. You enter the STORE files and parameters in a text file:

   @.@.@;DIRECTORY;ONVS=MPEXL_SYSTEM_VOLUME_SET,NV1

Give the text file a name that is easy to remember, and reference the text file name in a STORE command. The following STORE command references the file BACKUP as an indirect file:

   :STORE ^BACKUP;*T

The caret (^) is used prior to the filename to tell STORE that it is an indirect file.

The exclamation point (!) can also be used, but it will be interpreted by the command interpreter (CI) as a variable deference. If you do not intend for it to be used that way, you should specify two exclamation points (!!) to cause a single exclamation point ( ! ) to be passed to STORE. However, the recommended character is the carat ( ^ ).

Multiple indirect files can also be used. For example:

   :STORE ^BACKUP1,^BACKUP2;*T

Indirect files can also be nested. The maximum nesting level is 3. For example:

   INDIR1:  @.PUB.SYS;SHOW



   INDIR2:

   @.OUT.HPSPOOL

   ^INDIR1



   :STORE ^INDIR2;*T

Any commands that can be specified on the STORE command line can be specified in an indirect file. The one exception is the store device specification, which is usually specified immediately following the fileset list. The store device must always be specified on the command line. However, if multiple devices are being used for the backup, the STORESET option can be specified in the indirect file.

Options can be specified on both the command line and in the indirect file. Any options that are specified apply to all filesets in all indirect files, as well as any filesets specified on the command line.

Each line in the indirect file can contain fileset lists separated by commas, and options separated by semicolons. Fileset lists must always be specified first on a line. An option can also be specified first on a line, but once an option is specified, no fileset lists may follow them on the line.

Negative filesets can also be specified in indirect files. They should always immediately follow a fileset specification. Although one or more negative filesets can be specified on their own line, no options should be specified between the fileset and its associated negative filesets. As when specifying negative filesets on the command line, there is no limit to the number of negative filesets that can be specified.

Do not specify any continuation characters, such as ",", ";", "+", or "&", at the end of an indirect file line. If you need to specify more file sets than can fit on a line, just continue specifying them on additional lines. Do not start a line with the "," character. CI variables are not expanded in indirect files, so do not specify filesets using them.

Blank lines are not allowed in indirect files.

An example of a more complicated indirect file is:

   @.MYGR.MYACCT

   - A@.MYGR.MYACCT

   - /MYACCT/MYGR/B@;SHOW

   @.MYGR2.MYACCT - A##.MYGR2.MYACCT

   ;PROGRESS

   @.MYGR3.MYACCT, @.MYGR4.MYACCT

Using Filesets With the RENAME Option

If the RENAME option is specified, the fileset syntax is expanded to allow new filenames and creators to be specified. The RENAME syntax is:

The target name field specifies the new name and creator for the file on the store media. It has the form:

The filename can be any legal MPE filename or HFS pathname. The creator and creatoraccount must be legal creator and account names, respectively. The only wildcard character allowed is a single at sign (@) for each component of the filename, creator or creatoraccount. The wildcard character @ indicates that the source value for that component should be used. An HFS pathname which ends in a / is considered an HFS directory and no wildcard characters are allowed.

The RENAME option must be specified if the targetname is used. Refer to the RENAME section in Chapter 6, "STORE and TurboSTORE Command Options," for more details.

Storing Symbolic Links and Device Links

As of Release 5.0 and later, MPE/iX supports symbolic links and device links. When storing symbolic links, TurboSTORE only follows the link if it is not the last component of an HFS filename. If the symbolic link is the last component of an HFS filename, the only the link, or "container" will be stored. When storing device links, only the link is stored.

For example, if you have a symbolic link named /SYS/TESTDIR which points to the directory /MYACCT/MYDIR, then issuing the following STORE command would store all of the files in /MYACCT/MYDIR:

   STORE /SYS/TESTDIR/@;;SHOW

If you had a symbolic link name /SYS/PUB/MYFILE, which pointed to /MYACCT/PUB/TARGET, then the following STORE command would only store the symbolic link MYFILE, not the target file TARGET:

   STORE /SYS/PUB/MYFILE;;SHOW

For more information regarding symbolic links and device links, see the article "Symbolic Links on MPE/iX" in Chapter 5 of the Communicator 3000 MPE/iX General Release 5.0 (Core Software Release C.50.00) (30216-90124).