Re: SQL processing in RPG programs

>Gentlemen and gentlewomen,

:-)

>At our company the tradition has always been to use embedded SQL for 
>retrieving
>data from SQL tables for use in RPG programs.
>
>When I asked why the good old fashioned F spec and opcodes SETLL, CHAIN 
>etc were
>not used the response was that null capable fields in the SQL tables made this
>an unreliable method to adopt.
>
>Question : Just how well can RPG4 handle null capable input files??

Very well!

One >>cannot<< use EVAL FieldA = *NULL (the *NULL works only with pointers, 
sigh!).

One has to use EVAL %NULLIND(FieldA) = *ON to set a field to null and 
question with IF %NULLIND(FieldA) = *ON.

These are the drawbacks; i'd prefer a %NULLPTR(Ptr), because i use the Ptr 
= *NULL very seldom. (Of course, we used the %NULLIND a lot in our sources!)

The rest worked and works perfect! (We do also have logicals that do only 
contain records with a To-Date equal null, works also perfect).

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---