User`s guide

2-22
Messages
loading, the loading fails and no operations are possible until the
problem is corrected. If the error occurs later, during normal
operations, there are some additional issues to consider.
If the MicroKernel is already loaded when an error occurs creating
the transaction log file, it ceases transaction logging; however, the
MicroKernel attempts to resume transaction logging after every
update to a data file containing system data. Therefore, when the
condition causing the error is corrected (for example, when more
disk space is made available), the MicroKernel automatically
resumes transaction logging.
MKDE-75: The log file format is invalid
The MicroKernel returns this message when the log segment file
format is incompatible. Ensure that the version of the MicroKernel
doing the roll forward is the same as the version of the MicroKernel
that created the log file.
MKDE-76: An Open operation failed on “xxxx” with MKDE
error nn
The MicroKernel returns this message during roll forward
operations when a MKDE error occurs. The MicroKernel returns the
specified status code for the specified file. Refer to Chapter 1, Status
Codes for a description of Status Code nn.
MKDE-77: An unexpected MKDE error nn occurred on
INSERT to “xxxx”
The MicroKernel returns this message during roll forward
operations when an Insert error occurs. The MicroKernel returns the
specified status code for the specified file. Refer to Chapter 1, Status
Codes for a description of Status Code nn.
MKDE-78: An unexpected MKDE error nn occurred on
UPDATE in “xxxx”
The MicroKernel returns this message during roll forward
operations when an Update error occurs. The MicroKernel returns
the specified status code for the specified file. Refer to Chapter 1,
Status Codes for a description of Status Code nn.