Re: [EXTERNAL] statistics on a job using RUNSQLSTM`

Hi Alan - very welcome are you!

Visual Explain will give up to a ton of information - when run over the contents of a database monitor it will be more precise, being based on actual performance data.

2 hours compared to 2 minutes is more than a conumdrum. (And I have no explanation, either, for why I couldn't spell conundrum just now!)

The entire environment is an important factor in performance, the optimizer changes its results based on memory, CPU, disk space, all kinds of things.

The optimizer typically will take the least of the time - I don't have any sense of exactly how long, I've not seen anything published. But after a certain statement has been run some, that optimization is save in the plan cache, which will be used if there have been no significant environment changes.

Now maybe there were locks - those are independent of what the optimizer decides but can have a strong influence on run-time, seems to me.

If this happens again, it might be worth looking at performance tools output - wait time is recorded there. I've not used it lately, I think the performance collection is generally turned on.

Too much rambling on a Sunday pre-noon!

Regards
Vern

On 11/29/2020 10:56 AM, Alan Shore via MIDRANGE-L wrote:

Thanks Jon (and again, Vern)
When I tried to run it yesterday - it was going for over an hour (more close to 2) before I killed it
I couldn’t see anything that showed me it was moving
I couldn’t see anything that was slowing it down
When I signed in this morning, I submitted it again - just to see what would happen
And it finished in less than 2 minutes
It was "bang your head against a brick wall" time
Im definitely going to look into the Visual Explain, just to see what needs to be done if nothing else, and who knows what this thing will do in the future
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
‘If you're going through hell, keep going.’
Winston Churchill


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Sunday, November 29, 2020 11:35 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [EXTERNAL] statistics on a job using RUNSQLSTM`

Just to add to Vern's comments so that the difference is clear.

The STRDBG approach is (almost) deprecated. IBM have not removed the capability but my understanding is that it has not been enhanced in a very long time (since V5 days I think). The Visual Explain in ACS is not only better but the only one being updated to ensure that its recommendations are accurate.


Jon

On Nov 28, 2020, at 8:43 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote:

Hi Alan

If you just execute the STRDBG command, then do anything SQL, there will be optimizer messages in the job log. These will tell you a little about how the system decided how to run the statements.

Better is Visual Explain - if you have ACS, it is part of that. There is a performance monitor, if you have the options of ACS installed.

If you have the older Access for i, I think you can set up a database monitor - you can do that in ACS, too - set it up on your job, then run RUNSQLSTM, your monitor will have stuff where you can analyze the statement and ultimately be able to get to Visual Explain.

HTH
Vern

On 11/28/2020 5:26 PM, Alan Shore via MIDRANGE-L wrote:

Thanks for the reply Carl
How do you run RUNSQLSTM Zin debug mode?
Where is visual explain (or its newer implementation)



Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone


-------- Original message --------
From: Carel <coteijgeler@xxxxxxxxx>
Date: 11/28/20 18:12 (GMT-05:00)
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: [EXTERNAL] Re: statistics on a job using RUNSQLSTM`

Perhaps run interactively in debug mode.

Then see the different messages in the joblog.

Or Visual Explain (otr its newer implementation).


Op 28-11-2020 om 21:01 schreef Alan Shore via MIDRANGE-L:

Hi everyone
We are on V7r3

I have a job that uses SQL code contained in a text file using
RUNSQLSTM The RUNSQLSTM is submitted to run in batch (SBMJOB) and
sometimes it runs in a really short time (a couple of minute or so)
Other times, it looks like its not moving

Is there any way of looking at this type of job and determining
where its at or what is causing it to run slow When I use work with
job, the joblog tells me nothing, just the RUNSQLSTM The call stack
doesn't show me much The same with open files There are no locks


Alan Shore
E-mail : ASHORE@xxxxxxxx<mailto:ASHORE@xxxxxxxx>
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill

--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

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

--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

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

--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

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