Re: ILE procedure Question

["Joe Teff" <jteff19@xxxxxxx>]

If I understand your question correctly, you want to know to make a
commonly used function easily available to other programs. I would
make HSPROCP a service program (or a module in a service
program if other functions belong together). I would then add this
service program to binding list. You only then need to add the following
to your programs to use it:

    H  DftActGrp(*No)  ActGrp(*Caller)  BndDir('SOMELIB/SOMEBD')

       /Copy  HSPROCS

You may want to use something other than *Caller for the Activation
Group and use whatever Binding Directory suits you. Some may warn
you about the performance of Binding Directories, but I've never had
any problems with them. Now all you have to do is CRTBNDRPG
(option 14) to create your program.

Joe Teff


> I am trying to setup a library of commonly used procedures for our
> company
> 
> I have a NOMAIN module (HSPROCS) and a prototype (HSPROCP) member.
> 
> The Main Program has a /copy HSPROCP in the D specs
> 
> 
> eval newstr = FMTDATE(INVOICEDATE)
> 
> 
> So far so good ?
> 
> 
> Now what I don't understand - er one of the things I don't understand is
> how all of this compiles/binds together.
> 
> What should be a service program vs a bound module etc etc etc.
> 
> I would like to have a compile option in PDM so that programmers can
> automatically use these functions.
> 
> I tried to research this on the archive list but the server has been
> down most of the day :(
> 
> Thanks in advance
> 
> John Hall
> Home sales Co.

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