Re: Belt-and-suspenders on *SRVPGM

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>]

Hi, James:

If you want to let the binder do this for you (at CRTPGM or CRTSRVPGM 
time), then it is either one way or the other, but not both.

Or, you could use the API QleActBndPgm or QleActBndPgmLong (or the MI 
instruction ACTBPGM) to resolve to the *SRVPGM, and then use the API 
QleGetExp or QleGetExpLong to get the address of any needed "exports" 
(procedures).  This is a way to "dynamically" bind to a procedure in a 
*SRVPGM at runtime, rather than at "bind-time".

HTH,

Mark S. Waterbury

> James H. H. Lampert wrote:
> Is there a way to bind to a service program, such that it will look for 
> it BOTH in the *LIBL AND in a specific library?
>
> We have a situation involving a trigger that recently started using a 
> service program (HTTPAPIR4, if anybody's interested), and we've had 
> issues with certain jobs not finding it because it was bound in *LIBL, 
> and no library containing it was in the *LIBL. I've changed it, but I 
> wouldn't mind a belt-and-suspenders approach here.
>
> --
> JHHL
>