|
I wonder if you could use the exit point that Byteware uses in V5R3 to handle new IFS files? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 12/03/2004 01:01 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> cc Subject RE: Catch an error in ILE PRG On Fri, 3 Dec 2004 rob@xxxxxxxxx wrote: > > If there's a command RLSIFSLCK, doesn't that imply that there would be an > api to list ifs locks? If there is no IFS lock then process the file? > Don't know why I didn't think of this when receiving FTP from customers. > Yeah, there's an API called QP0LROR (Retrieve Object REferences) that will list the locks on an IFS object. Carsten Flensburg wrote a sample program that demonstrates this API at the following link (requires a free "associate' membership to the iSeries Network): http://www.iseriesnetwork.com/article.cfm?ID=18313 An interesting way to determine when a new file is added (instead of checking every 10 seconds) might be to journal an IFS directory. Use the RCVJRNE command in a NEP with an exit program that's called each time a new file is created in the IFS. Have the exit program use QP0LROR to wait until the file is unlocked, and then process it. I think Carsten may have done an article on that as well, but I can't find it... -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.