Re: RPG 7.1 CONST problem ** RESOLVED ** -- RPG400-L

Subject: Re: RPG 7.1 CONST problem ** RESOLVED **
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Thu, 24 Feb 2011 12:26:07 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: RPG 7.1 CONST problem ** RESOLVED ** , Joe Pluta

This mailing list archive is Copyright 1997-2025 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.