OSI/FTAM Programming Guide

NonStop FTAM Programming
HP NonStop OSI/FTAM Programming Guide—528612-001
3-11
Data Transfer Concepts
To use the tag parameter, assign a unique 32-bit integer value to the variable you will
use for the tag. When you call an FTAM request procedure in nowait mode, include the
tag in the parameter list. After the requested service is performed, the
MFM_AWAITIOX_ call returns the tag for this service, identifying which service was
completed. For reference information on the MFM_AWAITIOX_ procedure, see the
OSI/FTAM Programming Reference Manual.
Data Transfer Concepts
To develop an application using the NonStop FTAM initiator to transfer data to and from
a remote responder, you must understand these concepts:
•
data-value parameter of the FTM_DATA_REQ_ or FTM_DATA_IND_ procedure,
which passes data between the FTAM application and the initiator
•
Parameters associated with the contents type (universal–class,
string-significance, and maximum–string–length) specified in either the
create or open request and how they affect the transfer of data for the FTAM-1,
FTAM-2, and FTAM-3 document types
•
Files on the NonStop system that are compatible with each FTAM document type
These concepts are covered in the subsections that follow.
General Considerations
Important considerations to remember when transferring data include:
•
NonStop FTAM supports unbounded character strings, but enforces certain
limitations on the specification of the maximum-string-length parameter of the
contents type. Each data element of the data-value parameter contains a single
character string, the length of which must be less than or equal to the maximum
string-length value. The limitations of the maximum-string-length
parameter are described in greater detail in the subsections that follow.
•
For the universal-class parameter associated with FTAM-1 and FTAM-2
document types (the concept of universal-class does not apply to FTAM-3
documents), the initiator supports the universal-classes specified in Tables 19 and
20 of ISO 8571, Part 2. If no universal-class value is proposed in an initiator
open request or returned in an open confirm, the NonStop FTAM initiator assumes
that the responder is sending GraphicString data, in compliance with the ISO 8571
default for universal-class.
•
The initiator does no character-set verification. For FTAM-1 and FTAM-2 files, to
ensure that the file being transferred contains the correct character-string type as
specified in the universal-class parameter of the contents type, your
application should verify characters as it sends or receives data.
•
When the initiator receives data from a remote responder, it removes any escape
sequences embedded in a graphic (Universal class 25) or general (Universal