RE: Either null indicator variable, or, defaulting a value -- RPG400-L

Subject: RE: Either null indicator variable, or, defaulting a value
From: Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>
Date: Mon, 13 May 2002 16:00:13 -0400
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

I use null indicators, but you MUST check it before referring to the related
variable.  The problem with coalesce is that you might choose a value that
can actually occur in the data and not be able to tell that the variable is
null.  Either way you need to test before using the variable as 'real' data.
  --buck

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.