OSI/FTAM Programming Guide

NonStop FTAM Programming
HP NonStop OSI/FTAM Programming Guide—528612-001
3-39
Error-Handling Concepts
of the structure containing the desired field, ZDOCTYPE; on line 17, the name of the
field in ZDOCTYPE, ZDOCTYPENAME; and on lines 19 and 20, the names of the
subfields defining ZDOCTYPENAME, ZNUM^ELEMENTS, and ZOBJ^ID.
Therefore, to set up the document type name for an FTAM-3 file, use these lines of
TAL code:
contents_type.zdoctype.zdoctypename.znum^elements := 5;
contents_type.zdoctype.zdoctypename.zobj^id [0] := 1;
contents_type.zdoctype.zdoctypename.zobj^id [1] := 0;
contents_type.zdoctype.zdoctypename.zobj^id [2] := 8571;
contents_type.zdoctype.zdoctypename.zobj^id [3] := 5;
contents_type.zdoctype.zdoctypename.zobj^id [4] := 3;
Error-Handling Concepts
NonStop FTAM returns four classes of errors:
•
API errors
•
FTAM initiator errors
•
ISO diagnostic messages, generated mostly by the remote responder
•
Diagnostic errors defined by NonStop—that is, the subset of ISO diagnostic
messages that the NonStop initiator can generate
This subsection describes these four classes of NonStop FTAM errors, provides
diagrams explaining FTAM error handling, and ends by orienting you to further error
information in this manual and elsewhere.
API Errors
A procedure sometimes encounters syntactic, semantic, or operational problems
because of inappropriately specified procedure parameters, resource insufficiencies,
and so on. If this happens, the FTAM API returns an error, discontinues processing the
procedure call, and forwards no message to the initiator. API errors can be returned in
the error return code of confirm and indication procedures and in the error-code
output parameter of the APS_STATUS_ procedure that you call after a bad status
value is returned by a request or response procedure. For a list of the possible errors,
see the OSI/FTAM Programming Reference Manual.
NonStop FTAM Initiator Errors
FTAM initiator errors are locally generated. The initiator provides validation of
parameter values, eliminating the need to test across the network for procedure call
errors. Many errors generated at the initiator are FTAM protocol errors such as calling
a procedure out of sequence (as determined by the regimes) or providing an
inappropriate parameter value.