RE: Programming philosophy Was:RPG IV program - comments request ed

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

Absolutely!  Excellent suggestion, although not all 400's have the SQL
development kit.

Although SQL is itself a welcome abstraction from the physical file layout,
putting the SQL inside an "update" procedure, will allow you to quickly
change from "native" to SQL without impacting the calling code.  Using
procedures can let you experiment with the various trade-offs (run time cost
vs development cost vs maintenance cost) more readily than with inline code.
This helps to separate the business problem from the specific implementation
as well as creating the optimum implementation for your environment.

Buck Calabro
Aptis; Albany, NY
mailto:Buck.Calabro@aptissoftware.com

> -----Original Message-----
> From: Rob Berendt 
> Sent: Tuesday, September 28, 1999 9:22 AM
> To:   RPG400-L@midrange.com
> Subject:      RE: Programming philosophy Was:RPG IV program - comments
> request ed
> 
> If you want to know which fields you are updating, and don't want to look
> at output specs and use EXCEPT, then try the following:
> C/EXEC SQL                   
> C+ Update filename
> C+ Set TOLYTD=:VAR1, TOLAMT=:VAR2, TOLDAT=:VARX
> C+ Where CURRENT of CUR1
> C/END-EXEC                   
> 
> 
+---
| 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
+---