Stores the database root file and all data sets to a tape in a format
compatible with backup files created by the MPE STORE and SYSGEN commands.
DBSTORE differs from these commands in that it handles only
 TurboIMAGE/XL databases.


     [:FILE DBSTORE [=filename] [;DEV=device] [;REC=recsize] [; {BUF | NOBUF}] ]
WHICH DATABASE? database_name [/maint_word]


filename        filenameis the name (up to 8 characters) that replaces
 DBSTORE in the mount request at the operator's console.

device is the device class name of the device on which the
 data entries are to be stored.

recsize is the record size of the record to be written to the device;
 must be a multiple of 512 bytes and less than the configured
record size for the device.

database_name is the name of the TurboIMAGE/XL database to be stored.

maint_word is the maintenance word defined by the database creator.
 This word must be supplied by anyone other than the database creator.

INFO= is used for the parameters that can be passed to the
 MPE STORE/RESTORE process. For example, the TRANSPORT parameter
 ( INFO="TRANSPORT") allows you to migrate files from MPE/iX to
 MPE V with the MPE/iX STORE command.

The file equation is optional and specifies the device class name for the device
to which the database is to be stored. The default is device class TAPE.


If you try to store a database that needs recovery, DBSTORE will do the
recovery before storing the database.

Before copying the files, DBSTORE gains semi-exclusive access to the
referenced database; that is, DBSTORE determines that the only other
database activity consists of other users executing DBSTORE or application
programs that open the database in mode 6 or 8. If DBSTORE cannot gain
semiexclusive access, it terminates and prints the following message:


You must be the database creator or provide the maintenance word to use DBSTORE.

In session mode, DBSTORE prompts for the database name and maintenance word.

In job mode, the database name and maintenance word, if any, must be in the
record immediately following the RUN command.

After DBSTORE has copied the root file and all data sets, it prints a message
to signal completion.


DBSTORE does not store jumbo data sets or B-Tree index files. Instead, use
the STORE command with POSIX names or use TurboSTORE/iX 7x24 True-Online
Backup with ONLINE=START or ONLINE=END option.


DBSTORE updates a time stamp and store flag in the database root file before
storing the database. The time stamp designates the date and time of the
DBSTORE operation, and is used by DBRECOV to help identify the correspondence
between log files and backup databases.

The store flag is set by DBSTORE to indicate that the database has been stored;
this flag is cleared (reset) when the first modification to the database occurs
by a call to DBPUT, DBUPDATE, or DBDELETE. Both DBRECOV and DBUTIL interrogate
the status of the DBSTORE flag. DBRECOV (roll-forward) checks this flag to
ensure that no one has modified the backup database prior to recovery.
DBUTIL checks this flag whenever logging and recovery is enabled, because a
valid database backup copy must exist for roll-forward recovery to be possible.
If the store flag is not set when a DBUTIL user enables the logging option a
warning is printed:

WARNING: database modified and not DBSTORED

This warning does not necessarily indicate that a valid backup does not exist,
because either an MPE SYSGEN or STORE command could have been used instead of
DBSTORE. Because neither SYSGEN or STORE update the database time stamp and
store flag, the protection afforded by these mechanisms is not available if
this form of backup is selected. For this reason, it is highly recommended
to use DBSTORE as the backup facility when logging.

If the mirror database maintenance method is being used, storing the database
on the secondary system can be done differently than using the DBSTORE process.
When using DBRECOV STOP-RESTART recovery on the database, storing the database,
RESTART file, and the log files that were processed since the last successful
RESTART can be done with an MPE STORE command. DBRECOV STOP-RESTART places a
time stamp in the RESTART file and in the database to identify which RESTART
file to apply to which database. If naming conventions have been followed,
an MPE STORE @ command can be used to store all the necessary files and
database(s). If DBSTORE is used, the user must remember to use an MPE STORE
command to store the RESTART file and the log files.

Console Messages

After you supply the database name and DBSTORE opens the output file,
a message is displayed on the system console. A tape must be mounted
on the appropriate unit and identified through an operator reply. Refer
to the Volume Management Reference Manual for instructions about console interaction.

If more than one volume is required to store the database, a request is
displayed on the console for the next one. The next tape must be mounted
and the unit readied. The volume that has been removed should be properly
labeled with the database name and volume number.


   :JOB MGR.ACCOUNTA      Initiate job.
ORDERS/SELL Supply database name and maintenance word.
:EOJ Terminate job.

After copying the ORDERS root file and all data sets, DBSTORE prints the
following message on $STDLIST:



If you need to cancel a DBSTORE, reply zero to the tape request:

:REPLY pin#,0

Do not use Break and ABORT to abort the process when the tape mount is requested.
When DBSTORE is aborted by using Break and ABORT, the date-time stamp and store
flag in the root file are updated even though the database was not stored.

TurboSTORE/iX 7x24 True-Online Backup

You can also use TurboSTORE/iX 7x24 True-Online Backup to back up your database.
The advantages of using the option ONLINE=START or ONLINE=END are:

You can store the database even when it is open for access.

The related files including TC file, third-party indexing files, jumbo data set
files, and B-Tree index files are also stored along with it.

The DBSTORE flag and time stamp are also set before storing the database.

You can restore it using the MPE RESTORE command.

If the database is enabled for roll-forward logging, DBRECOV can recover the database.

You can store multiple databases with one command.

For more information, refer to the STORE and TurboSTORE/iX Products Manual.