RE: Optimizing SQL

It's not just SEQUEL. Look at your ORDER BY clause. You can contact me off
line if you need some help.

Paul Nelson
Cell 708-670-6978
Office 708-425-4198
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of AGlauser@xxxxxxxxxxxx
Sent: Thursday, March 01, 2007 3:22 PM
To: Midrange technical discussions
Subject: Optimizing SQL

Hi all,

I'm working on a report to which I need to add a field.  In order to do 
so, I have to join to another file (making this a five table query).  I'm 
joining to this table using the key fields of the table.  For some reason 
I can't fathom, adding this extra table to the mix causes a temporary 
index to be built when the query is run.  It is a query built using ASC's 
SEQUEL. I've seen some recommendations on this list about running queries 
after a STRDBG on a job in order to get optimization info.  I tried that, 
but I only get useless messages like:

 CPI432C    Information             00   03/01/07  14:21:13.114976 
QQQIMPLE     QSYS        *STMT    QRYO07      SEQUEL      0085 
                                      From module . . . . . . . . : 
QQQIMPLE 
                                      From procedure  . . . . . . : 
QQQSNDPMSG 
                                      Statement . . . . . . . . . :   4729 
 
                                      Message . . . . :   All access paths 
were considered for file DSP080. 

 CPI4321    Information             00   03/01/07  14:21:13.121816 
QQQIMPLE     QSYS        *STMT    QRYO07      SEQUEL      0085 
                                      From module . . . . . . . . : 
QQQIMPLE 
                                      From procedure  . . . . . . : 
QQQSNDPMSG 
                                      Statement . . . . . . . . . :   4729 
 
                                      Message . . . . :   Access path 
built for file DSP080. 

Well thanks ... I already knew that!  I want to know _details_ about the 
access path.

Am I getting burned by using SEQUEL, or is this the same type of info I'd 
get using RUNSQLSTM?

I also tried using Visual Explain in OpsNav, but I got an error about the 
query being 'too complex or using unsupported functions'.

Any ideas?
Adam

Attention:

The information contained in this message and or attachments is 
intended only for the person or entity to which it is addressed and may
contain 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in reliance upon,
this 
information by persons or entities other than the intended recipient is 
prohibited. If you received this message in error, please contact the sender
and 
delete the material from any system and destroy any copies. Thank you for
your 
time and consideration.

Attention: 

Le contenu de ce message et(ou) les fichiers ci-joints s?adressent 
exclusivement à la personne ou -entité à laquelle ils sont destinés. Ils
peuvent 
contenir de l?information confidentielle, protégée et(ou) classifiée. Il est

strictement interdit à toute personne ou entité autre que le(la)
destinataire 
prévu(e) de ce message d?examiner, de réviser, de retransmettre ou de
diffuser 
cette information, de prendre une quelconque action en fonction ou sur la
base 
de celle-ci, ou d?en faire tout autre usage. Si vous avez reçu ce message
par 
erreur, veuillez communiquer avec l?expéditeur(trice), supprimer ce message
et 
les fichiers ci-inclus de tout système, et en détruire toutes copies,
qu?elles 
soient électroniques ou imprimées. Nous vous remercions de votre entière 
collaboration.