fte:filemove Ant task

The fte:filemove task moves files between Managed File Transfer agents. When a file has been successfully transferred from the source agent to the destination agent, the file is deleted from the source agent.


Attributes

    cmdqm
    Optional. The command queue manager to submit the request to. Specify this information in the form qmgrname@host@port@channel, where:

    • qmgrname is the name of the queue manager
    • host is the optional host name of the system where the queue manager is running
    • port is the optional port number that the queue manager is listening on
    • channel is the optional SVRCONN channel to use

    If we omit the host, port, or channel information for the command queue manager, the connection information specified in the command.properties file is used. For more information, see The MFT command.properties file.

    We can use the com.ibm.wmqfte.propertySet property to specify which command.properties file to use. For more information, see com.ibm.wmqfte.propertySet.
    If we do not use the cmdqm attribute, the task defaults to using the com.ibm.wmqfte.ant.commandQueueManager property, if this property is set. If the com.ibm.wmqfte.ant.commandQueueManager property is not set, a connection to the default queue manager, defined in the command.properties file, is attempted. The format of the com.ibm.wmqfte.ant.commandQueueManager property is the same as the cmdqm attribute, that is, qmgrname@host@port@channel.

    dst
    Required. Specifies the destination agent for the copy operation. Specify this information in the form: agentname@qmgrname where agentname is the name of the destination agent and qmgrname is the name of the queue manager that this agent is directly connected to.

    idproperty
    Optional unless you have specified an outcome of defer. Specifies the name of a property to assign the transfer identifier to. Transfer identifiers are generated at the point a transfer request is submitted and we can use transfer identifiers to track the progress of a transfer, diagnose problems with a transfer, and cancel a transfer.
    We cannot specify this property if you have also specified an outcome property of ignore. However, we must specify idproperty if you have also specified an outcome property of defer.

    jobname
    Optional. Assigns a job name to the move request. We can use job names to create logical groups of transfers. Use the fte:uuid task to generate pseudo-unique job names. If we do not use the jobname attribute, the task defaults to using the com.ibm.wmqfte.ant.jobName property value, if this property is set. If we do not set this property, no job name is associated with the move request.

    origuser
    Optional. Specifies the originating user identifier to associate with the move request. If you do not use the origuser attribute, the task defaults to using the user ID that is used to run the Ant script.

    outcome
    Optional. Determines whether the task waits for the move operation to complete before returning control to the Ant script. Specify one of the following options:

      await
      The task waits for the move operation to complete before returning. When an outcome of await is specified the idproperty attribute is optional.

      defer
      The task returns as soon as the move request has been submitted and assumes that the outcome of the move operation is dealt with later using either the fte:awaitoutcome Ant task or fte:ignoreoutcome Ant task task. When an outcome of defer is specified the idproperty attribute is required.

      ignore
      If the outcome of the move operation is not important, we can specify a value of ignore. The task then returns as soon as the move request has been submitted, without allocating any resources for tracking the outcome of the transfer. When an outcome of ignore is specified the idproperty attribute cannot be specified.

    If we do not specify the outcome attribute, the task defaults to using the value await.

    priority
    Optional. Specifies the priority to associate with the move request. In general, higher priority transfer requests take precedence over lower priority requests. The priority value must be in the range 0 - 9 (inclusive). A priority value of 0 is the lowest priority and a value of 9 is the highest priority. If we do not specify the priority attribute, the transfer defaults to a priority of 0.

    rcproperty
    Optional. Specifies the name of a property to assign the result code of the move request to. The result code reflects the overall outcome of the move request.
    We cannot specify this property if you have also specified an outcome property of ignore or defer. However, we must specify rcproperty if you have specified an outcome of await.

    transferRecoveryTimeout
    Optional. Sets the amount of time, in seconds, during which a source agent keeps trying to recover a stalled file transfer. Specify one of the following options:

      -1
      The agent continues to attempt to recover the stalled transfer until the transfer is complete. Using this option is the equivalent of the default behavior of the agent when the property is not set.

      0
      The agent stops the file transfer as soon as it enters recovery.

      >0
      The agent continues to attempt to recover the stalled transfer for the amount of time in seconds as set by the positive integer value specified. For example, 
      <fte:filemove cmdqm="qm0@localhost@1414@SYSTEM.DEF.SVRCONN" 
              src=agent1@qm1 dst="agent2@qm2"
              rcproperty="move.result" transferRecoveryTimeout="21600">
                    
    <fte:filespec srcfilespec="/home/fteuser1/file.bin" dstfile="/home/fteuser2/file.bin"/>

</fte:filemove
      indicates that the agent keeps trying to recover the transfer for 6 hours from when it enters recovery. Maximum value for this attribute is 999999999.

    Specify the transfer recovery timeout value in this way sets it on a per transfer basis. To set a global value for all transfers in a Managed File Transfer network, we can add a property to the Transfer recovery timeout properties. For more information, see Timeout option for transfers in recovery.

    src
    Required. Specifies the source agent for the move operation. Specify this information in the form: agentname@qmgrname where agentname is the name of the source agent and qmgrname is the name of the queue manager that this agent is directly connected to.


Parameters specified as nested elements

    fte:filespec
    Required. We must specify at least one file specification that identifies the files to move. We can specify more than one file specification if required. See fte:filespec Ant nested element for more information.

    fte:metadata
    Optional. We can specify metadata to associate with the file move operation. This metadata is carried with the transfer and is recorded in the log messages generated by the transfer. We can only associate a single block of metadata with a given transfer element; however this block can contain many pieces of metadata. See the fte:metadata topic for more information.

    fte:presrc
    Optional. Specifies a program invocation to take place at the source agent before the transfer starts. We can only associate a single fte:presrc element with a given transfer. See the program invocation topic for more information.

    fte:predst
    Optional. Specifies a program invocation to take place at the destination agent before the transfer starts. We can only associate a single fte:predst element with a given transfer. See the program invocation topic for more information.

    fte:postsrc
    Optional. Specifies a program invocation to take place at the source agent after the transfer has completed. We can only associate a single fte:postsrc element with a given transfer. See the program invocation topic for more information.

    fte:postdst
    Optional. Specifies a program invocation to take place at the destination agent after the transfer has completed. We can only associate a single fte:postdst element with a given transfer. See the program invocation topic for more information.

If fte:presrc, fte:predst, fte:postsrc, fte:postdst, and exits do not return a success status, the rules are as follows in the order specified:

  1. Run the source start exits. If source start exits fail the transfer fails and nothing further is run.
  2. Run the pre-source call (when present). If the pre-source call fails, the transfer fails and nothing further is run.
  3. Run the destination start exits. If the destination start exits fail the transfer fails and nothing further is run.
  4. Run the pre-destination call (when present). If the pre-destination call fails, the transfer fails and nothing further is run.
  5. Perform the file transfers.
  6. Run the destination end exits. There is no failure status for these exits.
  7. If the transfer is successful (if some files transfer successfully, the transfer is considered successful), run the post-destination call (if present). If the post-destination call fails, the transfer fails.
  8. Run the source end exits. There is no failure status for these exits.
  9. If the transfer is successful, run the post-source call (if present). If the post-source call fails, the transfer fails.


Examples

This example shows a basic file move between agent1 and agent2. The command to start the file move is sent to a queue manager called qm0, using a client transport mode connection. The result of the file transfer operation is assigned to the property called move.result. 
<fte:filemove cmdqm="qm0@localhost@1414@SYSTEM.DEF.SVRCONN" 
              src=agent1@qm1 dst="agent2@qm2"
              rcproperty="move.result">
                    
    <fte:filespec srcfilespec="/home/fteuser1/file.bin" dstfile="/home/fteuser2/file.bin"/>

</fte:filemove>
Parent topic: fteAnt: run Ant tasks in MFT


Related information