|
You can journal the IFS but you need to process the journal. Same issue
you currently have as far as resource.
Another option might be to have an FTP logon exit program that could wake
up your monitor process. Still doesn't help with knowing the transfer is
complete. Any chance the sender can send a "sentinel" file at end to let
your program know it is done?
For a third-party we were sending to, I had a similar issue. They
monitored for CSV files arriving so I transferred it with a "WIP"
extension and then renamed it to CSV when done so they would not pick it up
too soon.
It's been discussed here before....
http://archive.midrange.com/midrange-l/201402/msg00300.html
http://www.easy400.net/ifstool/html/ifstool.htm#C5
Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power
________________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Paula
Rice <paulajrice@xxxxx>
Sent: Monday, May 2, 2016 3:49 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Automated Job Processing
We are trying to automate a job on the 400. I've done it in Windows, but
can't figure out how on the 400.
General idea is that anytime a file appears in a folder it triggers the
designated program to run. Only similar idea is to set a program to run
every few minutes to check the folder, but that is very system intensive
for
files that may only be processed once a day. I'm also concerned about
making sure the file has been completely transferred as they are coming
through FTP. Don't want to start processing half a file.
Any suggestions/ideas would be appreciated.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.