RE: Automated Job Processing

You can look at exit programs for the IFS. In particular QIBM_QP0L_SCAN_CLOSE

This exit program will be called every time an IFS file is closed. You can create a database with the directories to monitor. If the directory is not in the list, the exit program just ends with the appropriate exit code. If it is in the list, you can have an action to perform such as calling a program and passing the data from the exit point.


Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Harman
Sent: Monday, May 02, 2016 4:29 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Automated Job Processing

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