Comments on: When using IfNull in my SQL, records are ignored

By: tomliotta

tomliotta — Fri, 24 Dec 2010 03:15:03 +0000

If I go straight to STRSQL and run it, it’s fine.

Note that you can’t run the same SQL in STRSQL. In your embedded SQL, you are creating a CURSOR and then FETCHing into host (program) variables. This is a distinctly different process and requires different analysis.

You can test general query structures with STRSQL. But “host variable” procedures are basically guesswork as far as STRSQL is concerned.

Tom

By: Ddaswani

Ddaswani — Tue, 21 Dec 2010 17:29:19 +0000

check ur SQLCODE…

IF its negitive eg -504 means ur getting null values in field while fetching

By: tomliotta

tomliotta — Sat, 18 Dec 2010 02:13:24 +0000

You might also want to try bringing a null indicator in when you FETCH the column:

C/Exec sql 
C+ FETCH C1 
C+ INTO  accountID,:xaddress  addrind
C/End-Exec

Does it “skip” rows or does it end after retrieving four rows? That is, is the fifth row the first one with a null address?

Tom

By: philpl1jb

philpl1jb — Sat, 18 Dec 2010 00:56:45 +0000

It might be your SQLCOD .. 100 is no data found. You will want to find out what value you are actually getting.

•If SQLCODE = 0 and SQLWARN0 is blank, execution was successful.
•If SQLCODE = 100, no data was found. For example, a FETCH statement returned no data, because the cursor was positioned after the last row of the result table.
•If SQLCODE > 0 and not = 100, execution was successful with a warning.
•If SQLCODE = 0 and SQLWARN0 = ‘W’, execution was successful with a warning.
•If SQLCODE < 0, execution was not successful.

and accountID,:xaddress must be correct types for accountID, and address
Phil