HP 3000 Manuals HP 3000 Manuals
VSTORE
Verifies that the data on a backup media are valid (for example, there
are no media errors), and reports any errors incurred by STORE when
creating the backup.
Syntax
VSTORE [vstorefile][;filesetlist][;option[;...]]
where option is:
[;SHOW[=showparmlist]] [;ONERROR={QUIT}] [;DIRECTORY] [;COPYACD] [;NOACD]
[ {SKIP}]
[;TREE] [;NOTREE] [;NODECOMPRESS]
The following parameters are available with TurboStore products only:
[;RESTORESET=(device[,...])[,(device[,...])[,...]]]
[;MOSET=(ldev[,...])[,(ldev[,...])[,...]]] [;NAME=backupname]
Parameters
vstorefile The name of the device that contains the files you
want verified on the system. This file must be
backreferenced, using an asterisk (*). A FILE
equation for vstorefile should be set up before
invoking VSTORE. If you want to verify files from a
file called SOURCE enter this file equation before
running VSTORE:
:FILE SOURCE;DEV=TAPE
The vstorefile can now reference a remote device.
For example,
:FILE REMOTE;DEV=REMSYS#TAPE
:VSTORE *REMOTE;@;SHOW
NM Vstore will verify all files from the specified
remote device. Although the initial tape mount
request will appear on the remote console, all of
Vstore's console messages will be displayed on the
local console. Currently, labeled tapes and
Magneto-optical devices cannot be used for remote
verification.
A message is displayed on the system console
requesting the operator to mount the tape
identified by the vstorefile parameter and to
allocate the device.
If vstorefile is not supplied and the RESTORESET
option is not used, then VSTORE creates a default
file name. The default file name is the user's
logon username. No file equation is used.
Sequential and parallel devices are specified with
the RESTORESET option. Similarly, magneto-optical
devices are specified using the MOSET option. You
should not specify vstorefile when using RESTORESET
or MOSET.
filesetlist Specifies the set of files to be verified. The
default depends on the user's capability, as shown
below:
Default Capability
@ None
@.@ Account manager (AM)
@.@.@ System Manager and/or System
Supervisor (OP)
The is parameter has the form shown below:
filesetitem[,filesetitem[...]]
where filesetitem can be ^indirectfile or fileset.
indirectfile 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.
__________________________________________________
NOTE ^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.
__________________________________________________
fileset Specifies a set of files to be verified, and
optionally those files to be excluded from the
VSTORE operation. The fileset parameter has the
form:
filestovstore[-filestoexclude[..]]
Any file that matches filestovstore will be
verified unless the file also matches a
filestoexclude, which specifies files that are to
be excluded from the VSTORE operation. You may
specify an unlimited number of filestoexclude.
__________________________________________________
NOTE 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.
__________________________________________________
filestovstore Both filestovstore and filestoexclude may be
filestoexclude 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
verified, 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:
Letters a to z
Letters A to Z
Digits 0 to 9
Special 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:
@ specifies zero or more
alphanumeric characters.
# specifies one numeric
character.
? specifies one alphanumeric
character.
These wildcard characters can be used as follows
n@ Verify all files starting
with the character n.
@n Verify all files ending with
the character n.
n##...# Verify all files starting
with character n followed by
up to seven digits (useful
for storing all EDIT/3000
temporary files).
n@x Verify all files starting
with the character n and
ending with the character x.
?n@ Verify all files whose second
character is n.
n? store all two-character files
starting with the character
n.
?n Verify 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]@ Verify all files that begin
with the letters A, B, or C.
myset[e-g1] Verify all files that begin
with the name myset and end
in e, f, or g, or 1.
myset [d-e1-6] Verify all files that begin
with the name myset and end
in d or e, or 1, 2, 3, 4, 5,
or 6.
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.
__________________________________________________
NOTE 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.
__________________________________________________
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.
file.group.acct/ One particular file in one
ACCT particular group in one
/GROUP/FILE' particular account.
file.group/LOGON- One particular file in one
ACCT/GROUP/FILE particular group in the logon
account.
file ./FILE One particular file in the
logon group and account.
@.group.acct All files (MPE and HFS) in one
/ACCT/GROUP/ particular group in one
particular account.
?@.group.acct All MPE name files in one
particular group in one
particular account.
@.group/LOGON- All the files (MPE and HFS) in
ACCT/GROUP/ one particular group in the
logon account.
?@.group All MPE named files in one
particular group in the logon
account.
@.@.acct /ACCT/ All the files (MPE and HFS) in
all the groups in one
particular account, plus all
the files and directories under
the specified account.
thisisit.@.account Any MPE file named thisisit in
all groups in one particular
account.
?@.@.acct All MPE named files 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 the files and directories
(MPE and HFS) on the system.
?@.@.@ All MPE named files on the
system.
SHOW Request to list names of verified files. The
default is a listing of only the total number of
files verified, list of files not verified
(including the reason each was not verified), and
the count of files not requested to be verified.
The listing is sent to $STDLIST (formal designator
SYSLIST) unless you enter a FILE command to send
the listing to some other device. For example, you
would enter the following file equation before the
VSTORE command to send the listing to a line
printer.
FILE SYSLIST; DEV=LP
showparmlist Tells VSTORE what information to display for the
files that are verified. If you specify ;SHOW and
you 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. The format for showparmlist
is:
showparm [,showparm[,showparm[,...]]]
where showparm may be one of the options described
below. If you do not specify SHORT or LONG, then
the base information is SHORT if SYSLIST is less
than 132 characters, or LONG if SYSLIST is 132
characters or more.
__________________________________________________
NOTE 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 a 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.
__________________________________________________
showparm SHORT Overrides a default of LONG
and displays file, group, and
account name or the fully
qualified path name, volume
restrictions, file size (in
sectors), file code, and
media number.
LONG Overrides a default of SHORT
and displays all the
information that SHORT does
and adds the ending reel
number, record size, blocking
factor, number of extents,
EOF, and file starting and
ending media number. For
spoolfiles, the old spoolfile
name is also displayed.
NAMESONLY Displays only the filename
and the starting and ending
media number. NAMESONLY is
not allowed with SHORT or
LONG.
DATES Displays the creation date,
the last date of access, and
the last date of
modification.
SECURITY For MPE format listing,
causes SHOW to display the
creator and the file access
matrix for all the files
which do not have an active
ACD. For files with active
ACDs only, the phrase *ACD
EXISTS* is displayed.
For HFS format listing, the
phrase *ACD EXISTS* or *ACD
ABSENT* is displayed,
depending on whether the file
has an ACD.
PATH Forces all file listings to
be in HFS format. Full HFS
pathnames are displayed
instead of MPE style names.
OFFLINE Sends another copy of the
SHOW output to the formal
file designator OFFLINE,
which defaults to device LP.
ONERROR Tells VSTORE what to do if there is a tape read
error. If you omit this parameter, then the
default option is QUIT for labeled and unlabeled
tapes. ONERR is a synonym for ONERROR.
QUIT Tells VSTORE to abort after a
tape read error.
SKIP Tells VSTORE to perform a
file-skip-forward past a tape
error, resynchronize, and
resume reading from the tape.
DIRECTORY Specifies that the file system directory is to be
verified. Requires OP or SM capability. HFS
directories on the media are always verified.
COPYACD Directs VSTORE to copy the ACD associated with the
files or directories on the media. This option is
on by default.
NOACD Directs VSTORE to not copy the ACD associated with
the files or directories on the media. This option
overrides the default COPYACD option.
TREE 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 NOTREE.
NOTREE 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.
NODECOMPRESS Normally, VSTORE will decompress the data on a
Store-compressed media when verifying the files.
However, when NODECOMPRESS is specified, the files
will not be decompressed. Instead, just the
integrity of the raw data read from the media will
be checked. This results in a faster VSTORE of the
media, which just verifies physical consistency.
THE FOLLOWING OPTIONS ARE AVAILABLE ONLY IF TURBOSTORE XL OR TURBOSTORE
XL II IS INSTALLED ON YOUR SYSTEM. TURBOSTORE IS NOT PART OF THE
FUNDAMENTAL OPERATING SYSTEM, BUT MAY BE PURCHASED SEPARATELY.
For additional information on TURBOSTORE XL, refer to the Store and
Turbostore/iX Manual.
RESTORESET Specifies parallel and sequential backup devices.
This option cannot be use if the vstorefile
parameter is specified.
Consecutive tapes are specified in the following
way:
;RESTORESET = (*tape1,*tape2,*tape3,...)
This instructs MPE/iX to use only one drive at a
time for the vstore operation. When the first reel
of tape is exhausted, VSTORE will shift to the next
available drive, leaving the first free for
rewinding and changing reels. Thus, at any given
time, only one drive is occupied with the Vstore
operation.
Parallel devices are specified by
;RESTORESET=(*tape1),(*tape2),(*tape3)...
In this example, all three tapes will be used in
parallel during the VSTORE.
A set of sequential tapes to be verified in
parallel would be specified by
;RESTORESET=(*tape1,*tape2),(*tape3,*tape4)
In this example, two tapes would be verifying at
any particular moment, while the other two are
rewinding, permitting the operator to switch reels.
device Specifies the device from which the files are to be
verified. It must be a magnetic tape or DDS. This
device should be specified in a file equation
before you invoke the VSTORE command, ie:
:FILE DEVICE;DEV=TAPE
This file equation can also specify a remote
device.
MOSET Specifies parallel Magneto Optical (MO) backup
devices. This option is not available if the
storefile option is specified.
Parallel devices are specified by either of the two
following commands:
;MOSET = (12),(13),(15)
;MOSET = (MO),(MO),(MO)
All MO devices are used in parallel during the
vstore process. The preferred format is specifying
just "MO", since VSTORE will use the the NAME
parameter to locate the correct media.
NAME This parameter must be specified with the MOSET
option, and cannot be specified without it. It
specifies the logical name to be used for the
backup. For example:
VSTORE @.@.@;;MOSET=(12);NAME=DAILY.D23OCT90.BOZO
This name could indicate that the vstore process
should be taken from the daily backup done on 23
Oct 1990 on the system called BOZO.
backupname 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 is used to retrieve files from this
backup. The fname, gname and aname can be up to
8 alphanumeric characters. For example
DAILY.D24OCT90.SYSTEM.
Operation Notes
This command verifies that there are no media errors on backup media. It
reports any errors that may have occurred during the STORE procedure.
Your capabilities determine which files you may verify. If you have
system manager or system supervisor capability, you can verify any file
from a STORE backup. If you have account manager capability, you can
verify any file in your account. To verify files with negative file
codes, you need Privileged Mode (PM), system supervisor (OP), or system
Manager (SM) capability. If you have standard user capability, you can
verify only those files in your logon account.
This command applies only to NMSTORE tapes created in Native Mode. It
does not work on tapes created by Compatibility Mode Store.
The LOCAL option is no longer needed to verify files. All files will be
verified and displayed with their real filenames, even if parts of a
file's accounting structure do not exist on the system.
Use
This command may be issued from session, job, or program, but not in
BREAK. If you press [Break] during a Vstore, the operation continues
while you interact with the CI.
EXAMPLE
To verify all files on a backup:
1. Write a file equation to set up a device file.
:FILE T;DEV=TAPE
2. Use the VSTORE command and backreference the device file.
:VSTORE *T;@.@.@;KEEP;SHOW
Related Information
Commands STORE, RESTORE, REPLY, RECALL
Manuals STORE and TurboSTORE/iX Manual (30319-90001)
Magneto-Optical Media Management User's Guide
(36398-90001)