In the event of abnormal termination, a DBEnvironment may be
left with DBEFiles open or with locks still in place for
specific pages. ALLBASE/SQL provides a monitor process
that regularly checks for abnormal termination and
cleans up in such cases. If you have trouble re-connecting
to a DBEnvironment, wait a few seconds for the monitor to
do its work, then try again.
The monitor process starts
automatically the first time a user connects to a DBEnvironment.
Whenever cleanup occurs, messages describing the actions
taken by the monitor are sent to the console.
When a multiuser DBCore session terminates abnormally, ALLBASE/SQL creates
two files containing information about the error condition.
These files can be useful when support engineers debug the problem.
The files are created in the same group and account as
the DBECon file. If this cannot be done for security
reasons, they are created in the user's current group and account.
The files are as follows:
where xxxx is a unique name chosen by the system.
DBDC0000 through DBDC9999 and
DBDS0000 through DBDS9999
should be considered reserved filenames.
You can use an ordinary PRINT command to view file DBDSxxxx.
In order to view file DBDCxxxx, use the special utility program
CBFORMAT.PUB.SYS. After prompting for a file name, CBFORMAT opens
the privileged file, formats each record in hexadecimal and ASCII, and
prints the formatted records on the standard output.
After displaying the formatted records, CBFORMAT asks whether you
wish to delete the file:
Purge this file: (YES,NO)
|
Respond YES to purge the file.
DBDCxxxx and DBDSxxxx files can accumulate if you do not format and purge them
periodically.
