Re: How does the i handle programs in memory using different methods? -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: How does the i handle programs in memory using different methods?
From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
Date: Sun, 12 Jul 2015 11:58:04 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

One comment Alan.

Your statement is not true for an RPG IV program (only RPG/400).

ILE programs only release their storage with the AG. In order to preserve the old behaviour of an LR’d program as you describe it, ILE programs “pretend” to have gone away by closing files and setting an internal flag that ensures that when called the next time they will behave as if they are being loaded from scratch.

I may have missed it in those long posts but I didn’t notice any mention of the fact that storage used by program/service program instructions are shared system wide. Only data storage is unique to the job.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 12, 2015, at 8:10 AM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

If a regular RPG cycle program, memory get dumped when *INLR is turned on.
If not turned on, stays until either job ends or activation group. Default
activation group when job ends.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: How does the i handle programs in memory using different methods? , Alan Campin
Re: How does the i handle programs in memory using different methods? , Barbara Morris

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