At the moment we are transferring files with XCOM on top of Windows Server 2016 but we are doing that manually and we are trying to move to an automated process.
You can create a script consisting of xcomtcp or xcom62 commands, just as you would write them on the command line and save them as a .bat file. For example:
xcomtcp -c1 –f /temp/loop.cnf REMOTE_SYSTEM=127.0.0.1 REMOTE_FILE=/temp/test.txt LOCAL_FILE=/temp/del.me USERID=XCOMABC PASSWORD=XXXXXXX QUEUE=YES
Just as you can initiate multiple transfers from the command prompt by using the NEWXFER command, you can also use this parameter in configuration files and in scripts.
There is also a feature called Interdependent Transfers in our online documentation. This allows you to code transfers that depend on whether a previous transfer was successful or failed.
You can run the script using the Windows Server Task Scheduler. There is also a Task Scheduler for Windows 7 and 10. It will start scripts at the dates and times that you choose.
Microsoft Documentation for Windows Task Scheduler
Although this documentation refers to earlier version of Windows, it exists in later versions also.