Transfer CFT messages: CFTT

This topic lists the CFTTxx (CFT xnnx) messages and provides the type, a description, consequence, and corrective actions when applicable.

Message format

Earlier versions of Transfer CFT used a different message format than version 3.1.3 and higher. The error messages displayed in this document use the former, or earlier version, format. If your system uses the CFTLOG parameter Format = V24, the log display is as shown below:

CFTXXX: fixed text message <variables>

Example

CFTLOG FORMAT=[V23,V24]

For V23: CFTT57I PART=&part IDF=&idf IDT=&idt &str transfer started

For V24: CFTT57I &str transfer started <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

V23 format

V24 format

Error

CFTT00E CFT request warning _ &str

CFTT00E CFT request warning - &str

Explanation

An error may have occurred during a request sent to the Transfer CFT. The &str message label specifies the possible type of error:

  • Unknown protocol request: Internal error of the Transfer CFT, which receives an unexpected protocol event
  • Unknown oper request: The operator command received is unknown
  • Not computable state: The transfer is not possible (status other than "D" (Available)
  • Transfer for myself rejected: The target of the transfer is the local site (CFTPARM PART field) The Transfer CFT therefore refuses to activate a transfer to itself
  • Logger currently unreachable: A SWITCH command, switching log files, was attempted while the LOG task (CFT log) was not (or no longer) active
  • Ignored (Catalog Full): The catalog was 100% full and so the last SEND (or RECV) command could not be processed; if it was submitted via the Transfer CFT communication file, it is stored in the file and the associated communication process stops (for more information, refer to the CFTC01W message)
  • Request syntax error: There is a syntax error in the request; inform Product Support
  • Catalog request unknown :The request is invalid
  • Unknown process request: An internal Transfer CFT error was detected; inform Product Support
  • Unknown file request: An internal Transfer CFT error was detected; inform Product Support
  • Transfer already in progress: An attempt was made to restart a transfer in progress; the transfer was not restarted
  • File already transferred: An attempt was made to restart a terminated transfer; the transfer was not restarted
  • &file: A read error was detected on the authorizations file (&file); inform Product Support
  • Access Exit Task unreachable: &diagp: The directory exit task cannot be accessed (DIAGP specifies the cause); inform Product Support
  • Request Ignored : time-out: The request was not processed by the Transfer CFT (end time limit exceeded)
  • Unable to attach Client mailbox: Attachment to the client application was rejected
  • Unable to send data to Client mailbox: Data cannot be sent to the client application

 

V23 format

V24 format

Error

CFTT01E PART=&part IDF=&idf IDT=&idt _ Open mode not allowed

CFTT01E IDTU=&idtu PART=&part IDF=&idf IDT=&idt _ Open mode not allowed

Explanation

A transfer request was made in OPEN mode, but this mode is not supported for the partner concerned.

Consequence

The transfer is denied. The corresponding catalog entry is set to the KEEP status.

Action

Transfer the files with this partner in closed mode.

 

V23 format

V24 format

Error

CFTT02E PART=&part IDF=&idf IDT=&idt _ Transfer Area Full

CFTT02E _ Transfer Area Full <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

A new transfer request was made but the maximum number of transfers allowed at the same time has been reached.

Consequence

The transfer is not executed.

Action

Wait for a decrease in the number of transfers or increase the maximum number of authorized transfers (this increase can only be made by the technicians responsible for porting and customizing the Transfer CFT product).

 

V23 format

V24 format

Error

CFTT03E PART=&part IDF=&idf IDT=&idt _ Max retry Reached

CFTT03E _ Max retry Reached <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

The Transfer CFT has performed all retry actions to establish the link with the partner.

  • The transfer activation retry counter for this protocol has exceeded the value of the RESTART parameter (CFTPROT command) In this case there have been no other network connection attempts and there are no more protocols in this partner's protocol list In this case the DIAGI code is set to 406
  • The physical connection has resulted in an invalid network address. It is the last address for this protocol; there is no backup partner. The internal diagnostic code (DIAGI) is set to 405. When the catalog is displayed, it overrides the value 301 signifying an invalid address
  • The physical connection has resulted in a fatal network error. In this case the DIAGI code is set to 303; the DIAGP value defines the source of the error
  • The last physical connection attempted according to the values of the RETRYM, RETRYN and RETRYW parameters has failed. It is the last protocol in this partner's protocol list; there is no backup partner

Note: the internal diagnostic code (DIAGI) is set to 405. When the catalog is displayed, it overrides the value 302 signifying a non-fatal network error.

Consequence

The transfer is refused. The corresponding catalog entry is set to the KEEP status.

Action

Determine the error according to the DIAGI value. Analyze the DIAGP code.

 

V23 format

V24 format

Error

CFTT05E PART=&part IDF=&idf IDT=&idt _ Restart Failed

CFTT05E PART=&part IDF=&idf IDT=&idt _ Restart Failed

Explanation

A file transfer restart request is not possible (the restart identifier is unknown, for example).

Consequence

The transfer is not restarted.

Action

Try a new transfer.

 

V23 format

V24 format

Warning

CFTT06W PART=&part IDF=&idf IDT=&idt _ Partner switching IPART=&part

CFTT06W PART=&part IDF=&idf IDT=&idt _ Partner switching IPART=&part

Explanation

The partner (&part) cannot be reached within the authorized time slot (OMINTIME, OMAXTIME).

Consequence

The transfer will be retried via the intermediate partner IPART.

 

V23 format

V24 format

Warning

CFTT07W Ending Transfer Task &n Failed _ A transfer Running

CFTT07W Ending Transfer Task &n Failed _ A transfer Running

Explanation

Attempt to delete a transfer task for which not all transfers have been completed. &n designates an internal Transfer CFT task number incremented each time a transfer task is activated.

 

V23 format

V24 format

Error

CFTT08E PART=&part IDF=&idf IDT=&idt _No prot available

CFTT08E PART=&part IDF=&idf IDT=&idt _No prot available

Explanation

The maximum number of retries authorized for a transfer using the &prot protocol has been reached (see the Transfer CFT CFTPROT RESTART parameter).

Consequence

The entry corresponding to the transfer in the catalog is set to KEEP.

Action

Analyze the causes of the broken communication link.

 

V23 format

V24 format

Warning

CFTT09W PART=&part IDF=&idf IDT=&idt PROT=&prot _ Maximum cv affected

CFTT09W PART=&part IDF=&idf IDT=&idt PROT=&prot _ Maximum cv affected

Explanation

All virtual circuits associated with a partner in server mode have already been allocated

Consequence

The transfer is refused locally.

Action

Wait for virtual circuits to be freed or increase the maximum number of virtual circuits (see the Transfer CFT Online documentation CNXIN and CNXINOUT parameters).

 

V23 format

V24 format

Error

CFTT10E PART=&part PROT=&prot _ Protocol not authorized

CFTT10E PART=&part PROT=&prot _ Protocol not authorized

Explanation

The &prot protocol is not authorized for this partner.

Consequence

The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action

Check Transfer CFT parameter settings.

 

V23 format

V24 format

Error

CFTT11EPART=&part PROT=&prot CLASS=&n _ &net not found

CFTT11EPART=&part PROT=&prot CLASS=&n _ &net not found

Explanation

The network characteristics associated with the partner and for the &n class of resources have not been found in the Transfer CFT partner file.

Consequence

The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action

Check the Transfer CFT parameter settings.

 

V23 format

V24 format

Warning

CFTT12WPART=&part IDF=&idf IDT=&idt _ Out of time to call

CFTT12WPART=&part IDF=&idf IDT=&idt _ Out of time to call

Explanation

A transfer request was made outside the time slot authorized for this partner.

Consequence

The transfer is not executed (remains in the D state).

Action

Execute a new transfer within the time slot authorized for this partner.

 

V23 format

V24 format

Information

CFTT13IPART=&part (IDF=&idf IDM=&idm) IDT=&idt _ Session parameters PROT=&prot SAP=&sap DIALNUM(or HOST)= &dialnum (or &host)

CFTT13IPART=&part (IDF=&idf IDM=&idm) IDT=&idt _ Session parameters PROT=&prot SAP=&sap DIALNUM(or HOST)= &dialnum (or &host)

Explanation

Information message for each dialno (or host) switch and protocol.

 

V23 format

V24 format

Error

CFTT14E PART=&part IDF=&idf IDT=&idt _ Not found

CFTT14E PART=&part IDF=&idf IDT=&idt _ Not found

Explanation

The &part partner was not found in the Transfer CFT partner file.

Consequence

The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action

Check the Transfer CFT parameter settings.

 

V23 format

V24 format

Error

CFTT15E NPART=&part _ Not found

CFTT15E NPART=&part _ Not found

Explanation

The network identifier of the &part partner was not found in the Transfer CFT partner file.

Consequence

The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action

Check the Transfer CFT parameter settings.

 

V23 format

V24 format

Error

CFTT16E PART=&part IDF=&idf _ No implicit send

CFTT16E PART=&part IDF=&idf _ No implicit send

Explanation

The partner has made a selection request and no file is ready to be sent (SEND on HOLD or implicit SEND).

Consequence

The transfer is not executed (no catalog record is created).

Action

Prepare a transfer (SEND state=hold) or declare an implicit send in the Transfer CFT parameter settings.

 

V23 format

V24 format

Information

CFTT17I PART=&part IDF=&idf IDT=&idt _ STATE=HOLD

CFTT17I PART=&part IDF=&idf IDT=&idt _ STATE=HOLD

Explanation

A transfer request was voluntarily put on Hold (see Transfer CFT Concepts, Send on Hold).

Consequence

The transfer is not executed and is on hold for a possible reception request.

 

V23 format

V24 format

Error

CFTT18E PART=&part IDF=&idf CFTAUTH id=&id _ Not found

CFTT18E PART=&part IDF=&idf CFTAUTH id=&id _ Not found

Explanation

The identifier of the list of files authorized for a partner was not found in the Transfer CFT parameter file.

Consequence

The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action

Check the Transfer CFT parameter setting.

 

V23 format

V24 format

Error

CFTT19E PART=&part _ Invalid remote password &str *

CFTT19E PART=&part _ Invalid remote password &str *

Explanation

Transfer request was made and the partner sent an invalid password.

*where &str = supplied password is incorrect

Consequence

The connection is refused.

Action

Execute a new transfer with a valid password.

 

V23 format

V24 format

Error

CFTT20E PART=&part _ PVC not allowed

CFTT20E PART=&part _ PVC not allowed

Explanation

The call collect connection request received is not authorized for this partner.

Consequence

The connection is refused. 

 

V23 format

V24 format

Error

CFTT21E PART=&part IDF=&idf IDT=&idt _ Catalog access failed &scs ,&cr

CFTT21E PART=&part IDF=&idf IDT=&idt _ Catalog access failed &scs ,&cr

Explanation

During a transfer (or a transfer request) an undetermined Transfer CFT catalog access error was detected (input/output error for example).

Consequence

The transfer is interrupted (or not executed).

Action

Analyze the &scs code and inform Product Support if necessary.

 

V23 format

V24 format

Error

CFTT22E &str PART=&part IDF=&idf IDT=&idt_ &str

CFTT22E _&str <IDTU=&idtu PART=&part IDF=&idf IDT=&idt> &str

Explanation

Connection refused due to user authentication failure (rpasswd, spasswd error).

The  &str provides additional information.

For more information, see Password management.

Consequence

The transfer is not executed.

Action

Check the &str, correct, and retry.

V23 format

V24 format

Error

CFTT23E PART=&part Shutdown in progress _ &str

CFTT23E PART=&part Shutdown in progress _ &str

Information

A Transfer CFT shutdown is in progress, the request sent is not processed (the &str message specifies the type of request).

Connect in being refused: connection request from one of its partners.

 

V23 format

V24 format

Error

CFTT24E PART=&part PROT=&prot _ Invalid call number &n

CFTT24E PART=&part PROT=&prot _ Invalid call number &n

Explanation

The called number received (server end) is not in the list of numbers defined (and authorized) for this partner (&n represents the unauthorized number).

Consequence

The connection is refused.

 

V23 format

V24 format

Error

CFTT25E PART=&part IDF=&idf _ IDF not authorized

CFTT25E PART=&part IDF=&idf _ IDF not authorized

Explanation

During a transfer request the identifier of the file to be transferred is not authorized for this partner (server or requester end).

Consequence

The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action

Request that another file be sent or authorize this identifier.

 

V23 format

V24 format

Error

CFTT26E PART=&part IDF=&idf IDT=&idt _ Max transfer tasks

CFTT26E PART=&part IDF=&idf IDT=&idt _ Max transfer tasks

Explanation

A new transfer request was made but the maximum number of transfer processes has been reached (as has the maximum number of transfers per process).

Consequence

The transfer is not executed and remains in the D state.

Action

Wait for a decrease in the number of transfers or increase the maximum number of authorized processes or the maximum number of transfers per process. This increase can only be made by the technicians responsible for porting and customizing the Transfer CFT product.

 

V23 format

V24 format

Error

CFTT27E PART=&part IDF=&idf IDT=&idt _ Error &scs writing starts

CFTT27E PART=&part IDF=&idf IDT=&idt _ Error &scs writing starts

Explanation

The statistics relating to the designated transfer could not be written in the accounting file.

Consequence

The accounting file is incomplete.

Action

Analyze the file access system code (&scs) to determine the source of the error.

 

V23 format

V24 format

Error

CFTT28E No outgoing CV configured on Network

CFTT28E No outgoing CV configured on Network

Explanation

An outgoing call attempt was made on a network resource configured with the CALL = IN parameter (CFTNET command).

Consequence

The requester transfer cannot be executed.

The catalog entry is set to the K state with a protocol diagnostic code (DIAGP): "L 0B 22" - 0B meaning that network access is forbidden.

If another protocol (CFTPROT) using another network resource (CFTNET) is declared for this partner (PROT parameter of the CFTPART command), Transfer CFT will make another attempt on this resource.

Action

Change the parameter settings so that the protocol designated for the partner points to a network resource available for outgoing calls.

 

V23 format

V24 format

Error

CFTT29E DEST= &dest -Invalid use _Define for [BOTH/LOCAL/COMMUT] use only

CFTT29E DEST= &dest -Invalid use _Define for [BOTH/LOCAL/COMMUT] use only

Explanation

A broadcast list can be used (FOR = parameter) with the value:

  • LOCAL meaning that the partner list can only be used for a direct transfer.
  • COMMUT meaning that the partner list can only be used for store and forward operations.
  • BOTH meaning that the partner list is used locally and for store and forward operations.

 

V23 format

V24 format

Error

CFTT30E PART=&part IDF=&idf IDT=&idt _ Max Exit tasks

CFTT30E PART=&part IDF=&idf IDT=&idt _ Max Exit tasks

Explanation

A new transfer request with an associated EXIT was requested but the maximum number of EXIT processes has been reached.

Consequence

The transfer is not executed (remains set to the D state).

Action

Wait for a decrease in the number of transfers or increase the maximum number of processes allowed.

 

V23 format

V24 format

Warning

CFTT31W Ending Exit Task &n Failed _ A transfer Running

CFTT31W Ending Exit Task &n Failed _ A transfer Running

Explanation

Attempt to delete an EXIT task in which not all transfers have been completed. &n designates an internal Transfer CFT task number incremented each time a transfer task is activated.

 

V23 format

V24 format

Error

CFTT32E PART=&part IDF=&idf IDT=&idt _ Partner not found

CFTT32E _ Partner not found <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

The identifier of the &part partner was not found in the Transfer CFT partner file.

Consequence

The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action

Check the Transfer CFT parameter settings.

 

V23 format

V24 format

Error

CFTT33E PART = &dest IDF = &idf IDT = &idt _ Illegal use of CFTDEST

CFTT33E _ Illegal use of CFTDEST <IDTU=&idtu PART=&part &idf IDT=&idt>

Explanation

The identifier of a partner mentioned in a list (CFTDEST command) is itself a list identifier. As list embedding is not allowed, the transfer with this partner is interrupted.

Transfers with the previous partners in the list are nevertheless activated, but only for an explicit list (FNAME parameter of the CFTDEST command).

Consequence

The transfer is interrupted with a DIAGI 401.

Action

Change the partners list to show all the partners on one level.

 

V23 format

V24 format

Error

CFTT34E PART = &part IDF = &idf _ &cause

CFTT34E _ &cause<IDTU=&idtu PART = &part IDF=&idf>

Explanation

Access error on an external file describing a list of items:

  • Partners list: CFTDEST FNAME=#filename,
  • File group: SEND FNAME=#filename,

Possible values of &cause are:

  • Allocating external file &file
  • Opening external file &file
  • Reading external file &file

The file processing phase (allocation, opening or reading) is specified in the message.

Consequence

The external file cannot be read - the corresponding transfers are not activated.

Action

Correct the file access problem.

 

V23 format

V24 format

Warning

CFTT35W PART=&part IDF=&idf IDT=&idt DELETE file &fname Failed _&str

CFTT35W DELETE file &fname Failed _&str <IDTU=&idtu PART = &part IDF=&idf IDT=&idt>

Explanation

A DELETE command is executed on a catalog request (in receive mode and in a non-terminated H or K state).

The receive file corresponding to this request could not be deleted.

“ ” (no label): The file cannot be deleted; inform Product Support

  • Allocate file error: File allocation error
  • Open file error File open error
  • Close file error: File closing error
  • Free file error: File release error
  • Allocate memory error: Memory allocation error

Consequence

The request is deleted from the catalog but the user is notified that the &wfname file has not been deleted.

 

V23 format

V24 format

Warning

CFTT36W PART=&part IDF=&idf IDT=&idt ERASE file &fname Failed &str

CFTT36W ERASE file &fname Failed &str <IDTU=&idtu PART = &part IDF=&idf IDT=&idt>

Explanation

A DELETE command is executed on a catalog request (in receive mode and in a non-terminated state).K or H

The purge of the received file that corresponds with this request could not be carried out:

  • Allocate file error: File allocation error
  • Open file error : File open error
  • Close file error: File clofile close error
  • Free file error: File release error
  • Allocate memory error: Memory allocation error

Consequence

The request is deleted from the catalog but the user is notified that the &fname file has not been purged.

 

V23 format

V24 format

Information

CFTT37I PART=&part _ Not found and ignored for CFTDEST &id

CFTT37I _ Not found and ignored for CFTDEST &id <IDTU=&idtu PART=&part>

Explanation

The new parameter NOPART for the CFTDEST command can have on of the following values: ABORT (default value), CONTINUE, or IGNORE.

  • ABORT: Transfer CFT continues functioning as it was before the request for change.

No transfer is generated if a partner does not exist in the list of partners defined in the PART parameter. If the list of partners is defined in the PART parameter. If the list of partners is defined in a file (FNAME parameter) the transfers carried out for the only for existing partners and the treatment is identical to that for the NOPART=CONTINUE option.

  • CONTINUE: If the partner does not exist, Transfer CFT indicates this in a message in the LOG.

CFTT32E PART=idpart Not found. Pass the transfer in SFK diagi 408 and continue the transfers for the other partners. The generic post remains in the K state and the end of transfer procedure is not executed.

  • IGNORE:
  • If a partner does not exist in the list, Transfer CFT ignores the partner (there is no transfer) and moves on to the next partner.
  • A message is displayed in the LOG   CFTT37I PART=idpart _ Not found and ignored for CFTDEST iddest
  • The generic job passes to the T state and is under the end of transfer procedure.

 

V23 format

V24 format

Information

CFTT38I PART=&part _ Dynamic partner: &npart

CFTT38I _Dynamic partner: &npart < PART=&part DIAG=&diag>

Information

When receiving an incoming call from an unknown source (no local partner description corresponding to the &part network name received), the &npart dynamic partner creation mechanism is triggered.

 

V23 format

V24 format

Error

CFTT39E PART=&part DIAG=&diag _ Access Exit Connect Reject

CFTT39E _ Access Exit Connect Reject <PART=&part DIAG=&diag>

Explanation

The connection is refused by the directory EXIT task; &diag contains the field in the communication structure updated by the EXIT.

Consequence

The transfer is aborted with the following diagnostics codes: 403, 409, 410, 411, 414, 415, 416, 418, 425, 426.

 

V23 format

V24 format

Error

CFTT40E PART=&part DIAG=&diag _ Access Exit Error

CFTT40E _ Access Exit Error <PART=&part DIAG=&diag>

Explanation

An error has been detected in the directory EXIT task.

Consequence

The transfer is aborted with the following possible diagnostics codes: 134, 423.

 

V23 format

V24 format

Error

CFTT42E part&PART=<Partner switching IPART=PART not available

CFTT42E _ Partner switching IPART=PART not available <PART=&part>

Explanation

The IPART value must be different than the PART value.

 

V23 format

V24 format

Error

CFTT44E PART=&part IDF=&idf _ &str directory &file

CFTT44E _ &str directory &file <IDTU=&idtu PART=&part IDF=&idf>

Explanation

The file selection phase is indicated in the message, where &str can be allocating, opening, empty, or reading.

A directory access error has been detected when sending a list of file names or a group of files based on a selection.

SEND FNAME = # FIL* or SEND FNAME = # DIR*.

Consequence

If the directory could not be accessed (allocating, opening or empty), no transfers are triggered.

If the directory could not be read when selecting the files in the directory, all transfers preceding the error are triggered.

 

V23 format

V24 format

Error

CFTT44W PART=&part IDF=&idf _ &str directory &file (file not found ignored)

CFTT44W _ &str directory &file <IDTU=&idtu PART=&part IDF=&idf> (file not found ignored)

Explanation

The file selection phase is indicated in the message, where &str can be allocating, opening, empty, or reading.

A directory access error has been detected when sending a list of file names or a group of files based on a selection.

SEND FNAME = # FIL* or SEND FNAME = # DIR*.

Consequence

If the directory is empty, Transfer CFT ignores the fact that the file is not found, and passes the transfer to the X phase.

Action Ignore this error.

 

V23 format

V24 format

Error

CFTT45E PART=&part _ Partner switching IPART=&ipart not found

CFTT45E _ Partner switching not found <PART=&part IPART=&ipart>

Explanation

The intermediate partner (IPART) was not found.

Consequence

The transfer cannot be performed.

 

V23 format

V24 format

Warning

CFTT46W PART=&part ,IDF=&idf ,IDT=&idt _ Part inactive: mode &str

CFTT46W _ Part inactive: mode &str <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

The transfer attempt for partner &part cannot succeed as the partner is inactive in &str mode:

  • &str= requester or
  • &str = server

 

V23 format

V24 format

Error

CFTT47E PART=&part IDF=&idf IDT=&idt PROTOCOL=&id _ Cannot find SSL security profil

CFTT47E _ Cannot find SSL security profil <IDTU=&idtu PART=&part IDF=&idf IDT=&idt PROTOCOL=&prot>

Explanation

The attempted transfer the &part partner cannot be performed because the security profile was not found. For more information on SSL definition for CFTPART, see the SSL parameter description.

Consequence

The transfer can not be carried out.

 

V23 format

 

V24 format

 

V23 format

 

V24 format

 

Warning

CFTT47W PART=&part IDF=&idf IDT=&idt PROTOCOL=&prot SSLid=&id DIRECT=CLIENT _ Cannot find SSL security profil

CFTT47W _ Cannot find SSL security profil <IDTU=&idtu PART=&part IDF=&idf IDT=&idt PROTOCOL=&prot SSLID=&id DIRECT=CLIENT>

CFTT47W PART=&part SSLid=&id DIRECT=SERVER _ No SSL security profile for additional checks

CFTT47W _ No SSL security profile for additional checks <PART=&part SSLID=&id DIRECT=SERVER>

Explanation

The transfer attempt for partner &part uses a non-existent CFTSSL (&sslid).

Action

Check the configuration and add the missing profile.

 

V23 format

V24 format

Error

CFTT48E PART=&part SSL=&id _ Server Session rejected reason=&reason

CFTT48E _ Server Session rejected reason=&reason <PART=&part SSL=&ssl>

Explanation

The attempted transfer the &part partner cannot be performed because the security profile is not valid, with as an internal reason (&reason).

Consequence

The transfer can not be carried out.

Action

Note the REASON (&reason) value and contact the product support team if necessary.

 

V23 format

V24 format

Warning

CFTT49W Unable to send data to Synchronous task

CFTT49W Unable to send data to Synchronous task

Explanation

Synchronous communication task is inaccessible.

 

V23 format

V24 format

Error

CFTT50E PART=&part IDF=&idf IDT=&idt _ Duplicate transfer with IDTU=

CFTT50E _ Duplicate transfer with IDTU=&idtu <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

A duplicate transfer occurred. IDTU=&idtu is the previously performed transfer.

For more information, see the DUPLICAT field details.

 

V23 format

V24 format

Information

CFTT51I PART=&part ,&str session opened

CFTT51I PART=&part ,&str session opened

Explanation

The session is open, the connection request has been accepted (requester side (&str= requester if not secured, &str=SSL requester) or server (&str = server if not secured , &str=SSL server if secured)).

 

V23 format

V24 format

Information

CFTT52I PART=&part ,&str session closed

CFTT52I PART=&part ,&str session closed

Explanation

The session is closed: requester side (&str = requester if not secured, &str = SSL requester if secured) or server (&str = server if not secured , &str = SSL server if secured).

 

V23 format

V24 format

Information

CFTT53I PART=&part IDF=&idf IDT=&idt &str file &str1

CFTT53I &str file &str1 <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

The file is selected (&str1 = selected) or created (&str1 = created) either by the requester (&str = requester) or by the server (&str = server).

 

V23 format

V24 format

Information

CFTT54I PART=&part IDF=&idf IDT=&idt ,&str file deselected

CFTT54I &fname file deselected <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

The file is deselected either by the requester (&str = requester) or by the server (&str = server).

 

V23 format

V24 format

Information

CFTT55I PART=&part IDF=&idf IDT=&idt ,&str file opened

CFTT55I &fname file opened <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

The file is opened either by the requester (&str = requester) or by the server (&str = server).

 

V23 format

V24 format

Information

CFTT56I PART=&part IDF=&idf IDT=&idt ,&str file closed

CFTT56I &fname file closed <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

The file is closed either by the requester (&str = requester) or by the server (&str = server.

 

V23 format

V24 format

Information

CFTT57I PART=&part IDF=&idf IDT=&idt IDS=&ids,&str transfer started

CFTT57I &str transfer started <IDTU=&idtu PART=&part IDF=&idf IDT=&idt IDS=&ids>

Explanation

The transfer has been started either by the requester (&str = requester) or by the server (&str = server).

Note IDS refers to the session identifier.

 

V23 format

V24 format

Information

CFTT58I PART=&part IDF=&idf IDT=&idt IDS=&ids,&str transfer ended

CFTT58I &str transfer ended <IDTU=&idtu PART=&part IDF=&idf IDT=&idt IDS=&ids>

Explanation

The transfer has been completed either by the requester (&str = requester) or by the server (&str = server).

Note IDS refers to the session identifier.

 

V23 format

V24 format

Information

CFTT59I PART=&part IDM=&idf IDT=&idt ,&str <message|reply> transferred

CFTT59I &str <message|reply> transferred <IDTU=&idtu PART=&part IDM=&idm IDT=&idt>

Explanation

The message or the reply has been sent either by the requester (&str = requester) or by the server (&str = server).

 

V23 format

V24 format

Information

CFTT60I &str

CFTT60I IDTU=&idtu &str

Explanation

The &str message is an information message, sent by the file EXIT associated with the transfer.

 

V23 format

V24 format

Error

CFTT61E PART=&part IDM=&idf IDT=&idt local message reject &diagi ,&diagp

CFTT61E local message transfer reject <IDTU=&idtu PART=&part IDM=&idm IDT=&idt &diagi ,&diagp>

Explanation

The local partner rejects the message transfer.

Consequence

The message transfer is not executed.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT62E PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

CFTT62E <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The transfer was interrupted by the operator (&diagp = "OPER") or by the file EXIT (&diagp represents the phase of the EXIT which prompted the interruption = "ALLOC", "OPEN", TRANS or CLOSE).

Consequence

The transfer is aborted. The corresponding catalog entry is set to HOLD (after a HALT command from the operator or an interrupt by the EXIT), KEEP (after a KEEP command from the operator).

Action

After an interruption by the operator, the transfer can be restarted manually (START command).

After interruption by a file EXIT, the action is to be defined by the engineers responsible for this file EXIT.

 

V23 format

V24 format

Error

CFTT63E IDTU=&idtu MODE=&str Transfer refused due to product key limitation until &date

CFTT63E _ Transfer refused due to product key limitation until &date <IDTU=&idtu MODE=&mode>

Explanation

The license key is limiting the number of transfers in this time frame, where:

  • &str : REQUESTER or SERVER

 

V23 format

V24 format

Error

CFTT64E PART=&part IDF=&idf _ Flow does not exist and cft.default_idf.enable is set to 'no'

CFTT64E _ Flow does not exist and cft.default_idf.enable is set to 'no' <PART=&part IDF=&idf>

Explanation

The default IDF functionality is disabled for the command.

Consequence

The transfer is not executed and has the status K. The DIAGP also reflects this status.

Action

For parameter details, see UCONF: General unified configuration parameters.

 

V23 format

V24 format

Error

CFTT65E PART=&part IDF=&idf IDT=&idt PROT=&prot _ Protocol not available

CFTT65E _ PROT=&prot not available <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

The &prot protocol is not authorized for this partner.

Consequence

The transfer is not executed, and the corresponding catalog entry is set to KEEP. DIAGI=410 ,DIAGP = NO PROT

Action

Check the PROT value in the SEND or RECV transfer.

 

V23 format

V24 format

Error

CFTT66E Maximum number of partners authorized by license key reached (using PART=&part)

CFTT66E Maximum number of partners authorized by license key reached (using PART=&part)

Explanation

Transfer CFT license keys support either a limited or unlimited number of partners. The transfer is treated as if the partner does not exist.

Consequence

An error occurred because you have reached the maximum number of partners allowed by your license key.

Action

In a command line window, you can enter the command CFTUTIL ABOUT to check the number of partners that your license key authorizes. For additional information on license keys, contact an Axway sales representative.

 

V23 format

V24 format

Error

CFTT68E PART=&part IDF=&idf IDT=&idt _ Unexpected AT phase/phasestep at restart, converting T to K

CFTT68E _ Unexpected AT phase/phasestep at restart, converting T to K <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

If Transfer CFT was stopped abruptly when creating one or more child transfers for the current generic transfer, when you restart Transfer CFT you cannot manage these transfers (AT phase/phasestep).

Consequence

The corresponding transfer entry in the catalog now switches to the K phasestep instead of the previous T phasestep.

Action

You can continue to manage the affected transfer (those in K phasestep).

 

V23 format

V24 format

Error

CFTT69E PART=&part IDF=&idf IDT=&idt _ Unexpected YE phase/phasestep at restart, converting E to H

CFTT69E _ Unexpected YE phase/phasestep at restart, converting E to H IDTU=&idtu, PART=&part, IDF=&idf, IDT=&idt

Explanation

If Transfer CFT was stopped abruptly during the post-processing phase, when you restart Transfer CFT you cannot manage these transfers (YE phase/phasestep).

Consequence

The corresponding transfer entry in the catalog now switches to the H phasestep instead of the previous E phasestep.

Action

You can continue to manage the affected transfer (those in H phasestep).

 

V23 format

V24 format

Information

CFTT70I The user &user is connecting with method &method

CFTT70I The user &user is connecting with method &method

Explanation A client is trying to connect to the server.

V23 format

V24 format

Error

CFTT70E The user &user is not allowed to connect to the server

CFTT70E The user &user is not allowed to connect to the server

Explanation The user is not allowed to connect to the server, or the password or the authentication method is incorrect.
Action Correct the user name or password, or add a public key.

V23 format

V24 format

Error

CFTT71E PART=&part IDF=&idf IDT=&idt remote creation reject &diagi ,&diagp

CFTT71E remote creation reject <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The file was not created, the internal &diagi code explains the reason for the rejection (see the chapter on internal Transfer CFT codes).

Consequence

The transfer is not executed. The corresponding catalog entry is put on HOLD.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT72E PART=&part IDF=&idf IDT=&idt remote selection reject &diagi ,&diagp

CFTT72E remote selection reject <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The file was not selected; the internal &diagi code explains the reason for the rejection (see the topic on internal Transfer CFT codes).

Consequence

The transfer is not executed. The corresponding catalog entry is put on HOLD.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT72W PART=&part IDF=&idf IDT=&idt remote selection reject (file not found ignored) &diagi ,&diagp,

CFTT72W remote selection reject (file not found ignored) <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

Explanation

FILENOTFOUND=IGNORE The file was not selected because the file is not found.

Consequence

The transfer is aborted.

 

V23 format

V24 format

Error

CFTT72E PART=&part IDF=&idf IDT=&idt remote selection reject &diagi ,&diagp

CFTT72E remote selection reject <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

Explanation

FILENOTFOUND=ABORT The message was not sent.

Consequence

The message transfer is aborted. The corresponding catalog entry is put on HOLD.

V23 format

V24 format

Error

CFTT73E PART=&part IDM=&idf IDT=&idt &diagi ,&diagp

CFTT73E <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The message was not sent.

Consequence

The message transfer is aborted. The corresponding catalog entry is put on HOLD.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT74E PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

CFTT74E <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The transfer was interrupted by the remote partner.

Consequence

The transfer is aborted, the corresponding catalog entry is put on HOLD.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT75E PART=&part IDF=&idf IDT=&idt connect reject &diagi ,&diagp

CFTT75E connect reject <IDTU=&idtu PART=&part [IDF=&idf | IDM=&idm] IDT=&idt &diagi ,&diagp>

Explanation

The connection request was rejected by the partner.

Consequence

The transfer failed. If the called number was engaged or a network incident occurred (for example), the transfer will be retried several times (see the RETRYM, RETRYN and RETRYW parameters).

If all retries fail, the transfer is not executed and the corresponding catalog entry is set to KEEP.

Action

Analyze the internal &diagi error code for the transfer and try to correct it.

V23 format

V24 format

Error

CFTT75E Incorrect user or password <IDTU=&idtuPART=&part IDF=&idf IDT=&idf DIAGI=&diagi>

CFTT75E Incorrect user or password <IDTU=&idtuPART=&part IDF=&idf IDT=&idf DIAGI=&diagi>

Explanation

Cannot connect to the SFTP server because the user name or password is incorrect.

Action

Correct the user name or password.

 

V23 format

V24 format

Error

CFTT76E PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

CFTT76E <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The write transfer request is refused.

Consequence

The transfer is not executed. The corresponding catalog entry is put on HOLD.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT77E PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

CFTT77E <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The read transfer request is refused.

Consequence

The transfer is not executed. The corresponding catalog entry is put on HOLD.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT78E PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

CFTT78E <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

A problem was detected at the end of the transfer.

Consequence

The transfer has terminated but is not considered to be valid, the corresponding catalog entry is set to DISP (transfer to be restarted), on HOLD (the transfer may be restarted) or to KEEP.

Action

Automatically by Transfer CFT or manually by the user (correct the error, restart or try a new transfer).

 

V23 format

V24 format

Error

CFTT79E PART=&part IDF=&idf IDT=&idt remote deselect reject &diagi ,&diagp

CFTT79E remote deselect reject <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The file could not be deselected.

Consequence

The transfer is interrupted. The corresponding catalog entry is put on HOLD.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT80E PART=&part IDF=&idf IDT=&idt remote open reject &diagi ,&diagp

CFTT80E remote open reject <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The file could not be opened.

Consequence

The transfer is interrupted. The corresponding catalog entry is put on HOLD.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT81E PART=&part IDF=&idf IDT=&idt remote close reject &diagi ,&diagp

CFTT81E remote close reject <IDTU=&idtu PART=&part IDF=&idf IDT=&idt &diagi ,&diagp>

Explanation

The file could not be closed.

Consequence

The transfer is interrupted. The corresponding catalog entry is put on HOLD.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT82E PART=&part [IDF=&idf | IDM=&idm] IDT=&idt transfer aborted &diagi ,&diagp

CFTT82E transfer aborted <IDTU=&idtu PART=&part [IDF=&idf | IDM=&idm] IDT=&idt &diagi ,&diagp>

Explanation

A serious error was detected.

Example

19/02/19 16:01:37 CFTT82E Transfer aborted <IDTU=A0000008 PART=PARIS_KEY IDF=AS3SR IDT=B1916013 DIAGI=110

19/02/19 16:01:37 CFTT82E+ DIAGP=00000002 DIAGC=File not found: zohs.bat>

Consequence

The transfer is interrupted and the corresponding catalog entry is set to KEEP.

Action

Correct the error and try again.

 

V23 format

V24 format

Error

CFTT82W PART=&part IDF=&idf IDT=&idt transfer aborted (file not found ignored) &diagi ,&diagp

CFTT82W transfer aborted (file not found ignored) <IDTU=&idtu PART=&part [IDF=&idf | IDM=&idm] IDT=&idt &diagi ,&diagp>

Explanation

File not found error was detected.

Consequence

The transfer ignore the file not found problem and pass to X phase.

Action

Ignore the error.

 

V23 format

V24 format

Information

CFTT83I PART=&part IDF=&idf IDT=&idt change direction(CD) for request

CFTT83I change direction(CD) for request <IDTU=&idtu PART=&part [IDF=&idf | IDM=&idm] IDT=&idt>

Explanation

This message is only displayed for the ODETTE protocol and a RECV command. It indicates that the remote partner has accepted its turn to transmit.

 

V23 format

V24 format

Information

CFTT86I PART=&part IDS=&ids Change direction(TURN) sent

CFTT86I Change direction(TURN) sent <PART=&part IDS=&ids>

Explanation

For a PeSIT protocol in a DMZ profile, the token (TURN) has been sent to the partner &part.

 

V23 format

V24 format

Information

CFTT86I FNAME=&fname S=ByteCount

CFTT86I FNAME=&fname S=ByteCount

Explanation

Name of the file sent or received and the number of bytes in the file. This new message completes the CFTT54I message. Name of the file sent or received and the number of bytes in the file. This message completes the CFTT54I message.

 

V23 format

V24 format

Information

CFTT87I PART=&part IDS=&ids Change direction(TURN) received

CFTT87I Change direction(TURN) received<PART=&part IDS=&ids>

Explanation

In the case of PeSIT protocol in a DMZ profile, the token (TURN) has been received by the partner &part, where IDS is the reference for the session context.

 

V23 format

V24 format

Information

CFTT88I+IDT=&idt WORKINGDIR=&workingdir FNAME=&fname NBC=&n DURATION=&time

CFTT88I+<IDTU=&idtu WORKINGDIR=&workingdir FNAME=&fname NBC=&n DURATION==&time>

Explanation

This message completes the message CFTT54I.

The following fields indicated:

  • WORKINGDIR: if the WORKINGDIR is not defined, this field is empty
  • fname: name of the file sent
  • n: number of bytes in the file
  • time: transfer duration in seconds

 

V23 format

V24 format

Information

CFTT89I PART=&part IDF=&idf IDT=&idt Faction on FNAME=&fname : &str+"deleted" or "erased"

CFTT89I Faction on FNAME=&fname : &str+"deleted" or "erased" <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Explanation

Delete or erase message for a file after using the FACTION parameter in a transfer command (either SEND or RECV).

The file is either erased or deleted (FACTION=ERASE or FACTION=DELETE) at the end of the transfer.

Information CFTT89I Faction on FNAME=&srcfile as &archivefile <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>
Explanation

Archive message for a file after using the FACTION parameter in a transfer command (either SEND or RECV).

The file is archived (FACTION=ARCHIVE) at the end of the transfer.

 

V23 format

V24 format

Warning

CFTT90W IDF=&idf IDT=&idt Faction on FNAME=&fname : erase failed cs

CFTT90W IDF=&idf IDT=&idt Faction on FNAME=&fname : erase failed &scs

Explanation

At the end of a transfer, if the parameter FACTION=ERASE cannot be carried out (for example, if the file is already used by another user) the transfer moves to the T state.  

Warning

CFTT90W IDF=&idf IDT=&idt Faction on FNAME=&fname : delete failed cs

Explanation

At the end of a transfer, if the parameter FACTION=DELETE cannot be carried out (for example, if the file is already used by another user) the transfer moves to the T state.  

Action

Delete or erase the file manually.

 

V23 format

V24 format

Warning

CFTT91W PART=&part IDS=&ids Change direction(TURN) not supported by server

CFTT91W Change direction (TURN) not supported by server PART=DMZ1 IDS=&ids

Explanation

When using the DMZ mode, if the server does not accept the TURN, the session is closed by the requester without message. The IDS is the reference for this session context.

Action

This message is edited on LOG file.

V23 format

V24 format

Information

CFTT92I IDTU=&idtu CTX=&ctx IDT=&idt

CFTT92I <IDTU=&idtu CTX=&ctx IDT=&idt>

Explanation

Additional message for message CFTT57I, and is displayed only if ATM traces are activated.

CTX=&ctx provides the protocol context associated with the transfer.

 

V23 format

V24 format

Warning

CFTT93W PART=&part IDS=&ids Negative ack not supported

CFTT93W Negative ack not supported PART=&part IDS=&ids

Explanation

The  final partner signals to the initial file sender that application errors were detected. This occurs via a negative acknowledgments sent in a PeSIT Hors SIT message, where IDS is the reference for the session context.

 

V23 format

V24 format

Information

CFTT94I PART=&part IDF=&idf IDT=&idt FCHARSET=&str NCHARSET=&str

CFTT94I <IDTU=&idtu PART=&part IDF=&idf IDT=&idt FCHARSET=&str NCHARSET=&str>

Explanation This information message relates to the extended transcoding used for this transfer.

 

V23 format

V24 format

Error

CFTT95E Incorrect user or password <IDTU=&idtu PART=&part IDF=&idf IDT=&idtf DIAGI=&diagi>

CFTT95E Incorrect user or password <IDTU=&idtu PART=&part IDF=&idf IDT=&idt DIAGI=&diagi>

Explanation Cannot connect to the SFTP server because the user name or password is incorrect.
Action Correct the user name or password.

 

V23 format

V24 format

Information

CFTT96I &str transfer restarted <IDTU=&idtu PART=&part IDF=&idf IDT=&idt POS=&pos IDS=&ids>

CFTT96I &str transfer restarted <IDTU=&idtu PART=&part IDF=&idf IDT=&idt POS=&pos IDS=&ids>

Explanation The requester (&str = requester) or the server (&str = server) has restarted the transfer. &pos is the file position during restart.

V23 format

V24 format

Error

CFTT97E cmd prefix not allowed in procedure execution for SEND and RECV commands",

CFTT97E cmd prefix not allowed in procedure execution for SEND and RECV commands

Explanation

 

V23 format

V24 format

Error

CFTT98W PART=%-8.8s IDF=%-8.8s IDT=%.8s Rename ignored because WFNAME equals FNAME,

CFTT98W Rename ignored because WFNAME equals FNAME <IDTU=%.8s PART=%s IDF=%s IDT=%.8s>

Explanation The configuration has the same WFNAME as the RECV FNAME and so the renaming is ignored.

 

Related Links