RE: RPG ILE and *INLR -- RPG400-L

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

Subject: RE: RPG ILE and *INLR
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Date: Fri, 28 Dec 2001 16:00:56 -0600
Importance: Normal
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

It's definitely an artifact of the activation group, Chris.  I should have
realized that.  The *NEW activation group (which is the default on CRTPGM)
reinitializes everything, which makes perfect sense, because a *NEW
activation group is, in effect, a mini-PAG of its own.

By using *CALLER, things act pretty much the way they used to, with called
programs sitting around until they specifically shut themselves down.

I'm relatively comfortable with this, now I just have to decide which
technique (*NEW or *CALLER) I want to use <grin>.

Joe


> From: Chris Rehm
>
> Wow. That isn't what I'd have pictured. What are you calling from?
> Another ILE? Is it because of the default PAG handling? The call creates
> a new group that is zapped on exit so the main program is killed. Is
> that using *caller group?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: RPG ILE and *INLR , Chris Rehm

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.