HP 3000 Manuals HP 3000 Manuals
STORE Options
Listing the Files Stored (SHOW)
Whenever you store a set of files, the system displays the total number
of files stored at your terminal. If there was an error, it also
displays the number and names of files not stored and the reason each was
not stored. Use the SHOW parameter and its options to display the names
and additional information about the files stored and to list them on
your system printer as well as at your terminal.
Internally, the STORE program writes information about the files it
stores to a file with the formal file designator SYSLIST. It prints file
information at your terminal by equating SYSLIST with the standard
listing device for your session (your terminal). You can redirect the
file information to another file or device by issuing a FILE command that
assigns SYSLIST to that device or file. For example, you might want to
redirect the file information to a disk file so that you can keep it
online for your records.
To write STORE information to the disk file, SHOWFILE, enter:
:FILE SYSLIST=SHOWFILE;DEV=DISC
To print information on the files you stored at the system printer as
well as at your terminal, use the SHOW=OFFLINE option:
:FILE T;DEV=TAPE
:STORE @.OPERATOR.SYS;*T;SHOW=OFFLINE
To redirect the OFFLINE listing to another file or device, issue the
following FILE command, it will send a copy of the STORE listing to the
disk file SHOWOFFL:
:FILE OFFLINE=SHOWOFFL;DEV=DISC
To generate a store listing to the terminal as well as to a disk file,
enter the previous FILE command followed by the STORE command:
:STORE @.OPERATOR.SYS;*t;SHOW=OFFLINE
Using a Long or Short File Display.
The STORE command gives you two options for displaying additional
information about the files stored. Using the SHOW parameter, you can
choose to display file information in either long or short form.
A short file display prints the file's full name, volume restrictions,
number of sectors, file code, and media number for each file you store.
In addition to there being a long and a short SHOW listing, there are
also two different versions of each - MPE and HFS. The type of listing
printed depends on the input fileset list. You will get a HFS style
listing if:
* At least one file in the fileset list is specified in HFS syntax.
* A fileset wildcard is expanded to include a HFS syntax file.
The HFS style listing contains the same information as the MPE style
listing. The only difference is that the filename is printed as an
absolute pathname at the end of the line.
Since HFS pathnames can be of variable length, and can be quite long,
they are placed at the end of the line so that they will not affect the
spacing of the other columns. If the name does not fit on one line, it
will be wrapped to the next line. An asterisk (*) will be placed at the
last column of the line to indicate that the rest of the filename will
continue on the next line.
NOTE It is likely that a STORE with the fileset @.@.@ will result in a
HFS format listing, since MPE/iX, by default, contains some
HFS-named files.
To display the list of files stored using the short form in MPE format,
use the SHOW=SHORT option in your STORE command. For example:
:FILE T;DEV=TAPE
:STORE @.PUB.TEST;*T;SHOW=SHORT
Figure 6-1 illustrates a short file display in MPE format using the
above example.
________________________________________________________________________
| |
| |
| FILENAME GROUP ACCOUNT VOLUME RESTRICTIONS SECTORS CODE MEDIA |
| |
| FILE1 .PUB .TEST DISC :C 1104 1 |
| FILE2 .PUB .TEST DISC :C 0 1 |
| FILE3 .PUB .TEST DISC :C 32 1 |
| |
________________________________________________________________________
Figure 6-1. Short File Display (MPE Format)
This example uses the same fileset as the first example, except that it
is specified in HFS syntax.
:FILE T;DEV=TAPE
:STORE /TEST/PUB/@;*T;SHOW=SHORT
Figure 6-2 illustrates a short file display in HFS format using the
above example.
________________________________________________________________
| |
| |
| VOLUME RESTRICTIONS SECTORS CODE MEDIA FILENAME |
| |
| DISC :C 1104 1 /TEST/PUB/FILE1 |
| DISC :C 0 1 /TEST/PUB/FILE2 |
| DISC :C 32 1 /TEST PUB/FILE3 |
| |
| |
________________________________________________________________
Figure 6-2. Short File Display (HFS Format)
This example shows how the HFS syntax names will be wrapped, if they
cause the line to exceed 80 characters:
:FILE T;DEV=TAPE
:STORE /usr/lib/terminfo/e/e[t-z]@;*T;SHOW=SHORT
Figure 6-3 illustrates a short file display in HFS format with line
wrap using the above example.
____________________________________________________________________________
| |
| |
| VOLUME RESTRICTIONS SECTORS CODE MEDIA FILENAME |
| |
| DISC :C 256 1 /_HFSACCT/_HFSGRP/HFSMAP |
| DISC :C 16 1 /usr/lib/terminfo/e/ethern* |
| et |
| DISC :C 16 1 /usr/lib/terminfo/e/ex3000 |
| DISC :C 16 1 /usr/lib/terminfo/e/exidy |
| DISC :C 16 1 /usr/lib/terminfo/e/exidy2* |
| 500 |
| |
____________________________________________________________________________
Figure 6-3. Short File Display with Wrapped HFS Names
A long file display contains the same information as a short file display
plus each file's ending media number, record size, blocking factor,
maximum number of extents allowed, end-of-file, and file record limit.
Once again, there are two formats for the long listing--MPE and HFS. The
HFS format contains the same information as the MPE format, except that
the variable-length HFS filename is at the end of the line. It will be
wrapped in the same was as the short listing if the filename length
exceeds the line length.
To display the list of files stored using the long form in MPE format,
use the SHOW=LONG option. For example:
:FILE T;DEV=TAPE
:STORE @.PUB.TEST;*T;SHOW=LONG
Figure 6-4 illustrates a long file display from the above example.
_________________________________________________________________________________________________________
| |
| |
| FILENAME GROUP ACCOUNT VOLUME RESTRICTIONS SECTORS CODE MEDIA_NUM RSIZE BFCTR #EXT EOF LIMIT |
| |
| FILE1 .PUB .TEST DISC :C 1104 1 - 1 80 16 0 3500 3500 |
| FILE2 .PUB .TEST DISC :C 0 1 - 1 72 3 1 0 0 |
| FILE3 .PUB .TEST DISC :C 32 1 - 1 72 1 2 111 112 |
| |
_________________________________________________________________________________________________________
Figure 6-4. Long File Display (MPE Format)
Figure 6-5 illustrates the same example as above, except specifying
the filenames in HFS syntax:
_________________________________________________________________________________________________
| |
| |
| VOLUME RESTRICTIONS SECTORS CODE MEDIA_NUM RSIZE BFCTR #EXT EOF LIMIT FILENAME |
| |
| DISC :C 1104 1 - 1 80 16 0 3500 3500 /TEST/PUB/FILE1 |
| DISC :C 0 1 - 1 72 3 1 0 0 /TEST/PUB/FILE2 |
| DISC :C 32 1 - 1 72 1 2 111 112 /TEST/PUB/FILE3 |
| |
| |
_________________________________________________________________________________________________
Figure 6-5. Long File Display (HFS Format)
If you use the SHOW parameter, but do not specify either LONG or SHORT,
the system displays files in short form when the record size of the
output device or file (SYSLIST) contains fewer than 132 characters in
native mode and 114 characters in transport mode. The system displays
files in long form when the record size is equal to or greater than 132
characters in native mode and equal to or greater than 114 characters in
transport mode.
You can combine either LONG or SHORT with any of the other SHOW options,
except NAMESONLY, but you cannot specify both LONG and SHORT at the same
time within a STORE command.
Displaying File Dates.
To display each file's creation date, last access date, and last
modification date for the files stored, use the SHOW=DATES option. For
example:
:FILE T;DEV=TAPE
:STORE @.PUB.DOC;*T;SHOW=DATES
Figure 6-6 illustrates a file listing created from the above example.
_________________________________________________________________________
| |
| |
| FILENAME GROUP ACCOUNT VOLUME RESTRICTIONS SECTORS CODE MEDIA |
| CREATED ACCESSED MODIFIED |
| |
| FILE1 .PUB .TEST DISC :C 1104 1 |
| 1/12/1994 1/12/1994 1/12/1994 |
| |
| FILE2 .PUB .TEST DISC :C 0 1 |
| 1/12/1994 1/12/1994 1/12/1994 |
| |
| FILE3 .PUB .TEST DISC :C 32 1 |
| 1/12/1994 1/12/1994 1/12/1994 |
| |
_________________________________________________________________________
Figure 6-6. File Date Information (MPE Format)
When the output listing is in HFS format, an additional field is added to
the dates display. The STATE_CHANGE field indicates the last date that a
file attribute was changed. An example listing is:
Figure 6-7 illustrates a file listing created from the above example
in HFS format.
________________________________________________________________
| |
| |
| VOLUME RESTRICTIONS SECTORS CODE MEDIA FILENAME |
| CREATED ACCESSED MODIFIED STATE_CHANGE |
| |
| DISC :C 1104 1 /TEST/PUB/FILE1 |
| 1/12/1994 1/12/1994 1/12/1994 1/12/1994 |
| |
| DISC :C 0 1 /TEST/PUB/FILE2 |
| 1/12/1994 1/12/1994 1/12/1994 1/12/1994 |
| |
| DISC :C 32 1 /TEST/PUB/FILE3 |
| 1/12/1994 1/12/1994 1/12/1994 1/12/1994 |
| |
| |
________________________________________________________________
Figure 6-7. File Date Information (HFS Format)
Displaying File Security Information.
To display file security information for the files stored, use the
SHOW=SECURITY option. The listing includes the file creator's user and
account name, the security matrix, and a flag indicating the presence or
absence of an ACD. The HFS format displays the same security information.
For example:
:FILE T;DEV=TAPE
:STORE @.PUB.TEST;*T;SHOW=SECURITY
Figure 6-8 illustrates a file listing with security information from
the above example.
____________________________________________________________________________
| |
| |
| FILENAME GROUP ACCOUNT VOLUME RESTRICTIONS SECTORS CODE MEDIA |
| FILE1 .PUB .TEST DISC :C 1104 1 |
| LAURA .STSUPPNM (R:ANY; A:ANY; W:ANY; L:ANY; X:ANY) *ACD EXISTS* |
| |
| FILE2 .PUB .TEST DISC :C 0 1 |
| LAURA .STSUPPNM (R:ANY; A:ANY; W:ANY; L:ANY; X:ANY) *ACD ABSENT* |
| |
| FILE3 .PUB .TEST DISC :C 32 1 |
| LAURA .STSUPPNM (R:ANY; A:ANY; W:ANY; L:ANY; X:ANY) *ACD ABSENT* |
| |
____________________________________________________________________________
Figure 6-8. File Security Information
Displaying Names Only.
The SHOW=NAMESONLY allows an abbreviated listing to be displayed. The
only fields shown are the starting and ending media number, and the name
of the file. This option is most useful when displaying HFS syntax
files. Since they can be longer than MPE syntax names, it is sometimes
useful to allow more room on the line to display the full pathname.
NAMESONLY cannot be used with the SHORT or LONG options to SHOW. It has a
slightly different format for MPE and HFS. The HFS style has the filename
as the last field, while the MPE style has the filename as the first
field.
Figure 6-9 is an example for HFS format.
_________________________________________________
| |
| |
| MEDIA_NUM FILENAME |
| 1 - 1 /_HFSACCT/_HFSCRP/HFSMAP |
| 1 - 1 /usr/lib/terminfo/e/ethernet |
| 1 - 1 /usr/lib/terminfo/e/ex3000 |
| 1 - 1 /usr/lib/terminfo/e/exidy |
| 1 - 1 /usr/lib/terminfo/e/exidy2500 |
| |
_________________________________________________
Figure 6-9. Names Only Format
Forcing the HFS Format.
If SHOW=PATH is specified, the output STORE listing will be in HFS
format, even if no HFS syntax files are being stored. You may want to
use this so that all of your listings appear in the same format.
Displaying TurboSTORE/iX 7x24 True-Online Backup Information.
When creating backups using the ONLINE=START or ONLINE=END options of the
TurboSTORE/iX 7x24 True-Online Backup product, additional information is
shown in the STORE listing. This additional information is a single
character, immediately following the volume restrictions field. The
values and meanings for this character are as follows:
& After image file label data exists for this file,
since the file label was modified before the sync
point occurred. Only backups created with
ONLINE=END will have files with after image file
label data.
# After image data exists for this file, since the
file was modified before the sync point occurred.
Only backups created with ONLINE=END will have
after image file data.
+ This file was created during the backup, before the
sync point occurred. Only backups created with
ONLINE=END will have newly created files flagged
this way.
- This file was deleted or renamed out of this backup
before the sync point occurred. These files will
not be restored by RESTORE. Backups created with
ONLINE=START and ONLINE=END can have files flagged
this way.
An example of these flags follows. Note that FOO5 was modified during
the backup, FOO6's file label information was updated, FOO9 was removed
from the backup, and FOO1 was added to the backup.
_______________________________________________________________________________________
| |
| |
| FILENAME GROUP ACCOUNT VOLUME RESTRICTIONS SECTORS CODE MEDIA |
| FOO2 .PUB .MYACCNT MPEXL_SYSTEM_VOLUME_SET :S 16 1 |
| FOO3 .PUB .MYACCNT MPEXL_SYSTEM_VOLUME_SET :S 16 1 |
| FOO4 .PUB .MYACCNT MPEXL_SYSTEM_VOLUME_SET :S 32 1 |
| FOO5 .PUB .MYACCNT MPEXL_SYSTEM_VOLUME_SET :S# 16 1 |
| FOO6 .PUB .MYACCNT MPEXL_SYSTEM_VOLUME_SET :S& 16 1 |
| FOO7 .PUB .MYACCNT MPEXL_SYSTEM_VOLUME_SET :S 0 1 |
| FOO8 .PUB .MYACCNT DISC :C 32 1 |
| FOO9 .PUB .MYACCNT MPEXL_SYSTEM_VOLUME_SET :S- 0 1 |
| FOO1 .PUB .MYACCNT DISC :C+ 0 1 |
| |
_______________________________________________________________________________________
Selecting an Error Recovery Method (ONERROR)
When STORE encounters an error, it either automatically recovers or
terminates, depending upon the nature of the error and the error recovery
method you choose.
Unrecoverable Errors.
The following unrecoverable errors always cause STORE to terminate:
* A command syntax error.
* An error in the file system directory.
* An error opening a backup device or an indirect file. An indirect
file is a text file containing STORE commands and options. Refer
to "Using Indirect Files", in Chapter 5, "Storing Files".
Disk Read Errors.
If STORE encounters a disk read error while storing a file, it skips the
remainder of that file and sends an error message to the standard listing
device describing the offset from the start of the file and the number of
bytes that have been lost. STORE then continues to copy the remainder of
the files. The STORE operation does not terminate. Since the files that
contain disk errors are not stored, you will not be able to restore them.
Media Errors.
When a media error occurs while writing to a output device, the behavior
of STORE depends on the value of the ONERROR option, as explained below.
Tape Error Recovery.
The STORE command's ONERROR parameter lets you specify a backup error
recovery procedure. Your options are ONERROR=QUIT and ONERROR=REDO. REDO
is the default. QUIT instructs STORE to abort upon encountering a backup
I/O error while REDO instructs STORE to continue after encountering an
I/O error.
If you specify REDO and the STORE command encounters a backup I/O error
on any device, STORE sends a message to your terminal (or the file or
device to which you have assigned the file SYSLIST). This message
indicates where the error occurred. For example, STORESET=(*T1,*T2,*T3)
is requested and a backup error occurs on the device referenced by *T2
while it is creating reel 2. STORE rewinds the reel to the load point,
marks the reel as bad, and asks you to mount another reel. After you
mount the new reel, STORE automatically stores all the files from the
point where the bad reel began.
The message is similar to the following:
* The user sees:
STORE ENCOUNTERED MEDIA WRITE ERROR ON LDEV #
where LDEV # is the device referenced by *T2. This means that the
store error recovery occurs on the same device where the error
occurred.
* The operator sees the following messages on the console:
STORE IS MARKING REEL BAD ON LDEV #
MOUNT MEDIA # OF SET # FOR STORE ON LDEV #
Optical Disk Errors.
If an optical disk write error is encountered, STORE displays the same
error messages that it would display for tape backup devices.
You can determine which piece of media is has been marked bad by using
the STATUS command of the MOUTIL program. The status display indicates
which piece of media is bad by showing "THE MEDIA IS BAD" in the media
name field. If a disk write error occurs while storing to a disk file,
STORE aborts, irrespective of what ONERROR option was specified.
Bad Media.
Once a piece of media has been marked bad, it should not be used for
future STORE operations. If a media that has been marked bad is mounted
for use in a STORE operation, STORE will issue the following message to
the console:
MEDIA ON LDEV # IS BAD. CONTINUE ANYWAY?(Y/N)
If you reply YES, then STORE will write over this media. If you reply
NO, the media will be unloaded, and you should mount another piece of
media.
NOTE STORE will not check to see if a piece of media has been marked bad
if it is the very first reel mounted. Therefore, it is important
that once a reel has been marked bad by store, some note is made on
the physical label of the media to indicate that it encountered a
write error while storing to it.
Specifying Files by Date (DATE)
The DATE option specifies which files are stored based on two
possibilities:
* STORE files that have been modified since a specified date
* STORE files that have not been accessed since a specified date
Storing Files Modified Since a Specified Date.
You can use the DATE parameter to store only files that were modified or
their states were changed since a specified date. (The state change date
and time are updated any time the file is renamed or an ACD is changed.
However, this information is not automatically shown. The state change
date and time can be different from the last modified date displayed with
the LISTFILE filename,3 command. See the note below for information on
displaying the state changes.)
The DATE parameter enables you to do, among other things, a partial
system backup. For example, suppose a full system backup was performed
on September 30, 1993. The following STORE command would copy all system
and user files modified since that date:
:FILE T;DEV=TAPE
:STORE @.@.@;*T;DATE>=09/30/93
The date must be entered in either the above format (mm/dd/yy) or as
mm/dd/yyyy (for example, 09/30/1993). The files stored include any
modified on the same date as the date entered. The files stored also
include those modified since the specified date on nonsystem volume sets
that are online.
Use this form of the DATE parameter when you perform regular backups of a
fileset. Store the entire set, for example, once a week and store only
those files that were modified or their states were changed since the
full backup the remaining six days.
NOTE STORE uses the state change date when storing files with the
DATE parameter. To see the state change date, use the
FINFO(filename,42) and FINFO(filename,41) functions.
The following command file displays the state change date and time
for a specific file, such as TSETUTIL in this example:
_______________________________________________________________________________________
| |
| |
| parm file |
| setvar state_change 'STATE CHANGE = '+finfo('!file',42)+', '+finfo('!file',41) |
| echo !state_change |
| deletevar state_change |
| Example: |
| |
| (77)>chdate TSETUTIL |
| STATE CHANGE = TUE, OCT 31, 1995, 3:49 PM |
| (78)> |
| |
_______________________________________________________________________________________
Storing Files Not Accessed Since a Specified Date.
You can also use the DATE parameter to store only files that have not
been accessed since a certain date. For example:
:FILE T;DEV=TAPE
:STORE @.OPERATOR.SYS;*T;DATE<=06/10/93
The year can be entered as two digits or four digits (93 or 1993). The
above command stores any files in the OPERATOR group of the SYS account
that have not been accessed since June 10, 1993. You may want to use
this form of the DATE parameter with the PURGE parameter to remove
out-of-date files from your system. Refer to the next section.
Removing Stored Files from the System: Archiving Files (PURGE)
If your system contains infrequently used or out-of-date files, you can
store them onto backup and permanently remove them from the system disks
at the same time. This process, called archiving files, increases
available space and provides a backup copy of the files in case you need
them in the future. To store disk files and then delete the disk files
in a single operation, use the PURGE parameter of the STORE command. For
example:
:FILE T;DEV=TAPE
:STORE @.OLD.ACCTG;*T;PURGE
The command above stores all files in the OLD group of the account ACCTG
and deletes the files from disk. PURGE deletes the files only after it
has successfully stored all of them. Thus, if STORE terminates in the
middle of the process, it does not purge any files.
You can combine the DATE and PURGE parameters to periodically archive
unused files. For example, the following STORE command stores to backup
all files in the EMPRECS group of the PERSONEL account that have not been
accessed since February 2, 1992 and then deletes the disk files:
;FILE T;DEV=TAPE
:STORE @.EMPRECS.PERSONEL;*T;DATE<=02/02/92;PURGE
NOTE In order to use the PURGE parameter with a privileged file or
files, you must have system manager (SM), system supervisor (OP),
or privileged mode (PM) capability.
You may want to warn users before you archive files and inform them how
to request to have archived files restored. If you need to restore
purged files to the system, you can find them on the piece of media to
which you stored them and on the media from the last full system backup
you performed before you purged the files.
Displaying Progress Messages (PROGRESS)
Use the PROGRESS parameter to display STORE command progress messages at
regular intervals. For example, to display progress messages every five
minutes, use the following command:
:FILE T;DEV=TAPE
:STORE @.@.@;*T;PROGRESS=5
If you use the PROGRESS parameter alone, without specifying an interval,
STORE displays status messages every minute.
If STORE is being run from a MPE session, the progress messages will be
send to the standard list ($STDLIST). Otherwise, the messages will go to
the system console.
System Directory Backup (DIRECTORY)
The system directory keeps track of the accounts, groups, users, and
files in your system. Nonsystem volume set directories keep track of the
contents of nonsystem volumes. Directory information can be stored when
you back up system or nonsystem volumes. Storing directory information
helps you rebuild your system from backups should it unexpectedly lose
information. To store system directory information, use the DIRECTORY
parameter. All HFS directories on the system are also stored.
The following example will store all files on the system, plus the system
volume set accounting information.
:FILE T;DEV=TAPE
:STORE @.@.@;*T;DIRECTORY
To store nonsystem volume set directory information, use DIRECTORY and
ONVS in the same command. For example:
:FILE T;DEV=TAPE
:STORE @.@.@;*T;ONVS=VOL_SET_A;DIRECTORY
In the above example, the ONVS parameter will limit @.@.@ to only files
that reside on the specified volume sets. Only the directory information
for groups and accounts on the specified volume sets will be stored. The
system directory information will NOT be stored. See "Storing Files From
Volume Sets" in this chapter for more information.
As illustrated above, the DIRECTORY parameter of the STORE command allows
you to back up the system and/or nonsystem volume set directories
(account structure). You may then reload the account structure in the
event of a system disaster by restoring the directory onto the system
from the backup media. You have the added flexibility of backing up the
directories of nonsystem volumes attached to the system as a part of or
as a separate entity from the system. This allows a nonsystem volume
(volume set) to become a separate reliable entity. System supervisor
(OP) or system manager (SM) capability is required to use the DIRECTORY
parameter.
NOTE When using the DIRECTORY parameter, the default fileset list is
empty. This allows a backup to be created that contains only
directory accounting information for the system volume set, or for
the specified volume sets.
Here is an example of how to back up the system directory and all other
files along with a nonsystem volume set directory and its files:
:FILE T;DEV=TAPE
:STORE @.@.@;*T;DIRECTORY;ONVS=MPEXL_SYSTEM_VOLUME_SET,NV1
where NV1 is the name of a nonsystem volume set.