Re: RKACK - Overriding Masked Values - was: Another FieldProc question

On Sep 4, 2018, at 7:48 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Jon,

<snip>
...doing the right job
</snip>
Don't we run that risk with each and every user service program, program,
etc throughout the system already? Just basic testing etc...


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: "Jon Paris" <jon.paris@xxxxxxxxxxxxxx>
To: "Midrange-L Midrange-l" <midrange-l@xxxxxxxxxxxx>
Date: 09/03/2018 02:37 PM
Subject: Re: RKACK - Overriding Masked Values - was: Another
FieldProc question
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I agree Dieter - I think that they should have done exactly that. Even
then though you would still have issues potentially in that it relies on
the constraint not just existing buy doing the right job!


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Sep 3, 2018, at 2:12 PM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

<Birgitta>
may be I'm missing something or did not read all posts, but ... the

solution I provided is documented (as well as other pitfalls with their
solutions) in the "Row And Column Access Control" Redpaper:

</Birgitta>

The official documentation is the "SQL Reference" and there is not a

single word about any problems with Field Procs. The origin of the
problems is RLA and it's "native" access (and other "native" interfaces,
Query, CPYF and CRTDUPOBJ). For a solid solution. I would have expected,
that these interfaces could not corrupt the underlaying architecture and
it could not have been so hard to disable RLA access unless the needed
constraints are activated.

D*B
--
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
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 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