Cross File Transfer

Un article de Wikipédia, l'encyclopédie libre.
Aller à : navigation, rechercher

CFT (Cross File Transfer) est un logiciel de transfert de fichiers développé par la société Axway, créé par Crédintrans puis cédé à Axway [1]. On parle également de "moniteur" de transfert de fichier.

CFT et Inter.Pel(Pelican), sont désormais connus sous les noms de Axway Transfer CFT, Axway Transfer InterPEL, anciennement appelé XFB (Axway File Broker).

CFT est utilisé dans les systèmes informatiques complexes et multi plate-formes qui souhaitent transmettre des fichiers en appliquant des contrôles (sécurité, accusé de réception, reprise après interruption, traçage des erreurs).

Historiquement, CFT utilisait le protocole X.25 notamment sur le réseau Transpac. Depuis 1992, Transfer CFT fonctionne sur TCP/IP et est donc utilisé sur n'importe quel réseau IP (par exemple Internet) et ce de manière sécurisée.

CFT utilise des protocoles d'échanges comme PESIT, ETEBAC3 (protocoles français utilisés pour les échanges bancaires)[2], mais aussi OFTP (protocole du secteur automobile) ce qui le rend compatible avec d’autres produits comme Inter.Pel, Connect:Express, Pelican[3], etc.

Utilisation[modifier | modifier le code]

À l'instar de FTP, CFT sert à envoyer des fichiers vers une machine distante. Mais à la différence de celui-ci, Transfer CFT est un moniteur qui supervise les transferts de fichiers et fournit un ensemble de fonctionnalités permettant de fiabiliser les interactions à base de fichiers. Ainsi, Transfer CFT gère nativement la reprise des transferts interrompus, le déclenchement des processus distants, le renommage des fichiers selon un protocole spécifique, l'application des politiques de sécurité et la transposition des tables de caractères (ASCII vers EBCDIC par exemple). C'est donc un outil qui permet d'émettre et de recevoir des fichiers de façon fiable. De plus, l'ensemble des transferts est suivi, ce qui permet d'associer des fonctions de visibilité au moniteur de transfert de fichiers Transfer CFT. L'ensemble de ces fonctionnalités permet aux utilisateurs de faire face à des contraintes réglementaires de type « Sarbanes-Oxley » et des contraintes professionnelles de types contrat de niveau de service (Service Level Agreement).

Fonctionnement[modifier | modifier le code]

Chaque site souhaitant échanger un fichier est appelé un partenaire. Chaque partenaire CFT, quelle que soit la plate-forme (Windows {NT/XP/Vista/7}, Unix/Linux, VMS, MVS, GCOS, NetWare, System i {AS400/iseries}, HP 3000, HP NonStop (Tandem)) s'appuie sur une table des partenaires distants pour effectuer les transferts de fichiers. Tout partenaire CFT voulant envoyer ou recevoir des données d'un autre partenaire doit le déclarer dans cette table appelée « le fichier des partenaires » ou annuaire CFT.

À chaque partenaire CFT sont rattachées un certain nombre d'ADL (Adresse Logique), ces ADL permettent d'identifier des applications, des utilisateurs, ou même des imprimantes. De cette manière, CFT sait en fonction de l'ADL émettrice et en fonction de l'ADL réceptrice où implanter et comment nommer le fichier sur le serveur récepteur.

Afin d'échanger des fichiers, CFT doit être installé sur chaque plate-forme. Une plate-forme qui souhaite envoyer un fichier vers un partenaire distant envoie une requête sur le réseau en précisant la plate-forme distante via son nom de partenaire. CFT fonctionne alors en mode demandeur émetteur. Lorsque le partenaire distant reçoit la requête, il vérifie que celle-ci lui est bien destinée puis crée un enregistrement dans son catalogue local qui recense la liste des traitements (traités en mode FIFO). Lorsque vient le tour de la requête, le partenaire distant établit un protocole de connexion avec le partenaire émetteur, et l'avertit qu'il est prêt à recevoir. Le serveur émetteur envoie le contenu du fichier que le serveur récepteur recopie vers un répertoire local. Ce n'est donc pas le serveur émetteur qui décide de l'endroit où va être écrit le fichier sur le serveur distant. Il ne peut non plus obliger le serveur distant à réceptionner les données (ce dernier peut être engorgé par exemple). À tout moment, CFT signale l'état de chaque transfert, s'il est en attente, en cours, abandonné ou terminé correctement, ce qui garantit le bon acheminement des données.

CFT peut aussi commuter des transferts, c’est-à-dire retransmettre des données, pour le compte d'un ou plusieurs partenaires. Par exemple, pour faire communiquer des partenaires CFT de deux réseaux distincts, il suffit de placer une plate-forme CFT en passerelle entre les deux. L'émetteur déclare que le partenaire se trouve derrière la passerelle. À chaque transfert, la passerelle reçoit le fichier, puis initie un autre transfert vers le destinataire. Afin d'assurer que le destinataire final a bien reçu les données, il convient qu'il envoie un message d'acquittement qui fera le trajet inverse.

Il est généralement conseillé de confier la gestion des annuaires CFT (nommage, mise à disposition des annuaires) à l'entité d'administration du réseau.

CFT est un produit sous licence d'utilisation. Il s'utilise avec une clé logicielle qui limite l'usage de CFT à un type de machine donné et à un nombre maximum de transferts simultanés.

L'outil Open Source de monitoring de transfert de fichiers Waarp [4] fut créé pour pallier les limites de performances de la passerelle propriétaire CFT et supporter plus de 10 000 transferts par jour dans le cadre de la plate-forme d'archivage de la DGFIP (Ministère des Finances à Bercy) [5].

Codes erreur[modifier | modifier le code]

Erreur DIAGI (Internal diagnostic code) [6]

Lors d'un transfert avec une erreur, un champ nommé diagi nous fournie le numéro de l'erreur. Si le transfert c'est bien passé le champ est a 0.

Internal diagnostic codes table
Code Event Behavior
0 The transfer has terminated correctly ASIT EXIT

Execution of normal EXECRF or EXECSF end of transfer procedures

001 SYS: Error creating the message queue or allocating the memory H status - ABORT, EXECE, ASIT EXIT
002 Context definition error H status - ABORT, EXECE, ASIT EXIT
003 SYS - Context allocation error H status - ABORT, EXECE, ASIT EXIT
100 FILE - File input/output error H status - ABORT, EXECE, ASIT EXIT
101 FILE - Error creating the receive file H status - ABORT, EXECE, ASIT EXIT
102 1.FILE - Error allocating the transfer file (physical file or VFM database logical file)

2.FILE - The receive file cannot be allocated (FDISP=OLD case)

H status - ABORT, EXECE in requester mode, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT The file is deleted

103 1.FILE - The file cannot be deleted before the receive file is created (FDISP = DELETE case)

2.FILE - Error deleting the sent file, if a deletion has been requested (FACTION = DELETE)

H status - ABORT, EXECE in requester mode, ASIT EXIT

H status - ABORT, EXECE in requester mode, ASIT EXIT in requester mode

104 1. FILE - Error opening the transfer file (physical file or VFM database logical file)

2. FILE - The receive file cannot be erased (FDISP = ERASE case): file opening problem

3. FILE - Prior to reception, the receive file could not be opened to check that it was empty (FDISP = VERIFY case)

H status - ABORT, EXECE, ASIT EXIT
105 1. FILE - Error closing the transfer file, physical file or VFM base

2. FILE - The receive file cannot be erased (FDISP = ERASE case: file closing problem

3. FILE - Prior to reception, the receive file could not be closed after checking that it was empty (FDISP = VERIFY case)

4. FILE - The sent file cannot be deleted following an erase request (FACTION = ERASE case)

H status - ABORT, EXECE, ASIT EXIT
106 FILE - Error recording the current position in the transfer file (synchronization point setting) H status - ABORT, EXECE, ASIT EXIT
107 FILE - Error setting the pointer to a resynchronization point in the file (for a transfer restart) H status - ABORT, EXECE, ASIT EXIT
108 1. FILE - Send file read error in data transfer phase

2. FILE - Prior to reception, the receive file could not be read to check that it was empty (FDISP = VERIFY case)

H status - ABORT, EXECE, ASIT EXIT
109 FILE - Data write error in the receive file H status - ABORT, EXECE, ASIT EXIT
110 1. FILE - The send file does not exist

2. FILE - The receive file to be created does not exist, even though the FDISP parameter requires it (FDISP=OLD). DIAGP is then set to NO OLD

H status - ABORT, EXECE in requester mode, ASIT EXIT in requester mode

H status - ABORT, EXECE in requester mode, ASIT EXIT in requester mode

111 FILE - Insufficient space to create the file H status - ABORT in requester mode, EXECE in requester mode, ASIT EXIT in requester mode
113 FILE - The file to be created already exists, even though the FDISP parameter prohibits it (FDISP = NEW). DIAGP is then set to NO NEW H status - ABORT, EXECE in requester mode
114 FILE - Data write error in the receive file: file space full H status - ABORT, EXECE, ASIT EXIT
115 1. FILE - The transfer owner is not authorized to access the file

2. FILE - The file cannot be deleted before the receive file has been created (FDISP = DELETE case)Protected file

3. FILE - The sent file cannot be deleted following a deletion request

(FACTION = DELETE case) Protected file

H status - ABORT, EXECE in requester mode, ASIT EXIT in requester mode

H status - ABORT, EXECE in requester mode, ASIT EXIT in requester mode

H status - ABORT, EXECE, ASIT EXIT

116 FILE - Error selecting the logical file (VFM) H status - ABORT, EXECE in requester mode, ASIT EXIT in requester mode
117 FILE - Error opening the logical file (VFM) H status - ABORT, EXECE, ASIT EXIT
118 FILE - Error closing the logical file (VFM) H status - ABORT, EXECE, ASIT EXIT
119 FILE - Error releasing the logical file (VFM) H status - ABORT, EXECE, ASIT EXIT
120 PROT - Counter check error H status - ABORT, EXECE, ASIT EXIT
121 USER - Interruption by the operator H status - ABORT, EXECE, ASIT EXIT
122 SYS - Error allocating memory when the transfer is executed D status - RESTART
123 FILE - Error setting the pointer to a resynchronization point in the file: the restart point requested by the partner is incorrect H status - ABORT, EXECE, ASIT EXIT
124 PROT - Error: transfer aborted H status - ABORT, EXECE, ASIT EXIT
126 FILE - LRECL error (record length) H status - ABORT, EXECE, ASIT EXIT
127 FILE - The receive file is not empty (FDISP = VERIFY case) H status - ABORT, EXECE, ASIT EXIT
128 1. FILE - Error deselecting the file

2. FILE - Error deselecting the receive file

3. FILE - Error accessing the send file (allocating or opening), subsequent to a file erase request (FACTION = ERASE)

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT


H status - ABORT, EXECE and ASIT EXIT unless there is an allocation error in sender server mode

129 FILE - Error during file decompression H status - ABORT, EXECE, ASIT EXIT
130 FILE - Error during file compression H status - ABORT, EXECE, ASIT EXIT
131 PROT - IDF different on ODETTE SELECT H status - ABORT, EXECE
132 PARAM - Error accessing the parameter setting indirection file (list of files, list of partners) K status - ABORT

If the file does not exist, no transfer is executed. Only the generic request remains in the catalog. If an error occurs while reading the indirection file, the transfers generated for the items (files or partners) that have already been read are executed

133 PARAM - The FOR parameter in the CFTDEST command is invalid

1. FOR=LOCAL when in the switching mode

2. FOR=COMMUT when not in the switching mode

No catalog entry
134 FILE - CFTEXIT call error H status - ABORT, EXECE, ASIT EXIT
135 1. FILE - The send file is locked

2. FILE - The receive file is locked

D status - RESTART

H status - ABORT, EXECE, ASIT EXIT

136 FILE - Duplication of the temporary file H status - ABORT, EXECE, ASIT EXIT
137 FILE - The file exists, the "rename" operation is therefore impossible H status - ABORT, EXECE, ASIT EXIT
138 1. FILE - No temporary file has been defined in the send mode and the transfer requires the COPY mechanism. No transfer is triggered and the generic request remains in the catalog

2. FILE - No temporary file has been defined in the receive mode for a file with versions or for a transfer requiring deconcatenation (COPY)

State K - ABORT

State K - ABORT, EXECE, ASIT EXIT

142 FILE - The "rename" operation has failed H status - ABORT, EXECE, ASIT EXIT
144 MVS transfer busy. State D - Retry
145 FILE+VFM FILE - The security system prohibits access to the file to be sent by the user State H - ABORT, EXECE, ASIT EXIT
146 FILE+VFM FILE - The security system prohibits deletion of the file to be sent by the user State H - ABORT, EXECE, ASIT EXIT
147 FILE+VFM FILE - The security system prohibits resetting of the file to be sent by the user State H - ABORT, EXECE, ASIT EXIT
148 FILE+VFM FILE - The security system prohibits creation of the file to be sent for the user State H - ABORT, EXECE, ASIT EXIT
149 VFM FILE - The security system prohibits access to the logical file in read-only mode State H - ABORT, EXECE, ASIT EXIT
150 PARAM - Error accessing the parameter setting indirection file when the file is a directory State K - ABORT. If the directory does not exist, no transfers are triggered and only the generic request remains in the catalog. If an error is detected when reading the directory, the transfers generated for the items (directory menus) that have already been read are triggered
151 PARAM - The selection file cannot be used on the directory specified State K - ABORT. Only the generic request remains in the catalog. No transfers are activated
152 FILE - Error during the concatenation phase at the start of the transfer or during the deconcatenation phase at the send of the transfer State H - ABORT, EXECE, ASIT EXIT
153 FILE - Error during the transfer. The file has been overwritten State K - Short transfer cannot be restarted
154 ERRTRCOD - Transcoding error: no candidate in uconf:cft.inner_charsets to convert to charset EBCDIC. State H - ABORT, EXECE, ASIT EXIT
160 REC and REC ALL - This code indicates a "no outstanding transfer or implicit declaration" type of event. Refer to the parameter [RCVALLER] in the [CFTPARM] object
220 PROT - FPDU reception H status - ABORT, EXECE, ASIT EXIT
221 PROT - Int/ext type match error: the type of a PI is not consistent with its conversion type in the external format (for example, a PI in DATE format to be converted to the STRING format) H status - ABORT, EXECE, ASIT EXIT
222 PROT - Mandatory PI missing in FPDU H status - ABORT, EXECE, ASIT EXIT
223 PROT - Invalid PI length H status - ABORT, EXECE, ASIT EXIT
224 PROT - Invalid PGI length H status - ABORT, EXECE, ASIT EXIT
225 PROT - PGI missing from the FPDU H status - ABORT, EXECE, ASIT EXIT
226 PROT - PGI embedded in another PGI H status - ABORT, EXECE, ASIT EXIT
230 PROT - Protocol error. A protocol error has been detected: DIAGP is set to the PeSIT or ODETTE code of the error detected H status - ABORT, EXECE, ASIT EXIT
231 PROT - Invalid action H status - ABORT, EXECE, ASIT EXIT
232 PROT - Event not found. An interaction not recognized by the protocol mechanisms has been received in a given transfer context H status - ABORT, EXECE, ASIT EXIT
233 PROT - Message send operation refused by the protocol used. The following protocols do not support message send operations: ETEBAC3, ETEBAC5, PESIT SIT, PESIT EXT, ODETTE K status - ABORT
240 PROT - Time-out expired (RTO parameter) D status - RETRY/COMMUT
260 SSL - Security problem K state - ABORT
261 SSL - Error linked to an internal PKI K state - ABORT
262 SSL - Error linked to the PKI system K state - ABORT
263 SSL - Error linked to an external PKI K state - ABORT
278 SSL - Invalid security profile K state - ABORT
280 SSL - Client not authorized K state - ABORT
281 SSL - Insufficient authentification level K state - ABORT
301 NET - Network addressing error (dial number) at the time of connection D status - COMMUT

The transfer will be retried for a minimum period equal to the WSCAN parameter of the CFTCAT command. The next partner address in the DIALNO parameter list (CFTnetwork command) will be used for the next retry. If the invalid address is the last one in the list, the next protocol in the PROT parameter list (CFTPART command) will be used for the next retry. If the protocol used is the last in the list, the transfer is either switched to the backup partner (IPART parameter of the CFTPART command) or aborted (K status) with code 405, while maintaining the diagnostic code of the last retry

302 NET - Network link broken (cut-off, time-out) outside the connection phase. DIAGP is then set to VNRELI D status - RETRY/COMMUT

Up to "RETRYM" retries are performed for the transfer and the access data. If the number of retries reaches the value in the RETRYM parameter, the monitor "switches" the access data. The partner access data for the next retry will relate to the next DIALNO parameter (CFTnetwork command), or the next PROT parameter (CFTPART command). The restart counter is reset to 0. If the protocol used is the last in the list, the transfer is either switched to the backup partner (IPART parameter of the CFTPART command) or aborted with code 405, while maintaining the diagnostic code (DIAGP) of the last retry

303 NET - Network parameter error at the time of connection D status - COMMUT

The transfer will be retried using the next protocol in the PROT parameter list (CFTPART command) as the new partner access point. If the protocol used is the last in the list, the transfer is either switched to the backup partner (IPART parameter of the CFTPART command) or aborted (K status) with code 405, while maintaining the diagnostic code of the last retry (see below)

350 The user requesting the transfer is not authorized to perform it State H
351 The remote requester is not authorized to use the transfer. The transfer was in the H state. The monitor is running in the server/sender mode State H
352 The remote requester is not authorized to create a transfer. The monitor is running in the server/sender mode and the transfer was to be created via a CFTSEND IMPL=YES State H
399 Unreferenced error
401 PARAM - Embedded broadcast list explicitly refused K status - ABORT

In the case of an explicit "multi-partner" request (PART parameter in the CFTDEST command), a single partner, itself defined as a partner list, aborts the request; only the generic list request set to the K status remains in the catalog. No transfer is executed. In the case of a "multi-partner" request via an indirection file (FNAME parameter in the CFTDEST command), only the requests prior to the error are executed

402 PARAM - The PROT parameter of the CFTPART command does not belong to the active protocol list (PROT parameter of the CFTPARM command) K status - ABORT
403 PARAM: Invalid password No CAT
404 PARAM: Open mode not authorized No CAT
405 OUT: The monitor has tried all possible partner access points: DIALNO, PROT, IPART K status - ABORT, EXECE, ASIT EXIT
406 1. OUT - Maximum number of retries reached (RESTART parameter).

DIAGP is set to MAXRST

2. AUTH - The required start time for execution of the transfer is outside the authorized time slot (OMINTIME / OMAXTIME); there is no other possible protocol for this partner. DIAGP is set to CALL OUT


3. AUTH - The network resource associated with the protocol does not accept outgoing calls; there is no other possible protocol for this partner

DIAGP is set to L 0B 022

4. PARAM - There is no CFTnetwork command for the partner and for the last protocol in the list (CFTPART PROT parameter). DIAGP is set to MAXRST

5. OVER - The monitor has reached the limit (RESTART parameter) of authorized retries for the last partner protocol (CFTPART PROT parameter). DIAGP is set to MAXRST

6. PARAM - The SROUT parameter of the protocol cannot be used to execute the transfer; there is no other possible protocol for this partner. DIAGP is set to SROUT

K status - ABORT, EXECE

K status - ABORT, EXECE

K status - ABORT, EXECE

K status - ABORT, EXECE

K status - ABORT, EXECE

K status - ABORT, EXECE

408 PARAM - PART parameter not described by a CFTPART command K status - ABORT

If a single CFTPART command is missing from an explicit "multi-partner" request (PART parameter in the CFTDEST command), the request is aborted. Only the generic list request, set to the K status, remains in the catalog

No transfer is executed

In the case of a "multi-partner" request via an indirection file (FNAME parameter in the CFTDEST command), only transfers with no partner defined are halted

The other transfers are executed

Note:however, complete broadcasting (or collection) will be unsuccessful without operator intervention (partner definition and transfer retry)

The end of transfer procedure will not be executed

409 PARAM - Unknown NPART parameter H status - ABORT
410 PARAM - Unknown CFTPROT command K status - ABORT
411 AUTH - File identifier (IDF) not authorized K status - ABORT

If the IDF for one of the partners in an explicit "multi-partner" request (PART parameter in the CFTDEST command) is not authorized, the request is aborted; only the generic list request set to the K status remains in the catalog

No transfer is executed

In the case of a "multi-partner" request via an indirection file (FNAME parameter in the CFTDEST command), only transfers, the IDFs of which are not authorized for the partner (CFTAUTH command) are set to halted

The other transfers remain active. Note:however, complete broadcasting (or collection) will be unsuccessful without operator intervention (grant authorization to the partners and retry the transfer); the end of transfer procedure will not be executed

412 DATA - Catalog access error No change in the status or in DIAGI in the catalog as the file cannot be accessed
413 AUTH - File identifier not authorized H status - ABORT
414 1. AUTH - The start time for execution of the transfer is outside the authorized time slot (MAXTIME / MAXDATE of the SEND / RECV command)

DIAGP is then set to OUT TIME

2. PARAM - The outgoing time slot of the partner is null (OMINTIME / OMAXTIME)

There is no intermediate partner

DIAGP is then set to CALL OUT

3. AUTH - No outgoing call authorized for the network resource (CFTnetwork CNXOUT=0)

DIAGP is then set to NO CALL

K status - ABORT

K status - ABORT

K status - ABORT

415 OVER - Maximum number of partners reached D status - NEXT
416 1. OVER - Maximum number of transfers reached (MAXTRANS parameter)

The transfer cannot be executed

DIAGP is then set to MAXTRANS

2. OVER - Maximum number of connections reached for the network resource

The transfer cannot be executed

DIAGP is then set to MAXCNX

D status - NEXT

D status - NEXT

This status corresponds to a transfer refusal by the protocol task of the monitor, even though the scheduler has not reached the MAXTRANS limit

This occurs when the protocol task maintains active connections after transfers have ended

417 1. OVER - Maximum number of file tasks reached (MAXTASK parameter)

The transfer cannot be executed

2. SYS- Insufficient system resources available to execute an EXIT task

The transfer cannot be executed

D status - NEXT

D status - NEXT

418 OVER - The total number of transfers in progress exceeds one of the CNXIN, CNXOUT or CNXINOUT parameters for the partner

The transfer cannot be executed

D status - RESTART

If the number of retries exceeds the value of the RESTART parameter (CFTPROT command), the monitor switches to the access data of the next protocol for this partner

419 DATA - The transfer to be retried is not in the catalog at the server end ABORT
420 DATA - On reception of a REPLY-type message, the original transfer concerned by this reply is not found in the catalog at the server end ABORT
421 1. SYS - Error executing a monitor file task

2. SYS - Error executing a monitor EXIT task

D status - NEXT

K status - ABORT

422 PARAM - (Etebac 3) Undefined parameter card (CFTETB command) in requester mode K status - ABORT
423 SYS or PARAM - EXIT task creation error H status - ABORT
424 PARAM - CFTXLATE command not found for this transfer direction and the source and target alphabets H status - ABORT
425 USER (Directory Exit) - Call collect refused. No CAT
426 USER (Directory Exit) - Error in the Directory Exit task No CAT (server mode)

State K - ABORT (requester mode)

430 PARAM - Transfer is inactive on the requester side State D - ACT
451 1. PROT - (PeSIT) Reception of a protocol connection refusal (AckCONNECT FPDU). (Odette) Reception of a protocol connection refusal (ESID). DIAGP is then set to RELEASE

2. PROT - (PeSIT) (Odette) Violation of the protocol specifications (unknown FPDU, or invalid contents for example). DIAGP is then set to ACO in or RCO in ennsnn

3. PROT - (PeSIT)(Odette) Connection time-out reached without response (DISCTC parameter of the CFTPROT command). DIAGP is then set to TIMEOUT

D status - RESTART

D status - RESTART

D status - RESTART

452 PROT - (PeSIT) (Odette) Reception of a negative message confirmation FPDU H status - ABORT, EXECE, ASIT EXIT
453 PROT - (PeSIT) (Odette) Reception of a negative create confirmation FPDU H status - ABORT, EXECE, ASIT EXIT
454 PROT - (PeSIT) Reception of a negative select confirmation FPDU H status - ABORT, EXECE, ASIT EXIT
455 PROT - (PeSIT) (Odette) Reception of a negative deselect confirmation FPDU H status - ABORT, EXECE, ASIT EXIT
456 PROT - (PeSIT) Reception of a negative open confirmation FPDU H status - ABORT, EXECE, ASIT EXIT
460 PROT - (PeSIT) Reception of a negative end of transfer confirmation FPDU H status - ABORT, EXECE, ASIT EXIT
600 FILE - (PeSIT) (Odette) Transfer aborted by the remote end: file input/output error - PeSIT / Odette code: see DIAGP H status - ABORT, EXECE, ASIT EXIT
604 FILE - (PeSIT) Transfer aborted by the remote end: file opening error H status - ABORT, EXECE, ASIT EXIT
605 FILE - (PeSIT) Transfer aborted by the remote end: file closing error H status - ABORT, EXECE, ASIT EXIT
610 FILE - (PeSIT) (Odette) (Etebac3) Transfer aborted by the remote end: the file to be read does not exist H status - ABORT, EXECE, ASIT EXIT
611 FILE - (PeSIT) Transfer aborted by the remote end: insufficient space to create the file H status - ABORT, EXECE, ASIT EXIT
613 FILE - (PeSIT) Transfer aborted by the remote end: the file to be created already exists H status - ABORT, EXECE, ASIT EXIT
614 FILE - (PeSIT) Transfer aborted by the remote end: file space full H status - ABORT, EXECE, ASIT EXIT
620 PROT - (PeSIT) Transfer aborted by the remote end: counter control error H status - ABORT, EXECE, ASIT EXIT
621 PROT - (PeSIT) Transfer aborted by the remote end: interruption by the operator H status - ABORT, EXECE, ASIT EXIT
626 PROT - (PeSIT) (Odette) Transfer aborted by the remote end: error in record length H status - ABORT, EXECE, ASIT EXIT
635 FILE - (PeSIT) Transfer aborted by the remote end: file access conflict H status - ABORT, EXECE, ASIT EXIT
660 REC - Error 660, ASE 205 on the requester side K state - The remote download is stopped when there are no other files available
720 1. PROT - (PeSIT) Protocol abort by the remote end: incorrect FPDU (transmission error)

2. PROT - (Odette) Protocol abort by the remote end: negotiation error

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

722 PROT - (PeSIT) Protocol abort by the remote end: missing PI H status - ABORT, EXECE

H status - ABORT, EXECE, ASIT EXIT

730 1. PROT - Protocol error

2. PROT - (PeSIT) Transfer aborted by the remote end due to protocol error - PeSIT code: see DIAGP

3. PROT - (Odette) Reception of an ESID FPDU

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE

740 NET - (PeSIT) Transfer aborted by the remote end: time-out - PeSIT code: 317 D status - RETRY
850 PROT - (PeSIT) Protocol rejection by the remote end: authorization problem H Status - ABORT, EXECE
903 PROT - (ETEBAC 3) Invalid password H Status - ABORT, EXECE
904 PROT - (PeSIT) Protocol rejection by the remote end: transfer denied (open mode, authorizations for example) H status - ABORT, EXECE, ASIT EXIT
908 PROT - (ETEBAC 3) Partner unknown H status - ABORT
909 PROT - (PeSIT only) Protocol rejection by the remote end: requestee identifier unknown D status - RESTART
916 PROT - (PeSIT only) Maximum number of transfers reached at the partner end (MAXTRANS parameter) D status - NEXT
919 Restart context not available H status - ABORT, EXECE
920 PROT - (PeSIT) Protocol rejection by the remote end: on reception of a REPLY-type message, the partner does not find the transfer concerned by this reply in its catalog D status - RESTART
922 PROT - (ETEBAC 3) Error on parameter card H status - ABORT, EXECE
925 Call collect refused by the remote system No CAT
928 Invalid caller number H status - ABORT, EXECE
930 PROT - Partner is inactive on the server side ACT status
963 PROT - Protocol pre-connection phase rejected by the remote end (PeSIT LOGON): LOGON string rejected K status - ABORT, EXECE, ASIT EXIT
970 PROT - Protocol pre-connection phase rejected by the remote end (PeSIT LOGON): password expired K status - ABORT, EXECE, ASIT EXIT



Notes et références[modifier | modifier le code]

  1. Transfer CFT
  2. http://www.prod-info.fr/CFT/CFT-Memento.html
  3. http://www.01net.com/editorial/164651/lintegration-dapplications-un-chef-dorchestre-plein-dambition/
  4. http://www.waarp.it/fr/
  5. http://linuxfr.org/news/waarp-le-moniteur-de-transfert-de-fichier-open-source
  6. http://wiki.tuxunix.com/index.php/Doc_CFT

Liens externes[modifier | modifier le code]