|
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalfauthority
Of Rob Berendt
Sent: Tuesday, September 11, 2018 8:38 AM
To: Midrange Systems Technical Discussion
Subject: RE: How to retrieve all user profiles in an IFS object's
under the
Kevin,
Good concern. I don't think the OP was getting that we recommended
profile switching and fixing the authority automatically.
Kevin, one way to get around your concern is to start up a new job
proper user. When it's done it could communicate back to the otherprogram
that it's done. This avoid profile switching as it would use aseparate job.
One way the communication could be done is via a data queue.Mail
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
to: 2505 Dekko Drive<midrange-l@xxxxxxxxxxxx>
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Kevin Bucknum" <Kevin@xxxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
Date: 09/11/2018 08:29 AMobject's
Subject: RE: How to retrieve all user profiles in an IFS
authorityswitched
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
The program that I copied that source out of runs as *OWNER. That
doesn't help with authorities on the IFS, but at another point in the
program it uses the QSYGETPH and QWTSETP api's to swap the running job
to a profile with the proper authorities. It then swaps back to the
users profile. When you do that, you need to be very careful that you
trap all errors and deal with them. If something blows up while
and the user gets a command line, then they have the authority of thesupport
profile with elevated privileges.
Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] OnBehalf
Of Danauthority
Sent: Monday, September 10, 2018 7:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: How to retrieve all user profiles in an IFS object's
Thanks Scott. Apparently, this happens often enough that the
thepeople are tired of tracking this down and fixing it. Also, when
users areDTAAUT(*RWX)
halted from continuing, it quickly becomes a human metrics issue.sufficient
If the application runs into the issue where a user doesn't have
authority to remove others' authorities or to add *PUBLIC
toOBJAUT(*ALL), the application could capture that and send an email
removesupport. I'm not sure how the users are set up authority-wise onproduction.
telling
- Dan
On Mon, Sep 10, 2018 at 3:43 PM, Scott Klement <midrange-
l@xxxxxxxxxxxxxxxx>
wrote:
Dan,
Personally, I would catch the error, and then pop up a message
forthe user to contact the administrator (or whomever is appropriate)
veryassistance. Someone familiar with authorities should be able to
theeasily look at the files and fix the authority problems.
If you really need to get a listing of all user authorities (which
seems like a much more complicated solution) you could do so with
Qp0lGetAttr() API. You could loop through the responses and
here)thethose authorities... but, to my mind, this seems like overkill.
And, of course, the user would need sufficient authority to remove
other users' authority (remember, adopted authority won't work
mailingwhich makes this even more complicated.--
-SK
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
listaffiliate
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,take
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our
listlink: http://amzn.to/2dEadiD--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.