QleActBndPgm accepts as a parameter being a pointer from a Resolve System
Pointer which would be a pointer to the current object.

It then issues an activation mark for the pointer to that object.

It then in turn issues a procedure pointer to the activation mark which is
what is actually called.

If you don't resolve to the service program, then yes, you would get the
same activation mark.

On Wed, Sep 16, 2020 at 10:39 AM Nathan Andelin <nandelin@xxxxxxxxx> wrote:


Based on your assurances, I'll do more testing to see if QleActBndPgm()
behaves as you say. I thought I had already vetted it and found that the
procedure did NOT activate a new version of a service program, if



On Tue, Sep 15, 2020 at 8:44 PM Alan Campin <alan0307d@xxxxxxxxx> wrote:

Sorry, each time you call the api it gives you a new activation mark and
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.

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

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

This thread ...


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].