Re: Belt-and-suspenders on *SRVPGM

Hi James,

This is why there's an option when you build HTTPAPI that asks 'at run time, use *LIBL to find HTTPAPI?' to which you can answer Y or N.

If you answer N, the library you use (typically LIBHTTP) is included in the binding directory, so when you bind your programs they'll have LIBHTTP hardcoded as the library for HTTPAPI -- and therefore it doesn't have to be in your library list.

If you really want to load it dynamically, either by library or by library list, you'd have to activate it using the APIs as Mark Waterbury described. I've done that before, and it works. But I usually find it much cleaner/easier to just put my library at the end of the library list. Accomplishes the same thing, and far more people will understand it :)


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