Example 1
The FTAM partner RITTER is to be entered in the partner list. At BCAM generation, this system was assigned the processor name BURGHOF1. The transport selector is KUNIBERT, the session selector is SESSION1 and the presentation selector is FTAM.
/ADD-FT-PARTNER RITTER,FTAM://BURGHOF1:.KUNIBERT.SESSION1.FTAM
Positional operands were used in this statement. This is why the keywords are omitted.
If the partner requires a transport selector which is not in TRANSDATA format (8 character name in EBCDIC, filled with blanks if necessary), this must be defined in BCAM.
If the partner uses, for example, the 6-character transport selector TSKUNI in ASCII format, the BCMAP command must be as follows:
|
Example 2
Since some FTAM implementations respond with another address during connection setup, openFT (BS2000) requires a further entry defining the sender address of the partner for the purpose of checking the sender for this partner.
The partner responds with the FTAM1 transport selector, the SESSION2 session selector and the FTAM presentation selector (all in ASCII code):
|
The relevant BCMAP command must be:
|
Example 3
FTAM connection between openFT (BS2000) <-> openFT (Windows) (openFT as of V11.0)
The FTAM partner WINDOWS is to be entered in the partner list. The default transport selector has the name $FTAM in TRANSDATA format; the computer has the processor name WINDOWS2.
/ADD-FT-PARTNER WINDOWS,FTAM://WINDOWS2
A BCMAP command is no longer necessary for this connection!
Example 4
FTAM link: openFT (BS2000) <-> openFT (Windows) (openFT up to V10.0)
The FTAM partner WINDOWS is to be entered in the partner list. At BCAM generation, this system was assigned the processor name WINDOWS1. The transport selector is SNI-FTAM in ASCII code and the port number 4800.
/ADD-FT-PARTNER WINDOWS,FTAM://WINDOWS1:.SNI-FTAM
The relevant BCMAP command must be:
|