Re: Security Question

[Pat Barber <mboceanside@xxxxxxxxxxxxxxxx>]

That exactly what I'm seeing on V5R4.

I don't recall ever using the QSYSOPR profile.

Mark S. Waterbury wrote:

> Hi, Pat:
>
> Having a user "enrolled as *SYSOPR" is not the same as being signed-on 
> as QSYSOPR.
>
> At V5R2, when I do a DSPOBJAUT QSYS/PWRDWNSYS *CMD, I see this:
>
>                         Object    
> User        Group       Authority  
> QSYS                    *ALL       
> QSYSOPR                 *USE       
> *PUBLIC                 *EXCLUDE   
>
> Does that help?
>
> Mark S. Waterbury
>
> > Pat Barber wrote:
>  
>
> > I had an interesting problem the other day and I was wondering
> > how long this has been in place.
> >
> > I told an system operator to power down the box and do a restart.
> > He is enrolled as *sysopr. He could not.
> >
> > He does not have the authority to even see the power menu ???
> >
> > He could not execute the pwrdwnsys command ???
> >
> > This is on a 525 running V5R4.
> >
> > The authorties for that cmd are *USE for QSYSOPR
> >
> > I will grant you we don't power down very often, but I would
> > like the operator to be able to do that if neccessary.
> >  
> >