RE: EDTOBJAUT

Agree 100%. I originally thought I could do a GRTOBJAUT and add a user, but
it won't do it with a lock on the object. So I instead added the user to an
AUTL and then remove the user from the AUTL and it works flawlessly. AUTL's
are nice to have. Especially with a software provider we have. They update
their software and remove all authorities and only put back the ones that
THEY use as defaults. Not nice. By having the object secured by an AUTL, I
don't have to worry about it as much. If the file is deleted, so what? But
if it gets recreated, it uses the AUTL as if it were always there.

George

(712) 579-5444 (cell)
985 Oak Rd
Harlan, IA 51537

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Wednesday, March 21, 2018 3:00 PM
To: Midrange Systems Technical Discussion
Subject: Re: EDTOBJAUT

I hope that the question is just a curiosity thing and not an implication
that authorization lists are dated or some such thing.

I find that authorization lists allow easier changes on object authority
without having to get another lock (after initially assigning the
authorization list).

I've had bad experiences with supplemental groups affecting performance.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/21/2018 02:43 PM
Subject: Re: EDTOBJAUT
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



On Wed, Mar 21, 2018 at 2:10 PM, Kendall Kinnear <
Kendall.Kinnear@xxxxxxxxxxx> wrote:

GRTOBJAUT was created a long time before authorization lists existed if

I

remember correctly, clear back in Release 1 of System/38. I don't

remember

when Authorization Lists came about but I'm pretty sure it was later.
Course I'm getting old and my memory isn't as good as it used to be. :-)

Were authorization lists a S/36 thing? And came along in the S/36 S/38
-->
AS/400 merger?