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

Chapter 8 391
Using the Database Utilities
>CONTROL
>CONTROL NOSTAMP
>CONTROL STAMP
In both cases, the STAMP condition cancels the previous NOSTAMP. Recovery proceeds
with the time stamp check intact.
If additional databases are specified for simultaneous recovery, they are all governed by
the same >CONTROL options.
In the specifications below, default options are shown in brackets [ ]. The default conditions
for STOPTIME, ERRORS, and EOF are included with their descriptions.
Parameters
[STAMP] is the time stamp in the database root file. It is compared with the time
stamp in each DBOPEN log record in the log file. If the time stamps do not
match, DBRECOV returns an error message, and terminates recovery for
the offending database.
NOSTAMP disables the check of the database and log file time stamps. Allows
recovery to proceed regardless of the database and log file time stamps.
[STORE] is the DBSTORE flag in the database root file and is checked to ensure that
the database has not been modified between restoration and recovery. If
the flag has been cleared, the >RECOVER command fails. The DBSTORE flag
is set only when the database is stored using DBSTORE. It is cleared when
the database is accessed by DBDELETE, DBPUT, or DBUPDATE.
NOSTORE disables the check of the DBSTORE flag. Allows recovery to proceed whether
or not the DBSTORE flag is set. Useful when the database has been stored
by the MPE/iX STORE command rather than DBSTORE. Storing the
database using the STORE command does not set the DBSTORE flag, and is
not recommended.
[ABORTS] when transactions do not complete due to a program abort,
TurboIMAGE/XL appends an abnormal DBEND (DBABEND) to the log file
and considers the transactions completed. This enables DBRECOV to
recover these transactions and thereby avoids suppressing all subsequent
dependent transactions.
NOABORTS causes DBRECOV to suppress transactions not originally completed by user
programs. This option tells TurboIMAGE/XL a user or program abort is
abnormal, or incomplete. NOABORTS should only be used if all database
modifications were stopped immediately after the abort and recovery was
initiated. Otherwise, recovery can fail due to record file overflow (see
below). For more information on both ABORTS and NOABORTS refer to
chapter 7.
[NOUNEND] causes DBRECOV to suppress incomplete transactions. Recovery can fail
due to a record file overflow (see "Record Numbers" later in this section).
UNEND prevents DBRECOV from suppressing incomplete transactions.