The UPDATE-DATABASE statement can be used to apply AFIMs from ALOG files to realms and thus update them.
The required realms, which represent an older status of the database, must be first copied, read in from ARCHIVE backups, or recataloged and made available.
Detached realms can also be processed if BMEND is run in parallel with the DBH.
Inconsistent realms must be made consistent with the UPDATE-DATABASE statement before they are attached or detached.
UPDATE-DATABASE | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||
REALM-NAME = *ALL
All realms are updated.
REALM-NAME = *ALL-EXCEPT(...)
All realms except for those specified are updated.
NAME = list-poss(30): <realm-name>
Name of the realm that is not to be updated.
REALM-NAME = list-poss(30): <realm-name>
All specified realms are updated.
DEADLINE = *STD
The database is updated to the end of the last ALOG file closed. A consistency point recorded in an ALOG file that is not closed yet cannot be reached with DEADLINE = *STD.
DEADLINE = *BREAK-POINT
All consistent ALOG files, including the last, current, and possibly inconsistent ALOG file are used for the update. This allows an update up until the point at which failure occurred. If the last ALOG file is inconsistent, a warm start of the database is required afterwards.Realms of the shadow database are only updated with closed ALOG files.
DEADLINE = <alog-seq-no>
Sequence number of the ALOG file up to and including which AFIMs are to be applied.Only closed ALOG files are used for the update (leading zeros in the alog-seq-no may be omitted in the specification.)
DEADLINE = *TIME-STAMP(...)
Updates are applied to the database up to and including the last closed ALOG file for which the LOG_INTERVAL_END is less than or equal to the given *TIME-STAMP(...).
DATE = <date>
Date that limits the applied updates.
TIME = <time>
Time that limits the applied updates. If the time is not unique, daylight saving time (summer time) is assumed, and a warning is issued.
DELETE = *NO
The applied ALOG files are retained on disk.
DELETE = *YES
With the exception of the current file, all applied ALOG files (i.e. the files read in for the update) are automatically deleted, assuming that no error has occurred when executing this statement.
The DBDIR and the DBCOM are treated like any other realm. The realm DBCOM is implicitly addressed by the *ALL and *ALL-EXCEPT options.
If all the realms specified using the REALM-NAME operand are not available, the missing realms are not processed. Furthermore, no deletion of the ALOG file takes place even if requested.
The DEADLINE = *BREAK-POINT operand is meaningless for shadow databases. *BREAK-POINT is treated as *STD in such cases.
The sequence number of the next ALOG file required to reach the desired DEADLINE is saved in a job variable after each individual ALOG file has been applied (see the section on “Supplying job variables” on "Supplying the BMEND job variable").
If a logging gap is contained in the sequence of ALOG files to be applied, the update is terminated at that point.
A warning is issued if the DEADLINE (specified as an alog-seq-no or *TIME-STAMP(...)) could not be reached.
A realm other than the DBDIR can only be updated if it was addressed in the update session or matches the DBDIR, which is also being updated.
Statistics and summary report
On completion of the BMEND run, internal counters are evaluated and output for the SUMMARY REPORT:
| |
|
|
| |