As of openFT V10 for z/OS, the file for the partner list is created when openFT is started and does not have to be created by issuing a command any longer.
The following examples demonstrate how various partner systems, accessed using a variety of transport systems, are successively entered into the partner list.
In these examples it is assumed that the local system possesses the FT identifier ZOS1. All partner systems that use Network Description Files or partner lists containing symbolic names for partner systems (i.e. remote openFT (z/OS) systems and openFT (BS2000) systems) address the local openFT system under the symbolic name FTZOS1. Although this is not really necessary from a technical point of view (symbolic names do not need to be consistent throughout the network; they simply have to be unique within the partner list on each individual openFT instance), it helps to make the examples easier to follow.
The examples below have been harmonized with other examples presented in this manual, i.e.:
The examples relating to SNA interconnection have been harmonized with the examples relating to the generation of the transport system in the manual "openFT (z/OS) - Installation and Operation".
The examples relating to TCP/IP interconnection have been harmonized with the example for the TNSTCPIP member of the FT parameter library, see in the manual "openFT (z/OS) - Installation and Operation".
A partner system with openFT as of V8.1 and the symbolic name XAS1 is to be directly connected to the local system via TCP/IP. The instance identifier is
VAR2.MOULINET.FR.If the partner’s Internet address has been assigned to a host name (in the example: XAS123) in the z/OS name services, the remote openFT system can be entered in the local system’s partner list using the following command:
FTADDPTN PARTNER-NAME=XAS1,PARTNER-ADDRESS=XAS123,IDENTIFICATION=’VAR2.MOULINET.FR’This example functions for z/OS, BS2000, Unix and Windows partner systems, if the main station of the remote openFT system has been assigned the transport selector $FJAM and the port number 1100 there. These are the recommended default values in all openFT systems. Divergent values can be specified for the transport selector and the port number using the parameter PARTNER-ADDRESS in the FTADDPTN command, for example for port number 1111 and T selector TSELOPFT:
PARTNER-ADDRESS=XAS123:1111.TSELOPFTThe partner system with the symbolic name FTZOS1, a partner with openFT V9.0 for z/OS, is to be entered in the partner list. The connection to the partner is established via SNA. It has the ftid ZOS1 and the instance identifier VAR1.FUSINET.AT. The corresponding command is:
FTADDPTN PARTNER-NAME=FTZOS1,PARTNER-ADDRESS=FJMZOS1:SNA,IDENTIFICATION=’VAR1.FUSINET.AT’)In the case of partner systems with openFT V8.0 (or earlier), the instance identifier is derived from the processor name specifications and the partner system’s openFT main station (usually $FJAM).
A partner system with openFT as of V8.1 for Unix systems and the symbolic name FTUNIX1 is to be connected via SNA and TRANSIT-SERVER / TRANSIT-CLIENT. The LU name of the Unix partner system is FJML0717 and its instance identifier is UX.FUSINET.AT.
FTADDPTN PARTNER-NAME=FTUNIX1,PARTNER-ADDRESS=FJML0717:SNA,IDENTIFICATION='UX.FUSINET.AT'An FTP partner system using openFT (Unix systems) as of V10 and the symbolic name FTPX is to be connected over TCP/IP. The host name of the partner system is FTPHOST1 and the default port number 21 is to be used.
FTADDPTN PARTNER-NAME=FTPX,PARTNER-ADDRESS=FTP://FTPHOST1The partner system SERVER11 with openFT V11 for Unix systems is a remote administration server. The default port number (11000) is to be used for remote administration. The partner address is to be used for identification:
FTADDPTN PARTNER-NAME=ADMINSRV,PARTNER-ADDRESS=FTADM://SERVER11