Re: paradox ?

An attempt at clarifying state/domain:

State is a property only of pgms.  It's essentially a "capability," i.e. it
indicates how powerful a pgm is.  A system-state pgm can do just about
anything--in particular, it can access system-domain objects (as well as
user-domain objects).  A user-state pgm is wimpier--it can't access
system-domain objects, only user-domain.

Domain is a property of all objects.  It's like a "protection."  System-domain
objects are "protected" from user-state pgms--only system-state pgms can access
them.  User-domain objects aren't "protected"--they can be accessed by either
user- or system-state pgms.

Therefore, API pgms are user-domain (so normal user-state pgms can call them),
and they are system-state (so they can do powerful things user-state pgms
can't, like accessing system-domain objects).

Leif Svalgaard wrote:

> From: Tim McCarthy <timm@as400ftp.com>
>
> > Although technically we could have both system domain/system state and
> > system domain/user state only the former really makes any sense and I
> > don't know of any SD/US programs out there. So it's my understanding
> > that a System domain program can access any object.
>
> what I have are user domain/system state programs. All the APIs are also
> UD/SS programs. I don't think the system domain programs have any
> leg up on accessing any object.

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---