DATA_TRANSFER

Configures the queue as a data transfer queue for LSF data manager.

Syntax

DATA_TRANSFER=Y | N

Description

The DATA_TRANSFER=Y parameter enables a queue for data transfer through LSF data manager.

Only one queue in a cluster can be a data transfer queue. Any transfer jobs that are submitted by the data manager go to this queue. If the lsf.datamanager file exists, then at least one queue must define the DATA_TRANSFER parameter. If this parameter is set, a corresponding lsf.datamanager file must exist.

Regular jobs that are submitted to this queue through bsub are rejected.

Use the bstop, bresume, and bkill commands to stop, resume, and kill your own transfer jobs in a data transfer queue. LSF administrators and queue administrators can additionally use the btop and bbot commands to move transfer jobs in the queue. All other commands on jobs in a data transfer queue are rejected. You cannot use the bswitch command to switch jobs from other queues to a data transfer queue.

If you change this parameter, LSF data manager transfer jobs that were in the previous queue remain in that queue and are scheduled and run as normal. The LSF data manager is notified of their success or failure.

The following queue parameters cannot be used together with a queue that defines the DATA_TRANSFER parameter:
  • INTERACTIVE=ONLY
  • RCVJOBS_FROM
  • MAX_RSCHED_TIME
  • REQUEUE_EXIT_VALUES
  • SUCCESS_EXIT_VALUES
  • RERUNNABLE

A data transfer queue cannot appear in the list of default queues that are defined by the DEFAULT_QUEUE parameter in the lsb.params file. Jobs that are submitted to the data transfer queue are not attached to the application specified by the DEFAULT_APPLICATION parameter in the lsb.params file.

Use the SNDJOBS_TO to enable an LSF data manager data transfer queue as a remote send-jobs queue in the execution cluster.

If you specify a remote queue with the SNDJOBS_TO parameter in the data transfer queue in the execution cluster, the path of the FILE_TRANSFER_CMD parameter must exist in the submission cluster. You must also add the execution cluster to the RCVJOBS_FROM parameter (or use the allclusters keyword) for the remote queue in the submission cluster to receive jobs from (and push data to) the execution cluster.

Default

N