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



If you go out on www.think400.dk/downloads.htm you will find a document
called "Using Nulls in RPG and SQL" that might provide some insight. If you
have questions, please let me know.

Nulls can get trickee because RPG does not have the ability to specify that
a variable is null so you have to use separate variables for the nulls and
pass them around. IBM wants use to use SQL and nulls are a big part of a
database but they don't give use the tools to use it. Nulls are just one of
the best examples.


On Fri, May 9, 2014 at 9:25 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I have an SQLRPGLE program that's accessing a table with a column that
allows nulls. I'm fetching into a DS that's defined via a copybook. The
DS includes a 3i 0 field for the null indicator variable. The FETCH NEXT
lists each field individually. The SQL precompiler accepts all of the DS
fields except the one for the null indicator variable. If I use a locally
defined field, it'll take that.

Has anyone else seen this? Just a quirk in the SQL precompiler?
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



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.