Broadcast and collect

This section describes the following two types of transfer functions, which you can perform in requester mode:

  • Broadcast: Send one or more files or messages to several partners by activating a SEND command
  • Collect: Receive one or more files or messages from several partners by activating a single RECV command
Note When using these features with Central Governance, you must enable broadcasting for the flow. For more information, refer to the Central Governance documentation.

Broadcasting mode

This mode is used to send a file or a group of files through a single send request, to a group of partners where the number of partners in a group is limited to 200.

This diagram represents a send command for "mygroup", which is a collection of applications as defined in Central Governance, or CFTPART objects if defined in Transfer CFT.

Another method involves defining these identifiers in a file. The number of identifiers is then not limited. When using this method, if you change the runtime or import the configuration to a new environment you must remember to copy this file to the new runtime.

These two methods are mutually exclusive.

To broadcast a file called X, with N partners, a SEND PART=DEST, IDF=ID_EM, FNAME=X command generates N+1 transfer entries in the catalog that corresponds to:

  • An entry for each effective transfer (i.e. N entries)
  • And a generic virtual entry, which never leads to an effective transfer, used locally for broadcasting management

This virtual transfer is identified by a DIAGP code equal to DIFFUS, on querying the catalog. It is in the K state.

The associated post processing procedure is only executed when all the transfers are correctly completed (DIFFUS entry changes to the T or X state, depending on the compat mode).

The post processing procedure in the case of an error is executed for each transfer in the same way as for normal transfers.

To broadcast a group of P files if N partners are involved, a SEND PART = DEST, IDF = ID_EM, FNAME = <file_symb>GROUP command generates N (P+1) +1 transfer entries in the catalog corresponding to:

  • An entry for each effective transfer (i.e. N*P entries)
  • A generic virtual entry which never leads to an effective transfer, used locally for broadcasting management
  • Where <file_symb> is the OS appropriate symbol (# or @)

This virtual transfer is identified by a DIAGP code equal to DIFFUS, on querying the catalog.

  • And a generic virtual entry per partner used locally for the management of the group of files sent for the partner in question (i.e. N generic entries)

These virtual transfers are identified by a DIAGP code equal to LIST_FI, on querying the catalog.

The associated post processing procedure is activated in this case:

  • For each end of transfer, of all the files of the group, the "LIST_FI" entry changes to the T state
  • On completion of broadcasting, when all the partners have received all the files, the DIFFUS entry changes to the T or X state

Broadcasting and store and forward

You can use the store and forward mechanism for each transfer to a partner that is defined in a broadcasting list. You can also use the SEND command to broadcast from a store and forward site. The mechanisms and the associated parameter setting are described in Store and forward mode relay.

  1. SEND PART=ID_C, FNAME=FILE_TO_BROADCAST,...
  2. CFTPART ID=ID_C,..., OMINTIME=O, OMAXTIME=0, IPART=ID_B
  3. CFTDEST ID=C, FNAME=LIST, FOR=COMMUT

Collecting

This section describes the collecting mode. The collecting mode is when Transfer CFT receives one or more files or messages from several partners. The Collecting transfer mode is described in more detail in the section below.

Collecting mode

As in broadcasting, a single reception command is used to collect the partner files from a list of partners.

The collecting mechanism correspondences are displayed in the following command.

  • RECV PART=GROUP, IDF=IDF1,...
  • Defining a collecting partner list

    The list of partners can be described in one of two ways:

    • Explicitly by defining the PART parameter
    • Using a file in which this list is saved. The name of this file is defined in the FNAME parameter

    These two methods are mutually exclusive. The PART parameter cannot be used simultaneously with the FNAME parameter.

    This RECV command generates N+1 transfer entries in the catalog if there are N partners involved, the first one being a virtual transfer (generic) which never leads to a physical transfer. This transfer virtual is identified by a DIAGP code equal to COLLECT, on querying the catalog.
    The associated end of transfer procedure is only executed when all the transfers are correctly completed.

    End-of-send procedure

    When all transfers are completed, the end of transfer procedure is executed on the generic transfer.

    The error procedure is executed for each transfer in the same way as for normal transfers.

    It is a special case when a single command is used to collect all available files from all partners in the list.

    For each partner, the mechanism used is RECV IDF=*, FILE=ALL. See the paragraphs relating to the use of the RECV command for PeSIT in the Managing Protocol book.

    The end of transfer procedure is only executed when all the transfers are correctly completed (COLLECT entry changes to the T or X state). No procedure is submitted for the generic collection entry, which remains in K state when reception is complete.

    No error procedure is submitted for created entries that include errors.

    Related Links