Transfer CFT messages: CFTS

This topic lists the CFTSxx (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>

Warning

CFTS01W: Synch. response time-out _ Waitresp uplifted

Explanation

The message placed in a synchronous queue has received no response (time limit expired).

Consequence

Another attempt will be made.

 

Error

CFTS02E: PART=&part [IDF=&idf | IDM=&idm] IDT=&idt DIRECT=&direct  &fname not found

Explanation

The &fname procedure was not found for a given transfer (&idt).

This procedure was requested after a file or message transfer or subsequent to an error (see the Transfer CFT Online documentation, EXEC parameters).

 

Information

CFTS03I: PART=&part [IDF=&idf | IDM=&idm]IDT=&idt _ &fname executed

Action

The procedure (&fname) has just been executed for a given transfer (&idt).

This procedure was requested at the end of a file or message transfer, or in the event of an error (see the EXECxxx parameters).

 

Warning

CFTS04W: Action file &fname is empty

Explanation

An action is envisaged at the end of a transfer or in the event of an error (see the Transfer CFT Online documentation, EXECxxx parameters); the file to be submitted is empty.

 

Error

CFTS05E: Error code &scs _ Trying to access &str

The &str variable can have the following values:

&fname

Explanation

An access error was detected on a file.

This file (&fname) corresponds to an action requested at the end of a transfer or in the event of an error (see the Transfer CFT Online documentation EXECxxx parameters).

Consequence

The procedure will not be executed. If the action was requested at the end of a transfer, the transfer ends normally.

Action

Check that the characteristics of the file to be submitted are correct (attributes and length) and inform Product Support if necessary.

 

Error

CFTS06E: Error code &scs _ Trying to access temporary file

Explanation

An action was requested at the end of a transfer or in the event of an error. This action is submitted (see the EXECxxx parameters) through a buffer file (&fname).

An access error was detected on this buffer file.

Consequence

The procedure will not be executed. If the action was requested at the end of the transfer, the transfer ends normally.

Action

  • Check that the characteristics of the buffer file are correct (attributes and length).
  • Check that it exists (created or defined logically in the Transfer CFT startup procedure).
  • Contact Product Support.

 

Error

CFTS07E: Insufficient space for temporary file

Explanation

An action was requested at the end of a transfer or in the event of an error. This action is submitted (see the Transfer CFT Online documentation, EXECxxx parameters) through a buffer file (&fname). The space reserved for this file proves insufficient.

Consequence

The procedure will not be executed. If the action was requested at the end of the transfer, the transfer ends normally.

Action

Increase the file size, inform Product Support.

 

Error

CFTS08E: Error code &scs _ Executing temporary file

Explanation

The procedure (&fname) could not be executed for a given transfer (&idt).

This procedure was requested at the end of a file or message transfer or in the event of an error (see the Transfer CFT Online documentation EXECxxx parameters).

Consequence

The procedure will not be executed. If the action was requested at the end of the transfer, the transfer ends normally.

Action

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

 

Error

CFTS10E: File communication task error (&str1) _ &str2

Explanation

Following a synchronous message queue time-out, the communication task aborted.

The str1 and str2 values are:

str1

Associated str2 value

define sem

terminating

open

terminating

memory

terminating

post

terminating

invalid sem

terminating

catalog full

terminating

<cs code>

terminating

read

continue

delete shut

continue

 

Action

Contact Product Support.

 

Error

CFTS11E: Allocation error _ Trying to access temporary file

Explanation

An action was requested at the end of a transfer or in the event of an error.

This action is submitted (see the Transfer CFT Online documentation, EXECxxx parameters) through a buffer file (&fname). An allocation error was detected on this buffer file.

Consequence

The procedure will not be executed. If the action was requested at the end of the transfer, the transfer ends normally.

Action

  • Check that the characteristics of the buffer file are correct (attributes and length).
  • Check that it exists (created or defined logically in the Transfer CFT startup procedure).
  • Contact Product Support.

 

Warning

CFTS12W: Error code &scs _ CFT write messages to output stream

Explanation

The Transfer CFT logging process can no longer write messages in the log file(s) (problem adding to the file, system incident).

Consequence

Transfer CFT messages will be written to the standard output (screen for example).

Action

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

 

Error

CFTS13E: Semaphore failure &cs_CFTTPRO aborted

Explanation

Problem receiving an internal Transfer CFT message by the PROTOCOL task.

Consequence

A message has perhaps been lost; the reactions are unpredictable.

Action

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

 

Error

CFTS14E: ID=&id error initializing process

Explanation

Cannot run the end of transfer exit task. This message follows the Transfer CFT message CFTI01.

Consequence

No effect on the actual transfer (catalog not updated). The exit is not executed. If an end of transfer procedure was defined, it is run.

Action

Inform Product Support.

 

Information

CFTS15I: PART = &part Kill Session Reference &ctx:&ctx

Explanation

Internal message to Transfer CFT giving information on the transfer context killed. The &ctx values specify the context concerned.

 

Error

CFTS16E: Synch. response time-out_End transfer exit

Explanation

The exit task is run but does not respond to the Transfer CFT. This corresponds to the initial phase establishing communications between the Transfer CFT and the exit task.

Consequence

None on the actual transfer (catalog not updated). The exit is not executed. If an end of transfer procedure has been defined, it is run.

Action

Inform Product Support.

 

Error

CFTS17E: Error code &scs _ Trying to access End transfer exit

Explanation

Error posting a Transfer CFT message to the exit task during inter-task communications.

Consequence

None on the actual transfer (catalog not updated). The exit is does not receive any directives from the Transfer CFT.

Action

Inform Product Support.

 

Warning

CFTS18W: PART=&part [IDF=&idf | IDM=&idm] IDT=&idt _ Catalog record label

Explanation

label equals "State not updated x -> y" (x = current state, y = requested state) or "not deleted".

Transfer CFT catalog update problem.

Consequence

The catalog entry corresponding to the transfer is not updated.

Action

Inform Product Support.

 

Information

CFTS19I: PART=&part [IDF=&idf | IDM=&idm]IDT=&idt _ Catalog record label

Explanation

Information message label equals "updated x -> y"  (x = current state, y = requested state) or "deleted".

The Transfer CFT catalog is updated.

 

Information

CFTS20I: Message

Explanation

Message specific to the user exit.

 

Information

CFTS21I: PART=&part [IDF=&idf | IDM=&idm]IDT=&idt Exit request ID=&id

Explanation

Information message prior to sending information to the end of transfer exit.

Consequence

None.

 

Information

CFTS22I: Task time out End of transfer exit

Explanation

Exit task re-entry time-out. The task is stopped automatically.

Consequence

The exit task will be rerun by the next call.

Action

If necessary, increase the value of the WAITTASK parameter in the CFTEXIT card.

 

Error

CFTS23E: Bad user return code <details>

Explanation

Error message specific to the end-of-transfer user exit. The details that display in the message depend on the CFTLOG format (v23 or v24).

Example

V24 format:

CFTS23E Bad User return code: 4 <IDTU=idtu PART=part1 IDF=idf1 IDT=idt >

V23 format:

CFTS23E Bad User return code : 4 PART=part1 IDF=idf1 IDT=idt

Consequence

None.

 

Error

CFTS26E XTRK task error &str 

Explanation

Error initializing the Sentinel monitoring task.

Action

Take note of the complete text of the message (&str) and contact Axway Product Support. 

 

Error

CFTS27E: Synchronous communication task error CR=&cr &str

Explanation

Synchronous communication task error.

CR=&cr &str CFT

  • Internal synchronization error.
  • Password authentication error due to invalid user or password.

Consequence

Depending on the severity of the problem, the synchronous communication task can be stopped or continued (and either Terminating or Continue is displayed in the accompanying message &str).

Action

Notify Technical Support, if necessary. Furnish the complete message as well as the synchronous communication media parameters.

 

Information

CFTS29I Cannot acces XTRK task _ &str"

Explanation

Problem in communication with the Sentinel monitoring task.

Action

Take note of the complete text of the message and contact Axway Product Support. 

 

Information

CFTS30I XTRK Information &str"

Explanation

Elements of information concerning the Sentinel monitoring task.

The field "&str" is an explicit string:

“Buffer File Info : Current = nn , Max=mm”

where:

  • number of current records = nn
  • maximum number of records = mm

 

Warning message

CFTS31W XTRK Warning &str Error Code = &cr \n"

Explanation

The user is warned of a problem in communication with the Sentinel Server or the Sentinel Agent. The message is stored in the overflow file for the Sentinel monitoring task.

The text of the &str message specifies the possible type of warning:

sendMessage : send of a message to Sentinel

 

Warning

CFTS32W TCOMS Connection refused (address=nnn.nnn.nnn.nnn, name=userid)

Explanation

An incoming connection from name=userid and address=nnn.nnn.nnn.nnn was rejected because this address is not authorised for Synchronous Communication. See the CFTCOM object  ADDRLIST parameter.

 

Information

CFTS33I CFTLOG current file before switch

Explanation

For SWITCH LOG or SWITCH ACCNT:

  • Transfer CFT start-up
  • SWITCH operator
  • SWITCH cache command
  • SWITCH if file is full during a write
  • If no switch procedure is defined

 

Information

CFTS34I CFTLOG executed switch proc

Explanation

For SWITCH LOG or SWITCH ACCNT:

  • Transfer CFT start-up
  • SWITCH operator
  • SWITCH cache command
  • SWITCH if file is full during a write
  • If no switch procedure is defined

 

Information

CFTS35I CFTLOG current file after  switch

Explanation

For SWITCH LOG or SWITCH ACCNT:

  • Transfer CFT start-up
  • SWITCH operator
  • SWITCH cache command
  • SWITCH if file is full during a write
  • If no switch procedure is defined

 

Information

CFTS36I CFTACCNT current file (no switch executed)

Explanation

For SWITCH LOG or SWITCH ACCNT:

  • Transfer CFT start-up
  • SWITCH operator
  • SWITCH cache command
  • SWITCH if file is full during a write
  • If the two CFTLOG files are full and are not performing the switch:
  • CFTS36I CFTLOG current file (no switch executed): CFTOUT
  • If the two CFTACCNT files are full and are not performing the switch:
  • CFTS36I CFTACCNT current file (no switch executed): Files full

Information  

CFTS37I CRONJOB ID=%idcron, CRONTAB=%cronname %exec executed, NEXT=%s

CFTS37I CRONJOB: ID=%s, CRONTAB=%s ACT DONE

CFTS37I CRONJOB: RECONFIG type=CRON DONE

Explanation

Job defined by %exec is executed. correctly;The next submit is indicated in NEXT=date time

 

Error  

CFTS39E CRONJOB ID=%idcron, CRONTAB=%cronname exec %exec failed

Explanation

 Job failed. Could not file the file to submit. Check file properties.

 

Information

CFTS40F: CFTACCNT FORMAT=(V23/V24) not available for &fname

Explanation

An error occurred in the FORMAT=V23/V24 (V23 default) parameter of CFTFILE TYPE=ACCNT.
When using the V23 format, the saved description (for ACCOUNT files) is the same
as in previous versions.
However when using the V24 format, the length for saving is 2048,and  the saved description
takes into account the new longer field lengths.
Note: The FORMAT parameter for the CFTACCNT command must be the same setting as for
 CFTFILE TYPE=ACCNT. If not, a message displays in the LOG and Transfer CFT does
not start. The message is either::
   CFTS40F CFTACCNT FORMAT=V24 not available for CFT.ACCNT    

   CFTS40F CFTACCNT FORMAT=V23 not available for CFT.ACCNT
Followed by the message: CFTI17F Init error _ Account file .CFT.ACCNT

 

Information

CFTS41I: Catalog Alert exec &fname executed

Explanation

The procedure &FNAME for a catalog alert was executed.

  • When the critical fill threshold is reached, a message CFTC29W is recorded in the Transfer CFT log.

A batch, which is defined by the CFTCAT TLVWEXEC parameter, is submitted.

  • When the alert ceases, a message CFTC30W is recorded in the Transfer CFT log.

A batch, which is defined by the CFTCAT TLVCEXEC parameter, is submitted.

 

Error

CFTS42E: Catalog Alert exec &fname not found

or

CFTS42E : Catalog Alert exec &fname failed

Explanation

The procedure &FNAME for a catalog alert was not found or failed on access producing this error.

  • When the critical fill threshold is reached, a message CFTC29W is recorded in the Transfer CFT log.

The batch, which is defined by the CFTCAT TLVWEXEC parameter, is not executed

  • When the alert ceases, a message CFTC30W is recorded in the Transfer CFT log

The batch, which is defined by the CFTCAT TLVCEXEC parameter, is not executed.

 

Information

CFTS43I: RECONFIG 

Explanation

Displays information about CFTUTIL RECONFIG TYPE=UCONF.

 

Warning CFTS44W Unexpected message Class &n <TASK=&str>
Explanation An internal message received by the &str task has an unexpected class value (&n).
Consequence The message is ignored.

 

  CFTS45W Unexpected Message Type &n <TASK=&str CLASS=&str>
Explanation An internal message received by the &str task with CLASS=&str has an unexpected type value (&n).
Consequence The message is ignored.

 

Fatal CFTS46F CFTPRX error _ &str
Explanation A fatal error occurred in the proxy task (CFTPRX). The error details are in &str.
Consequence Transfer CFT stops.
Action If necessary, contact Axway support.

 

Error CFTS47E CFTPRX error _ &str
Explanation A significant error occurred in the proxy task (CFTPRX). The error is detailed in &str.
Consequence The concerned transfer goes into error.
Action If necessary, contact Axway support.

 

Warning CFTS48W CFTPRX _ &str
Explanation An anomaly occurred in the proxy task (CFTPRX). The anomaly details are in &str.

 

Information CFTS49I CFTPRX _ &str
Explanation Information message from the Proxy task (CFTPRX). The &str value gives additional details.

 

Fatal CFTS50F CFTJRE error _ &str
Explanation A fatal error occurred when starting the CFT Java task (CFTJRE). The error is detailed in &str.
Consequence Transfer CFT is stopping.
Action If necessary, contact Axway support.

 

Error CFTS51E CFTJRE error _ &str
Explanation A significant error occurred in the Transfer CFT Java task (CFTJRE). The error is detailed in &str.
Consequence The concerned transfer goes in error.
Action If necessary, contact Axway support.

 

Warning CFTS52W CFTJRE _ &str
Explanation An anomaly occurred in the Transfer CFT Java task (CFTJRE). The anomaly is detailed in &str.

 

Error CFTS53I CFTJRE _ &str
Explanation Information message from the Transfer CFT Java task (CFTJRE). The &str value gives additional details.

 

Error CFTS54F CFTACC task fatal CR=&cr &str
Explanation A fatal error occurred in the accelerator task (CFTACC). The error is detailed in &str.
Consequence Transfer CFT is stopping.
Action If necessary, contact Axway support.

 

Information CFTS55I Acceleration &str
Explanation Information message from the Accelerator task (CFTACC). the &str value gives more detail.

 

Error CFTS56E Central Governance error (<error_code>) <error_msg>
Explanation

An error occurred when executing a <request> on Central Governance.

Consequence The Transfer CFT instance does not display the correct status.

 

Warning

CFTS57W : Synchronous communication _ Authentication ignored : authentication_enable=yes but authentication_method=none

or

CFTS57W : Synchronous communication _ Authentication ignored : User=user01 Group=group01 provided a password but authentication_enable=no

Explanation

There are two possible scenarios:

  • Authentication_enable=yes but authentication_method=none

    In this case, in the unified configuration authentication is enabled but no mode is defined: uconf: cft.server.cftcoms.authentication_enable=yes

    uconf: cft.server.authentication_method=none

  • User=user01 Group=group01 provided a password but authentication_enable=no

    In the CONFIG command the PASSWORD parameter is set, but in the unified configuration it is disabled: uconf:cft.server.cftcoms.authentication_enable=no

 

Error CFTS59E Multi-node error _ &str
Explanation An important error occurred during the transfer recovery. The error is detailed in &str.
Consequence The transfer in question is not recovered.
Action Contact the support team if necessary.

Warning CFTS60W Multi-node _ &str
Explanation An anomaly occurred during the transfer recovery. The anomaly is detailed in &str.

 

Information CFTS61I Multi-node _ &str
Explanation Displays information about the multi-node transfer recovery phase. The &str value provides additional details.

 

Information

CFTS62I: Schedule

Explanation Displays information about UCONF scheduling.

 

Fatal

CFTS63F Secure Relay fatal error _ %s\n"

Explanation  

 

Information

CFTS64I Secure Relay _ %s\n"

Explanation  

 

Error

CFTS70F License key error _ %s\n"

Explanation  

Related Links