Re: Row or object in *FILE in use

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

You don't, that's kinda the whole point behind an authorization list.  You
only have one place to manage all of the authorities on the object.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Thu, Nov 8, 2018 at 1:04 PM Matt Olson <Matt.Olson@xxxxxxxx> wrote:

> Seems like you can't assign more than one authorization list to a file.
> How do you get around that?
>
> -----Original Message-----
> From: Rob Berendt <rob@xxxxxxxxx>
> Sent: Thursday, November 8, 2018 12:39 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Subject: Re: Row or object in *FILE in use
>
> Matt,
>
> This is why many people use authorization lists instead.
> Once you've assigned the authorization list to an object (which initially
> cannot be in use) it becomes easy to add/change/delete members of the
> authorization list while the file is in use.
>
>
> 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:   "Matt Olson" <Matt.Olson@xxxxxxxx>
> To:     "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Date:   11/08/2018 01:32 PM
> Subject:        Row or object in *FILE in use
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
>
>
>
> Why is it that when you want to grant permissions you might get: Row or
> object in *FILE in use
>
> Here is the statement: GRANT SELECT ON library.filename TO group_name
>
> Is it normal to not be able to grant permissions while a system is in use.
> We have to enter restricted state to assign permissions?
>
> --
> 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: https://amazon.midrange.com
>
>
> --
> 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: https://amazon.midrange.com
>
> --
> 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: https://amazon.midrange.com