× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi, Bryce:

See embedded replies below.

Mark

> Bryce Martin wrote:
I have a question about reclaiming an activation group on a job other than my own.

Can it be done?
Yes, but I think you would be "solving the wrong problem" with this approach. (see below)
Say I have a program that I wrote that is using a named activation group. And then I make a change to that program during the day and I need the users to pick up this change. The only way to do this is to reclaim the activation group in their job. But the user doesn't have command line access to do this, and that isn't something you want to be telling the users to do. It isn't very user friendly. So what I'm wondering is... Can I write a program to reclaim the activation group across all the jobs so that when the user calls the program the next time then it will get the right version? How do other's handle this situation.

My project structure looks like this...

OPM Program calls RPGLE Program that has a named Activation Group --> RPGLE Pgm calls modules in a service program. --> Module in Service Program calls RPGLE Pgm with Activation *New (recursive BOM)

If I change the recursive BOM program and recompile I don't see the changes until I reclaim activation group of the RPGLE Pgm that is in the Named activation group.
With ACTGRP(*NEW), that program should be automatically deactivated and the *NEW AG gets reclaimed whenever that program returns.

This suggests the true cause of this problem. See my post of 2/20/2009 in the RPG400-L mailing list, subject "Re: Problem with duplicated program names". Here is a link to this thread:

http://archive.midrange.com/rpg400-l/200902/msg00256.html

Any modules in the service program that call the "recursive BOM" program have already resolved a pointer to that program, and so even after you replaced that program, the *SRVPGM will continue to call the original *PGM, using the pointer it had previously resolved.

Change the caller(s), per the thread mentioned above, and I believe this issue will be resolved.
I hope this is clear enough.

Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
--- This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us and destroy this message immediately. ---

As an Amazon Associate we earn from qualifying purchases.

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.