Re: Help with SQL

I think we're agreeing violently! Both Run SQL Scripts and STRSQL typically involve a person entering statements and pressing Enter or Ctrl-R - that has an "interactive" feel. Embedded SQL is can more often be running in batch, esp. when processing sets of records, a very common scenario.

OK, back to sleep I go!
Vern

On 1/17/2020 12:45 PM, Charles Wilt wrote:

It's not really interactive vs batch...

It's OPTIMIZE = *FIRSTIO vs OPTIMIZE = *ALLIO

STRSQL and Run SQL Scripts default to *FIRSTIO, embedded SQL defaults to
*ALLIO

But either can be changed.

Charles

On Fri, Jan 17, 2020 at 11:42 AM Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

This is also true - generally speaking interactive will try for faster
response, so it gets the first records. Batch tends to go for all.

The only situation that is truly interactive, IMO, is a display session.
Running statements in remote connections will tend toward the batch
approach.

Vern

On 1/17/2020 12:24 PM, Sam_L wrote:

Digging into my memory, seems to me that the optimizer may decide
differently on batch vs interactive execution. but it's been a while...

Sam

On 1/17/2020 11:49 AM, Vernon Hamberg wrote:

I agree with using Visual Explain - it would show any difference in
what the optimizer does.

Of course, when the environment changes, the optimizer might make
different choices.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com