User`s guide

1-61
1 to 199
13: The MicroKernel could not open the extension file for
an extended file
The MicroKernel could not open the extension file for an extended
file that the application tried to open. An extended file can consist of
a base file and up to 31 extension files. Extension files must remain
in the same volume and directory as their base files. The MicroKernel
returns this status code if you delete, move, or rename the extension
files.
14: The MicroKernel cannot create or open the pre-image
file
The MicroKernel uses pre-image files only for pre-v6.0 data files.
The MicroKernel returns this status code in one of the following
situations:
 The MicroKernel cannot create a new pre-image file because the
disk directory is full. The MicroKernel must be able to create a
pre-image file.
 The MicroKernel cannot open the pre-image file to restore file
integrity. If the pre-image file is erased or damaged, the
MicroKernel cannot restore the file integrity. Refer to Advanced
Operations Guide for more information about recovering
damaged files.
 The workstation MicroKernel cannot assign a handle to the pre-
image file because the MicroKernel was not started by a user
with access rights to the pre-image file.
 The file structure of a pre-image file created by this MicroKernel
is different from the file structure of a pre-image file created by a
v5.x MicroKernel. If you have an extraneous .PRE file in v5.x
format, the MicroKernel returns this status code when you try to
open the data file to which the .PRE file belongs.
15: The application encountered an I/O error during pre-
imaging
The MicroKernel uses pre-image files only for pre-v6.0 data files.
 The pre-image file is damaged and the integrity of the data file
cannot be ensured. Refer to Advanced Operations Guide for more
information about recovering damaged files.
 The disk is full. Erase any unnecessary files.