× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Craig,
Instead of using the IFS Scan on Close, try journaling the IFS Folder,
then using a journal exit program to get the names of any new files.
I have been using the RCVJRNE command with the parms:

JRNCDE((B *ALLSLT)) ENTTYP(JT) ENTFMT(*TYPE1) EXITPGM(XXX)

The Exit Program then gets the file and path names for processing.
On Thu, Aug 9, 2012 at 12:58 PM, <craigs@xxxxxxxxx> wrote:


I'm looking at the IFS Scan on Close exit program (QIBM_QP0L_SCAN_CLOSE)
for executing a command after a file is placed in the IFS. The archives
mentioned this being used for antivirus software packages but I haven't
found any other uses. I thought I could use it for normal use but the
program data required (from the IBM InfoCenter) when registering the exit
program mentions the user profile, scan key, and scan key signature for the
qp0lscan.h as data type Qp0l_Scan_Program_Data_t. I looked at the
InfoCenter list of IFS exit programs from the InfoCenter and there were
only 4. This one looked closest to one I was wanting.
I know I could create a never-ending job to monitor for IFS files not
processed in another list or the never-ending job check last modified date.
I would like to use an exit program so extra processing wouldn't be
occurring for these files which aren't really going to be that frequent in
the first place.

Has anyone used the IFS Scan on Close exit program to execute commands to
execute after a file is created in the IFS? Any ideas what I would enter
in the scan key and scan key signature fields?

Thanks.
Craig Strong

--
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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.