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



On 2/24/2011 11:26 AM, Barbara Morris wrote:
On 2/24/2011 12:09 PM, Joe Pluta wrote:
Yes. Think about it: wouldn't it be the same as executing a program
with ACTGRP(*CALLER) in *DFTACTGRP? I haven't seen such a thing blow up,
although it's a discouraged practice.

It's not quite the same. Programs created with DFTACTGRP(*YES) get
deactivated when they end with LR on or abnormally, and there are things
that bound procedures can do that cause problems during this
deactivation. (Things that I never really understood.)

So this rule for the RPG compiler about DFTACTGRP(*YES) is not at all
related to the discouraged practice of *CALLER programs that run in the
default activation group.

So a program with DFTACTGRP(*YES) has a procedure and ends with LR. The program is deactivated but the procedure has done something that might cause havoc in the deactivation.

Now instead that same program calls a program with DFTACTGRP(*CALLER) which has bound procedures. When the calling program ends with LR and gets deactivated, would not the same caveats apply? Or is it different because the procedure is actually part of the program that is deactivated?

Not that it's a terribly important distinction, since the issue will be moot once the compiler again disallows such programs. But I like to understand these things :).

Joe

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.