× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Michael,

Try running the process under debug (STRDBG/ENDDBG). That will get the SQL access plan printed in the job log. You can then review the access plan to see if it's actually using the logicals. Sometimes SQL will reject a logical for a sequential access if the previous run was very fast. It thinks a sequential read through the file will be faster than including the overhead of an indexed read.

Paul Morgan

Principal Programmer Analyst
IS Supply Chain/Replenishment

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Schutte, Michael D
Sent: Tuesday, December 21, 2010 8:37 AM
To: Midrange Systems Technical Discussion
Subject: Processing Unit Time

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>




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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