I've got a 4 step process I'm trying to chain together to satisfy requirements from my vendor on file retrieval.

Step #1 logs onto their server using FTPS, and downloads a file. Works fine.

Step #2 should change directory on their server (while still logged in) and do a read/write and copy some files that are on that directory to a location on my local server. This does not appear to work.
Step #3 consolidates the files on my server. Works fine.
Step #4 sends consolidated files over to another server in my network. Works fine.

The troubles seems to be with attempting to change to a different directory in Step #2. I was under the assumption that once I executed Step #1, that I was logged into their server until I ended the entire Job. Is this correct? It behaves as if it executes #1 and then logs off, and Step #2 is "lost" so when it issues a CD command and file copy command, it just loops. When I stop the task, within the job I get a -1 return code.

Can I build a task that references a task which will run a script, or do I have to structure this differently in VC? I have to be able to maintain the FTPS session, while read/writing files from and to the remote server.

Hi esolch,

Every FTP task starts and ends the FTP session.
So task 1 opens and closes the connection.
Task 2 should also be an FTP task.

Can't you combine task 1 and 2 together in one FTP/FTPS/SFTP task?
You can have multiple up- and downloads in one task.


Also, the title is: Executing script from an FTPS connection Job, but in your tasks your not talking about executing a script, or is the CD command a script?


NB. When you are doing a custom command, you are not able to do file transfer.

Regards,
Erik

---

I've worked this out by splitting the tasks on the script out, and adding them as sub-tasks to the tasks under the job since the FTPS connection does not stay "open" in between. So instead of running a script, I've added "Upload", "Download", "Upload" and "Delete" to the task and it appears to work OK. The only thing I was thinking is that I could excute a script from a task within a job and I assumed that FTPS session stays "OPEN" during the duration of the job.

Still learning about this product. So far I give the product a big thumbs up. 👍