×
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.
We compile with 'Allow null values' (ALWNULL) = *yes
This seams to work for us.
William Moore
California Fine Wire
805-489-5144
wjmoore@xxxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Monday, October 04, 2010 1:39 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RPG SQL and database null values
Is there an easy way to deal with null values being read by RPG using embedded SQL? I can't get by the -305 error when there is a null value coming in. ALWNULL(*INPUTONLY) has already been tried and did not help. I do not need to know when a field is null in this application. Getting the default value for the field type will be OK in my situation. Is the null indicator variable the only way?
--
This is the RPG programming on the IBM i / System i (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.
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.
midrange.com
