END - Confirm the end of processing

This topic describes the END command. The END command is used to declare that the processing script (pre, post, or acknowledgement) has been executed correctly.

In most cases, this command is submitted to Transfer CFT via the processing procedure(s). It can, however, be submitted manually. The transfers must be in the C phasestep and changes to the next phase. See also About phase and phasestep for details on transfer work flows.

If there is an associated processing procedure, the PREEXEC, EXEC, ACKEXEC parameters of the CFTPARM, CFTSEND/SEND and CFTRECV/RECV commands are executed.

To declare the correct execution of the associated processing on completion of the transfer, an END command can be initiated by the operator or the processing procedure. After the END command is executed, the associated catalog entry changes to the next phase.

In the Odette, PeSIT E and PeSIT CFT profile protocols, an acknowledgement message can be sent to the sending partner. The sending of this message may be initiated by the operator or the post-processing procedure using the SEND TYPE=REPLY command. An example is given in Transfer-related procedures .


Use this command to declare that all the operations related to the end-of-transfer, both send and receive, have been executed correctly.



Catalog block number. If the values '*' or ' ' are used then all transfers are selected regardless of the block that they belong to.


Transfer direction for the requests in question.

The possible values are:

  • BOTH: (default) takes both send transfers and receive transfers into account,
  • RECV: limits the action to receive transfers,
  • SEND: limits the action to send transfers.


Local identifier of the transfer assigned by the user or user application.


Model file identifier.


Transfer identifier.


Catalog identifier. It is a unique, local reference to a transfer.


Partner identifier.

The value of this parameter may be:

  • an identifier: the command only concerns the transfers with this partner
  • a mask: the command concerns the transfers with the partners, whose identifiers correspond to this masks

Example 1








IDA = X32451


The send and receive transfers (DIRECT=BOTH by default) with the partner (PART) HQ whose local identifier (IDA) is X32451 and relative to the model file identified by (IDF) TEST, are set to the "terminated" state.

Example 2





IDT = A0110503


The transfer identified by (IDT) A0110503 relative to the partner (PART) HQ is set to the executed state. This transfer may be a send or receive transfer (DIRECT=BOTH by default).

Related Links