TurboIMAGE/XL Database Management System Reference Manual MPE/iX V6.5 (30391-90011)

Chapter 8 407
Using the Database Utilities
DBSTORE
parameter (INFO="TRANSPORT") allows you to migrate
files from MPE/iX to MPE V with the MPE/iX STORE
command.
Operation Discussion
1 The optional file equation that specifies the device class name for the
device on which the database is to be stored, the record size of the records
written to the device, and whether records are to be buffered. The default
device class is TAPE.
2 Initiates execution of the DBSTORE program in the PUB group of the SYS
account. The MPE
STORE options are parameters that can be passed to the
STORE/RESTORE process. For example, the TRANSPORT option is used
when moving a TurboIMAGE/XL database to MPE V.
Note that the database may be too large to move to MPE V because, with
the expanded file size available on MPE/iX, data sets can exceed the MPE
V file size limit. If the database contains a data set larger than the MPE V
limit, an MPE error is displayed.
3 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.
4 After DBSTORE has copied the root file and all data sets, it prints a
message to signal completion.
NOTE 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.
Logging
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