Inbound mapping the document type

The following tables provide information on mapping the document type during file transfer. A distinction is made here between openFT for as the receiving system and openFT for as the sending system.

Mapping of the document type for Inbound Receive (FTAM --> Local system)

FTAM (virtual filestore in the remote system)			Local receive file
document type	universal class	string significance
FTAM-1	25 - GraphicString	variable/fixed	text file
FTAM-1	26 - VisibleString	variable/fixed	text file
FTAM-1	27 - GeneralString	not significant	text file
FTAM-1	22 - IA5String	not significant	text file
FTAM-3	----	not significant	unstructured binary file
FTAM-3	----	variable	record-structured binary file
FTAM-3	----	fix	binary file with fixed record structure

No provision in made for transfer of FTAM-3 files with variable and fixed string significance in the functional standard ENV 41204. openFT provides additional support for this function, since the file format corresponds to the user format in Unix and Windows systems.

Mapping of the document type for Inbound Send (FTAM <-- Local system)

FTAM (specifications in request and/or entries in the FTAM catalog / catalog extension in the local system)			Local send file
document type	universal class	string significance
not specified	not specified	not specified	text file
FTAM-1	not specified	not specified	text file
FTAM-1	25 - GraphicString	variable/fixed	text file
FTAM-1	26 - VisibleString	variable/fixed	text file
FTAM-1	27 - GeneralString	not significant	text file
FTAM-1	22 - IA5String	not significant	text file
FTAM-3	----	not specified	unstructured binary file
FTAM-3	----	not significant	unstructured binary file
FTAM-3	----	variable	record-structured binary file
FTAM-3	----	fix	binary file with fixed record structure

If there is an entry for the send file in the FTAM catalog / catalog extension, the file format specifications in the request must correspond to this entry. Otherwise, files inconsistencies may occur and file transfer requests involving the particular file may be aborted.

If there are no specifications in the request, the entries in the FTAM catalog / catalog extension apply.