|
I'd question the *SPLCTL...
As it means the user can work with _any_ spool file on the system.
A user always has control of their own spool files without *SPLCTL
Charles
On Thu, May 23, 2024 at 3:28 PM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
1. Generally the only special authority would be *SPLCTL. I would prefer
to give less authority and wait for a authority problem than to give more
authority than needed and never know.
2. What have you got in the QHTTP library. On my system there are only 2
user indexes ?
Library lists should be easily set and not require a change to the
initial
program but maybe you only have one application.
<Vendor Plug>
For Library lists and Menus look at Admin4i
https://msd.net.au/applications/admin4i/
</Vendor Plug>
Cheers
Don
From: "K Crawford" <kscx3ksc@xxxxxxxxx>
To: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
Date: 24/05/2024 06:43 AM
Subject: Security Level 20 to Level 30 questions.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
I have been wanting to clean this up for some time. If we get the new
system it will be time. I know going to a Power 10 will bump my Level 20
to a Level 30. So I am looking at my system to figure out the impact. I
know for a fact (don't beat on me for this) that I will need/should change
user profiles security. I want to get rid of *ALLOBJ from normal users. I
want to change the User Class to *USER. I have set up a user to test
with.
Questions:
1. for your everyday users what "User Class" and "Special Authorities" do
they have? I know it depends.
2. In our initial program it sets up the library list. I have the library
QHTTP in it. This fails with CPF2182 - Not authorized to library. Looking
at QHTTP it has *PUBLIC *EXCLUDE. Any suggestions? Add a group profile
to
the library authority, almost all of our users have a group profile. The
reason we have this library in the user library list is some programs call
items in this library.
I am sure I will have more questions.
TIA
--
Kerwin Crawford
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
--
This email has been scanned for computer viruses. Although MSD has taken
reasonable precautions to ensure no viruses are present in this email, MSD
cannot accept responsibility for any loss or damage arising from the use of
this email or attachments..
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
