tbt/400.com French version
French version
  Home page Info. request Contact us Wished Evolutions Download


Protocol supported by TBT/400

General information:

Data communications are being increasingly used for exchanges between banks and their clients. The protocol is defined by interbank standards, and in particular ETEBAC 3 covering transfers over the Transpac networking X25, X32 or ISDN procedure.

The Remote ETEBAC 3 interface in handles file transfers under this protocol, from both Customer to Bank and Bank to Customer. It ensures transfer of the parameter card, checking of same, and the transfer itself. Depending on the protocol rules, TBT/400 is in this case always initiated by the call.

The server ETEBAC allows any workstation or computer of the 'client' type to log on to TBT/400 under the ETEBAC protocol in order to transfer files.

The main functions of Etebac are:

Access security

TBT/400 uses the internal directory. All ETEBAC parties must be listed under a logical name, which must be used for identity purposes on the parameter card. Updates take effect immediately. Each party has several "attributes", including a password, and an optional list of X25 call numbers. The party can only call up under ETEBAC 3, and exclusively from one of these numbers (maximum safety option). In addition, parties may be authorised or not depending on particular applications.



Identification of applications

Once a call has been identified, and therefore the ETEBAC protocol has been selected, an application identification comes in to effect. This is accompanied by receipt and decoding of a parameter card.

The structure of this card is defined at installation (position and length of each field), and includes:

  • a user code (20 characters maximum),

  • one or two passwords (20 characters maximum),

  • an "Application requested" (8 characters maximum),

  • a date (YYMMDD format or N format signifying date - N (optional),

  • a sequence number (6 characters maximum, optional),two free selection criteria (8 characters maximum each, optional),

  • the number of records to receive, in the server direction (8 characters maximum, optional).



File provisions

Any file provided for receiving by the Client (direction "R" on the parameter card) will have previously been defined to TBT/400 by the transmission API. A provided file is a file issued in the direction "TBT/400" to the "ETEBAC" party, for an Application, a date and a defined sequence number. The transmission API validates these notions according to which items were completed (Directory, application table). The various updates are synchronous, that is, they take effect immediately. During dropping of a message, the status of the TBT/400 sub-system is not important: the drop can take place with the kernel stopped or active. The drop does not presume the type of output (BSC or X25).

In addition, TBT/400 offers flexibility in terms of file forwarding. For example, during the request to send, an file duplication option may be employed, in which case TBT/400 frees the initial file as soon as the query has been lodged, and will then start clearing up the files according to various optional criteria:

  • clearing after transmission onto the network: in this case, the user can only collect the file once;

  • clearing according to history file (with reference to general timeframe): the file flips into the history file after sending;

  • clearing without reference to history file (with reference to general timeframe): part of the automatic component clear-up routine.


Processing of incoming calls

When TBT/400 receives an incoming call of the ETEBAC type, it reads and decodes the parameter card, and after certain checks, either accepts or refuses it. Under ETEBAC 3, the refusal is identified by a "NOKxxxx" response and waiting for the following parameter card; under ETEBAC 1-2, there is a sharp break in the communication.

Related checks:

  • validating of transmission direction ("C "or "A" - calling or answering),

  • validating of the user code according to the directory,

  • validating of the calling number (if requested, in which case only X25 is authorized),

  • validating of the application,

  • validating of the date (by default, today's date + increment (numeric, configurable),

  • validating of the sequence number (by default 1),

  • if direction R, validating of presence of file that must be dropped first. An option (declared during at installation), allows collecting of several files at a time.

When access has been authorized and validated, the transfer can take place:

  • If receiving (direction "C"), a file is allocated dynamically, and an event of the "message" type is inserted in the message waiting line after reception. A processing application can then be started immediately by TBT/400, or later in a given time slice.

  • For sending (direction "A"), an event of the message acknowledgement type is inserted in the message waiting line, to inform the application. This event is positioned only during the first "grab", if the "multiple collect" option was activated.


Dual signature or order confirmation

TBT/400 has another standard feature in the form of a dual signature option: in this case, the recipient must confirm his command by sending a second password, either when sending the file, or later during another call, by sending a second parameter card with the second password. The file is only considered as runnable if both valid passwords were received.


<< Other protocols supported by TBT/400 >>

   For more information, visit the web site www.etebac.com

All rights reserved © 2015 IPLS - Legal informations >>Top Updated: Février 16, 2018 12:55