|
>Running it as an interactive program would kill the performance on our iSeries. Brian, when you say "interactive" do you mean vs. "batch" where interactive is subject to processor restrictions and batch isn't, or do you mean interactive where a user waits and batch where they don't? Any request coming from ASP is going to be batch as far as iSeries work management is concerned -- the interactive "tax" doesn't apply to ASP applications. If you're worried about the user waiting, then simply write the records and call a CL to submit the job. The easiest way to call is CL from ASP is to descibe the CL as a stored proc to SQL (create procedure...) -Walden ------------ Walden H Leverich III Tech Software (516) 627-3800 x3051 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
