Re: Procedure pointers - can I do this??

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

> Here's the rub - to export the getter method I would flag it as EXPORTable 
> and compile the module. I'd then explicitly export the getter method from the 
> service program object using binder language. BUT this is now available to 
> ANY program that binds to the utility service program. There is no way (that 
> I know of) that the utility service program can determine whether it should 
> export or not.

Instead of having trust between different service programs, maybe you 
could set them up as modules?  I.e. have a large service program that's 
made up of a main module, and possibly several utility modules.

Special "getter" and "setter" routines can be exported so that the 
various modules that make up the service program can call them.  It's 
possible to export them to other modules in the same srvpgm without 
exporting them outside the service program.


> Having said that, as we can only perform early binding, it isn't as much of 
> an issue as it would be if we could perform late binding.

You can perform "late binding". There are various APIs that you can call 
at runtime that will locate a service program, activate it, and retrieve a 
procedure pointer to one of it's routines. You can then call that 
procptr...

Take a look at the QleActBndPgm and QleGetExp APIs, or the simplified QZRUCLSP
API...   there are examples of these in teh archives and on the web if you 
do a search for the API names, you should be able to find them.