Acceptance by Transfer CFT:

Process whereby a transfer request is taken into account by Transfer CFT when it is recorded in the catalog.

Accounting file:

File containing the descriptive and quantitative properties of all successfully completed transfers (defined via CFTACCNT, file created via CFTFILE TYPE=ACCNT).

Acknowledgement anticipation window:

Parameter determining the number of synchronization points that the file sender can set without waiting for an explicit response from the receiver for each point.

This mechanism is used by the PeSIT protocols.

Acknowledgement (EERP):

See EERP (End to End Response) acknowledgement.

Authorized identifiers:

List of model file identifiers (IDFs) governed by the same transfer authorizations or denials (user-defined in the CFTAUTH command).

Availability for Transfer CFT:

Process whereby a request is made available to the monitor when it is processed in the communication medium.

Availability for the partner:

Process whereby a file is made available to a partner so that it can be sent on reception of the request from the partner. The file can be made available implicitly (see Implicit send) or explicitly, in which case the transfer is put on hold in the catalog (SEND STATE=HOLD).



Sending of a file or group of files to a set of partners defined in a list via a single request (partner list defined in CFTDEST).

Broadcast list:

List defined in parameter or file form to send a file or group of files to one or more partners via a single request (user-defined in the CFTDEST command).


Card (parameter):

See Command (parameter).


File containing the control and monitoring data associated with transfers (usage mode defined via CFTCAT, file created via CFTFILE TYPE=CAT).

Catalog entry:

Record corresponding to a transfer in the catalog file.

Catalog identifier:

See IDTU (catalog identifier).

Catalog sharing:

Option available in some environments, whereby the user can monitor several instances of Transfer CFT via a single catalog file.

CD (Change Direction):

Odette protocol service whereby a token is exchanged between partners. Only the partner in possession of the token can send a file.


Programming interface used to integrate Transfer CFT into applications developed in either C or COBOL.


Command used to define the accounting data logging mode for successfully completed transfers.




Command used to define a list of file identifiers governed by the same transfer authorizations or denials.

This list can be stored in a file or defined explicitly via the IDF parameter in the command.


Command used to set transfer catalog management parameters.


Command used to set parameters controlling communications between user programs and the Transfer CFT. See also Communication medium.


Command used to define a list of partners for broadcast/collect operations. This list can be stored in a file or defined explicitly via the PART parameter in the command.


Command used to create or delete Transfer CFT files (parameter, partner, catalog, accounting, log and communication files).


Command used to set the log file management parameters for the monitor.


Main Transfer CFT task used to schedule transfers. It controls transfer execution and authorizations.


Command used to define the properties of a network resource.


Command used to define a file transfer protocol and the way in which it is implemented.


Command used to define the properties of a given type of transfer (storage of the data received and execution of receive operations).


Command used to define the properties of a given type of transfer (access to the data to be sent and execution of send operations).


File access tasks that can be activated concurrently. Depending on the configuration, a CFTTFIL task can be permanent or will stop on completion of the transfers for which it was created.


Protocol task giving access to the resources defined via CFTNET commands and the application-level protocols declared in CFTPROT commands.


Batch or line mode tool giving access to all Transfer CFT functions and parameters.


Command used to define user conversion tables. Files can be converted in both the send and receive modes, irrespective of the protocol used.


Coding or encryption technique whereby information is protected against illicit read operations.

The information can only be read or processed by entities in possession of the ciphering "key". See also Cryptography.

Closed mode:

Mode whereby only the receiver can determine the physical name (location) of the received file.


Reception of a file or group of files from several partners via a single request (list of partners defined in CFTDEST).

Command (parameter):

Command used to declare a monitor and set up the working environment.


Instructions used in Transfer CFT to configure the monitor and working environment and to control the monitor and associated transfers.


The types of compression are:

  • 01: compression of a string of characters (compression of blank characters)
  • 02: horizontal compression (repetitive characters are deleted in the record)
  • 04: compression of characters (each alphanumeric character is compressed)
  • 08: vertical compression (only the characters which are different from the previous record are transferred)

Communication medium:

File or mailbox used to transmit the requests submitted to the monitor (defined via CFTCOM, file created via CFTFILE TYPE=COM).


Property resulting from ciphering data so that it cannot be read by an unauthorized third party on the network.


Translation of data, character by character, from one data coding system to another (EBCDIC to ASCII for example). The conversion can take place "ON LINE" during transmission, or "OFF LINE" (optionally defined in the CFTXLATE, SEND/RECV, CFTSEND/CFTRECV and CFTPART commands).

Conversion table:

Table defining the correspondence between two coding systems and used during conversion. The conversion table, defined for each transfer direction and conversion mode, can be internal to Transfer CFT or created by the user (CFTXLATE command).


Graphic user interface for Transfer CFT.


For the Odette protocol, maximum number of data packets that the sender can transmit before the server must acknowledge reception by assigning a new "credit".  

Transfer CFT simulates a synchronization point for each credit message sent or received.


Data resulting from a ciphering operation.


Discipline comprising data transformation principles and mechanisms with the aim of masking the meaning of data.

There are two main systems:

  • Shared-key or symmetric systems for which the ciphering and deciphering keys are the same; see DES (IBM Data Encryption  Standard)
  • Dual-key or asymmetric systems for which the ciphering and deciphering keys are different; see RSA (Rivest Shamir Adelman)


Request to trigger a transfer at regular intervals. The interval can be expressed in minutes, days or months (defined in CFTSEND, CFTRECV and RECV).


Data compacting:

Data compression mode specific to the PeSIT protocol with a CFT profile. Only the most significant half-bytes in numbers or spaces coded in EBCDIC are transferred.

Data compression:

Action whereby the volume of data sent and therefore the transfer times are reduced.

Data integrity:

Property whereby the system guarantees that the data has not been accidentally or intentionally modified or deleted.

DES (IBM Data Encryption Standard):

Cipher algorithm based on a symmetrical key. See also Cryptography.

Direct transfer:

Transfer that does not use the store and forward mechanism.

Directory exit:

In server mode, exit substituting the standard controls applied by Transfer CFT when a remote partner requests that a session be opened. In requester mode, it is used to supply all information required to establish a connection with a remote partner.

Dynamic partner:

Partner created when the connection is established, based on a model partner (defined in CFTPART).



Transfer protocol used by German and French banking institutions. Operates as an Internet protocol, enveloping XML data for transfer either with or without TSL.

EERP (End to End Response) acknowledgement:

Odette protocol service used to generate an end-to-end acknowledgement for the transfer at application level. In Transfer CFT, this acknowledgement takes the form of a reply-type message (see Reply message).

End of transfer exit:

Exit called at the end of a file or message transfer to automate any type of processing deemed necessary after the transfer.

End of transfer procedure:

Procedure to be submitted by the monitor when a file or message has been successfully sent or received (defined in CFTPARM, CFTSEND or CFTRECV).

Environment variable:

Information that can be accessed by programs via a predefined symbolic name and that contains a character string initialized when the execution environment was set up for the programs (OS-dependent feature).

Error procedure:

Procedure executed when a transfer is aborted or interrupted (defined in CFTPARM).


User function, in the form of a subprogram, called directly by the monitor (defined in CFTEXIT).


File exit:

Exit used to take control at various stages of a file transfer.

File identifier:

See IDF.

File transfer protocol or application protocol:

Set of rules governing dialog and exchange management between two standard Transfer CFTs. These standards are based on a network access mode defined in CFTPROT. See PeSIT.

FPDU (File Protocol Data Unit):

Data unit for the PeSIT protocol. Protocol-level message supporting dialog between two PeSIT "protocol layer" entities. It includes a fixed and a variable part. See also PI (Parameter Identifier).


Horizontal compression:

Replacement of characters repeated within a record by a delimiter, a counter or a single occurrence of the character.



Presentation phase at the start of a connection.

The partners submit their names and passwords and the connection is then either accepted or refused.


Model file identifier. See also Model file.


Transfer identifier. Label associated with each transfer for a given partner and in a given direction.

IDTU (catalog identifier):

Unique identifier assigned to a transfer by Transfer CFT. It is used in local transfer monitoring and catalog list commands.

Implicit send:

Mechanism used to make a file available on a permanent basis (CFTSEND IMPL=YES). See also Availability for the partner.

Integrity checking:

Process whereby data is protected against intentional deletion or tampering by an unauthorized third party on the network.


List exit:

File exit used by remote partners to query the Transfer CFT catalog on a host.

List of model file identifiers:

See Authorized identifiers.

Log file:  

File containing all messages recording monitor activity related events (defined via CFTLOG, file created via CFTFILE=LOG).



Medium used to transmit the requests submitted to the monitor (defined via CFTCOM, created via CFTFILE TYPE=COM). See also Communication medium.


Character string specified via a send command and sent by the monitor in a specific transfer. In Transfer CFT and for given protocols, two type of messages can be sent: simple messages or reply messages.

Model file:

Each file transfer is processed by Transfer CFT in line with a model file or file identifier (IDF) associated with the data (or physical file) to be sent. The processing and data file definition parameters are specified in the CFTSEND configuration command for send operations and in the CFTRECV command for receive operations.

Monitor ( Transfer CFT):

Control programs scheduling transfer requests, file access operations and transfers using network communication facilities.


Process whereby Transfer CFT activities are controlled by querying the catalog (transfer properties and state) and the log file (chronological history of all events in information or error message form).


Network resource:

Entity via which connections can be established (defined in CFTNET).

NSDU (Network Service Data Unit):

Data unit for the network service in the PeSIT protocol. It is made up of the data exchanged between two users and can contain several FPDUs. See also rrusize and srusize.



European body in the automotive industry governing transfer exchange standardization (Organisation de Données Echangées par TéléTransmission en Europe - European Organization for Data Transmission). This organization defined the Odette File Transfer Protocol (OFTP) used particularly to exchange data between car manufacturers and their suppliers. This protocol is based on X.25-type links (TCP/IP in future versions). The two terms OFTP and ODETTE are sometimes used interchangeably.

OFTP (Odette File Transfer Protocol):


Open mode:

Mode whereby a requester can determine, in send mode, the physical name to be assigned to the transferred file on the receiver site and in receive mode, the physical name of the file to be received.



Logical entity, to which Transfer CFT can send data and from which it can receive data. A partner generally corresponds to a remote file transfer monitor or a subset of a remote monitor (defined in CFTPART, file created in CFTFILE TYPE=PART).


PeSIT (Protocole d'Echanges pour un Système Interbancaire de Télé- compensation):

Exchange protocol for an interbank clearing system, first used within the SIT network and then enhanced by defining broader usage profiles. The non-SIT and secured profiles can be used for non-banking applications.

PI (Parameter Identifier):

Number identifying the parameter type carried in a PeSIT FPDU.

Programming interface:

Set of rules defining how a service is used by an application. See CFT API .


Reading or read-mode transfer:

For the PeSIT protocol, triggering by the requester of a file transfer from the server.


Command triggering a file receive operation. The transfer properties must be defined in the RECV command itself or in the associated CFTRECV command.

Reply message:

Character string used in the PeSIT E, PeSIT D (CFT profile) or Odette protocols and corresponding to a reply to a previous transfer from the remote partner concerned by the message. Used for example at the end of a file transfer to inform the sender that all receive-related operations have been successfully executed.


Local request submitted to the communication medium but not yet recorded in the catalog file by the monitor.


Partner initiating the connection.

Requester mode:

Mode whereby the monitor initiates the connection with the remote partner.


Partner or application requesting the connection and wishing to receive a file.


Partner or application requesting the connection and wishing to send a file.


Protocol-based mechanism whereby an exchange can be restarted from the last synchronization point acknowledged.

This mechanism is used during data transfer following a recoverable incident that did not cause the transfer to abort (ODETTE and PeSIT).


See Store and forward mode and Store and forward mechanism.

RSA (Rivest Shamir Adelman):

Cryptographic algorithm based on asymmetric keys. See also Cryptography.


Secondary file:

File used when switching log or accounting files. See Switching.

Secured mode:

Means whereby data can be ciphered or sealed using DES- or RSA-type algorithms. See Ciphering, DES (IBM Data Entrcyption Standard) and RSA (Rivest Shamir Adelman).


Batch or interactive mode utility processing all security system commands.


For the PeSIT protocol, possibility of transferring records using successive data units (NSDU).


Command used to submit a file, simple message or reply send request. The transfer properties can be declared in the SEND command itself or in the associated CFTSEND command.

SEND (implicit):

See Implicit send and Availability for the partner.

Send on hold:

Explicit provision of a file to be sent to a partner. See also Availability for the partner.

Sending of a group of files:

Sending of several files in a single request, using either an indirection file containing the list of files or a wildcard-based selection.


Partner receiving and accepting the connection.

Server mode:

Mode whereby the monitor responds to an incoming connection and accepts the transfer requests.


Partner receiving and accepting the connection and then receiving the file.


Partner receiving and accepting the connection and then sending the file.

Simple message:

Character string used with the PeSIT E protocol to exchange small volumes of freeform information between partners.

Software protection:

Key associated with the contractual conditions in which the software is used and provided when the product is installed. To use Transfer CFT, the key must be specified in the CFTPARM command.

Store and forward mechanism:

Routing technique used by Transfer CFT, whereby a file or message is received on a store and forward site and immediately forwarded to the next adjacent partner.

Store and forward mode:

Transfer CFT feature whereby files can be routed via one or more intermediary Transfer CFT sites, called store and forward sites. This feature is only available from a requester/sender (write-mode transfer). See Store and forward mechanism.

Store and forward site:

See Store and forward mode and Store and forward mechanism.


Operation whereby the monitor log or accounting files are swapped so that two versions are used alternately (operator SWITCH command).

Symbolic variable:

Transfer CFT variable representing a data item associated with the transfer and for which the value will only be known when the transfer is executed and not when the parameters are set.

Synchronization interval:

Maximum volume of data that a sender can transmit between two consecutive synchronization points. If the data is compressed, the interval calculation is based on the volume of data after compression. This concept is used for the PeSIT protocols.

Synchronization point setting:

Means whereby the sender transmits markers assigned sequence numbers during data transfer, these markers being acknowledged by the receiver and allowing the transfer to be restarted by either end following an incident.



Time during which calls are authorized to or from a partner (defined in CFTPART, CFTSEND or CFTRECV).


Data transport and exchange of the actions to be taken on the data (read/write/create/delete) from one computer (partner) to another via a network. One of the partners is the SENDER and the other the RECEIVER.

Transfer identifier:

See IDT.

Transfer owner:

A transfer owner is associated with each transfer. See userid.

Transfer restart:

Protocol-based mechanism whereby a transfer can be restarted at the point at which it was interrupted. Depending on the protocol used, the transfer restarts at the current record (ODETTE) or at the last synchronization point acknowledged (PeSIT) prior to the transfer interrupt.

Transfer resumption:

Means whereby a suspended transfer can be resumed either automatically or manually.

Transfer scheduling:

Process whereby transfers are executed in line with their priority, the number of concurrent transfers allowed and the timeslot or period (cycle) defined. See also Cycle and Timeslot.

Transfer state:

Transfers can be set to one of six states.

  • C: The transfer is in progress (Current).
  • D: The transfer is available (at Disposal) and will be triggered automatically as soon as the Transfer CFT resources and partner access authorizations allow it.
  • H: The transfer is pending (on Hold) on the initiative of the transfer requester, an operator (HALT command) or the monitor subsequent to an incident. The transfer can be resumed by the operator or the remote partner.
  • K: The transfer is pending (Kept) on the initiative of the transfer requester, an operator (KEEP command) or the monitor subsequent to an incident. The transfer can only be resumed by the operator.
  • T: The transfer has successfully Terminated.
  • X: All end of transfer operations have been successfully eXecuted and the monitor has been notified via the END command.


Virtual circuit assigned a connection identifier and maintained throughout the transfer (pipe, window mechanism).

Vertical compression:

Comparison between the current record and the previous record with the aim of transferring only those characters that are different.


Writing or write-mode transfer:

For the PeSIT protocol, sending of a file from the requester to the server.

Related Links