HP 3000 Manuals HP 3000 Manuals
Specifying Files in a STORE Command The files that you are allowed to store depend on your capability. In general, you may only store files that you have read access to. If you are a system manager, system supervisor, or system operator, you can store any file in the system. The following section describes how you specify which files you want to be stored. The entire set of files to be stored is known as a fileset list. The fileset list is the first argument to the store command. If no files are specified, the default set is all files in your current working directory, or "@". This is the default no matter what capabilities you may have.
NOTE 1. If an empty fileset list is specified, and the DIRECTORY option is used, the default set is empty. This allows a system administrator to create a backup containing just the system accounting structures, without storing any files. 2. If a fileset list is not specified, a semi-colon (;) place holder must be used instead. For example: :FILE T;DEV=TAPE :STORE ;*T
If a fileset list is specified, it must follow certain guidelines. The list is made up of comma separated fileset items. Each item can be either a fileset or an indirect file. 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: filestostore [- filestoexclude [-....]] 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: * MPE syntax * HFS syntax MPE Syntax. A file is specified as: filename[.groupname[.accountname]] If accountname is omitted, the file is looked for in your logon account. If groupname is omitted, the file is looked for in your current working directory. A lockword may be specified for a file, in the form: filename/lockword.group.account HFS Syntax. A file is specified as: /dir_lev_1/dir_lev_2/.../dir_lev_i/.../filedesig or ./dir_lev_i/dir_lev_j/.../dir_lev_k/.../filedesig If the name begins with a dot ( . ), then it is fully qualified by replacing the dot with the current working directory (CWD). Each of the components dir_lev_i and filedesig can have a maximum of 255 characters with the full pathname being restricted to 1023 characters. Each of the components dir_lev_i and filedesig can use the following characters: * Letters a to z * Letters A to Z * Digits 0 to 9 * Special characters - _ . For HFS syntax, the lowercase letters are distinct from the uppercase letters (no upshifting). Names in MPE syntax are upshifted. 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: @ Specifies zero or more alphanumeric characters. # Specifies one numeric character. ? Specifies one alphanumeric character. The characters can be used as follows: n@ All files starting with the character n. @n All files ending with the character n. n####### All files starting with character n followed by seven digits (useful for storing all EDIT/3000 temporary files). n@x All files starting with the character n and ending with the character x. ?n@ All files whose second character is n. n? All two-character files starting with the character n. ?n All two-character files ending with the character n. Also, character sets may be specified in the following syntax: [ct] Specifies letter c or t. [c-t] Specifies any letter from range c to t. [e-g1] Specifies any letter range e to g or digit 1. Examples of using character sets are: [A-C]@ All files that begin with the letters A, B, or C. myset[e-g1] All files that begin with the name myset and end in E, F, or G, or 1. myset[d-e1-6] All files that begin with the name myset and end in D or E, or 1, 2, 3, 4, 5, or 6. 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. file.group.acct One particular file in one particular group in one particular account. file.group One particular file in one particular group in the logon account. file One particular file in the CWD. ./file @.group.acct All files (MPE and HFS) in one particular group in one /ACCT/GROUP/ particular account. ?@.group.acct All MPE-named files in one particular group in one particular account. @.group All the files (MPE and HFS) in one particular group in the /LOGONACCT/GROUP/ logon account. ?@.group All MPE-named files in one particular group in the logon account. @.@.acct All the files (MPE and HFS) in all the groups in one /ACCT/ particular account, plus all the files and directories under the specified account. ?@.@.acct All MPE-named files in all the groups in one particular account. thisisit.@.acct Any MPE-file named thisisit in all the groups in one particular account. @ All (MPE and HFS) files in the CWD. This is the default for everyone, regardless of permissions. @.@ All (MPE and HFS) files in the logon account. ?@.@.@ All MPE-named files in the system. @.@.@ All the files and directories (MPE and HFS) in the system. / 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
* Storing a single file :STORE FILE1.PUB.RESEARCH;*T * Storing several files :STORE FILE1.PUB.RESEARCH,FILE2.PUB.MYACCT;*T * Store several files with wildcards * Store all MPE and HFS files in GROUP1.ACCTNAME: :STORE @.GROUP1.ACCTNAME;*T * Store all MPE and HFS files in the dir3 directory: :STORE ./dir3/@;*T * Store all HFS files that start with lower case letters in the CWD: :STORE ./[a-z]@;*T * Exclude some files from a fileset: * Store everything on the system except files in PUB.SYS, MPE format: :STORE @.@.@-@.PUB.SYS;*T * HFS format: :STORE / - /SYS/PUB/@;*T * Store everything on the system except the 3000devs account: :STORE @.@.@ - /3000devs;*T * Store only the HFS-named files on the system: :STORE / - @.@.@;*T * Store only the MPE-named files on the system: :STORE ?@.@.@;*T * All files in the TEST group, except those that begin with A or B: :STORE @.TEST - A@.TEST - B@.TEST;*T 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: * Be an existing permanent or temporary file. * Have a record length between 8 and 14K bytes. * Have read access allowed, although the file may be open shared or intrajob. 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: filestostore [- filestoexclude [-...]][=targetname] The target name field specifies the new name and creator for the file on the store media. It has the form: filename[:creator[.creatoraccount]] 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). Storing Database Files Storing TurboIMAGE Databases. Prior to MPE/iX Release 5.5, the only way to logically back up databases was by using the DBSTORE and DBRESTOR commands. However, the DBSTORE program only allowed certain STORE options, and could only store or restore one database at a time. The features of DBSTORE are now available when using STORE, TurboSTORE/iX II or TurboSTORE 7x24 True-Online Backup. To specify a complete database to be stored, only the root filename needs to be specified. (By default, STORE does not allow you to specify an incomplete TurboIMAGE database to be stored when you use the 7x24 true-online backup option ONLINE=START or ONLILNE=END.) When STORE encounters a database root file, it will use the database to determine what other files are part of the database. Third-party indexing files will also be included in this list, if available. If a wildcard that includes an entire database is specified, TurboSTORE/iX will still verify the file list with the database to ensure that all database files are being written to the backup. If database dataset files are specified for a backup, but their root file is not specified, those dataset files will not be stored. For each file specified, the following warning will be displayed: MUSIC03.MUSIC.MYDB NOT STORED: FILE IS PART OF AN IMAGE DATABASE AND ROOT IS NOT SPECIFIED. If any of the dataset files are specified in addition to the root file, no warning will be displayed but the individual dataset files will be counted as redundantly specified files. If you are using the TurboSTORE/iX 7x24 true-online backup ONLINE option, then all TurboIMAGE databases fully specified, either by wildcards or by specifying the root file, are quiesced at the online backup sync point. If you want to back up part of an IMAGE database, you can specify the PARTIALDB option. For more information on PARTIALDB and storing databases with 7x24 true-online backup, see "Storing Database Files Using PARTIALDB or FULLDB" in Chapter 6, "STORE and TurboSTORE Command Options."
CAUTION If some of the dataset files are missing from the database, the quiesce may not succeed. STORE will still back up the dataset files listed in the fileset list.
Storing ALLBASE/SQL Databases. A similar convention exists for ALLBASE/SQL databases. Only the DBE file for an ALLBASE/SQL database needs to be specified. STORE will query the database to get the complete list of files to be stored. If an individual ALLBASE/SQL database file is specified without the DBE file, it will not be stored, and the following message will be issued: MYSET01.MYDB.SYS NOT STORED: FILE IS PART OF AN ALLBASE DB ENVIRONMENT AND DBCON IS NOT SPECIFIED. If any of the dataset files are specified in addition to the root file, no warning will be displayed but the individual dataset files will be counted as redundantly specified files. If you are using the TurboSTORE/iX 7x24 true-online backup ONLINE option, then all ALLBASE/SQL databases fully specified, either by wildcards or by specifying the root file, are quiesced at the online backup sync point. If you want to back up part of an ALLBASE DBEnvironment database, you can specify the PARTIALDB option. For more information on PARTIALDB and storing databases with 7x24 true-online backup, see "Storing Database Files Using PARTIALDB or FULLDB" in Chapter 6, "STORE and TurboSTORE Command Options."
CAUTION If some of the dataset files are missing from the database, the quiesce may not succeed. STORE will still back up the dataset files listed in the fileset list.
Storing Non-HP Databases. When storing databases other than than TurboIMAGE/SQL and ALLBASE/SQL databases, STORE does not enforce any root file/data set rules. You should continue to store other databases using the same procedures used prior to MPE/iX Release 5.5.