|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.