Re: Service programs and QSRVSRC

How about this for an example?

I have multiples modules that have recursive BOM subprocedures in them.
Since I need to do something a little different in the very internals of
the BOM subprocedures I can't roll this into a single module. So I have a
service program that houses all my recursive BOM modules. Its a nice way
to keep them in one place.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
10/15/2009 02:35 PM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
<rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Service programs and QSRVSRC






Hhmm, doesn't the protected export you mentioned will only applied to
*module to *module binding? If so, I think we are talking about the
samething. As mentioned, at our shop, a program is always created from a
module. We don't create a program using 2 or more *MODULE. Don't never
see the need to break a program into multiple *module.



"Charles Wilt" <charles.wilt@xxxxxxxxx> wrote in message
news:<mailman.6761.1255631084.1811.rpg400-l@xxxxxxxxxxxx>...
Lim,

The idea of protected procedures has nothing to do with "bind by
copy"....or at least nothing to do with having modules bound into a
program with bind by copy; since technically if you have service
programs made up of multiple modules then you have bound those modules
by copy into the service program.

I like be able to break up the code into multiple source members. But
the resulting modules are only used in a single *SRVPGM.

Charles

On Thu, Oct 15, 2009 at 2:08 PM, Lim Hock-Chai
<Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:

Our shop does not use bind-by-copy. So... Protected level doesn't quite
apply to our shop. But I can see that would be useful for others.

I don't ever think of a situation where I would want to create a program
using multiple *MODULE. If there are common functions that needed by
other programs, I put those functions in a service program and bind them
with the service program.




"Charles Wilt" <charles.wilt@xxxxxxxxx> wrote in message
news:<mailman.6401.1255463858.1811.rpg400-l@xxxxxxxxxxxx>...
I'd recommend always using binder language, never export *ALL.

By using binder language, your procedures can have 3 levels of
visibility
1) Public (exported and in binder source)
2) Protected, only usable by other procedures in the service program
(exported but NOT in binder source)
3) Private, only usable by other procedures in the same module (not
exported)

Without binder source, your only options are public or private.

I'd say your option 2 should be
2) Use binder source with only a PGMLVL(*CURRENT). You'll need to
rebind anything using teh service program if you add exports.

-Charles
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing

list

To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

----------