RE: Passing a Null Date to a Procedure -- RPG400-L

Subject: RE: Passing a Null Date to a Procedure
From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
Date: Mon, 4 Jan 2010 09:44:23 +0100
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Happy new year all,

We pass a lot of dates to procedures and always need to know if the value is null.

Actually, we have no null capable date fields in our db. We record the value 0001-01-01 to represent a null date. All our programs have the constant gNULL_DATE from a copybook and the parameter would be compared with that.

I always wondered why we never used real null values and didn't realise that this would be an issue or that RPG did not have full null support.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Passing a Null Date to a Procedure , Doug Palme

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.