Transfer CFT messages: CFTF

This topic lists the CFTFxx (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 the current version 3.1.3. 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>

Error

CFTF01E: PART=&part IDF=&idf IDT=&idt local file [&fname] creation error &diagi

Explanation

During a transfer request a local error was detected when creating a file.

Consequence

The transfer is not executed. The corresponding entry in the catalog is set to the K state if RKERROR=KEEP and the catalog entry is deleted by the Transfer CFT if RKERROR=DELETE.

Action

Analyze the file access system code, correct the error and try again.

 

Error

CFTF02E: PART=&part IDF=&idf IDT=&idt local file selection error &scs

Explanation

During a transfer request a local error was detected when selecting a file.

Consequence

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

Action

Analyze the file access system code, correct the error and try again.

 

Error

CFTF03E: PART=&part IDF=&idf IDT=&idt local file deselect error &scs

Explanation

During a transfer a local error was detected when releasing the transferred file.

Consequence

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

Action

Analyze the file access system code, correct the error and try again.

 

Error

CFTF04E: PART=&part IDF=&idf IDT=&idt local file open error &scs

Explanation

During a transfer request a local error was detected when opening a file.

Consequence

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

Action

Analyze the file access system code, correct the error and try again.

 

Error

CFTF05E: PART=&part IDF=&idf IDT=&idt local file close error &scs

Explanation

During a transfer a local error was detected when closing the file.

Consequence

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

Action

Analyze the file access system code, correct the error and try again.

 

Error

CFTF06E: PART=&part IDF=&idf IDT=&idt local file note error &scs

Explanation

During a transfer a local error was detected when recording the current position in the file.

Consequence

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

Action

Analyze the file access system code, correct the error and try again.

 

Error

CFTF07E: PART=&part IDF=&idf IDT=&idt local file point error &scs

Explanation

During a transfer restart a local error was detected when repositioning the pointer in the file.

Consequence

The transfer is not restarted and the corresponding catalog entry remains on HOLD.

Action

Analyze the file access system code, correct the error and restart the transfer.

 

Error

CFTF08E: PART=&part IDF=&idf IDT=&idt local file read error &scs

Explanation

During a transfer a local error was detected when reading the file.

Consequence

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

Action

Analyze the file access system code, correct the error and try again.

 

Error message

CFTF09E: PART=&part IDF=&idf IDT=&idt local file write error &scs

Explanation

During a transfer a local error was detected when writing the file.

Consequence

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

Action

Analyze the file access system code, correct the error and try again.

 

Error

CFTF13E: PART=&part IDF=&idf IDT=&idt remote file deselect error &diagp

Explanation

The file deselect operation was refused by the partner.

Consequence

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

Action

Correct the error and try again.

 

Error

CFTF21E: PART=&part IDF=&idf IDT=&idt storage allocation error &scs

Explanation

During a transfer a local error was detected when allocating memory.

Consequence

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

Action

Analyze the memory access system code, correct the error and try again.

 

Error

CFTF22E: PART=&part IDF=&idf IDT=&idt duplicate file &diagp

Explanation

A transfer requests the creation of a file but the file already exists - the FDISP parameter prevents the existing file from being erased.

Consequence

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

Action

Delete the existing file, revise the parameter settings, or receive the data in another file.

 

Error

CFTF23E: PART=&part IDF=&idf IDT=&idt file space allocation exhausted &scs

Explanation

During a transfer a local error was detected when writing the file (insufficient space reserved for the file).

Consequence

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

Action

Allocate more available space for this file.

 

Error

CFTF24E: PART=&part IDF=&idf IDT=&idt duplicate working file

Explanation

During a transfer using an intermediate file (CFTRECV FNAME =) an error was detected: the intermediate file already exists and consequently cannot be created.

Consequence

The transfer is interrupted.

 

Error

CFTF25E: PART=&part IDF=&idf IDT=&idt working file rename error &scs

Explanation

At the end of a transfer using an intermediate file (CFTRECV WFNAME =) an error was detected: the intermediate file could not be renamed.

Consequence

The file is correctly transferred but an error is reported to the Transfer CFT user.

 

Error

CFTF26E: PART=&part IDF=&idf IDT=&idt will be unable to rename working file

Explanation

During a transfer using an intermediate file (CFTRECV FNAME = ) an error was detected: the intermediate file could not be renamed at the end of the transfer (as the real file already exists).

Consequence

The transfer is interrupted.

 

Error

CFTF27E PART=part IDF=idf IDT=idt local /virtual file attribute mismatch

Explanation

There are invalid file attributes in CFTRECV command. The local file attributes (FLRECL or FRECFM) do not match with virtual file attributes.

(This is only applicable if FCHECK parameter is set to YES in the CFTRECV command.)

Consequence

The transfer is cancelled with DIAGP 139. DIAGP = ERR LRECL or ERR RECFM.

 

Warning

CFTF30W: PART=&part IDF=&idf IDT=&idt diagc&

Explanation

After an error, an additional message or two containing the DIAGC zones are displayed:

  • CFTF02E PART=BCLPM  IDF=TRTR  IDT=D1411215 local file selection error 38362112
  • CFTF30W PART=BCLPM  IDF=TRTR  IDT=D1411215 SIFM ALLOC : FILE NOT EXIST
  • CFTF30W PART=BCLPM  IDF=TRTR  IDT=D1411215 vbf.tst

 

Information

CFTF31I: PART=&idf IDF=&idf IDT=&idt EXIT=&id &user1  User id changed to &user2 the user id is modified by the exit

Explanation

Possibility for a file type exit to change the transfer owner (userid) in the Before File Allocation phase for a new transfer. This possibility is offered regardless of the transfer direction.

  • When sending, to open the file for the 'userid' account furnished by the exit.
  • When receiving, to create the file for the 'userid' provided by the exit.

 

Error

CFTF32E: PART=&part IDF=&idf IDT=&idt _ Maximum number of rename retries reached

Explanation

Maximum number of rename retries reached <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>.

Action

Check why the filename exists (when it should not).

Correct filename issue, for example manually rename the filename in question.

Restart the transfer.

See also Post-transfer file renaming.

 

Information

CFTF33I: PART=&part IDF=&idf IDT=&idt _ Rename to FNAME=&FNAME done

Explanation

The file was renamed, when using RETRYRENAME, and any post-processing or exits are executed.

 

Error

CFTF34E: PART=&part IDF=&idf IDT=&idt _ WFNAME=&WFNAME not found

Explanation

The rename operation failed because the file referenced by &WFNAME was not found (or does not exist).
Action

Check that the WFNAME is defined on the receiver side.

Correct and start a new transfer.

Related Links