FTAM/9000 Programmer's Guide

336 Chapter 9

Handling Errors

General Approach to Troubleshooting FTAM

General Approach to Troubleshooting

FTAM

To write a supportable program, you must check for errors. If you receive

an error, use the following guidelines and Figure 9-1 to help you resolve

the problem.

1. Check all error codes (return_codes, vendor_codes, diagnostics). The

“Interpreting Errors” section describes the values you interpret.

2. Use ft_gperror() to format errors into printable character strings and

to obtain log instances.

3. Correct the errors as indicated by these values. If needed, look up the

error code in the HP FTAM/9000 Reference Manual to determine

probable causes and corrective actions.

4. If the error still occurs, check the log ﬁle (described in the “Logging

Errors” section) for error information, such as error codes, program

status, and log instance. If you do not have a log instance, ﬁnd the

logged error by searching on the error string in the log ﬁle and by

searching on the relative time when the error occurred.

5. If the error still occurs, record the following error information and

refer to the OSI Planning and Troubleshooting Guide for corrective

actions.

• Speciﬁc function call that failed

• Input parameters passed to the function

• Function return value

• inout_dcb->result.return_code

• inout_dcb->result.vendor_code

• inout_dcb->diagnostic

• return_string returned by ft_gperror()

• vendor_string returned by ft_gperror()

• Log instance (upper 16 bits of the vendor_code)