Re: Securing one particular field within a file

[Alan Campin <alan0307d@xxxxxxxxx>]

The way I have seen it done at other places is to lock the physical file.
No one has authority to access the file. All data access is through a view.

The view joins to a security table that authorizes you to the requested
table. If you want to access that field, you use that view and you must
have been defined to view that field.

The same thing could be done with a logical.

Have not used RCAC so cannot comment on that. Might give you everything you
need.

On Wed, Oct 21, 2020 at 11:45 AM Rob Berendt <rob@xxxxxxxxx> wrote:

> I think I would study RCAC or Row and Column Access Control.  I believe it
> came out in 7.2
>
> https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahf/rzahfrcactitle.htm
>
> Now, before this, one would give access to the PF only through the object,
> like *OBJOPR.  No data authority.  Then they would use LF's to access it
> and they would only use a subset of the data.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  7310 Innovation Blvd, Suite 104
>           Ft. Wayne, IN 46818
> Ship to:  7310 Innovation Blvd, Dock 9C
>           Ft. Wayne, IN 46818
> http://www.dekko.com
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Alan Shore via MIDRANGE-L
> Sent: Wednesday, October 21, 2020 1:58 PM
> To: midrange-l@xxxxxxxxxxxxxxxxxx
> Cc: Alan Shore <ashore@xxxxxxxx>
> Subject: Securing one particular field within a file
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Hi everyone
> We are on V7r3
> My question is:-
> Is there a way to secure a field in a file so that no one can
> update/change it?
> I realize that there needs to be a way to actually update/change the
> value- but that will need to require a password (or something), so that it
> CAN be updated/changed
>
> I tried a google search, but nothing of any relevance was displayed
>
> As always - all responses gratefully accepted
>
> Alan Shore
> E-mail : ASHORE@xxxxxxxx<mailto:ASHORE@xxxxxxxx>
> Phone [O] : (631) 200-5019
> Phone [C] : (631) 880-8640
> 'If you're going through hell, keep going.'
> Winston Churchill
>
> --
> 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.
>
> 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@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.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com