2023年6月26日发(作者：)

This chapter lists the transfer diagnostic codes specific to the CFT monitor.

⊙ CFT常见诊断码分类支持

CODE

EVENT

（1）传输文件配置错误（物理文件或VFM库逻辑文件）

（2）接收文件不能配置（FDISP=OLD case）

ERROR TYPE

RESPONSE

IMEX

IMEX

IMEX

ESO/PROD

IMEX

IMEX

IMEX

OPERATOR

IMEX

ESO/PROD

IMEX

IMEX

LGT（用于分析）LGT（用于分析）TRVD/EOOP

TRVD/EOOP

IMEX

LGT（用于分析）LGT（用于分析）101

接收方创建接收文件错误

102

FILE

FILE

FILE

FILE

FILE

FILE

USER

PROT

FILE

FILE

FILE

PROT

PROT

NET

OUT

FILE

PROT

PROT

104

传输文件打开错误（物理文件或VFM库逻辑文件）

107

设置指向文件（for a transfer restart）中再同步点的指针时错误

110

要发送的文件不存在

116

逻辑文件（VFM）选择错误

121

被运行员中断

124

被中止的传输

129

文件解压时出错

136

临时文件复制

137

文件存在，因而RENAME操作不可能

230

协议错误：DIAGP is set to the PeSIT or ODETTE code of the error240

Time-out expired（RTO参数）

+302

网络连接超时（cut-off，time-out）outside the connection phase

405

MONITOR尝试了所有可能的PARTNER访问点：DIALNO，PROT，IPART

113

要创建的文件已经存在，但是FDISP参数禁止（FDISP=NEW）FILE

+600

（PeSIT）Transfer aborted by the remote end：文件输入/输出错误620

（PeSIT）Transfer aborted by the remote end：counter control error621

（PeSIT）Transfer aborted by the remote end：interruption by the

operator

740

Transfer aborted by the remote end：time-out

916

（PeSIT only）Partner端自动发送重试次数达到了最大值（MAXTRANS parameter）

（PeSIT）Protocol rejection by the remote end：on reception of a

NET（PeSIT）

LGT（用于分析）PROT

ESO/PROD

920

REPLY-type message，the partner does not find the transfer concern

PROT

by this reply in its catalog。传接双方速度不协调所致

注：000

+，更多信息见《DIAGI-CFT Internal Diagnostics》。

CFT文档

1/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

CFT菜单模式-UNIX平台

在UNIX平台的CFT菜单模式，通常按F3键可从当前菜单页面回退到上一级菜单页面，同时按Ctrl和X键可从CFT菜单模式退出。

1> 菜单首页

各页面快捷键可看菜单最下端，如下：

其中，F7（或在COMMAND行输入字符“P”，然后回车）为向上页翻，F8（或在COMMAND行输入字符“N”，然后回车）为向下页翻。

2> 在COMMAND行输入“gs”，回车进入菜单“Select and sort catalog entries”

CFT文档

2/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

3> 示例-查询指定的IDF（如PWDPND48）信息

如果所显示的结果为很多行内容，则可以按要求排序（如下图中是指定以IDF、IDT、PART为顺序排列的）。

IDF指定后回车可进入如下图界面，其中DIAG列为CFT传输返回码（返回码为0时表示传输正常），%列为文件传输的百分率（100表示文件传输了100%）。

CFT文档

3/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

注意：当文件传输的百分率大于0小于100时，表示文件接收方接收到的文件不完整。

CFT文档

4/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

CFT Internal Diagnostic Codes

This code provides general information on the cause of the error. It is independent of the

operating system and of the network access method used for the transfer. Some codes are specific

to a protocol; indication is provided in the label if need be.

Codes with a value between 001 and 499 indicate a local fault; values between 501 and 999

correspond to a fault reported by the partner.

★ Event

The "Event" column explains the possible cause(s) of the transfer error.

Brief information on the type of error which caused the transfer failure:

Type Information

SYS

NET or PROT

FILE

DATA

PARAM

AUTH

OVER

OUT

USER

SSL

System error

Error detected by the network layers (CFT layers, manufacturer network

layers)

Fault detected by the file transfer protocol

Transferred file access error returned by the operating system

Error accessing CFT basic data: parameter, partners, catalog, communication,

log, statistics and secondary indirection files (lists of partners, files, and so on)

Transfer execution error following a parameter setting error

Transfer denied following an authorization check by CFT

The transfer cannot be executed because the monitor's resources are saturated

or a parameter setting limit has been exceeded

The transfer request is aborted after the maximum number of retries

The transfer is interrupted following an action by the operator

Incident detected by the secured protocol SSL（incident：事件，事变）

★ Behavior

The "Behavior" column provides information on the behavior of the monitor following a

transfer failure.

（1）The resulting status of the transfer: D, H or K:

1）D: the transfer can still be executed using the RESTART, NEXT, RETRY or COMMUT

mechanisms

2）H or K: the transfer is aborted, the error procedure and ASIT EXIT (PeSIT SIT) may be

executed

（2）Further transfer attempts:

1）RESTART: the transfer has been interrupted

The monitor waits for a period fixed by the WSCAN parameter (CFTCAT command) before

trying to restart the transfer with the same access data. It increments the restart counter for the

protocol, the counter limit being determined by the RESTART parameter (CFTPROT command)

2）NEXT: the transfer has been interrupted

CFT文档

5/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

The monitor waits for a period fixed by the WSCAN parameter (CFTCAT command) before

trying to restart the transfer with the same access data. It does not increment the restart counter.

There is therefore no limit to the number of retries following this error

3）RETRY: the transfer has been interrupted

The monitor waits for a period fixed by the RETRY* parameters before trying to restart the

transfer, without changing the partner access data (same protocol, same network address). It

increments the retry counter specific to the partner access data, the counter limit being determined

by the RETRYM parameter (CFT network command)

4）COMMUT (switching): the transfer has been interrupted.

The monitor waits for a period fixed by the WSCAN parameter (CFTCAT command) before

trying to restart the transfer. It ignores the transfer access data and tries a "switching" path to reach

the partner: another dial number, another protocol or a backup partner

Note: protocol switching also means communication system (network) switching.

The switching mechanism does not provide for use of other network resources (CFTNET

commands associated via the CLASS) for a given protocol (CFTPROT command). Problems

associated with network resources are masked by the common network access method which

manages them

5）ABORT: the transfer is aborted

（3）Execution of the error procedure if the transfer switches to the K or H status:

EXECE: the procedure is executed

This is the procedure defined by CFTPARM EXEC*E parameters. If these parameters are not

set, the procedure is not executed

（4）Execution of the ASIT EXIT in PeSIT SIT protocol:

ASIT EXIT: if the transfer uses the PeSIT protocol SIT profile, the ASIT EXIT is executed

The EXIT is executed before the error procedure is submitted, if necessary. If this indication

is not declared, the ASIT EXIT is not executed

The "No CAT" indication specifies that no catalog entry had been created for the transfer

when the error occurred. The transfer request is rejected.

Code

0

Event

The transfer has terminated correctly

SYS - Error creating the message

queue or allocating the memory

Context definition error

SYS - Context allocation error

FILE - File input/output error

FILE - Error creating the receive file

Behavior

ASIT EXIT

Execution of normal EXECRF or

EXECSF end of transfer procedures

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

001

002

003

100

101

CFT文档

6/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code Event Behavior

102

1、FILE - Error allocating the transfer

H status - ABORT, EXECE in requester

file (physical file or VFM database

mode, ASIT EXIT

logical file)

H status - ABORT, EXECE, ASIT EXIT

2、FILE - The receive file cannot be

The file is deleted

allocated (FDISP=OLD case)

1、FILE - The file cannot be deleted

H status - ABORT, EXECE in requester

before the receive file is created (FDISP =

mode, ASIT EXIT

DELETE case)

H status - ABORT, EXECE in requester

2、FILE - Error deleting the sent file, if

a deletion has been requested (FACTION

mode, ASIT EXIT in requester mode

= DELETE)

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)

103

104

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

H status - ABORT, EXECE, ASIT EXIT

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)

FILE - Error recording the current

position in the transfer file H status - ABORT, EXECE, ASIT EXIT

(synchronization point setting)

FILE - Error setting the pointer to a

resynchronization point in the file (for a

transfer restart)

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

106

107

108 H status - ABORT, EXECE, ASIT EXIT

CFT文档

7/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code

109

Event

FILE - Data write error in the receive

file

Behavior

H status - ABORT, EXECE, ASIT EXIT

110

1、FILE - The send file does not exist

2、FILE - The receive file to be created

H status - ABORT, EXECE in requester

does not exist, even though the FDISP

mode, ASIT EXIT in requester mode

parameter requires it (FDISP=OLD).

DIAGP is then set to NO OLD

H status - ABORT in requester mode,

FILE - Insufficient space to create the

EXECE in requester mode, ASIT EXIT in

file

requester mode

FILE - The file to be created already

exists, even though the FDISP parameter H status - ABORT, EXECE in requester

prohibits it (FDISP = NEW). DIAGP is mode

then set to NO NEW

FILE - Data write error in the receive

file: file space full

H status - ABORT, EXECE, ASIT EXIT

111

113

114

115

1、FILE - The transfer owner is not

authorized to access the file

H status - ABORT, EXECE in requester

2、FILE - The file cannot be deleted

mode, ASIT EXIT in requester mode

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, ASIT EXIT

116

117

118

119

120

121

122

FILE - Error selecting the logical file H status - ABORT, EXECE in requester

(VFM) mode, ASIT EXIT in requester mode

FILE - Error opening the logical file

(VFM)

FILE - Error closing the logical file

(VFM)

FILE - Error releasing the logical file

(VFM)

PROT - Counter check error

USER - Interruption by the operator

SYS - Error allocating memory when

the transfer is executed

FILE - Error setting the pointer to a

resynchronization point in the file: the

restart point requested by the partner is

incorrect

PROT - Error: transfer aborted

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

D status - RESTART

123

H status - ABORT, EXECE, ASIT EXIT

124 H status - ABORT, EXECE, ASIT EXIT

CFT文档

8/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code

126

127

Event

FILE - LRECL error (record length)

FILE - The receive file is not empty

(FDISP = VERIFY case)

1、FILE - Error deselecting the file

2、FILE - Error deselecting the receive

file

Behavior

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

128

3、FILE - Error accessing the send file H status - ABORT, EXECE and ASIT

(allocating or opening), subsequent to a EXIT unless there is an allocation error in

file erase request (FACTION = ERASE) sender server mode

FILE - Error during file decompressionFILE - Error during file compression

PROT - IDF different on ODETTE

SELECT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE

129

130

131

132

H status – ABORT

If the file does not exist, no transfer is

executed Only the generic request remains

PARAM - Error accessing the

in the catalog

parameter setting indirection file

If an error occurs while reading the

(list of files, list of partners)

indirection file, the transfers generated for

the items (files or partners) that have

already been read are executed

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

FILE - CFTEXIT call error

1、FILE - The send file is locked

2、FILE - The receive file is locked

FILE - Duplication of the temporary

file

FILE - The file exists, the "rename"

operation is therefore impossible

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)

133

No catalog entry

134

135

136

137

H status - ABORT, EXECE, ASIT EXIT

D status - RESTART

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

State K – ABORT

138

State K - ABORT, EXECE, ASIT EXIT

CFT文档

9/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code

142

Event

FILE - The "rename" operation has

failed

VFM FILE - The security system

prohibits access to the VFM database for

the specified action

FILE+VFM FILE - The security

system prohibits access to the file to be

sent by the user

FILE+VFM FILE - The security

system prohibits deletion of the file to be

sent by the user

FILE+VFM FILE - The security

system prohibits resetting of the file to be

sent by the user

FILE+VFM FILE - The security

system prohibits creation of the file to be

sent for the user

VFM FILE - The security system

prohibits access to the logical file in

read-only mode

Behavior

H status - ABORT, EXECE, ASIT EXIT

144 State H - ABORT, EXECE, ASIT EXIT

145 State H - ABORT, EXECE, ASIT EXIT

146 State H - ABORT, EXECE, ASIT EXIT

147 State H - ABORT, EXECE, ASIT EXIT

148 State H - ABORT, EXECE, ASIT EXIT

149 State H - ABORT, EXECE, ASIT EXIT

150

State K – ABORT

If the directory does not exist, no

transfers are triggered and only the generic

PARAM - Error accessing the

request remains in the catalog

parameter setting indirection file when

If an error is detected when reading the

the file is a directory

directory, the transfers generated for the

items (directory menus) that have already

been read are triggered

PARAM - The selection file cannot be

used on the directory specified

FILE - Error during the concatenation

phase at the start of the transfer or during

the deconcatenation phase at the send of

the transfer

PROT - FPDU reception

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)

PROT - Mandatory PI missing in

FPDU

State K - ABORT

Only the generic request remains in the

catalog. No transfers are activated

151

152

State H - ABORT, EXECE, ASIT EXIT

220 H status - ABORT, EXECE, ASIT EXIT

221 H status - ABORT, EXECE, ASIT EXIT

222

H status - ABORT, EXECE, ASIT EXIT

CFT文档

10/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code

223

224

225

226

Event

PROT - Invalid PI length

PROT - Invalid PGI length

PROT - PGI missing from the FPDU

PROT - PGI embedded in another PGI

PROT - Protocol error

A protocol error has been detected:

DIAGP is set to the PeSIT or ODETTE

code of the error detected

PROT - Invalid action

PROT - Event not found

An interaction not recognized by the

protocol mechanisms has been received in

a given transfer context

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

Behavior

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

230

H status - ABORT, EXECE, ASIT EXIT

231 H status - ABORT, EXECE, ASIT EXIT

232

H status - ABORT, EXECE, ASIT EXIT

233

K status - ABORT

240

260

261

262

263

278

280

281

PROT - Time-out expired (RTO

D status - RETRY/COMMUT

parameter)

SSL - Security problem

SSL - Error linked to an internal PKI

SSL - Error linked to the PKI system

SSL - Error linked to an external PKI

SSL - Invalid security profile

SSL - Client not authorized

SSL - Insufficient authentification levelK state - ABORT

K state – ABORT

K state – ABORT

K state – ABORT

K state – ABORT

K state – ABORT

K state - ABORT

CFT文档

11/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code Event Behavior

301

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 (CFT network command)

will be used for the next retry

If the invalid address is the last one in

NET - Network addressing error (dial

the list, the next protocol in the PROT

number) at the time of connection

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

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

NET - Network link broken (cut-off,

will relate to the next DIALNO parameter

(CFT network command), or the next

time-out) outside the connection phase

PROT parameter (CFTPART command)

DIAGP is then set to VNRELI

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

302

CFT文档

12/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code Event Behavior

303

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

NET - Network parameter error at the

If the protocol used is the last in the list,

time of connection

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)

The user requesting the transfer is not

authorized to perform it

State H

350

351

The remote requester is not authorized

to use the transfer. The transfer was in the

H state State H

The monitor is running in the

server/sender mode

The remote requester is not authorized

to create a transfer

The monitor is running in the

State H

server/sender mode and the transfer was

to be created via a CFTSEND

IMPL=YES

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

PARAM - Embedded broadcast list

generic list request set to the K status

remains in the catalog

explicitly refused

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

PARAM - The PROT parameter of the

CFTPART command does not belong to

the active protocol list (PROT parameter

of the CFTPARM command)

PARAM - Invalid password

352

399 Unreferenced error

401

402

K status - ABORT

403 No CAT

CFT文档

13/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code

404

Event

PARAM - Open mode not authorized

OUT - The monitor has tried all

possible partner access points: DIALNO,

PROT, IPART

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 CFT network

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

Behavior

K status - ABORT (requester mode only)No CAT (in server mode)

K status - ABORT, EXECE, ASIT EXIT 405

406

K status - ABORT, EXECE

CFT文档

14/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code Event Behavior

408

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

PARAM - PART parameter not

via an indirection file (FNAME parameter

described by a CFTPART command

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

PARAM - Unknown NPART parameterK status – ABORT

PARAM - Unknown CFTPROT

K status – ABORT

command

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

AUTH - File identifier (IDF) not

in the CFTDEST command), only transfers,

authorized

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

CFT文档

15/20

409

410

411 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code

412

413

Event

DATA - Catalog access error

AUTH - File identifier not authorized

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 (CFT network

CNXOUT=0)

DIAGP is then set to NO CALL

OVER - Maximum number of partners

reached

Behavior

No change in the status or in DIAGI in

the catalog as the file cannot be accessed

H status - ABORT

414

K status - ABORT

415

D status - NEXT

1、OVER - Maximum number of

transfers reached (MAXTRANS

parameter) D status - NEXT

The transfer cannot be executed

DIAGP is then set to MAXTRANS

416

D status - NEXT

This status corresponds to a transfer

2、OVER - Maximum number of

refusal by the "protocol" task of the

connections reached for the network

monitor, even though the scheduler has not

resource

reached the MAXTRANS limit

The transfer cannot be executed

This occurs when the protocol task

DIAGP is then set to MAXCNX

maintains active connections after transfers

have ended

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

417

D status - NEXT

CFT文档

16/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code Event Behavior

418

D status - RESTART

OVER - The total number of transfers

If the number of retries exceeds the

in progress exceeds one of the CNXIN,

value of the RESTART parameter

CNXOUT or CNXINOUT parameters for

(CFTPROT command), the monitor

the partner

switches to the access data of the next

The transfer cannot be executed

protocol for this partner

DATA - The transfer to be retried is not

in the catalog at the server end

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

1、SYS - Error executing a monitor

"file" task

2、SYS - Error executing a monitor

"EXIT" task

PARAM - (Etebac 3) Undefined

parameter card (CFTETB command) in

requester mode

SYS or PARAM - EXIT task creation

error

PARAM - CFTXLATE command not

found for this transfer direction and the

source and target alphabets

USER (Directory Exit) - Call collect

refused.

USER (Directory Exit) - Error in the

Directory Exit task

PARAM - Transfer is inactive on the

requester side

ABORT

419

420

ABORT

421

D status - NEXT

K status - ABORT

422 K status - ABORT

423

H status - ABORT

424 H status - ABORT

425

426

430

No CAT

No CAT (server mode)

State K - ABORT (requester mode)

State D - ACT

CFT文档

17/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code Event Behavior

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

D status - RESTART

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

PROT - (PeSIT) (Odette) Reception of

a negative "message confirmation" FPDUPROT - (PeSIT) (Odette) Reception of

a negative "create confirmation" FPDU

PROT - (PeSIT) Reception of a

negative "select confirmation" FPDU

PROT - (PeSIT) (Odette) Reception of

a negative "deselect confirmation" FPDU

PROT - (PeSIT) Reception of a

negative "open confirmation" FPDU

PROT - (PeSIT) Reception of a

negative "write confirmation" FPDU

PROT - (PeSIT) Reception of a

negative "end of transfer confirmation"

FPDU

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

452

453

454

455

456

459

460 H status - ABORT, EXECE, ASIT EXIT

600

FILE - (PeSIT) (Odette) Transfer

aborted by the remote end: file

H status - ABORT, EXECE, ASIT EXIT

input/output error - PeSIT / Odette code:

see DIAGP

FILE - (PeSIT) Transfer aborted by the

remote end: file opening error

FILE - (PeSIT) Transfer aborted by the

remote end: file closing error

FILE - (PeSIT) (Odette) (Etebac3)

Transfer aborted by the remote end: the

file to be read does not exist

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

604

605

610 H status - ABORT, EXECE, ASIT EXIT

CFT文档

18/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code

611

Event

FILE - (PeSIT) Transfer aborted by the

remote end: insufficient space to create

the file

FILE - (PeSIT) Transfer aborted by the

remote end: the file to be created already

exists

FILE - (PeSIT) Transfer aborted by the

remote end: file space full

PROT - (PeSIT) Transfer aborted by

the remote end: counter control error

PROT - (PeSIT) Transfer aborted by

the remote end: interruption by the

operator

PROT - (PeSIT) (Odette) Transfer

aborted by the remote end: error in

record length

FILE - (PeSIT) Transfer aborted by the

remote end: file access conflict

Behavior

H status - ABORT, EXECE, ASIT EXIT

613 H status - ABORT, EXECE, ASIT EXIT

614

620

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT, EXECE, ASIT EXIT

621 H status - ABORT, EXECE, ASIT EXIT

626 H status - ABORT, EXECE, ASIT EXIT

635

H status - ABORT, EXECE, ASIT EXIT

720

1、PROT - (PeSIT) Protocol abort by

the remote end: incorrect FPDU H status - ABORT, EXECE, ASIT EXIT

(transmission error)

2、PROT - (Odette) Protocol abort by

the remote end: negotiation error

H status - ABORT, EXECE

H status - ABORT, EXECE, ASIT EXIT

722

PROT - (PeSIT) Protocol abort by the

remote end: missing PI

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

730

H status - ABORT, EXECE

D status - RETRY

H status - ABORT, EXECE

H status - ABORT, EXECE

H status - ABORT, EXECE, ASIT EXIT

H status - ABORT

740

850

903

904

908

NET - (PeSIT) Transfer aborted by the

remote end: time-out - PeSIT code: 317

PROT - (PeSIT) Protocol rejection by

the remote end: authorization problem

PROT - (ETEBAC 3) Invalid passwordPROT - (PeSIT) Protocol rejection by

the remote end: transfer denied (open

mode, authorizations for example)

PROT - (ETEBAC 3) Partner unknownCFT文档

19/20 This chapter lists the transfer diagnostic codes specific to the CFT monitor.

Code

909

Event

PROT - (PeSIT only) Protocol rejection

by the remote end: requested identifier

unknown

PROT - (PeSIT only) Maximum

number of transfers reached at the partner

end (MAXTRANS parameter)

Restart context not available

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

PROT - (ETEBAC 3) Error on

parameter card

Call collect refused by the remote

system

Invalid caller number

PROT - Partner is inactive on the

server side

PROT - Protocol pre-connection phase

rejected by the remote end (PeSIT

LOGON): LOGON string rejected

PROT - Protocol pre-connection phase

rejected by the remote end (PeSIT

LOGON): password expired

Behavior

D status - RESTART

916

919

D status - NEXT

H status - ABORT, EXECE

920 D status - RESTART

922

925

928

930

H status - ABORT, EXECE

No CAT

H status - ABORT, EXECE

ACT status

963 K status - ABORT, EXECE, ASIT EXIT

970

K status - ABORT, EXECE, ASIT EXIT

CFT文档

20/20