If openFT (BS2000) is the initiator, the FT user can use the file type specification (DATA-TYPE= *CHARACTER/*BINARY/*NOT-SPECIFIED) 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 BS2000 system.
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.
openFT as initiator and send system (BS2000 send file --> FTAM)
Case a1:
Transfer a text file to the FTAM partner. No entries in the local FTAM catalog,
Entries in the TRANSFER-FILE(NCOPY) command:
TRANSFER-DIRECTION = TO DATA-TYPE = *CHARACTER WRITE-MODE = any
BS2000 | FTAM (virtual filestore of the remote system) | |||
send file | document type | universal class | string significance | |
SAM | V | FTAM-1 | 25 - GraphicString | variable |
SAM | F | FTAM-1 | 25 - GraphicString | fix |
SAM | U | not supported as FTAM text file | ||
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.
Case a2:
Transfer a text file to the FTAM partner,
The entry in the local FTAM catalog is DATA-TYPE=*CHARACTER(*GRAPHIC) or DATA-TYPE=*CHARACTER(*VISIBLE)
BS2000 | FTAM (virtual filestore of the remote system) | |||
send file | document type | universal class | string significance | |
SAM | V | FTAM-1 | see FTAM catalog | variable |
SAM | F | FTAM-1 | see FTAM catalog | fix |
SAM | U | not supported as FTAM text file | ||
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.
Case a3:
Transfer a text file to the FTAM partner,
The entry in the local FTAM catalog is DATA-TYPE=*CHARACTER(*GENERAL) or DATA-TYPE=*CHARACTER(*IA5)
BS2000 | FTAM (virtual filestore of the remote system) | |||
send file | document type | universal class | string significance | |
SAM | V | FTAM-1 | see FTAM catalog | not-significant |
SAM | F | not supported | ||
SAM | U | not supported | ||
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.
Case b1:
Transfer a binary file to the FTAM partner,
No entry in the local FTAM catalog or the entry is DATA-TYPE=*BINARY
Entries in the TRANSFER-FILE(NCOPY) command:
TRANSFER-DIRECTION = TO DATA-TYPE = *BINARY WRITE-MODE = any
BS2000 | FTAM (virtual filestore of the remote system) | |||
send file | document type | universal class | string significance | |
SAM | V | FTAM-3 | ----- | variable |
SAM | F | FTAM-3 | ----- | fix |
SAM | U | FTAM-3 | ----- | not-significant |
Transferring FTAM-3 files with variable string significance is not provided for in the function standard EN 10607-3. openFT provides additional support for this function because this file format corresponds to the user format in Unix and Windows systems.
FTAM-3 files are not converted.
Case b2:
Transfer a structured binary file with variable record length,
No entry in the local FTAM catalog or the entry is DATA-TYPE=*BINARY
Entries in the TRANSFER-FILE(NCOPY) command:
TRANSFER-DIRECTION = TO DATA-TYPE = *USER WRITE-MODE = any
BS2000 | FTAM (virtual filestore of the remote system) | |||
send file | document type | universal class | string significance | |
SAM | V | FTAM-3 | ----- | variable |
SAM | F | illegal combination | ||
SAM | U | illegal combination | ||
Transferring FTAM-3 files with variable string significance is not provided for in the function standard EN 10607-3. openFT provides additional support for this function because this file format corresponds to the user format in Unix and Windows systems.
FTAM-3 files are not converted.
Case c1:
Transfer a file to the FTAM partner. No entry in the local FTAM catalog,
Entries in the TRANSFER-FILE(NCOPY) command:
TRANSFER-DIRECTION = TO DATA-TYPE = *NOT-SPECIFIED WRITE-MODE = any
BS2000 | FTAM (virtual filestore of the remote system) | |||
send file | document type | universal class | string significance | |
SAM | V | FTAM-1 | 25 - GraphicString | variable |
SAM | F | FTAM-1 | 25 - GraphicString | fix |
SAM | U | FTAM-3 | ----- | not-significant |
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.
Case c2:
Transfer a file to the FTAM partner,
The entry in the local FTAM catalog is DATA-TYPE=*CHARACTER(*GRAPHIC) or DATA-TYPE=*CHARACTER(*VISIBLE)
BS2000 | FTAM (virtual filestore of the remote system) | |||
Send file | document type | universal class | string significance | |
SAM | V | FTAM-1 | see FTAM catalog | variable |
SAM | F | FTAM-1 | see FTAM catalog | fix |
SAM | U | not supported as FTAM text file | ||
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.
Case c3:
Transfer a file to the FTAM partner,
The entry in the local FTAM catalog is DATA-TYPE=*CHAR(*GENERAL). or
DATA-TYPE=*CHARACTER(*IA5)
BS2000 | FTAM (virtual filestore of the remote system) | |||
send file | document type | universal class | string significance | |
SAM | V | FTAM-1 | see FTAM catalog | not-significant |
SAM | F | not supported | ||
SAM | U | not supported | ||
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.
Case c4:
Transfer a file to the FTAM partner,
The entry in the local FTAM catalog is DATA-TYPE=*BINARY
BS2000 | FTAM (virtual filestore of the remote system) | |||
send file | document type | universal class | string significance | |
SAM | V | FTAM-3 | ----- | variable |
SAM | F | FTAM-3 | ----- | fix |
SAM | U | FTAM-3 | ----- | not-significant |
Transferring FTAM-3 files with variable string significance is not provided for in the function standard EN 10607-3. openFT provides additional support for this function because this file format corresponds to the user format in Unix and Windows.
FTAM-3 files are not converted.
Case d1:
Transfer a library member to the FTAM partner,
In this case, the send file is a library member.
BS2000 | FTAM (virtual filestore of the remote system) | ||
send file | document type | universal class | string significance |
S | FTAM-1 | 25 - GraphicString | variable |
R | not transferable | ||
C, L | not transferable | ||
other | FTAM-1 | 25 - GraphicString | variable |
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.
Case d2:
Transfer a library member to the FTAM partner as a binary file,
In this case, the send file is a library member.
BS2000 | FTAM (virtual filestore of the remote system) | ||
send file | document type | universal class | string significance |
S | FTAM-3 | ----- | variable |
R | not transferable | ||
C, L | not transferable | ||
other | FTAM-3 | ----- | variable |
Transferring FTAM-3 files with variable string significance is not provided for in the function standard ENV10607-3. openFT provides additional support for this function because this file format corresponds to the user format in Unix and Windows systems.
openFT is initiator and receive system (FTAM --> BS2000 receive file)
Case e:
Transfer a text file from the FTAM partner
Entries in the TRANSFER-FILE(NCOPY) command:
TRANSFER-DIRECTION = FROM DATA-TYPE = *CHARACTER WRITE-MODE = any
FTAM (virtual filestore of the remote system) | BS2000 | |||
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 |
If the BS2000 receive file already exists as a SAM file of a different record type and WRITE-MODE=EXTEND is specified in the FT request, the request is rejected.
Likewise, the request is rejected when WRITE-MODE=EXTEND if the information from the virtual filestore of the remote system is not compatible with the entries in the local FTAM catalog for the file that is to be extended.
If FTAM-1 files are mapped to the real filestore of BS2000, the data is converted to EBCDIC.DF.04 format (see code tables).
Case f1:
Transfer a binary file from the FTAM partner
Entries in the TRANSFER-FILE(NCOPY) command:
TRANSFER-DIRECTION = FROM DATA-TYPE = *BINARY WRITE-MODE = any
FTAM (virtual filestore of the remote system) | BS2000 | |||
document type | universal class | string significance | ||
FTAM-3 | ----- | fix | SAM | F |
FTAM-3 | ----- | variable | SAM | V |
FTAM-3 | ----- | not-significant | SAM | U |
Transferring FTAM-3 files with variable string significance is not provided for in the function standard EN 10607-3. openFT provides additional support for this function because this file format corresponds to the user format in Unix and Windows systems.
If the BS2000 receive file already exists as a SAM file of a different record type and WRITE-MODE=EXTEND is specified in the FT request, the request is rejected.
Likewise, the request is rejected when WRITE-MODE=EXTEND if the information from the virtual filestore of the remote system is not compatible with the entries in the local FTAM catalog for the file that is to be extended.
FTAM-3 files are not converted.
Case f2:
Transfer a structured binary file with variable record length from the FTAM partner
Entries in the TRANSFER-FILE(NCOPY) command:
TRANSFER-DIRECTION = FROM DATA-TYPE = *USER WRITE-MODE = any
FTAM (virtual filestore of the remote system) | BS2000 | |||
document type | universal class | string significance | ||
FTAM-3 | ----- | variable | SAM | V |
Case g:
Transfer a file from the FTAM partner without specifying data type
Entries in the TRANSFER-FILE(NCOPY) command:
TRANSFER-DIRECTION = FROM DATA-TYPE = *NOT-SPECIFIED WRITE-MODE = any
FTAM (virtual filestore of the remote system) | BS2000 | |||
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-3 | ----- | not-significant | SAM | U |
Files with different combinations of the file characteristics in the virtual filestore cannot be transferred with openFT.
If the BS2000 receive file already exists as a SAM file of a different record type and WRITE-MODE=EXTEND is specified in the FT request, the request is rejected.
Likewise, the request is rejected when WRITE-MODE=EXTEND if the information from the virtual filestore of the remote system is not compatible with the entries in the local FTAM catalog for the file that is to be extended.
If FTAM-1 files are mapped to the real filestore of BS2000, the data is converted to EBCDIC.DF.04 format (see code tables). FTAM-3 files are not converted.
Case h:
Transfer a library member from the FTAM partner
In this case, the receive file is a library member.
BS2000 | FTAM filestore of the remote system) | ||
Receive file | document type | universal class | string significance |
S | FTAM-1 | 25 - GraphicString | variable |
S | FTAM-1 | 26 - VisibleString | variable |
S | FTAM-1 | 27 - GeneralString | not-significant |
S | FTAM-1 | 22 - IA5String | not-significant |
S | FTAM-3 | ----- | variable |
R | not transferable | ||
C, L | not transferable | ||
other | FTAM-1 | 25 - GraphicString | variable |
other | FTAM-1 | 26 - VisibleString | variable |
other | FTAM-1 | 27 - GeneralString | not-significant |
other | FTAM-1 | 22 - IA5String | not-significant |
other | FTAM-3 | ----- | variable |
In this case, there is no memory for the FTAM-specific file attributes. The default values are assigned, provided this is compatible with the FTAM attributes of the send files.
If FTAM-1 files are mapped to the real filestore of BS2000, the data is converted to EBCDIC.DF.04 format (see code tables). FTAM-3 files are not converted.