Outbound mapping of the document type

If openFT is the initiator, the FT user can use the file type specification (options -t, -u, -b in ft and ncopy command) to specify in the request whether text or binary data is to be transferred. There is no attribute for binary or text data in the real store on the Unix or Windows system.

In Windows systems, please note that only NTFS files can have entries in the FTAM catalog. No entries can be generated or edited in the FTAM catalog for files on mounted net drives or UNC shares, as mounted systems and UNC shares are handled in the same way as FAT file systems.

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

Outbound Sending (Local system --> FTAM)

Local system	FTAM attributes)
File type	document type	universal class	string significance
Text (-t)	FTAM-1	25 - GraphicString	variable 1)
User format (-u)	FTAM-3	----	variable 1)
Binary (-b)	FTAM-3	----	not significant 1)
Binary + record length (-b -r=max record length)	FTAM-3	----	fixed
1)If one of the options -t, -u, or -b are specified and an entry for the send file on the local system exists in the FTAM catalog /catalog extension, this entry must correspond to the entries in the above table.

If the FT user does not specify a file type in the request, the entries in theFTAM catalog are used. If there is no entry in the FTAM catalog, FTAM1, GraphicString, and variable are used.

No provision is made for transfer of FTAM-3 files with variable string significance in the functional standard ENV 41204. openFT systems provides additional support for this function.

Outbound Receive (Local system <-- FTAM)

For outbound receive, the type of the receive file depends on whether and which file type, if any, was specified in the FT request. The following cases must be differentiated here.

1. No file is specified in the request

   FTAM (virtual filestore in the remote system)			Receive file on the local system
   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

2. -t option resp. Text Format specified for file type in request

   FTAM (virtual filestore in the remote system)			Receive file on the local system
   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

3. -u option resp. User format specified for file type in the request

   FTAM (virtual filestore in the remote system)			Receive file on the local system
   document type	universal class	string significance
   FTAM-3	----	variable	record-structured binary file
   FTAM-3	----	fix	binary file with fixed record structure

4. -b option resp. Binary specified for file type in the request

   FTAM (virtual filestore in the remote system)			Receive file on the local system
   document type	universal class	string significance
   FTAM-3	----	not significant	unstructured binary file

5. -b and -r (max. record length) options resp. Binary + Maximum Record Length specified for file type in the request

   FTAM (virtual filestore in the remote system)			Receive file on the local system
   document type	universal class	string significance
   FTAM-3	----	fix	binary file with fixed record structure