Not ideal for most shops but give each user *SPLCTL ... to handle the outq 
issue
_____________________
Kirk Goins CCNA
Systems Engineer, Manage Inc.
IBM Certified i5 Solution Sales
IBM Certified iSeries Solutions Expert
IBM Certified Designing IBM e-business Solutions 
Office 503-353-1721 x106 Cell 503-577-9519
kirkg@xxxxxxxxxxxxx   www.manageinc.com

Email Response Times: 
Same Day Maybe, Next Day Probably



Pat Barber <mboceanside@xxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/21/2006 12:30 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
V3R2 to V5r3 continues







One thing that has come out of all this.

I didn't think much about the security levels on the
old box because of the method I used for conversion.

They were running level 10 (password only) on the 9406-200.

They are currently on level 40 which is standard these days.

So "far", the only issue I have heard about is the shutdown
of folks being able to view other folks outq's.

I suspect there will be other issues as the days go by.

What changes would you make that will keep the screaming
down ???

I don't believe I have ever run across a problem exactly
like this. All of my accounts have been in place for a
good many years, so all that security twitching went away
a long time ago.

I have a "manager" who needs pretty much all authority short
of QSECOFR and half dozen clerks, two of which will act as
system operators.

The manager is currently at "secadmin" and the users are either
"user" or "sysopr". There is one qsecofr and one DST qsecofr.

The outq's are the biggest bitch at the moment.

I prefer to keep this VERY simple.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.