Looked at it most of yesterday. And Visual Explain. The one stand out was
the HASH PROBE marked by VE as the biggest time consumer, the good run vs
the bad run, the I/O was about 10x more. Again Static data, Development
box, only two tables in Lib. Personally, I'm convinced after fighting this
for 6 days that IBM has a slight bug in their optomizer. I hope I'm wrong
and someone has an answer. IBM does not like to say they have an issue.

On Fri, Oct 19, 2018 at 1:11 PM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

My next thought would be another vote to try Performance Monitor.

-----Original Message-----
From: Dexter Thompson [mailto:dexter.thompson@xxxxxxxxx]
Sent: Friday, October 19, 2018 11:57 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: RPG and SQL

A very reasonable suggestion. I have already done this however and no
change. Sorry.

On Fri, Oct 19, 2018 at 10:45 AM Justin Taylor <JUSTIN@xxxxxxxxxxxxx>

I would definitely run this thru Visual Explain and create the
recommended index(es). It could improve it from minutes/hours to
Maybe not that much, but it should help.

If the system already has an access path, that can speed up execution.
I can't imagine that would cause it to jump, apparently randomly,
between minutes and hours to execute.

This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

This thread ...


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

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