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

[Jon Paris <jon.paris@xxxxxxxxxxxxxx>]

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.