Memory control

Hi Scott,

> > Not directly - there is no equivalent to the %parms built-in-function.
> > However, there may be an MI eqivalent. Another option is to attempt to
> > do something with each parameter and MONMSG for the relevant MCH* error
> > (MCH3601? I can't remember)...
>
> The problem with this is that you're expecting memory that your program
> doesn't own or control to always be *NULL.

I've always labored under the impression that the AS400 was able to keep a
program from overstepping its bounds, memory-wise; i.e. I cannot write an
HLL program that will modify the memory allocated by another program, or at
least, certainly not by another job.  I also have this idea that it's not
possible for a program to modify its own executable code, only the data
portion of its memory.

I guess my question is, what are the system-enforced memory boundaries for a
program?  The program's data segment?  Any memory available to the job it's
running in?

Peter Dow
Dow Software Services, Inc.
www.dowsoftware.com
909 793-9050 voice
909 793-4480 fax

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.8/114 - Release Date: 9/28/2005