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



Very cool! In many counselors there is often wisdom!

Cheers
Vern

On 10/2/2017 5:05 PM, Don Brown wrote:
Thank you to all who replied.

I have modified the sql as follows which has solved the issue - joblog now
down to 3 pages.

TotAmt = 0;
select COALESCE(sum(uddamt + uddaoa + uddeam - uddcct - uddbkf), 0)
into :TotAmt

Just to reply to a couple of questions raised;

All the fields in the sum( ) are from the same file and are numeric fields
so if a record is retrieved there will not be null values in any of the
summed fields.

The where clause did result in no records found quite commonly and
therefore the reason the SQL0305 was being received - no records found =
null result. But the TotAmt was initialised to zero so while the sql
statement resulted in a null result the return value was still zero.

And I have removed the sql prefix from the variable :-)

Cheers


Don Brown




From: "Sam_L" <lennon_s_j@xxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 03/10/2017 03:46 AM
Subject: Re: SQL0305 Message in 5000 page joblog
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Don,

This suggestion from Steve appears to be what you should be doing:

> select (sum(coalesce(uddamt,0) + coalesce(uddaoa,0) +
coalesce(uddeam,0) - coalesce(uddcct,0) - coalesce(uddbkf,0)) into
:sqlToaAmt from your_table

From what I can tell, you are using 4 files and selecting just one
field, which is the sum over 5 fields. I can't tell from the names, but
I'd guess that the 5 fields come from at least two different files.

So, probably one (or more) of the joined files has no matching record
and the field from that file results in a null value. This null in turn
results in the sum returning a null.

Depending on your underlying logic, the program may currently be
returning incorrect results. I'd hazard a guess that if you change it to
use coalesce, you'll get different results from the original program
using the same data.

Sam

(Is the program checking SQLCOD or SQLSTATE after the select statement?
If not, it should.)


On 10/2/2017 8:35 AM, Steve Needles wrote:
Don,

I think that your math will fail as presented if any of the variables is
null. I don't know if it would result in an SQL0305 error or not.
You need to resolve each potentially null variable before being able to
use it in a SUM scalar function. I think that you will need something
like:
select (sum(coalesce(uddamt,0) + coalesce(uddaoa,0) + coalesce(uddeam,0)
- coalesce(uddcct,0) - coalesce(uddbkf,0)) into :sqlToaAmt from
your_table
Otherwise you are attempting math on invalid values. Nulls aren't
numbers after all.
Steve Needles
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.