RE: RPG procedures

If you need to use the programs with dynamic calls you have two choices:

1.)  Leave the plist in the called program and prototype it in the calling
program using the "extpgm" keyword on the D spec with the program name.
This will give you a prototyped dynamic call.  You can do this with programs
where you have may have a good reason not to convert from RPG Classic.

2.) Convert the called program to RPGIV.  Put a prototype and procedure
interface in the called program to replace the plist.  Use crtbndrpg to
compile. Prototype it in the calling program as in choice 1.  Again you'll
have a prototyped dynamic call, but you'll have the features of ILE
available to you.  The converted program can still be called from RPG
Classic programs.  (Activation group *CALLER on the compile is good for
this.)

I'm not a purist; I think there are situations where option 1 is a
reasonable choice.  There are also a lot of situations where a dynamic call
is, for all practical purposes, as efficient as a bound call.    

> -----Original Message-----
> From: Gwecnal@aol.com [mailto:Gwecnal@aol.com]
> Sent: Wednesday, March 01, 2000 8:35 AM
> To: RPG400-L@midrange.com
> Subject: RPG procedures
> 
> 
> As we move to rpg4 we are trying to put all our definitions 
> in d-specs.  We 
> use prototypes to call stand-alone programs (so we don't need 
> to c-spec 
> plists), but don't quite understand what we need to do to the 
> called program 
> to be able to d-spec the *entry plist.  It almost looks like 
> we have to make 
> it a procedure, but when we do that it compiles OK but hangs 
> up when called.  
> We are not ready  to do the whole binding thing yet - not 
> every program 
> calling the called program is rpg4 yet or any time soon.  Are 
> we just missing 
> something?  TIA, Lance
+---
| 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
+---