If you don't want to change a system value, you can also do something like
this to alter the QAQQINI for a specific job.  I use this method to control
the IGNORE_DERIVED_INDEX value.  I'm thinking that this routine becomes
obsolete with V6R1, at least for what I use it for.  I decided to put a
version of QAQQINI in library ROUTINES, so that I could alter its security,
since normal users don't have access to do a CRTDUPOBJ on QSYS/QAQQINI.
     PGM
/* Setup query options so that recursive SQL can be done to MBM  +
   despite having logicals built against it with selection +
   criteria which will not allow the new query engine to work */
     DLTF       FILE(QTEMP/QAQQINI)
     MONMSG     MSGID(CPF0000)
     CRTDUPOBJ  OBJ(QAQQINI) FROMLIB(ROUTINES) OBJTYPE(*FILE) +
                  TOLIB(QTEMP)
     CPYF       FROMFILE(QSYS/QAQQINI) TOFILE(QTEMP/QAQQINI) +
                  MBROPT(*ADD)
     CHGQRYA    QRYOPTLIB(QTEMP)
     RUNSQL     REQUEST('UPDATE QTEMP/QAQQINI SET QQVAL=''*YES'' +
                  WHERE QQPARM=''IGNORE_DERIVED_INDEX'' AND +
                  QQPARM<>''*YES''')
     ENDPGM
                                                                           
             "Steve R."                                                    
             <sriedmue@xxxxxxx                                             
             om>                                                        To 
             Sent by:                  midrange-l@xxxxxxxxxxxx             
             midrange-l-bounce                                          cc 
             s@xxxxxxxxxxxx                                                
                                                                   Subject 
                                       Re: RPG SQL and multi-threading     
             03/28/2008 12:11                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           
Wow, thanks for the quick response Darren.
In looking at the QQRYDEGREE system value, I see we have *OPTIMIZE on our
Dev and QA servers, but *NONE in Production.  I will try changing Dev
and/or
QA to *NONE and see if it resolves this issue.  We caught the problem in
Dev/QA and never moved the process up to Prod.
--
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.
As an Amazon Associate we earn from qualifying purchases.