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.
Operational considerations for when the database prohibits authorization
The NOAUTH keyword specifies the action that the Reorg function takes if the database status in DBRC prohibits authorization.
This situation occurs if you have issued a DBRC command like CHANGE.DB DBD(dbdName) NOAUTH.
If you intend to block DBRC authorization for everything except the reorganization by issuing the CHANGE.DB DBD(dbdName) NOAUTH command, use NOAUTH(RUN). The authorization process for the Reorg function ignores the DBRC NOAUTH flag that you set.
If an error occurs during data set name swapping or if the DBD definition changes during the reorganization (OLDDBD keyword) and you specified SWAP(YES) or SWAP(D), the Reorg function sets the DBRC NOAUTH flag.
