Re: Everything is System state

John Earl wrote on 06/17/2005 01:47:24 PM:

> We're talking to a client who has a problem where every non program
> object they load, or create, on their system becomes a *SYSTEM State
> object.  We've seen this on restores, as well as on the create of
> individual objects (CRTLIB for example).
>
> Anyone seen this before?  Anyone have first hand knowledge of this?
>
> The system admin is new to the account, so he does not have a lot of
> history on why things are like this and he would like to have it put all
> back right.  Anyone have an idea on how to fix this?

John, I do not believe it. It seems more likely that someone has mixed up
state and domain. Only a program object can have a state. All objects have
a domain. The domain of almost all objects should be system domain. The
biggest class of user domain objects would be program objects.

The reason that almost all objects are system domain is so that they can
not be directly modified by a user state program. The reason programs are
user domain is so that users and other user state programs can call them.

Ed Fishel,
edfishel@xxxxxxxxxx