The FTAM extension available in openFT also enables openFT to perform file transfer and file management with partner systems which support ISO protocols in layers 5 - 7 of the OSI Reference Model. In the rest of this manual, these systems are referred to as FTAM partners, since they use the protocols for file transfer defined in the international standard ISO 8571 (FTAM, File Transfer, Access and Management).
BS2000 systems also require the OSS software package to implement layers 5 - 7.
FTAM is not available on z/OS.
Implementation of FTAM Standards in openFT
A subset of the complete functional scope of the base standards has been selected in accordance with international and European profiles ISO/EN ISP 10607-3 and ISO/EN 10607-6. This functional standardization has, in turn, been harmonized with other functional standards (and implementation agreements), e.g. the corresponding implementation agreements of IGOSS in North America and corresponding profiles in Asia and Australia.
ENV 41204 and ENV 41205 are the old, nevertheless still applicable, designations for EN 10607-3 and EN 10607-6 and their contents are identical to the international profiles ISO/IEC ISP 10607-3 (1990) and ISO/IEC ISP 10607-6 (1990) agreed by ISO. EN 10607-3 and EN 10607-6 contain additional European character repertoires.
These profiles specify the file attributes actually used, for example, and the operations permitted with these attributes, irrespective of the operating system used. A virtual filestore is used to permit presentation across several operating systems; here, the contents of the real store are transferred with a representation of the file attributes in accordance with the standard. Conversion of the file attributes to FTAM Standard in the operating system and vice versa is part of the FTAM functionality. There are three groups of file attributes: kernel group, storage group and security group (see "Virtual filestore").
Compliance with the FTAM standard also restricts the functional scope offered by openFT protocols. Transfer of follow-up data to FTAM partners is not possible with the protocol.
The mapping mechanism between the real filestore and the virtual filestore is described in detail on "Virtual filestore".