Re: Looking for file structure details -- MIDRANGE-L

× 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.

According to the information I’ve been given in recent years by IBM’s database experts such as Mike Cain, Kent Milligan and others it is becoming increasingly risky to base decisions on creating new indexes etc. on the debug information. It is many, many years since the debug information has been updated and consequently the decisions being made by the optimizer are not adequately reflected.

As Vern says, Visual Explain is the best and in practice should probably be the only tool you use.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jun 26, 2015, at 7:34 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote:

Another thought - less effort then Visual Explain - put your job in debug - just run the STRDBG command and be sure you say to update production files, if needed. Our STRDBG defaults to UPDPROD(*NO).

The run your SELECT or your program - the job log will have messages about which indexes were considered and why some were not used.

Hope this gives you a direction to go - these tools will save your backside!

I mentioned Visual Explain - that's the best, for lots of reasons - c'mon back if you want to hear more - many here know how to use it well.

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.