RE: V4R5 Query Select or Omit error..

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

Generally you need to open the query in change mode and then save it.  No
changes need to be made.  This updates the query optimizer setting for the
query and the new OS.  Believe it or not it works for most query problems
after upgrading the OS or changing the files from 4G to 1T.  That is why
when you run interactively from the work query screen, option 2, and press
F5 it works cause it builds new optimization before running where as the
runqry does not update the optimization table so the query basically is not
optimized.  I have had horrid queries that I run in debug, followed the
recommendations by building the access paths and saw so change until I
opened and saved the query.

Christopher K. Bipes      mailto:Chris.Bipes@xxxxxxxxxxxxxxx
Operations & Network Mgr  mailto:Chris_Bipes@xxxxxxxxx
CrossCheck, Inc.          http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884

NOTICE--This e-mail may contain confidential and privileged material for the
sole use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.



-----Original Message-----
From: Larry Bolhuis

> My guess is that there was a change in the query optimizer.  it's
> evaluating all fields in your select/omit list before determining how to
> build the query, and it thinks it will run faster by accessing that field
> first.

   We think so too.


   Additional update: Said query runs if you submit it as a RUNQRY but FAILS

if the RUNQRY is inside a CLP! What? The CLP is PGM, RUNQRY, ENDPGM!