Send Cancelation command

You can cancel the Send processing that is in progress and the Send processing that is queued in the Send Queue.

(1) Send Cancelation Command

F  Job name of Send program,CANCEL,F=fileid[,H=hostname][,{FORCE|ABSTP}]

F  Job name of Send program,CANCEL,NO=99999..999[,{FORCE|ABSTP}]

F=fileid

This parameter defines the file ID for the Send processing you want to cancel that is in progress or in the Send Queue. (Mandatory)

To cancel the sending-side transferring for instant transfer, specify "_INSTANT_TRANSFER_" for the file ID.

H=hostname

This parameter defines the name of the host on the receiving side for the Send processing that is in progress or in the Send Queue. (Optional)

Defaulting this parameter cancels all the Send processing for the relevant file ID.

NO=99999..999

This parameter defines the Send SEQ No. for the Send processing you want to cancel that is in progress or in the Send Queue. (Mandatory)

FORCE|ABSTP

These parameters define methods for canceling the Send processing. (Optional)

FORCE:

Forcibly cancel the Send processing.

ABSTP:

Forcibly cancel the Send processing and regenerate the Send Subtask after clearing the Send Subtask.

When you forcibly cancel the Send processing, the command may or may not notify the remote host of the cancelation, depending on the state of the Send program (XRSND).

When you default these parameters, the command notifies the remote host of the cancelation.

Note

  • The command cancels all the Send processing with the same host name or the same file ID.

  • The following processing is not carried out when the command cancels the Send processing:

    • Startup of the Post-send Job

    • Output to the Send Control file (HULFT.QUEUE)

  • In the following cases, even if the Send Cancelation request is acknowledged, it may take some time until cancelation of the Send processing is actually carried out:

    • The Transfer Interval (INTERVAL) is set to a large value.

    • HULFT is waiting for a response from a remote host.

  • You cannot cancel the Send processing in the following cases:

    • Connection to the remote host is not established yet

    • A Post-send Job is already started

    • An attempt of dynamic allocation processing for the Send file is in progress

  • By defining 'FORCE' to cancel the Send processing, you can also cancel the Send processing for which communication with the remote host is not taking place. However, when you define 'FORCE,' the command may or may not notify the remote host of the cancelation. If the remote host receives notification of the cancelation, HULFT on the remote host cancels the transfer. If the remote host does not receive the notification, the processing ends unsuccessfully on the remote host.

    Define 'FORCE' only to forcibly cancel the processing for which communication is not taking place.

  • Use 'ABSTP' only to cancel the Send processing when a deferred mount request is executed.

  • When you define 'ABSTP' to cancel the Send processing, the following restrictions apply:

    • For the Synchronous Transfer, the command cancels the transfer, but it does not cancel the synchronization of the Send File program (XRSNDGO) and the synchronization of the Send Request program (XRRCVREQ).

      To cancel the synchronization of the Send File program (XRSNDGO), refer to Send File and cancel the Synchronous Transfer.

      To cancel the synchronization of the Send Request program (XRRCVREQ), refer to Observe Cancelation command and cancel the service of the relevant Send Request.

    • For the Work File Transfer, the command does not delete work files. Delete the work files manually.

  • If you define 'ABSTP' to cancel the Send processing, HULFT may not release memory depending on the timing of the cancelation.

  • If you define 'ABSTP' to cancel the Send processing for some reason, HULFT may enter an unexpected state in which, for example, HULFT may not release the Send file.

    In this case, restart the Send program (XRSND) when possible.