Problem

Doing a post-transfer procedure with only a REPLY and an END command is for people who need belt and suspenders!

Double check your needs, it is most probably an unnecessary additional anti-performance treatment.

The same apply doing only a END command in an EOT script.

In both cases above, the best choice is doing nothing.

Resolution

This is what are doing CFT's delivered EOT procedures but it is provided as samples to have things working as a DEMO out of the box.

Unfortunately, too many customers implemented the same in real life.

More than that, using default 'demo' samples they also set the flows with Ack required.

This considerably weighs down the configuration for steps that are useless at all.

A Reply, issued to Ack a transfer, is at a price of a new session. (The transfer session is not re-used for this since it is an applicative Ack not supposed to be sent straight after the transfert done)

Doing it from the EOT procedure does not add any value since the EOT procedure is itself executed only if the transfer is completed already.

The Ack feature should to be use when an application Acknowledgement is needed.

An EOT procedure doing only the END command is also useless since no EOT procedure, the transfer is automatically ENDed.

If the CFTPARM is set with default EOT procedures (EXECSF/EXECRF), it can be bypassed at CFTRECV / CFTSEND level (or flow level) in setting EXEC = '_none_', that way, no EOT script will be triggered and the transfer will be completed (ENDed) automaticaly.