STORE

Specifies the set of files to be stored. The default set is @ meaning all files in the current working directory (CWD) regardless of the user's capabilities. If the DIRECTORY option is specified, the default file set is empty (no files).

The filesetlist parameter has the form shown below:

filesetitem[,filesetitem[...

where filesetitem can be ^indirectfile or fileset.

A file name that backreferences a disk file. The syntax is

^indirectfile or !indirectfile

This file may consist of fileset(s) and option(s), but only options can appear after the first semicolon (:) on each line. An option specified on one line will operate on all files in the filesetlist.

^indirectfile is the preferred format. If you use !indirectfile, the CI will interpret this as a variable reference, so you will have to specify !!indirectfile instead.

Specifies a set of files to be stored and optionally those files to be excluded from the STORE operation. The fileset parameter has the form:

filestostore[-filestoexclude[-filestoexclude[-...]

An alternate syntax exists for use with the RENAME option:

filestostore[-filestoexclude[-...[=targetname]

The system stores any file that matches filestostore unless the file also matches filestoexclude, which specifies files to be excluded from the STORE operation. You may specify an unlimited number of filestoexclude.

Since "-" is a valid character for HFS syntax file names, a blank character must separate it from HFS file sets to obtain the special negative file set meaning.

Both filestostore and filestoexclude may be entered in MPE or HFS syntax. Wildcards are permitted for both MPE and HFS syntax.

The MPE syntax is as follows:

filename[.groupname[.accountname

A lockword may be specified for files to be stored, in the form:

filename/lockword.group.account

The HFS syntax is as follows:

/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 path name being restricted to 1023 characters. Each of the components dir_lev_i and filedesig can use the following characters:

For HFS name syntax, the lowercase letters are treated distinctly from the uppercase letters (no upshifting). Names in MPE syntax are upshifted.

Both MPE and HFS name components can use the characters @, #, and ? as wildcard characters. These wildcard characters have the following meaning:

These wildcard characters can be used as follows

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

Examples of using character sets are:

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

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

Since the hyphen (-) is a valid character for HFS syntax file names, 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.

Specifying Database Files

When specifying TurboIMAGE and ALLBASE/SQL databases to be stored, only the root file or DBCon file needs to be specified. STORE will determine which other files belong to that database, and will store all of them. If dataset file(s) are specified without specifying a root file, then a warning will be printed for each file, and they will not be stored. Individual database files can be stored without the root file by specifying the ;PARTIALDB option on the STORE command line.

Database corruption may result if not all database files are restored from a backup. Be sure that you only want to restore certain database files before overriding the default behavior with ;PARTIALDB.

MPE and HFS Naming Equivalences

When an MPE name component is a single @ wildcard, the @ will be "folded" to include all MPE and HFS named files at that level and below. To specifiy only MPE-named files, use ?@ instead.

MPE wildcards are not expanded in filestoexclude. This means that @.@.@-@.@.@ is NOT an empty fileset. It contains all of the HFS named files on the system.

A fileset may be entered in any of the following formats and may use wildcard characters. Equivalent MPE and HFS formats are grouped together as follows.

Specifies the name and creator for the file on the store media. The targetname parameter 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 @ 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 in the filename.

The RENAME option must be specified if the targetname is used.

The name of the device to which the stored files are to be written. This may be any magnetic tape or DDS device. This file must be backreferenced, by using an asterisk (*). You must do this by using a File equation before invoking STORE.

A message is displayed on the system console requesting the operator to mount the tape identified by the storefile parameter and to allocate the device.

The storefile can now reference a remote device. For example, if you issue the following commands, NM Store will store all files to the specified remote device.

 :FILE REMOTE;DEV=REMSYS#TAPE
 :STORE @;*REMOTE;SHOW

NM STORE will store all files to the specified remote device. Although the initial tape mount request will appear on the remote console, all of the STORE console messages will be displayed on the local console. Currently, labeled tapes and Magneto-optical devices cannot be used for remote backup.

A message is displayed on the system console requesting the operator to mount the tape identified by the storefile parameter and to allocate the device.

If storefile is not supplied and the STORESET option is not used, then STORE creates a default storefile name. The default file name is the user's logon username. No file equation is used.

Sequential and parallel devices are specified with the STORESET option. Similarly, magneto-optical devices are specified using the MOSET option. Storefile should not be specified when using STORESET or MOSET.

If using TurboSTORE/iX 7x24 True-Online Backup, a disk file can also be specified with a file equation for storefile. An example of such a file equation would be:

:FILE MYDISC=DISCBACK.DAILY.BACKUP;DEV=DISC

Note that DEV=DISC must be specified for STORE to recover files from disk backups. All other information in the file equation will be ignored by STORE. STORE creates a binary, fixed record file containing the backup data. This disk file can be restored using the same file equation for RESTORE.

By default, STORE creates the disk file with a 4Gig limit. If the data being stored exceeds this, or an existing file with a smaller limit is specified for the backup, then STORE will create and write to additional disk files. It will append the "reel" number to the disk file name originally specified. For example, if the backup disk file specified was /SYS/BACKUPS/DAILY, and STORE ran out of room, it would create /SYS/BACKUPS/DAILY.2, /SYS/BACKUPS/DAILY.3, and so on. The additional files are HFS-named files.

TurboSTORE/iX 7x24 True-Online Backup must be used to create disk backups.

Specifies that STORE is to report information for every file that is stored. If you omit the SHOW parameter, then only the names of the files not stored are listed, along with the number of files stored and the number of files not stored. This listing is sent to $STDLIST (formal file designator SYSLIST) unless a FILE command is entered to send the listing to some other device. For instance, if you enter the following file equation before issuing the STORE command, the listing will be sent to a line printer.

FILE SYSLIST; DEV=LP

Tells STORE what information to display for the files that are stored. If you specify ;SHOW and omit showparmlist, then the default is SHORT if the recordsize of SYSLIST is less than 132 characters, or LONG if the recordsize is equal to or greater than 132 characters. The format for showparmlist is:

showparm [,showparm[,showparm[,...]

where showparm may be one of the options described below.

If an HFS-named file is specified in the filesetlist, or the expansion of a wildcard includes an HFS-named file, then an HFS-style output listing will be used. This listing shows the same information as the MPE format, but puts the name of the file at the right end of the listing to allow for longer HFS names. If an HFS name is too long to fit in the record size of the output file, it will be wrapped onto the next line. Wrapping is signified by a "*" as the last character on the line.

If a 7x24 True-Online backup is performed with the sync point at the end of the backup, additional information will be written to the listing. This information consists of a single character immediately following the volume restrictions. The possible values and meanings of this character are as follows:

For more information on performing 7x24 True-Online backups, refer the the Store and TurboSTORE/iX Manual (30319-90001).

Tells STORE what to do if there is a tape write error. If you omit this parameter, then the default option is REDO. ONERR is a synonym for ONERROR.

Instructs STORE to store only selected files. A moddate value (indicated by >=, equal to or greater than) limits the STORE to those files that were modified on or after a particular date.

An accdate value (indicated by <=, less than or equal to) limits the STORE to those files that were accessed on or before a particular date.

The date is expressed in the form mm/dd/yy[yy]. The year may be expressed in two or four digits (for example, 87 or 1987).

This option cannot be used for files that are attached to a log set.

Instructs STORE to purge all the files that were successfully stored, after the Store operation has ended. In an interactive session, MPE/iX prompts the user to enter any lockwords that have been omitted if the user does not have system manager, system supervisor, or account manager capabilities. In a job, if the user does not have SM, AM, or OP capability, the lockword(s) must be provided.

A file with a negative file code can be purged only by a user who has Privileged Mode (PM) capability.

If a file cannot be purged, a file system error message is sent to the user, stating that the file was not purged.

Instructs STORE to report its progress at regular intervals by displaying the message STORE OPERATION IS nnn% COMPLETE. For interactive users, this message is displayed on $STDLIST. For jobs, this message is sent to the system console.

A positive number specifying the number of minutes between progress messages. The maximum is 60. The default (and minimum) is 1 minute.

Specifies that the file system directory plus all HFS directories are to be stored. This option requires system manager (SM) or system supervisor (OP) capability.

If ONVS or SPLITVS is not specified, the DIRECTORY defaults to storing the system directory. Otherwise, the directories of the specified volume sets are stored. This way, operators and manager can store or copy private volume sets in their entirety.

Maximum number of MPE/iX files that may be stored when using the TRANSPORT option. The default is 4000. If the number of files requested is greater than this number, an error occurs and the store is not performed.

This parameter is ignored when you are storing without the TRANSPORT option. In that case, no limit is imposed.

Specifies that an MPE V/E compatible tape is to be written. TRANSPORT invokes the CMSTORE program, which limits the MPE/iX STORE command to the capabilities of the MPE V/E STORE command syntax. Also, you may specify only one file to exclude from the store.

The TRANSPORT option may also be activated by setting the CI variable HPCMSTORE to TRUE.

This option is not available if you have specified DIRECTORY, FCRANGE, SPLITVS, MAXTAPEBUF, STORESET, INTER, COMPRESS, ONLINE, MOSET, NAME, ONVS, TREE, or NOTREE options.

(optional) If MPEXL is specified, then STORE writes out MPE XL compatible media. If the TRANSPORT parameter is used and MPEXL is not specified, then MPE V compatible media is produced. This option is used to facilitate transport of files with a later version attribute to older systems. At present, ACDs are the only attributes that are translated.

Indicates that the access control definition (ACD), if one exists, will be stored with the file. This is the default parameter .

Indicates that the access control definition (ACD) should not be stored with the file. If this parameter is not specified, the ACD will be stored.

The set of file code ranges that are to be stored.

A file code range. A filecode is an integer between -32768 and 32767. ;FCRANGE=1000/1040 would store only those files having file codes between 1000 and 1040. You may specify a maximum of eight file code ranges.

Directs STORE to use the maximum available buffer size during the store operation. Currently, the maximum tape buffer sizes for the following tape drives are (in Kilobytes):

7974  16  7978B  32 DDS  32
7976  16  7979  32 MO  32
7978A  16  7980  32 3480  32

This option is also available by setting the CI variable HPMAXTAPEBUF to TRUE.

Notifies the user when the files being stored are available to be accessed. If an ONLINE store is being done, this notification is done at the end of the attach period, when the FILES ARE NOW FREE message is sent to the console. For a non-ONLINE store, the notification is done at the successful end of the entire store. Notification is done by streaming a job specified by the formal file designator NOTIFY. This file equation should be set up before the store command is run:

:FILE NOTIFY=MYJOB.PUB.SYS

STORE will attempt to issue a STREAM *NOTIFY at the appropriate time. If STORE is being run from a session, and the job requires passwords, the user will be prompted to enter them. If STORE is being run in a job and passwords are required, the job will fail to stream. The output from streaming the job is sent to $STDLIST. If the job fails to stream for any reason, STORE will print the error, but will not abort.

ON Volume Set. Specifies that only files in the filesetlist that reside on the volume specified are to be stored.

The example below stores the files on VOLUME_SET_A.

:STORE @.@.@;*TAPE; ONVS=VOLUME_SET_A

A set name included for the SPLITVS option can not be specified for the ONVS option. However, ONVS and SPLITVS can be both used in the same STORE command with different volume set names. The ONVS option also provides the ability to restrict, or enhance the creation of directory information on the store tape. If the DIRECTORY option is specified in conjunction with the ONVS option, only those accounting structures on the specified volume sets are stored.

Up to twenty volume sets may be specified.

A volume set name specified for the ONVS option. This volume set may be a split volume set. However, the files will be stored from the user volumes, not the backup volumes. If the files are in use for writing, they will not be stored.

"Split volume set." Specifies that only files in the filesetlist that reside on the backup volumes belonging to the specified split volume set are to be stored. The files may be concurrently in use while they are being stored, since users can only access files on the user volumes.

The following example stores the files on a split volume set called, SPLIT_SET_A:

:STORE @.@.@; *TAPE; SPLITVS=SPLIT_SET_A

A set name included for the ONVS.. option cannot be specified for the ``SPLITVS option. However, SPLITVS and ONVS can be both used in the same STORE command with different volume set names. The SPLITVS option also provides the ability to restrict, or enhance the creation of directory information on the store tape. If the DIRECTORY option is specified in conjunction with the SPLITVS option, only the accounting structures on the specified split volume set are stored.

Up to twenty volume sets may be specified.

A split volume set name specified for the SPLITVS option. This volume set must be a mirrored volume set which was split through VSCLOSE; SPLIT.

Renames the file, group, account, and optionally, specifies a new creator for each entry in a fileset. STORE will rename the files while creating the "file candidate list", which is a list of files created by examination of the fileset parameter of the STORE command.

The targetname syntax is used to specify the new target name for the fileset. For more details on the use of RENAME, refer to the Store and Turbostore Manual.

Forces each fileset to be scanned recursively. This is equivalent to using the trailing slash (/) in an HFS name. The TREE option yields a recursive scan in the hierarchical directory. This option is mutually exclusive with the NOTREE option.

Forces each HFS syntax fileset to not be scanned recursively. The NOTREE option yields a horizontal cut in the hierarchical directory. The NOTREE option is mutually exclusive with TREE.

Specifies that STORE should create a disc file that contains the backup media label and directory information. This file will be placed in the store_dirs directory of the HPSTORE.SYS group (/SYS/HPSTORE/store_dirs/). If this path does not exist, the directory file will not be created. The disc directory file can help to speed up the recovery process, particularly if ONLINE=END was used to create the backup. Because of this, this option is automatically enabled if ONLINE=END is specified.

All disc directory files are created with a file name that uniquely identifies the backup. The format is:

:/SYS/HPSTORE/store_dirs/store_yyyymmdd_hhmmsstt_pin##_day

where yyyymmdd represents the day the backup was started, hhmmssstt represents the time the backup was started, pin## is the pin number of the process that created the backup, and day is a three letter abbreviation of the day of the week the backup was started.

If specified, a symbolic link will be created with the filename specified. This link will point to the disc directory file created in /SYS/HPSTORE/store_dirs. This allows the user to associate a more meaningful name to the disc directory file. The name can be specified in either MPE or HFS format. If it is not fully qualified, it will be fully qualified using the CWD. If the disc directory file could not be created, then then symbolic link will also not be created.

Specifies that STORE should not create a disc file containing the backup directory. This is the default unless ONLINE=END is specified. Use this option with ONLINE=END to prevent STORE from creating the disc directory file.

Allows RESTORE to restore individual database dataset files without specifying the database's root or DBCon file.

Database corruption may result if not all database files are restored from a backup. Be sure that you only want to restore certain database files before overriding the default behavior with ;PARTIALDB.

Displays extra statistics about the backup. These include: amount of data written to each piece of media in each parallel set, amount of time required for each piece of media, throughput for each piece of media, and retries for each piece of media. If software compression is used, then the amount of compressed data and the compression ratio for each media is displayed. If an online backup is performed, the amount of log data written is displayed.

Specifies that file interleaving is to be used, which provides a higher disk data rate. Interleaving is accomplished by reading from several disk drives (files) simultaneously. The file data is blocked together and then stored to the specified device(s). The effect is to accelerate the store process.

INTER cannot be used with the TRANSPORT option.

Specifies parallel and sequential backup devices. This option cannot be used if the storefile parameter is specified, and it cannot be used in conjunction with the TRANSPORT option.

Sequential tapes are specified in this way

;STORESET = (*tape1,*tape2,*tape3,...)

This instructs STORE to use only one drive at a time from the specified serial pool for the store operation. It will select *tape1 first. When the first reel of tape is exhausted, STORE will shift to the next drive specified (*tape2), leaving the first free for rewinding and changing reels. Thus, at any given time, only one drive is occupied with the store process. The effect is to accelerate the process by eliminating the wait for a rewind and reel switch to occur. When STORE has written to the last device specified, it will wrap around to the first device.

To specify parallel devices, enter:

;STORESET=(*tape1),(*tape2),(*tape3) . . .

In this example, all three tapes will be used in parallel during the Store.

You can also specify that a set of tapes be stored in parallel. In the following example, two tapes would be storing at any particular moment, while the other two are rewinding, which permits the operator to switch reels.

;STORESET=(*tape1,*tape2),(*tape3,*tape4)

Specifies the device on which the file is to be stored. It must be magnetic tape or DDS. This device should be specified in a file equation before you invoke the STORE command, for example:

FILE DEVICE;DEV=TAPE

This file equation can also specify a remote device. If you are using the TurboSTORE/iX 7X24 True-Online Backup product, then a disk file can also be specified here. However, disk files can only be used with parallel STORE sets, not serial STORE sets.

STORESET cannot be used in conjunction with TRANSPORT.

Specifies that host data compression is to be used during the store operation. Currently, two levels of data compression are supported in backup. If you do not specify a level, the default is HIGH.

Informs STORE what type of compression is to be done. HIGH and LOW are the only valid parameters. HIGH and LOW cannot be used together.

Specifies parallel Magneto Optical (MO) backup devices. This option is not available if the storefile or TRANSPORT options are specified.

Parallel devices are specified by:

;MOSET = (12),(13),(15)

or

;MOSET = (MO),(MO),(MO)

All MO devices would be used in parallel during the store process.

If this parameter is present then the specified name and ensuing options are applied to the backup media. The NAME parameter is only valid for MO backup devices. It specifies the logical name for the backup. For example:

:STORE @.@.@;;MOSET=(12);NAME=BK1200PM.D23OCT90.BOZO

This name could indicate that a backup was created on 23 Oct 1990 at 12:00 PM on the system called BOZO. If the name parameter is not specified, a similar default name will be generated by STORE based on the other backup options. In either case the backup name is displayed on the SYSLIST/OFFLINE listing as:

THE BACKUP TO DASS NAME IS backupname

It is recommended that users provide CI variables and scripts to generate their own unique NAMEs for system backups.

A three field name of a total maximum length of 26 characters. The format is fname.gname.aname. The name represents the "handle" to this particular backup and can be used on a subsequent restore to retrieve files from this backup. The fname, gname and aname can be up to 8 alphanumeric characters. For example:

DAILY.D24OCT90.SYSTEM

Online backup. The store fileset is attached to a log handler and the users can concurrently read, write or purge files in the fileset after the files are attached to the log environment. The files must not be open for write before STORE is invoked, but write access is allowed as soon as the tape mount request appears on the console. The following message indicating completion of the attach phase is also sent to the system console:

FILES LOCKED BY ONLINE STORE ARE NOW FREE FOR READ/WRITE/PURGE

See the NOTIFY option for an additional way to notify users that the attach phase has completed.

Specifies that a 7x24 true-online sync point should occur at the beginning of the backup, before any files are stored. All files being stored do NOT have to be closed for write access when the backup starts.

Specifies that a 7x24 true-online sync point should occur at the end of the backup, after all files are stored. All files being stored do NOT have to be closed for write access at any time during the backup.

Specifying the option causes file log data to be written at the end of the backup. This media format is NOT backwards compatible, and media created with ONLINE=END CANNOT be verfied or restored on a pre-5.5 system.

Specifies when the true-online sync point should occur, in in 24-hour format, as HH:MM:SS.

The time must be specified with either START or END. If specified with START, the sync point will occur at the time specified, or after all of the files being stored are attached to shadow log files, whichever happens last. If specified with END, the sync point will occur at the time specified, or once all files have been stored, whichever happens last.

If the time specified is before the time the backup is started, then STORE will wait until that time the following day. This is helpful if you start the backup at 11:00 PM and want the sync point to occur at 2:00 AM the next morning.

When specified, will cause TurboSTORE to pause with an operator request before the true-online sync point. If you reply "N" to this request, you will be given the option of aborting the backup or continuing to wait.

After you reply to the console request, the sync point will occur.

This option can be specified with time, and must be specified with either START or END.

The name of the volume set where the shadow log files should reside, which must be a valid, currently mounted volume set.

RESTORE, VSTORE, REPLY, RECALL

| STORE and TurboSTORE/iX Manual

Magneto-Optical Media Manager User's Guide

Volume Management Reference Manual

Mirrored Disk/iX User's Guide