RE: Dynamic select, null dates, -183, COALESCE, CRTSQLRPGI, DATFMT(*ISO)

Well, so much for progress; I have tons of null dates.  SQL reminds me of
free-form I-specs, replete with opportunities for swapped data elements,
etc.  Seems to me there's an opportunity for the RPG developers to clean
this interface up a little...

Indicator variables: after going through my $300 iSeries SQL library, I've
noticed the same examples showing up in different books by the same author.
I wonder if I can get a refund?

Change: you mean to WinNT?  Is this the change I have to want to do?

Buck, thanks for your help.  I appreciate it!

-rf

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Buck Calabro
Sent: Friday, August 09, 2002 12:47 PM
To: rpg400-l@midrange.com
Subject: RE: Dynamic select, null dates, -183, COALESCE, CRTSQLRPGI,
DATFMT(*ISO)

>I'm trying to solve the problem of SQL -183 errors
>when reading from a DDS PF and finding records with
>null dates (the null date is valid).
>
>After a couple of RTFM and RTFFAQ's sessions,
>I'm getting the records (using this select
>statement) as long as I specify DATFMT(*ISO) on
>the CRTSQLRPGI command.
>
>coalesce(nuucandt,''0001-01-01'')

You can also use indicator variables.  Then the compiler settings no longer
matter.  Of course, since you're using dynamic selects, that means more work
on the coding side...

>And how do you deal with SETLL and READE
>separation anxiety?

Q. How many psychiatrists does it take to change a light bulb?
A. Just one, but it really truly has to WANT to change.
  --buck
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.