|
The RCVJRNE command itself is quite efficient. Since you haven't described what your exit program will be doing with the journal receiver entries, then the answer is gonna be rather vague as well. We have a number different processes using journal receiver entries and processing them in batch is quite controllable with the use of RUNPTY and TimeSlice settings. Another nice application is to invoke remote journals... Having a second 400 process the journal receiver entries off-loads the RCVJRNE command altogether. Good luck, you're on the right track since the files are already being journalled. No need to impact the I/O with triggers at this point. Ken Slaugh (707) 795-1512 x118 Chouinard & Myhre, Inc. CA/400 Certified Specialist iSeries Network/MSE Administrator http://www.cm-inc.com/ G Armour <garmour400m@xxxxxxx To: midrange-l@xxxxxxxxxxxx om> cc: Sent by: Subject: Questions on RCVJRNE and exit program midrange-l-bounces@x idrange.com 08/25/2003 12:27 PM Please respond to Midrange Systems Technical Discussion It appears that RCVJRNE is going to solve a dilemma for us very nicely. However, before we go headlong into it, we'd like to have an idea as to the additional overhead and whether user response may be impacted. Currently, the system on which we are considering doing this has thousands of users. Apparently, user response time is nearing an unacceptable threshold. I know this is vague, but is all I was given for the time being. So this will be difficult, if not impossible, for us to test in our development environment of ten users on a more than ample system. The file which we want to do a RCVJRNE is *already* being journaled; so the "additional impact", as I see it, is strictly whatever the RCVJRNE & exit program is doing. Before anyone asks, using a trigger program is out of the question, since triggers are already in use for the file and we are not being allowed to change them. TIA, GA __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com _______________________________________________ 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 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.