HP FTAM/9000 Reference Manual page 79

MESSAGE
5023
CAUSE
ACTION
MESSAGE
5024
CAUSE
ACTION
MESSAGE
5026
CAUSE
ACTION
Chapter 3
F_PROC_MD_INCONSISTENT
The bits set for the processing_mode FT_FA_XXX
defined constants are not a subset of the bits set for
the requested_access FT_PA_XXX defined
constants.
Correctly set the FT_FA_XXX bits or call ft_open()
with a valid processing_mode. The processing_mode
must be a subset of the requested_access values on
ft_select() or ft_create().
F_ACCESS_CNTXT_NOT_AVAIL
The access_context is not available. Given a
particular document type, a VFS implementation
may not support certain access_contexts.
EXAMPLE: You tried accessing an FTAM-2 file
with an access_context of HA (Hierarchical All).
Use an access_context value that is consistent with
the file document type.
F_BAD_WRITE
On an ft_write() function, the Ft_fadu_location in
Ft_fadu_identity points to a non-existent FADU;
therefore, you cannot write to the file (FTAM-1,
FTAM-3, and INTAP-1) or FADU (FTAM-2).
Call ft_sdata() with a valid fadu_identity. For
FTAM-1, FTAM-3, and INTAP-1 document types,
fadu_identity must be FT_FIRST. For FTAM-2
document types, fadu_identity must be FT_BEGIN.
Diagnostic error_ids
inout_dcb->diagnostic->error_id
79