× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We blogged about this some time back when we became concerned at the somewhat cavalier approach some people were taking in applying this capability to tables that were also handled by native RPG.

Here's the blog post http://ibmsystemsmag.com/blogs/idevelop/archive/rcac-two-steps-forward-one-back/ <http://ibmsystemsmag.com/blogs/idevelop/archive/rcac-two-steps-forward-one-back/> if you read the comments you'll see Kent Milligan's take on it.

Our advice remains to be very very careful in applying this to existing applications.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Aug 30, 2018, at 3:00 PM, James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:

On 8/30/18, 11:50 AM, Rob Berendt wrote:
I think Buck is right on with his suggestion to supply feed back at the
end of his long reply.
JSMITH reads the row using an RPG read.
The value of SSN is shown to him as *****1234.
The program does: ssn='123456789' then an RPG update. Does it accept
that and store the encrypted value of '123456789' or what? Like, "so I
can't read it, can I set the value instead"?

Mr. Berendt guessed right. The circumstances in question are indeed strictly native Record Level Access. What happens if the record is updated by somebody who sees a redacted value, both with and without attempting to change the value?

Thanks, Rob, for saving me the trouble of clarifying the circumstances.

--
JHHL
--
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.