KB Article #179537

CFT Transfer does not start (stays in State "TD" or "AD")

Problem

You may have an instance when transfers are stuck in States “TD” (or “AD” is you have Pre-Process Script) and would not start.

CFTUTIL LISTCAT may show output like this:

PARIS SFH TH TXT_SERI E0210494 0 0 110 38380544
PARIS SFD TD TXT_SERI E0210495 0 0 0 00:00:00
PARIS SFD TD TXT_SERI E0210500 0 0 0 00:00:00
PARIS SFD TD TXT_SERI E0210501 0 0 0 00:00:00
PARIS SFD TD TXT_SERI E0210502 0 0 0 00:00:00
PARIS SFD TD TXT_SERI E0210503 0 0 0 00:00:00


Resolution

This could be caused by "Transfer Serialization" (introduced in CFT 3.2.4).

When the Transfer Serialization is enabled (SERIAL=’Y’ or ‘X’), any transfer of the same IDF will wait for the previous transfer to COMPLETE (PHASE Y or X) before starting (stays in STATE D).

In the example above, first transfer (IDF= E0210494) failed with DIAGI=110 (file not found), and 5 transfers are waiting (STATE D) for the first transfer to complete.

To resolve this, you can either (1) fix the issue with the first transfer or (2) delete the first transfer from the catalog.

After the first transfer issue is resolved (or deleted in this example), the rest of transfers will complete in sequence (one by one):

PARIS SFX XX TXT_SERI E0210495 112 112 0 CP NONE
PARIS SFX XX TXT_SERI E0210500 112 112 0 CP NONE
PARIS SFX XX TXT_SERI E0210501 112 112 0 CP NONE
PARIS SFX XX TXT_SERI E0210502 112 112 0 CP NONE
PARIS SFX XX TXT_SERI E0210503 112 112 0 CP NONE

If you define End of Transfer script (EOT), and you code SERIAL=X, the EOT script must execute “END” command for the next transfer to start.

Also, if you defined a Pre-Process script, it is very important that the script executes “END” command, so that transfer will start (regardless of Serialization).