Defining partners

For Transfer CFT a partner is a logical entity such as a bank, the government or trading partner that can be the origin or destination of a data exchange. A partner usually corresponds to a remote file transfer monitor.

This topic defines a partner, access control, and lists possible protocols for communicating with a partner.

Partner definition

The CFTPART command describes the characteristics of each partner:

  • relative to the network/protocol environment by defining the:
    • Transfer CFT protocols which can be used with this partner and the associated SAP, protocol selector, values
    • network identification - network name, password - known by the partner/ identifying the partner
    • intermediate partner identification, if there is no direct connection
  • relative to the transfers performed by defining the:
    • transfer mode
    • translation table associated with the partner
    • partner computer operating system type, allowing the partner’s data code or file types to be deduced
    • authorized call periods (to the partner / from the partner)
    • lists of file identifiers authorized for send transfers and receive transfers
    • partner state (active or inactive, in requester or server mode)

Associated configuration parameters

Some of its parameters are used to reference configuration commands associated with this partner relative to the:

  • Network CFTxxx command
  • Protocol CFTPROT command
  • Authorization control CFTAUTH command:
    • Receiving RAUTH parameter
    • Sending SAUTH parameter
  • Translation table CFTXLATE command

Several protocols and several CFTxxx network commands, for example, can be associated with a given partner.

Partner with the same NRPART value

About the NRPART value

This facility is only available in PeSIT and OFTP (ODETTE) protocols, when using the REQUESTER mode.

In requester mode, the Transfer CFT provides the possibility of identifying itself using various identifications as regards a given remote partner: use of various values of NSPART, in association with a given NRPART.

This facility is used if the IMINTIME and IMAXTIME parameters have the same value. The time slot defined for incoming calls is zero, thereby inhibiting the use of the SERVER mode. Any transfer attempt in SERVER mode using the NSPART value so defined will fail.

Example for setting the parameters of the multiple requester identifier facility

The following commands summarize the parameter setting possible for accessing a computer B. These parameters are applicable for both the server and requester mode. This sample command summary of the parameters is followed by a diagram of the multiple identifier facility below.

CFTPART     ID     = ID_B,
     NSPART     = A,
     NRPART     = B,...
     (IMINTIME and IMAXTIME by default)

Usable in requester mode only:

CFTPART     ID     = ID_B_1,
     IMINTIME     = 0,
     IMAXTIME     = 0,
     NSPART     = A1,...
     NRPART     = B,...

 

CFTPART     ID     = ID_B_2,
     IMINTIME     = 0,
     IMAXTIME     = 0,
     NSPART     = A2,...
     NRPART     = B,...

This diagram displays the resulting parameter settings for the Requester A and Server B. Remember that you must first create a CFTPART with an ID_B for the example below to work.

A computer handling this configuration can be accessed in SERVER mode if just one CFTPART object has a parameter set with an IMINTIME value that differs from the IMAXTIME value. The server is only aware of one NRPART parameter for accessing a defined requester.

Related Links