RE: ILE Propoganda

Alan Addison wrote:
 
> If it is exactly the same in each program,  why not create a copy 
> member and
> use that instead.   Then you only have to compile all the 
> programs that use
> it once its changed.
> 

If it were placed in a service program, you wouldn't have to compile
all the programs, just the service program.

What if you have to "link into" say an ERP system. If you create a service
programs with various routines, you have one (or very few) source
members to change if (when) a new release comes along (with data base changes).

As a matter of fact, you would probably not have to change more than those
service programs routines even if the ERP system was exchanged by another!


Copy members don't have local variables, and using copy members in a large 
program
could easily crash with variable definitions, indicators, etc.
Besides, if using database files, you would need several copy members.

I try to use service programs as VB (Visual Basic) classes with routines similar
to VB class properties; eg. Customer service program (CUST)
Routines: CustGetName, CustGetAddr, CustIsValid, aso

Very few programs (normally just one), update a given file. Using the above 
technique
only a handful of programs need to be recompiled when a database files is 
changed.

Before using ILE, we could have between 100 and 200 programs to compile for 
each 
database change. I would estimate that 80% of all use of basic system files is 
either checking for a valid key or retrieving the Name or text of a given key 
(code).



        

+---
| 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
+---