END - Confirm the end of processing

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 SEND and 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 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.

Select transfer parameters

You can use the following parameters to select a transfer.


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



APPCYCID Modify the processing cycle identifier
APPOBJID Modify the tracked object name
APPSTATE State of the end phase for the processing script to restart


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

DIAGC Modify the complimentary diagnostic information


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.
FNAME Name of the local file, directory, indirection file, selection mask or selection directory


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.

ISTATE Intermediate state indicating that the end phase has not finished
KDATE Command deposit date
KTIME Command deposit time
NFNAME The name of the physical file at the receiver partner site
PARM User parameter


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
PRI Priority of scheduled transfers
PHASE Phase of a catalog entry
PHASESTEP Phase step of a catalog entry
RAPPL The identifier of the file receiver application
RPASSWD The password for the user who is receiving the file
RUSER The identifier for the user who is receiving the file
STATE Transfer request state
SIGFNAME Contains signatures of the different signatories and the subscriber as defined by SUSER
SAPPL The identifier of the file sender application
SUSER The identifier for the user who is sending the file
SPASSWD The password for the user who is sending the file


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).

Modify transfer entries parameters

The following tables describes the parameters used to modify a transfer entry in the catalog.

Command Parameter Value Description
END DIAGC string Specify a comment.
FNAME string Modify the FNAME.
NFNAME string Modify the NFNAME.
SIGFNAME string Modify the SIGFNAME.
RAPPL string Modify the RAPPL.
SAPPL string Modify the SAPPL.
RUSER string Modify the RUSER.
SUSER string Modify the SUSER.
RPASSWD string Modify the RPASSWD.
SPASSWD string Modify the SPASSWD.


  • YES: The END command is only a checkpoint.
  • NO (default): This is the final end command indicating that the processing is over. Once the END completes, the transfer enters the next phase.
PHASE char The transfer phase at which the command is applied.
PHASE STEP char The phase step at which the command is applied.
APPSTATE string Specify an application state for the processing script that will help the script to restart at the right step if the script is relaunched.

Related Links