RE: Job Triggering on FTP Completion

You might ask the vendor to send a one record file with the current date and
time as the last step. Your job could check this file before starting
processing. If it hasn't changed since the last time then you know you need
to wait.

Albert


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, January 07, 2010 12:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: Job Triggering on FTP Completion

There is an ftp exit point, but it only works BEFORE the put. The
intention was to see if you wanted them to allow to perform an operation,
not process something after an operation was done. However, you could use
this exit point to do something like
- remote client wants to put a file here, tell them ok.
- dlyjob for a spell
- use some api's to see if there is a lock on the file being sent. (is the
put done?)
- process data...

Another technique is to routinely poll a library or directory to see if
there is an object in there and, if it is not locked, post it.

Or you could get tricky with journal entries to track when the stream file
or object is ready.


Rob Berendt