Problem

Often Transfert CFT fails to start due to a time-out reason

Error message after "cft start" is issued:

Starting Transfer CFT...

Starting Transfer CFT with IDPARM "IDPARM0" and 128 transferts active

Transfer CFT Working Directory : /opt/axway/Q/cft/runtime

***Timeout Reached.................]17% STARTING Multinodes Init (timeout 31/30)

Or:

***Timeout Reached.................]49% STARTING Tr Sched Alloc (timeout 31/30)

CFT installation is a standalone and not a multi-node

Resolution

Delete (or backup) all CFT.OUT files and start again.

Such an issue is usually due to the existing CFT.OUT file being very large or filled with unexpected contents.

The root cause is usually due to scripts launched by CFT (EOT procedure) and issuing CFTUTIL commands.

The default stdout for those script is the CFT.OUT files.

A good habit is to ensure CFTUTIL output is not filling the CFT.OUT files and it can be achieved by adding the option "/m=40" to all CFTUTIL call in post processing scripts:

For example:
Use

cftutil /m=40 send part=part1,idf=test

instead of:

cftutil send part=part1,idf=test