OSI/FTAM Programming Guide

NonStop FTAM Programming
HP NonStop OSI/FTAM Programming Guide—528612-001
3-33
Using Predefined Data Structures
2. Call the procedure.
3. After calling the procedure:
°
Check the status or error code returned by the procedure. A procedure
that performs I/O operations returns a status code; a procedure that does not
perform I/O operations returns an error code.
°
If status is not equal to ZAPS-VAL-STATUS-OK (0), call APS_STATUS_ for
error-code and error-subcode values.
°
If status equals ZAPS-VAL-STATUS-OK (0), check any returned values from
the procedure.
°
If error equals ZAPS-ERR-OK (0), check any returned values from the
procedure.
•
Section 4, Using FTM Procedure Calls provides details on the various FTAM
programming tasks you will perform in the course of developing FTAM applications.
This manual also provides you with examples of calling NonStop FTM, APS, and
MFM procedures. You can find these examples in these locations.
•
Section 5, NonStop FTAM Programming Examples and Appendix G of the
OSI/FTAM Programming Reference Manual provide example programs, which
reside in the FTAM distribution subvolume ZOSIFTAM. Use these example
programs to learn how to sequence procedure calls to complete file-handling tasks.
•
The OSI/FTAM Programming Reference Manual provides procedure-call examples
for procedure calls that are not used in the example programs. These
procedure-call examples are described in the reference material for the relevant
procedure calls. Use these examples to learn how to use individual procedures.
The OSI/FTAM Programming Reference Manual also provides information on the MFM
and APS procedure calls used in the NonStop FTAM programmatic interface.
Using Predefined Data Structures
The OSI/FTAM Programming Reference Manual summarizes, in DDL (Data Definition
Language) format, the data structures used in the parameters to the FTM procedure
calls. The information in that manual gives you the foundation for referring to the
various fields of the parameter data structures in your C and TAL programs; that is, it
explains the significance of each structure and each field. This subsection provides
examples of how to specify identifiers and access fields in the C and TAL data
structures provided in ZFTMC, ZAPSC, ZFTMTAL, and ZAPSTAL. These examples
will be most meaningful if you also look at the corresponding DDL definitions for
background information.
To demonstrate, consider the parameter structure ZFTM-DDL-CNTNTS-TYPE, for
which you might define and assign the value contents_type as the parameter
variable. The DDL definition for this structure is as follows: