If the initiative lies with the FTAM partner, then only SAM files and library elements can be transferred (in other words, no ISAM or PAM files). In the process, openFT (BS2000) maps the file formats to the virtual filestore of the partner system.
In contrast, if files are transferred from FTAM partners to openFT (BS2000), the file format from the virtual store is mapped to a SAM file format. If files are transferred from FTAM partners to openFT (BS2000) and are to be stored as library members, there is no “memory” for the FTAM-specific attributes. Therefore, in this case there is no FTAM catalog entry.
The following table provides details on mapping FTAM attributes to the real BS2000 file system and vice versa.
openFT as the responder and receive system (FTAM --> BS2000 receive files)
FTAM (virtual filestore of the remote system) | BS2000 file | |||
document type | universal class | string significance | ||
FTAM-1 | 25 - GraphicString | variable | SAM | V |
FTAM-1 | 26 - VisibleString | variable | SAM | V |
FTAM-1 | 27 - GeneralString | not-significant | SAM | V |
FTAM-1 | 22 - IA5String | not-significant | SAM | V |
FTAM-1 | 25 - GraphicString | fix | SAM | F |
FTAM-1 | 26 - VisibleString | fix | SAM | F |
FTAM-3 | ----- | fix | SAM | F |
FTAM-3 | ----- | variable | SAM | V |
FTAM-31 | ----- | not significant | SAM | U |
If FTAM-1 files are mapped to the BS2000 real storage, the data is converted to the
EBCDIC.DF.04 format and transferred as text files. FTAM-3 files are not converted, in other words they are transferred as binary files.
If a partner specifies file format attributes while attempting to write or extend files in BS2000 without regenerating them, the attributes specified must be compatible with the attributes of the existing file. This means:
The document type which the initiator may have specified must correspond to the data type (DATA-TYPE) of the file.
document type
DATA-TYPE
FTAM-1 (unstructured text)
*CHARACTER or -
FTAM-3 (unstructured binary)
*BINARY or -
not specified
any
If the initiator specifies the document type parameter string significance, it must correspond to the record format (RECORD-FORMAT) of the file as displayed in the SHOW-FILE-FT-ATTRIBUTES command.
string significance
RECORD-FORMAT
variable
v
fixed
f
not significant
u
not specified
any
The following combinations are possible for the character repertoire and the universal class number (document type parameter, only with unstructured text):
universal class number
character repertoire
GRAPHIC
*GRAPHIC
VISIBLE
*GRAPHIC or *VISIBLE
GENERAL
*GENERAL
IA5
*GENERAL or *IA5
openFT as the responder and send system (FTAM --> BS2000 send file)
FTAM (virtual filestore of the remote system) | BS2000 file | |||
document type | universal class | string significance | ||
FTAM-1 | 25 - GraphicString | variable | SAM | V |
FTAM-1 | 26 - VisibleString | variable | SAM | V |
FTAM-1 | 27 - GeneralString | not significant | SAM | V |
FTAM-1 | 22 - IA5String | not significant | SAM | V |
FTAM-1 | 25 - GraphicString | fix | SAM | V |
FTAM-1 | 26 - VisibleString | fix | SAM | F |
FTAM-3 | ----- | fix | SAM | F |
FTAM-3 | ----- | variable | SAM | V |
FTAM-3 | ----- | not significant | SAM | U |
Files that are mapped to FTAM-1 files must be in EBCDIC.DF.04 format (see code tables). Code extensions by means of escape sequences are not permitted. FTAM-3 files are not converted.
If a partner attempts to read files in BS2000 and specifies the file format attributes, the specifications must be compatible with those of the existing file. This means:
The document type, which the initiator may have specified must correspond to the data type (DATA-TYPE) of the file.
document type
DATA-TYPE
FTAM-1 (unstructured text)
*CHARACTER or -
FTAM-3 (unstructured binary)
*BINARY or -
not specified
any
If the initiator specifies the document type parameter string significance, it must correspond to the record format (RECORD-FORMAT) of the file as displayed in the SHOW-FILE-FT-ATTRIBUTES command.
string significance
RECORD-FORMAT
variable
v
fixed
f
not significant
u
not specified
any
The following combinations are possible for the character repertoire and the universal class number (document type parameter, only with unstructured text):
universal class number
character repertoire
GRAPHIC
*VISIBLE or *GRAPHIC
VISIBLE
*VISIBLE
GENERAL
*GENERAL or *IA5
IA5
*IA5
Access protection
openFT supports the security group of the virtual filestore. This provides an effective protection mechanism against unauthorized access to files.
For access authorization to the virtual filestore of a system you need the FTAM protocol parameters initiator identity and filestore password. openFT (BS2000) maps these parameters to the BS2000 parameters USER-IDENTIFICATION (user ID) and PASSWORD (password of the user ID).
For file transfers with FTAM partners it is also possible to use the the functions of the addon product openFT-AC for extended protection against unauthorized forms of access. If an admission profile in BS2000 is to be addressed by an FTAM partner, then the transfer admission (TRANSFER ADMISSION) for the profile concerned must be supplied in the protocol parameter initiator identity. The parameters filestore password and account must not be specified. Apart from this, the rules of the openFT-AC described in this manual apply here (e.g. referencing a file that has been predefined in the admission profile either with the specification *NOT-SPECIFIED for the file name).