RE: Automated upload - how to initiate.

Bob,

I've done something similar but with a subdirectory. PUT the file to the subdirectory then RENAME it to the primary directory for processing. The receiving process then scans the primary directory and doesn't have to worry about file extensions.

Paul

Principal Programmer Analyst
IT Supply Chain/Replenishment

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche
Sent: Friday, December 02, 2011 10:56 AM
To: Midrange Systems Technical Discussion
Subject: Re: Automated upload - how to initiate.

Another is to send the file with one extension and then rename it in the
ftp script to the final extension. I've done this with one company with
text files. They won't process the file until it has the correct
extension.





From:
rob@xxxxxxxxx
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
12/02/2011 09:51 AM
Subject:
Re: Automated upload - how to initiate.
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



One traditional way is to ftp two files. One is that file and another is
another file and your ftp exit point then processes the first file. Why
two files? Because the exit point is designed more for permissions than
this and therefore might try to process the file before it is finished
arriving. IOW, it gets called to see if the PUT is allowed, not after the

PUT is completed.

Another way is to ftp the file and use QUOTE RCMD to submit a command to
process it.

Another way is to use a journal entry process that says the file has
arrived, let's process it.

Another way is to use the exit points originally designed for virus
checking to say a stream file has arrived, let's process it.




Rob Berendt