A view is just an encapsulated SELECT statement. There is no access plan stored with it - it gets re-optimized every time it is run. Now having said that, if it runs in SQE on V5R4, you have a system-wide plan cache that can help things. But you probably really need to see what the system recommends to make it run better - and you should probably put an OPTIMIZE clause in the SELECT - with just a few rows, to bias it toward returning more quickly, if it can. The easiest way to get performance info is in OpsNav - set up a monitor over ODBC jobs (QZDASOINIT) and run the thing. Give a call if you have not done that and want some help - we can talk lefse and bul pulsa and fatigmand.


-------------- Original message --------------
From: "Paul Nelson" <nelsonp@xxxxxxxxxxxxx>

I have managed to build a monster SQL view over a bunch of JD Edwards files.
The purpose is to access this view via an ODBC connection being used by a
web program.

When the first request from a user comes through, the results come back in
about five minutes, but thereafter, the retrieval is very quick.
Unfortunately, this happens for each user.

My request is this: I'm looking for suggestions for a way to have some
program either in the System i or in the web server get the file to open and
then keep it open until the end of the processing day.

For the old timers on the list, the best example I can think of is the
NEP-MRT technique used on the S/36 platform.


Paul Nelson
Cell 708-670-6978
Office 512-392-2577

This thread ...


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

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