Transfer CFT messages: CFTT

CFTT00E: CFT request warning _ &str

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

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

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

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

Transfer the files with this partner in closed mode.

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

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

The transfer is not executed.

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).

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

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.

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

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

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

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

The transfer is not restarted.

Try a new transfer.

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

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

The transfer will be retried via the intermediate partner IPART.

CFTT07W: Ending Transfer Task &n Failed _ A transfer Running

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.

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

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

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

Analyze the causes of the broken communication link.

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

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

The transfer is refused locally.

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).

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

The &prot protocol is not authorized for this partner.

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

Check Transfer CFT parameter settings.

CFTT11E: PART=&part PROT=&prot CLASS=&n _ &net not found

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

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

Check the Transfer CFT parameter settings.

CFTT12W: PART=&part IDF=&idf IDT=&idt _ Out of time to call

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

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

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

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

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

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

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

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

Check the Transfer CFT parameter settings.

CFTT15E: NPART=&part _ Not found

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

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

Check the Transfer CFT parameter settings.

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

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

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

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

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

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

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

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

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

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

Check the Transfer CFT parameter setting.

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

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

*where &str = supplied password is incorrect

The connection is refused.

Execute a new transfer with a valid password.

CFTT20E : PART=&part _ PVC not allowed

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

The connection is refused. 

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

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

The transfer is interrupted (or not executed).

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

CFTT23E: PART=&part Shutdown in progress _ &str

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.

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

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

The connection is refused.

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

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

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

Request that another file be sent or authorize this identifier.

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

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).

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

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.

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

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

The accounting file is incomplete.

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

CFTT28E: No outgoing CV configured on Network

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

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.

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

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

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.

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

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

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

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

CFTT31W: Ending Exit Task &n Failed _ A transfer Running

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.

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

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

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

Check the Transfer CFT parameter settings.

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

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).

The transfer is interrupted with a DIAGI 401.

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

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

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.

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

Correct the file access problem.

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

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

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

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

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

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

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

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.

CFTT38I: PART=&part _ Dynamic partner: &npart

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.

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

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

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

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

An error has been detected in the directory EXIT task.

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

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

The IPART value must be different than the PART value.

CFTT44E: PATR=&part IDF=&idf _ &str directory &file

&str can be allocating, opening, empty, 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*. The file selection phase is indicated in the message.

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.

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

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*.

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

CFTT45E : PART=&part IDF=&idf _ &char not allowed in filename

Generic file receive requests are not supported.

&char designates the indirection character (FILE_SYMB) specific to each environment.

The transfer cannot be performed.

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

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

• &str= requester or
• &str = server

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

The attempted transfer the &part partner cannot be performed because the security profile was not found.

The transfer can not be carried out.

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

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

The transfer can not be carried out.

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

CFTT49W: Unable to send data to Synchronous task

Synchronous communication task is inaccessible.

CFTT50E _ Duplicate transfer with IDTU=A0000001 <IDTU=A000000A PART=BCLPM + IDF=HETERODUP IDT=B0915105>

A duplicate transfer occurred.

IDTU=A000001 is the previously performed transfer.

For more information see the DUPLICAT field details.

CFTT51I: PART=&part ,&str session opened

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)).

CFTT52I: PART=&part ,&str session closed

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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

CFTT60I: &str

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

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

The local partner rejects the message transfer.

The message transfer is not executed.

Correct the error and try again.

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

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).

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).

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.

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

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).

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).

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.

CFTT64E PART=part IDF=idf _ Default IDF not enable

The default IDF functionality is disabled for the command.

The transfer is not executed and has the status K.

For parameter details, see UCONF General unified configuration parameters.

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

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

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

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

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

Correct the error and try again.

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

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

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

Correct the error and try again.

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

The file was not selected because the file is not found.

Transfer CFT ignores that the file is not found, and passes to the X phase.

Ignore the error.

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

The message was not sent.

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

Correct the error and try again.

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

The transfer was interrupted by the remote partner.

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

Correct the error and try again.

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

The connection request was rejected by the partner.

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.

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

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

The write transfer request is refused.

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

Correct the error and try again.

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

The read transfer request is refused.

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

Correct the error and try again.

CFTT78E: PART=&part IDF=&idf IDT=&idt remote transfer end reject &diagi ,&diagp

A problem was detected at the end of the transfer.

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.

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

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

The file could not be deselected.

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

Correct the error and try again.

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

The file could not be opened.

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

Correct the error and try again.

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

The file could not be closed.

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

Correct the error and try again.

CFTT82E: PART=&part IDF=&idf IDT=&idt transfer aborted &diagi ,&diagp

A serious error was detected.

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

Correct the error and try again.

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

File not found error was detected.

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

Ignore the error.

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

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.

CFTT86I FNAME=%-64.64s S=ByteCount

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

CFTT86I FNAME=%-64.64s S=ByteCount

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

CFTT86I PART=&part Change direction(TURN) sent

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

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

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.

CFTT88I FNAME=&fname NBC=&n;

-or-

CFTT88I WFNAME=&wfname NBC=&n;

This message completes the message CFTT54I.

The following fields indicated:

• fname: name of the file sent
• n: number of bytes in the file

When using FACTION=RETRYRENAME:

• wfname: name of the temporary file
• n: number of bytes in the file

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

New delete or erase message for a file following the faction parameter for a transfer command (either send or receive).

At the end of the transfer the file was either erased or deleted (FACTION=ERASE or FACTION=DELETE).

• IDF=&idf  
• IDT=&idt
• Faction on FNAME=&fname
• &str\n str = deleted or erased

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

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.  

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

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.  

Delete or erase the file manually.

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

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.

This message is edited on LOG file.

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

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

None