FTAM/9000 Programmer's Guide

340 Chapter 9
Handling Errors
Interpreting Errors
HP-UX-Specific Errors
Errors detected by the interface, an ftam_init, or an FTAM responder
may contain HP-UX FTAM implementation-specific error information
that is returned to the user program. The vendor_code contains both
HP-UX—specific error information (lower 16 bits) and the log instance
(upper 16 bits).
• The inout_dcb->result.vendor_code contains the vendor errors;
however, not all errors returning in inout_dcb->result have an
accompanying vendor_code.
• To receive a printable character string and a log instance, call
ft_gperror().
• The vendor_code frequently provides additional information when
errors return on HLCF functions.
Many vendor_codes indicate internal errors that require HP support
assistance. Refer first, however, to the HP FTAM/9000 Reference
Manual for a list of HP-UX—specific errors and possible corrective
actions.
Synchronous
Calls
• The MAP 3.0 FTAM result.return_code is
always the same as the function return value.
• If result.return_code is SUCCESS, the
request successfully passed to the application
interface, ftam_init, and responder, and
returned back to the user program.
Asynchronous
Calls
• If result.return_code indicates an error, the
application interface, ftam_init, or responder
detected the error.
• The em_wait() function returns a value for a
specific event. If an error occurs in ftam_init
or the responder, the function return value of
em_wait() indicates SUCCESS and the
result.return_code of the original function
identifies the error.
• The inout_dcb pointer and structure are not
valid until the em_wait() request returns
successfully. If you do not call em_wait(), you
will not know if the request completed.