The following applies to the addressing of a partner system:
You can specify the name of the partner from the partner list provided that the partner has been entered in the partner list.
A partner has to be entered in the partner list by the FT administrator. For this purpose, the FT administrator can use the following commands:
ftaddptn
ftmodptn
You can access a partner directly via its address in FT or file management requests even if it is not entered in the partner list. This is only possible if the “dynamic partner” function is enabled via operating parameters.
Partner addresses
A partner address has the following structure:
[protocol://]host[:[port].[tsel].[ssel].[psel]]
host (= computer name, see "Specifying partner addresses" ) is mandatory; all other specifications are optional. In many cases, the other specifications are covered by the default values, so that the host name suffices as the partner address, see “Examples” . Final ’.’ or ’:’ can be omitted.
The individual components of the address have the following meanings:
protocol://
Protocol stack via which the partner is addressed. Possible values for protocol
(uppercase and lowercase are not distinguished):
openft
openFT partner, i.e. communication takes place over the openFT protocol.
ftam
FTAM partner, i.e. communication takes place over the FTAM protocol.
ftp
FTP partner, i.e. communication takes place over the FTP protocol.
ftadm
ADM partner, i.e. communication takes place over the FTADM protocol for remote administration and ADM traps.
Default value: openft
Exception: if a global name from the TNS is used for host and a presentation
selector is assigned to this name in the TNS then ftam is the default value.
host
Computer name via which the partner is addressed. Possible entries:
Internet host name (e.g. DNS name), length 1 to 80 characters
Global name from the Transport Name Service (TNS), up to 78 characters long, with full support for the 5 name parts. In this event, the following applies:
TNS must be activated ( ftmodo -tns=y ) and operation with CMX must be enabled to allow a global name from the TNS to be used in requests. In this case, the
TNS name takes precedence over the Internet host name.The partner address must end with host and must not contain any other address components, such as port , tsel etc.
ftp is not permitted for protocol , as openFT-FTP does not support TNS
operation.If the TNS entry contains a presentation selector for this global name, only ftam is permitted for protocol .
If the TNS entry does not contain a presentation selector, ftam is not permitted for protocol .
Note for Windows systems
If you are using TranSON, the partner is only available over the TNS.
To do this, a proxy must be entered in TNS.
For further information, refer to the online Help system for the "TNS User
Interface" application of PCMX-32.IPv4 address with the prefix %ip, e.g. %ip139.22.33.44
You should always specify the IP address with the prefix %ip since the specification is then immediately treated as the IP address. Omitting this prefix results in performance impairments since in this case a search is initially performed in the TNS and then in the hosts file. The pathname is / etc/hosts (Unix systems) or
%SystemRoot%\system32\drivers\etc\hosts (Windows systems).
The IP address must always be specified as a sequence of decimal numbers
separated by dots and without leading zeros.IPv6 address with the prefix %ip6, e.g.
%ip6[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210](IPv6) or%ip6[FE80::20C:29ff:fe22:b670%5](IPv6 with ccope ID)The square brackets [..] must be specified.
The scope ID designates the local network card via which the remote partner can be accessed in the same LAN segment. It must be appended to the address with a % character. In Windows systems, this is a numerical value (e.g. 5). On other s ystems, it may also be a symbolic name (e.g. eth0 ). The scope ID can be identified using the ipconfig command (Unix systems) or the ifconfig command (Windows systems).
If a unique allocation is required via the partner address, one and the same IPv6 address (with the same selectors) and with a different scope ID should not occur twice in partner list entries. If we are dealing with a link-local IPv6 address here, the scope ID in operation without CMX is nevertheless passed up in the sender address, thus enabling unique partner allocation even with identical link-local
addresses plus different scope IDs.Example: A partner was entered in the partner list with the following command:
ftaddptn ftampart –pa=ftam://%ip6[FE80::222:333:444:555%eth0]If this partner now sends a message, he answers with the sender address
ftam://%ip6[FE80::222:333:444:555]In openFT or FTADM partner entries the scope ID or line number is not transferred to the identification in case of defaulting.
Partner address of an X.25 partner
The host part in the partner address has the following structure when using the FarSync X.25 transport system:
%x25[DTE address%line number]The prefix %x25, the square brackets [...] and the DTE address are mandatory and must be specified. The specification of the local line number of the FarSync X.25 card after the percentage is optional, the standard is 0:0 (Windows) i.e. 0 (Linux).
Example for Windows systems
%x25[123456%0:3]Example for Linux systems
%x25[123456%0]If optional X.25 facilities or a special value for the transport protocol class are to be specified when setting up the connection, it is essential for the partner system to create a named partner list entry.
If a unique allocation is required via the partner address, one and the same DTE address (with the same selectors) and with a different line number should not occur twice in partner list entries.
TNS name from the z/OS library (TNSTCPIP member), up to 8 characters in length.
port
When a connection is established over TCP/IP, you can specify the port name under which the file transfer application can be accessed in the partner system.
Permitted range of values: 1 through 65535.
Default value:
1100 for openFT partners.
A different default value can also be set in the operating parameters using the
following command: ftmodo -ftstd=4800 for FTAM partners.
21 for FTP partners
11000 for ADM partners
tsel
Transport selector under which the file transfer application is available in the partner system. The transport selector is only relevant for openFT partners and FTAM partners . You can specify the selector in printable or hexadecimal format (0xnnnn...).
The specification will depend on the type of partner:
openFT partner:
Length, 1 through 8 characters; alphanumeric characters and the special
characters # @ $ are permitted. A printable selector will be coded in EBCDIC in the protocol and may be padded with spaces internally to the length of eight characters.Default value: $FJAM
FTAM partner:
Length 1 to 10 characters; a printable selector will be coded as variable length
ASCII in the protocol. Exception: T-selectors that start with $FTAM (default value) are coded in EBCDIC and padded with spaces to the length of 8 characters.All alphanumeric characters and the special characters @ $ # _ - + = and * can be used with ASCII selectors.
Default value: $FTAM
Note :
As a rule, SNI-FTAM must be specified for Windows partners with openFT-FTAM up to V10. As of openFT-FTAM V11 for Windows, the default value has been
changed to $FTAM and can therefore be omitted.
Printable transport selectors are always used in uppercase in openFT even if they are specified or output in lowercase.
ssel
Session selector under which the file transfer application is accessible in the partner system. You can specify the selector in printable or hexadecimal format (0xnnnn...). Length, 1 through 10 characters; alphanumeric characters and the special characters @ $ # _ - + = * are permitted. A printable selector is encoded in ASCII with a variable length in the log.
Default value: empty
Printable session selectors are always used in uppercase in openFT even if they are specified or output in lowercase.
psel
Only relevant for FTAM partners.
Presentation selector under which the file transfer application is available in the partner system. You can specify the selector in printable or hexadecimal format (0xnnnn...). Length, 1 through 10 characters; alphanumeric characters and the special characters @ $ # _ - + = * are permitted. A printable selector is interpreted as ASCII with a variable length in the log.
Default value: empty
Printable presentation selectors are always used in uppercase in openFT even if they are specified or output in lowercase.
Examples
The partner computer with the host name FILESERV is to be addressed over different protocols/connection types:
Connection type/protocol | Address specification |
openFT partner | FILESERV |
FTAM partner (Windows system as of V11.0, | ftam : / /FILESERV |
FTAM partner (Windows system with default | ftam : / /FILESERV:.SNI-FTAM |
Third-party FTAM partner | ftam: / /FILESERV:102.TS0001.SES1.PSFTAM |
FTP partner | ftp : / /FILESERV |
FTADM partner | ftadm://FILESERV |