OSI/FTAM Programming Reference Manual

NonStop FTAM Initiator Error Messages
HP NonStop OSI/FTAM Programming Reference Manual528611-001
B-2
Status Codes
see the “Errors” subsections in the individual procedure descriptions in Section 4, FTM
Procedures. For information about MFM and APS procedures, refer to Appendix E,
MFM Procedures and Appendix F, APS Procedures, respectively.
For the data structures related to error messages, see the following entries in
Appendix A, DDL Definitions:
ZAPS-DDL-CURRENT-ERROR
ZAPS-DDL-DIAG-BUF
ZAPS-DDL-ERROR-CODE
ZAPS-DDL-FILENAME
ZAPS-DDL-ORIGINAL-ERROR
ZAPS-DDL-SERVICE-ID
ZFTM-DDL-DIAGNOSTIC
Status Codes
In general, the status codes returned by the FTM and APS procedures and by
MFM_AWAITIOX_ indicate the success or failure of a procedure call. If a procedure
call fails, the status code indicates the recommended recovery action. This code can
inform you, for example, to wait until later to retry an operation or not to retry the
operation at all. Treat the recovery actions listed in this section as recommendations,
not as strict rules.
The special status code value ZAPS-VAL-STATUS-EVENT indicates that an event has
been received. This code is returned only on the completion of the
APS_EVENT_RECEIVE_ procedure call.
Table B-1 summarizes the most common status code values you can receive
programmatically. The name of each value starts with ZAPS-VAL-STATUS-. More
detailed descriptions of the values follow the table, listed in numeric order by status
code. For a list of all possible status codes that can be either returned
programmatically or observed in traces, see the OSI/FTAM Programming Guide
.
Table B-1. Status Code Values
Constant
(ZAPS-VAL-STATUS-) Code Meaning
OK 0 Operation succeeded.
EVENT 1 Event received; call APS_STATUS_ to determine
which event.
NO-RETRY 2 Operation failed; don’t retry.
RETRY-LATER 4 Operation failed; retry after a delay.
DISCARD 7 Operation failed; status unknown; discard association.