1 Reply Latest reply on Apr 21, 2019 1:25 PM by Mark Francome

    Control-M Archival and File Transfer Job Failed Troubleshooting

    Kaiquan Mah
      Share This:

      Hi all,


      1. The moment a Control-M File Transfer job has successfully completed, the source file would no longer be in the source system folder. True/False?


      2a. Is there a way to archive the source system file once the transfer job was successfully completed?

      2b. Is there a way to ensure that the source system file is no longer found in the source system folder after archival has successfully completed?


      3a. When the Control-M File Transfer job fails, the original source file remains in the source system folder? True/False?

      3b. From 3a, the target file which is still being transferred and failed will be removed from the target system folder? True/False?


      4. From 3a and 3b, when the Control-M File Transfer job fails, we can restart the File Transfer job. Is there a way to ensure that the source system file we are sending in the restarted job is not already in the target system folder?

        • 1. Re: Control-M Archival and File Transfer Job Failed Troubleshooting
          Mark Francome



          Yes to all of these (nearly all, at least) but you'll have to check out the 'advanced' settings on the AFT/MFT job definition.


          Once you define the job, enter the source and destination details of the file(s) and then click the advanced button. You might be limited to some options depending on the kind of job that you are defining.


          1. You don't necessarily need to delete the source file but in the advanced area you'll see an option like "delete source after transfer completed" - click that and the local file will be deleted


          2a. Again on the advanced button - select "copy file to new location" and enter the details you require.


          2b. You could create a separate file watcher job to do this, or even try to use a post-exec command to get this functionality).


          3a/b. This is defined in the job. Again in the advanced area, there are options to specify what to do in the event of a transmission failure. Usually you define it to delete the destination file on failure and leave the source alone.


          If the files are big then there's also the "restart from failure", so you don't waste too much when re-running.


          4. There are several advanced options to deal with duplicates, my suggestion is that you overwrite the destination file if there's one there already there with the same name.


          The advanced options should give you enough scope to cover your needs.

          1 of 1 people found this helpful