I just finished setting up an inbound ftp thread using advanced scheduling. There were a couple of surprises for me. One was that I needed to use a tps directory parse script to parse out subdirectories from the inbound list of files to grab. Without the directory parse script the engine tries to grab everything including subdirectories. When it can’t grab the subdirectory (not a file) it tosses an error in the process log file. The second is that despite the advanced scheduling if I bounce the process the ftp thread on startup goes to the server and looks for a file to grab. The thread is very stable. A third surprise is a temp log file that the ftp fileset protocol places in the process directory. The file is read/write/execute locked so it was causing backups to fail until the backup was changed to exclude this file. Other than this I like the thread it is reliable and it allows me to create the same smat files that my other threads are creating. I even changed the standard directory parse script to add entries into the process log file to indicate what files were found in the directory and which files it would try to parse for messages adding the date time to these messages.
