Sorry, each time you call the api it gives you a new activation mark and it
loads a new copy. If the service program has been changed (New version
moved in) it gets activation mark of new version so subsequent calls uses
the new version. I use this technology in many different ways. I have
installed it in 4 companies (Newer version) so I figure it works. I use a
user space with a timestamp that triggers the reload.



On Tue, Sep 15, 2020, 3:55 PM Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Alan,

It looks like your trigger mediator uses QleActBndPgm() to dynamically
activate service programs. If I recall correctly, subsequent calls to that
procedure won't activate a newer version of a service program. It just
retains the old version, which was previously loaded in memory, no matter
how many times you call QleActBndPgm(). The only way I know of to
deactivate a service program and reactivate it is by ending and restarting
the activation group.

For a while, I held out hope that the DEACTPG MI Instruction might
deactivate a service program, so that the next time QleActBndPgm() was
called, it would activate a newer version. But the MI Instruction didn't
help, either.
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].