RE: Processing Unit Time

Yes, I'm certain the it used the new logical PRTSQLINF shows that it used it.
Thanks,

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Luis Rodriguez
Sent: Tuesday, December 21, 2010 9:07 AM
To: Midrange Systems Technical Discussion
Subject: Re: Processing Unit Time

Michael,

Some (random) ideas:

* Use Coalesce in your SQL statements, in order to deal with null data.
* Are you sure the system used the index you created? Run your user's
statements with iSeries Nav's Visual Explain and check them.
* As I see it, processing time is the allocated CPU time, but between one
slice of time and another your system has a lot to do with another users and
processes (including, I suppose, dealing with those 23,000 job log pages :-
) )

My .02 cents :-) (and merry Xmas to you all)

Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries
--



On Tue, Dec 21, 2010 at 9:06 AM, Schutte, Michael D <
Michael_Schutte@xxxxxxxxxxxx> wrote:

I'm having trouble finding an explanation of this but I was wondering if
someone could explain this here. A user submitted a job the other day that
took 6 hours to complete. By looking at the SQL statement in the program, I
saw where an improvement could be made. I created a new logical by the
selection keys in the where clause, so now the statement take less than a
second to run for a month of data and the entire company. The user
resubmitted the job yesterday and this time it took 12 hours to complete
while using the new logical. If you look at the job log it says that it
only used 1448 seconds processing unit time. That's only 24 minutes. So
why did it take 12 hours. Is it because it created a 23,000 page job log?

There are two messages that are repeated over and over again that I can
fix. Dataarea CGIDEBUG not found and null indicator require. The reason
for the CGIDEBUG message is because I'm using the CGIDEV2 procedures to
build an HTML page and then use write to stream file function so that I can
email it to the user. Then for the null indicator, the sql statement is
summing a field but I'm not checking any statuses nor using a null
indicator. I've always just set the INTO field to zero prior to executing
the statement. I should change my habit to always use a null indicator so
that this message isn't created in the job log. But I don't see why this
would cause the program to run for 12 hours.

Any thoughts?


Bob Evans makes the holidays easier. Our Farmhouse Feast is a complete
holiday meal to go, ready to heat at home, serve and enjoy. Serves 6-8 for
just $74.99. Pre-order through your local Bob Evans or online at
www.bobevans.com/onlineordering<http://www.bobevans.com/onlineordering>



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