DIAGI: Diagnostic codes

Transfer CFT internal diagnostic codes

Diagnostic codes provide 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. If so, this is indicated in the label.

Diagnostic code values

Codes with a value between 001 and 499 indicate a local issue; values between 501 and 999 correspond to a fault reported by the partner.

This means that when you troubleshooting, if the code is greater than 500 it refers to a remote issue. To find the actual DIAG, subtract 500 from the displayed code. If the DIAG is 916, for example, the issue is a remote problem corresponding to DIAG 416 (Maximum number of transfers reached).

Event column in diagnostic codes

The Event column explains the possible cause of the transfer error. Brief information on the type of error which caused the transfer failure:

  • SYS: System error
  • NET: Error detected by the network layers ( Transfer CFT layers, manufacturer or network layers)
  • PROT: Fault detected by the file transfer protocol
  • FILE: Transferred file access error returned by the operating system
  • DATA: Error accessing Transfer CFT basic data: parameter, partners, catalog, communication, log, statistics and secondary indirection files (lists of partners, files, and so on)
  • PARAM: Transfer execution error following a parameter setting error
  • AUTH: Transfer denied following an authorization check by Transfer CFT
  • OVER: The transfer cannot be executed because the monitor's resources are saturated or a parameter setting limit has been exceeded
  • OUT: The transfer request is aborted after the maximum number of retries
  • USER: The transfer is interrupted following an action by the operator
  • SSL: Incident detected by the secured protocol SSL 

Consequence column in diagnostic codes

The Consequence column provides information on the Transfer CFT behavior following a transfer failure. The resulting status of the transfer D, H or K:

  • D: the transfer can still be executed using the RESTART, NEXT, RETRY or COMMUT mechanisms
  • H or K: the transfer is aborted, the error procedure and ASIT EXIT (PeSIT SIT) may be executed

Further transfer attempts

For the D status, the following are possible to execute the transaction:

  • 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).
  • NEXT: 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 does not increment the restart counter. There is therefore no limit to the number of retries following this error.
  • 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 (CFTnetwork command).
  • 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.

In the case of an H or K status the transfer is aborted, the error procedure and ASIT EXIT (PeSIT SIT) can be executed:

  • ABORT: the transfer is aborted
  • 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.
  • 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.

Internal diagnostic codes table

Code Event Consequence
Code Event Consequence

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

004 MQCONN  
005 MQOPEN  
006 MQPUT  

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

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

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

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 re-synchronization 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

112 Nonexistent unit  

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

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

125 Max LRECL error  

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

139 Incorrect attributes file  
140 Invalid spacing  
141 Cannot create directory  

142

FILE - The "rename" operation failed

H status - ABORT, EXECE, ASIT EXIT

143 FILE LREC error  

144

MVS transfer busy

State D - Retry

145
  1. The SEND file is outside of the workingdir tree.
  2. The temporary SEND file is outside of the workingdir tree.
K status - ABORT
148

1. The RECV file is outside of the workingdir tree.

2. The temporary RECV file is outside of the workingdir tree.

K status - ABORT

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 de-concatenation 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 An error occurred when trying to transcode a file using NCHARSET parameter in the CFTSEND command before a send.

Generates a DIAGI=730, DIAGP=ABO 399 on the remote Check on Partner Side side as the sender cannot transcode before sending.

See also DIAGC.

155 This preprocessing error occurs when a preexec is specified, but launching the exec file failed (usually because the file was not found, but could be due to a busy or migrated file on MVS).

Generates:

  • DIAGP: NO EXEC
  • DIAGC: PREEXEC LAUNCH ERROR
156 This occurs when the post-transfer file renaming fails.

When  FACTION=RETRYRENAME the following DIAGC is generated: RETRYRENAME MAX RETRIES REACHED.

160

Handles the event 'no outstanding transfer or implicit declaration'.

No catalog entry is created.

200 An error occurred on a child transfer of this parent (generic) transfer. Refer to the child transfer in error for more information.  
203 PROF=SIT non-priority transfer  

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: PESIT SIT, PESIT EXT, ODETTE

K status - ABORT

240

PROT - Time-out expired (RTO parameter)

D status - RETRY/COMMUT

241 Transfer time-out - requester  
241 Transfer time-out - server  
243 Network connection time-out  
244 Pre-connection time-out  

260

SSL - Security problem

K state - ABORT

DIAGP=PKI with I, E or S nnn

nnn = SSL code alert

See SSL alert errors.

261

SSL - Error linked to an internal PKI

K state - ABORT

DIAGP=PKI I nnn

nnn = SSL code alert

See SSL alert errors.

262

SSL - Error linked to the PKI system

K state - ABORT

DIAGP=PKIS nnn

nnn = SSL code alert

See SSL alert errors.

263

SSL - Error linked to an external PKI

K state - ABORT

DIAGP=PKIE nnn

nnn = SSL code alert

See SSL alert errors.

278

SSL - Invalid security profile

K state - ABORT

279 Requester opposition  

280

SSL - Client not authorized

K state - ABORT

281

SSL - Insufficient authentication level

K state - ABORT

282 Embedding required  
283 Encoding required  
284 Signature required  
285 Double signature required  
286 Closed service file  
287 Sever does not recognize this bank (entity)  
288 File type not supported  
289 Secondary client id not recognized  
290 Secondary bank id not recognized  
291 First signatory is invalid  
292 Second signatory is invalid  
293 First signatory mechanism conflict  
294 Second signatory mechanism conflict  
295 File type is not compatible  

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, Transfer CFT "switches" the access data. The partner access data for the next retry will relate to the next DIALNO parameter (CFTNET 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 is 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)

304 Requester not authorized (PESIT)  

350

The user requesting the transfer is not authorized to perform it

State H

351

The remote Check on Partner Side 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 Check on Partner Side 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

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 (in server mode)

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 CFTN 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

407

PARAM - Paramètre NIDF inconnu

Etat K - ABORT

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: 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

As the file could not be accessed, there is no change in the status or in the catalog DIAGI

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), Transfer CFT switches to the access data of the next protocol for this partner

See Configure multi-node simultaneous transfers.

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

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)

428    

430

PARAM - Transfer is inactive on the requester side

State D - ACT

431

USER (Security) - CFTAPPL card is absent

No CAT

432 Duplicate transfer error  
433 User/password error  
434 AUTH - File identifier (default IDF) is not authorized K status - ABORT

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

457 Reception of a negative closed confirmation  
458 Reception of a negative read confirmation  

459

PROT - (PeSIT) Reception of a negative write 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

461 Received an abort with diagnostics  
462 No data sent on network  
463 Logon entry not recognized  
470 Expired password  
471 PROT - (EBICS) Protocol recoverable error. See DIAGP, DIAGC. H status - ABORT
472 PROT - (EBICS) Protocol non-recoverable error. See DIAGP, DIAGC. K status - ABORT
473 PROT - (EBICS) invalid order type K status - ABORT
474 PARAM - (EBICS) An error caused by the signature file has been detected. See DIAGC. K status - ABORT
475 PARAM - (EBICS) mandatory parameter is missing. See DIAGC. K status - ABORT
499 ( ODETTE) CD okay  

Codes with a value between 001 and 499 indicate a local issue; values between 501 and 999 correspond to a fault reported by the partner.

Therefore when troubleshooting if the code is greater than 500 it refers to a remote issue. To find the actual DIAG, subtract 500 from the displayed code. If the DIAG is 916, for example, the issue is a remote problem corresponding to DIAG 416 (Maximum number of transfers reached).

500 Constant to add to a remote Check on Partner Side code  

600

FILE - (PeSIT) (Odette) Transfer aborted by the remote Check on Partner Side end: file input/output error - PeSIT / Odette code: see DIAGP

H status- ABORT, EXECE, ASIT EXIT

604

FILE - (PeSIT) Transfer aborted by the remote Check on Partner Side end: file opening error

H status - ABORT, EXECE, ASIT EXIT

605

FILE - (PeSIT) Transfer aborted by the remote Check on Partner Side end: file closing error

H status - ABORT, EXECE, ASIT EXIT

610

FILE - (PeSIT) (Odette) Transfer aborted by the remote Check on Partner Side end: the file to be read does not exist

H status - ABORT, EXECE, ASIT EXIT

611

FILE - (PeSIT) Transfer aborted by the remote Check on Partner Side end: insufficient space to create the file

H status - ABORT, EXECE, ASIT EXIT

613

FILE - (PeSIT) Transfer aborted by the remote Check on Partner Side end: the file to be created already exists

H status - ABORT, EXECE, ASIT EXIT

614

FILE - (PeSIT) Transfer aborted by the remote Check on Partner Side end: file space full

H status - ABORT, EXECE, ASIT EXIT

620

PROT - (PeSIT) Transfer aborted by the remote Check on Partner Side end: counter control error

H status - ABORT, EXECE, ASIT EXIT

621

PROT - (PeSIT) Transfer aborted by the remote Check on Partner Side end: interruption by the operator

H status - ABORT, EXECE, ASIT EXIT

626

PROT - (PeSIT) (Odette) Transfer aborted by the remote Check on Partner Side end: error in record length

H status - ABORT, EXECE, ASIT EXIT

635

FILE - (PeSIT) Transfer aborted by the remote Check on Partner Side end: file access conflict

H status - ABORT, EXECE, ASIT EXIT

660

REC (PeSIT) - Error 660, ASE 205 on the requester side

H state - Transfer aborted by the remote Check on Partner Side end: no outstanding transfer

720

1. PROT - (PeSIT) Protocol abort by the remote Check on Partner Side end: incorrect FPDU (transmission error)

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

H status - ABORT, EXECE, ASIT EXIT

 

H status - ABORT, EXECE, ASIT EXIT

722

PROT - (PeSIT) Protocol abort by the remote Check on Partner Side 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 Check on Partner Side 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 Check on Partner Side end: time-out - PeSIT code: 317

D status - RETRY

850

PROT - (PeSIT) Protocol rejection by the remote Check on Partner Side end: authorization problem

H Status - ABORT, EXECE

904

PROT - (PeSIT) Protocol rejection by the remote Check on Partner Side end: transfer denied (open mode, authorizations for example)

H status - ABORT, EXECE, ASIT EXIT

909

PROT - (PeSIT only) Protocol rejection by the remote Check on Partner Side 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

See Configure multi-node simultaneous transfers.

919

Restart context not available

H status - ABORT, EXECE

920

PROT - (PeSIT) Protocol rejection by the remote Check on Partner Side 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

925

Call collect refused by the remote Check on Partner Side system

No CAT

928

Invalid caller number

H status - ABORT, EXECE

930

PROT - Partner is inactive on the server side

ACT status

933 Error in password management parameter RPASSWD or SPASSWD: non-authorized requester identification  

963

PROT - Protocol pre-connection phase rejected by the remote Check on Partner Side end (PeSIT LOGON): LOGON string rejected

K status - ABORT, EXECE, ASIT EXIT

970

PROT - Protocol pre-connection phase rejected by the remote Check on Partner Side end (PeSIT LOGON): password expired

K status - ABORT, EXECE, ASIT EXIT

SSL alert errors

Code

Description

0

Close notify

10

Unexpected message

20

Bad record MAC

21

Decryption failed

22

Record overflow

30

Decompression failure

40

Handshake failure

41

No certificate

42

Bad certificate

43

Unsupported certificate

44

Certificate revoked

45

Certificate expired

46

Certificate unknown

47

Illegal parameter

48

Unknown CA ( Certificate authority)

49

Access denied

50

Decode error

51

Decrypt error

60

Export restriction

70

Protocol version

71

Insufficient security

80

Internal error

90

User cancelled

100

No renegotiation

110

Unsupported extension

111

Certificate unobtainable

112

Certificate unobtainable

113

Bad certificate status response

114

Bad certificate hash value

Related Links