Re: Renaming service programs: any gotchas?

shouldn't need to rename the service program...

Just adjust the library shown in the binding directory(ies) used to compile
your programs.

Assuming it has HTTPAPI now, you could change it to another library or just
*LIBL.

Note that when it's *LIBL in the binding directory, the *LIBL is used to
find the service program at bind time and at run-time.

Whereas, with an actual library name in the binding directory, then at run
time your program will always use the service program from that library.

Charles



On Tue, Mar 7, 2017 at 1:04 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

I'm finding that I'm running into conflicts between different versions of
a service program (specifically, Scott Klement's HTTPAPIR4).

Are there any "gotchas" I should know about, where renaming a service
program is concerned?

Or is it a simple matter of adjusting the binding directory used by the
programs calling the "special" version?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD