Re: Procedures

>Do I create a module or bound program?

Depends. I create modules from similar procedures
and then put them in a service program. I register this
service program in a binding directory. I then use an
H-spec like
      H  DftActGrp(*No)  ActGrp(*Caller)  BndDir('MYLIB/MYDIR')
I can then use any procedure in my program without
worrying where it is.

>do I need a Binding directory?

Binding directories can be useful when using service programs.

>How do I compile the module into the binding directory?

You don't compile a module into a binding directory. When
creating a program, the compiler needs to know where any
unreferenced objects (programs if using CALLB or 
subprocedures) are. A binding directory can accomplish
this. You register your service program (or modules) in the
binding directory by using the addbnddire command.

>Do I make it a service program?

If you only use a procedure in one program, then no. If you
will use it in many places then yes.

Again, there has been much written about procedures in
the trade magazines. There are several people who give
seminars on RPG/ILE. COMMON is another good way to
learn.

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