RE: Everything is System state

I would imagine that he is talking about the following on the DSPOBJ command 
output:

Creation information:                                        
  Creation date/time . . . . . . . . :   01/07/02  19:51:14  
  Created by user  . . . . . . . . . :   *IBM                
  System created on  . . . . . . . . :   00000000            
  Object domain  . . . . . . . . . . :   *SYSTEM             


Object domain is *SYSTEM.

Something sounds fishy if everything is being created as *SYSTEM state.

Your client is not a FAST/400 user is he?

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx
> [mailto:midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx]On 
> Behalf Of
> phil Kestenbaum
> Sent: Friday, June 17, 2005 3:10 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Everything is System state
> 
> 
> John, I am not seeing an Object type that is *SYSTEM. is this 
> for an object attribute?
> 
> Phil Kestenbaum
> System Admin
> G-III Leather Fashions
> 
> 
> -----Original Message-----
> From: John Earl [mailto:john.earl@xxxxxxxxxxxxx]
> Sent: Friday, June 17, 2005 2:47 PM
> To: Midrange Systems Technical Discussion
> Subject: Everything is System state
> 
> 
> 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?
> 
>  
> 
> This is pretty weird stuff - never seen this before but it cain't be
> healthy....
> 
>  
> 
> jte
> 
>  
> 
> --
> 
> John Earl | Chief Technology Officer
> The PowerTech Group
> 
> 19426 68th Ave. S
> Seattle, WA 98032
> (253) 872-7788 ext. 302
> john.earl@xxxxxxxxxxxxx
>  <http://www.powertech.com> 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.
> 
> --
>  
>  
> --------------------------------------------------------
> 
> This message contains confidential information and is 
> intended intended only for the individual named. If you are 
> not the named addressee you should not disseminate, 
> distribute or copy this e-mail. Please notify the sender 
> immediately if you have received this e-mail by mistake and 
> delete this e-mail from your system. Finally, the recipient 
> should check this email and any attachments for the presence 
> of viruses. The company accepts no liability for any damage 
> caused by any virus transmitted by this email.
> 
> -- 
> 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.
> 
>