Where the database resides on the machine from which you are running the database integrity check, run the utility with the −LOCAL command tail to improve performance.
From release 4.621 DBCHECK automatically determines whether the database to be checked is local or not by examining the network status table. The −LOCAL option will be selected automatically unless the resil_type field indicates that databases are remote. You can still use −LOCAL to force local file handling to be invoked even where the database should be remote, and you can use -REMOTE to force the database to be treated as though it were remote.
Under FlexOS 2.x, use DBCHECK.280, by copying it to DBCHECK.286, rather than the supplied dbcheck.286 because it loads the terminal manager as an overlay rather than a separate process and will considerably improve performance.
On the DP4 System menu, select the Run program option, and type the command:
DBCHECK −LOCAL
and press <Enter> to execute it.