Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
DBR commands
The Online Reorg function enables you to reorganize a database and leave it available online to applications.
Online Reorg must have exclusive access to the database for a short time at the beginning and end of the reorganization. While Online Reorg has exclusive control, it quiesces and starts the database that is being reorganized.
When you submit the reorganization job, Online Reorg uses its AOI to issue an IMS /BMCPAU or /DBR DB dbdName NOFEOV command to clear all buffers and quiesce the database. At this point, the database is in recording mode and Online Reorg issues a /STA command to get the database back online and to release any suspended transactions. The database is reopened, DBRC authorization is granted, Online Reorg prepares to record the updates, and the reorganization begins. The entire process should take only a few seconds.
When the reorganization is complete and an image copy has been taken, Online Reorg uses a batch job to apply the changes to the reorganized (shadow) database. This is a standard batch update job, and it creates a standard batch log. In most standard batch jobs, a /DBR must occur before a batch update job can begin. After the job is complete, a /STA command is issued to start the database. Between the /DBR and the /STA, the batch update job has exclusive control of the database. This is also true for the Online Reorg function.
In general, when a /DBR is issued, the OLDS are switched. Online Reorg allows you to not switch the logs when the /DBR is issued (see DBR). Online Reorg issues an /SWI OLDS command before starting the databases.
