OSI/FTAM Programming Reference Manual

NonStop FTAM Programming Examples
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
G-2
Example Structure and Protocol
Appendix A, DDL Definitions lists and defines the DDL structures used by the FTM
procedures. DDL structures are punctuated with hyphens (-) while structures in C code
are punctuated with underscores ( _ ), and in TAL code, with circumflexes ( ^ ).
Structure names in C and TAL end with “_def” and “^DEF,” respectively. For
descriptions of the information contained in the FTAM structures used in the
programming examples, see the corresponding DDL structures in Appendix A, DDL
Definitions.
For information about error codes and subcodes returned on FTAM procedures, refer
to Appendix B, NonStop FTAM Initiator Error Messages. Section 4, FTM Procedures
lists errors returned on specific procedure calls and indicates what some of them mean
in the context of that call. The OSI/FTAM Programming Guide describes how to handle
errors returned in applications on FTM procedure calls.
This appendix also includes diagrams of the primitive sequences used in the two
programming examples.
Example Structure and Protocol
This subsection provides protocol diagrams for the four programming examples that
follow. Example 1 updates a remote FTAM-2 file in nowait mode. The example is
provided in two versions:
•
EXCINSF2 written in the C programming language (for details, refer to page G-12);
•
EXTINSF2 written in the TAL programming language (for details, refer to page
G-56
).
Example 2 moves an FTAM-3 file between two remote systems in wait mode. The
example is also provided in two versions:
•
EXCMOVF3 written in the C programming language (for details, refer to page
G-106);
•
EXTMOVF3 written in the TAL programming language (for details, refer to page
G-161).
The Translation Application Example on page G-221 opens the responder and issues
the Enable Translation command. It then reads its $RECEIVE and processes all
translation requests.
Note. Besides making changes to the environmental variables contained in the programming
examples in this manual, you might need to modify the examples to exclude certain procedure
calls, depending upon the FTAM implementation with which you are interoperating. For
example, the F-CHANGE-ATTRIB primitive might not be supported by all vendors; if the
responding system does not support the F-CHANGE-ATTRIB primitive, you should not call the
FTM_CHANGE_ATTRIB_REQ_ used in the examples.