RE: Using CALLB with a Service Program

["Stone, Brad V (TC)" <bvstone@xxxxxxxxxxxxxx>]

As someone else mentioned, I also tend to use CALLP to subprocedures that
don't return anything.  Otherwise it's called with an Eval, If, Do, etc.

I group like subprocedures in a module, then create a serivce program from
the module and delete the module.  Then add the service program to my
binding directory.  (Bind by copy got old quick).

Bradley V. Stone
Taylor Corporation - OASIS Programmer/Analyst   
bvstone@taylorcorp.com


> -----Original Message-----
> From: Joe Teff [SMTP:jteff19@idt.net]
> Sent: Friday, June 04, 1999 10:27 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Using CALLB with a Service Program
> 
> Brad wrote:
> 
> >CALLB has nothing to do with bind by copy or bind by reference.  It is
> >simply calling a bound procedure. 
> >
> >Bind by copy and bind by reference refer to creation of an RPG program.
> >Since you are using the Qtmhxxxx proceudres from the QTMHCGI service
> >program, when you compile your program you will have to reference the
> >service program in the CRTBNDRPG program directly or through a binding
> >directory.  You are binding by reference, here.  
> >
> >The Qtmhxxxx APIs are proceudres written in C and are in a service
> program
> >QTMHCGI in library QTCP.
> 
> Dennis wrote:
> 
> >No, that's close but not quite right.  CALLB can also be bound by
> >reference, and that's why your program will function correctly.  The
> >service program is "activated" when your program is called, and the bind
> >is performed at that point.
> 
> I've used bound programs in the past, specifically to break up larger
> programs where chunks of code were replicated. This has worked well
> to reduce redundant code without loosing any performance or function.
> I've also used procedures with service programs. I just never thought
> about putting a "normal" *module in a service program and calling it with
> a CALLB. The light has come on. I can already think of one application
> that I would have done differently because of this.
> 
> Thanks!  Joe Teff
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---