× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. January 2008

Re: Security Question

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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.