RE: Everything is System state -- MIDRANGE-L

Ahh!  Ed and Bruce, you two are wise beyond your years!  (And how many
years is that to be wise beyond???)

And now I am blushing because I got it wrong.  The client sent an object
description after I posted the note and indeed it is the object domain
that was listed as *SYSTEM, not he state that was listed as system...

 

Creation information:

  Creation date/time . . . . . . . . :   06/18/05  16:44:27

  Created by user  . . . . . . . . . :   ZZZZZ

  System created on  . . . . . . . . :   SSSSSSSS

  Object domain  . . . . . . . . . . :   *SYSTEM                     
         ^^^^^^                          ^^^^^^^

Sorry to have jumped the gun.  If I may quote Rosanna Rosannadanna....

Nevermind!

jte

--
John Earl | Chief Technology Officer
The PowerTech Group
19426 68th Ave. S
Seattle, WA 98032
(253) 872-7788 ext. 302
john.earl@xxxxxxxxxxxxx
www.powertech.com 
 

 
This email message and any attachments are intended only for the use of
the intended recipients and may contain information that is privileged
and confidential. If you are not the intended recipient, any
dissemination, distribution, or copying is strictly prohibited. If you
received this email message in error, please immediately notify the
sender by replying to this email message, or by telephone, and delete
the message from your email system.
--

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of Ed Fishel
> Sent: Friday, June 17, 2005 12:26 PM
> To: Midrange Systems Technical Discussion
> Subject: 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
> 
> --
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.