RE: [MI400] MI as the MI language of the as400.

["Steve Richter" <srichter@xxxxxxxxxxxxx>]

-----Original Message-----
From: mi400-admin@midrange.com [mailto:mi400-admin@midrange.com]On
Behalf Of Leif Svalgaard

>for one: activation groups. To quote Dr. Frank:

>"Each process has a PAWA. Within this PAWA is the PAGP
>and two or more ACTGRPs. Each ACTGRP has a PACB
>that contains multiple MBVs, an ActGrp directory, a PRT,
>a heap list, one of more heap spaces, auto storage segments,
>and static storage segments. Now isn't this perfectly clear?"

>Even the snide question is Dr. Frank's.
>And in his summary he forgot: tombstone segments, Process
>Queue space, PCB, ...

a process is a big guy, it has a lot to do and will have a lot of pieces to
it. The important thing to me is that the call stack be open so a non ile
entry like the external module jump I described can be added to it. Also
that the call stack be extendable so that it can support marshalled calls.
And 3rd you need to be able to walk the call stack so that exception
handling can be handled in a non ile way.

Steve