Re: V4R5 Query Select or Omit error..

[Larry Bolhuis <lbolhuis@xxxxxxxxxx>]

We had checked the options file and it was the correct one. I set the option 
there for debug level output to prove it.

Further testing appears to bear out these changes:

 In V4R5 the order in which Select/Omit is evaluated has changed from V4R3. 
The DB records causing the errors DID in fact have bad date data (though 
stored as numerics and converted to dates in result fields). However NONE of 
the records with bad dates should have been selected due to other select 
criteria. What we think has happend is that the 'weight' given to each 
select/omit line has changed. If select/omit was processed from top to bottom 
(as V4R3 SEEMED to do) then all was well. Now they appear to be processed by 
some internal weight. So when we added an additional s/o criteria which was 
simpler than the date (in our case omit records with month=0) now they run 
just fine consistantly.

 I can understand the changes though I cannot find them documented, but what 
really floors me is that they fail intermittantly. A query that runs 
interactively, runs with sbmjob cmd(runqry xxx) FAILS when inside of a CL 
program both in batch and on line! What is the difference there? Whyizzat?

rob@xxxxxxxxx wrote:
> WRKOBJ OBJ(*ALL/QAQQINI)
>
> Maybe it picks a different options file?
>
> Rob Berendt


--
Larry Bolhuis           | IBM eServer Certified Systems Expert
Vice President          |     iSeries Technical Solutions V5R2, V5R1, V4R5...
Arbor Solutions, Inc.   |     iSeries LPAR Technical Solutions V5R2
(616) 451-2500          |     e-business for AS/400 V4R2
(616) 451-2571 -fax     | IBM eServer Certified Systems Specialist
lbolhuis@xxxxxxxxxx     |     iSeries System Administrator for OS/400 V5R2
www.arbsol.com          |     RPG IV Developer
                        |     iSeries System Command Operations V5R2
                        |     Client Access


---
[This E-mail scanned for viruses by Declude Virus]