RE: Field encryption for a unique key field

I have a question here.

I have tried implementation a fieldproc on a key field but was unable to do so.

The issue we had was that key field was also used in a Join Logical file to join on another file. FIELDPROC doesn't like that. Do we have a solution for this ?

In fact I contacted IBM and they suggested not to encrypt the Key Fields instead use an alternative file/field.

FIELDPROC comes with a tagline of "No Application Changes" right ? But that is not 100% true right ? We still have to see and make changes in the programs where we have a READ/READE ? Agree ?

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Thursday, December 15, 2016 7:31 AM
To: Midrange Systems Technical Discussion
Subject: Re: Field encryption for a unique key field

Mike,

If you're using FIELDPROC support, I don't think you need to do anything.
The DB does it transparently behind the scenes.

One tidbit this article,
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibmsystemsmag.com_power_Systems-2DManagement_Security_townsend-5Ffieldproc_-3Fpage-3D3&d=DgIGaQ&c=mDGyhZvuvk998Q8jXoZ8lA3z0DKS1L90j6LdL2xh18c&r=k1NUFTPDWHz_7YCTmYDbACLRD76gjE5KBFabKAAI4bc&m=Vwx_8LkJYil1lAVUEowM9sfKf2Ip-oOb9vzyOKGg3Qw&s=-1XCSBVTpmxHQYHgPdrVy9su4q3Fxo5dR43aGZhxffM&e=

CHAIN/SETLL will work as expected, but READ doesn't return in the order expected (as the index is encrypted)

If you want to use the masking support, be sure to understand the options for FIELDPROC_ENCODED_COMPARISON value in QAQQINI.
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mcpressonline.com_rpg_db2-2Dfield-2Dprocedures-2Dfinally-2Dsupport-2Dconditional-2Dmasking.html&d=DgIGaQ&c=mDGyhZvuvk998Q8jXoZ8lA3z0DKS1L90j6LdL2xh18c&r=k1NUFTPDWHz_7YCTmYDbACLRD76gjE5KBFabKAAI4bc&m=Vwx_8LkJYil1lAVUEowM9sfKf2Ip-oOb9vzyOKGg3Qw&s=QEfWDiG3O0YyL_nC7tdpTc-g8R0svep1X9FIg6EuNyY&e=

Charles


On Wed, Dec 14, 2016 at 11:25 AM, Mike Cunningham <mike.cunningham@xxxxxxx>
wrote:

We have a field we need to encrypt but we have multiple RPG applicants
that do a CHAIN and some SQL that do a SELECT WHERE on the field as a
unique key. We need to let users find a record using this key field as
we get lots of government data with this as the only unique value we
can use for a lookup. If we encrypt the field in the database, is the
only thing we need to do is encrypt the data the user enters before we
issue the CHAIN command and then everything else works as usual?

Thanks

Mike Cunningham
VP of Information Technology Services/CIO Pennsylvania College of
Technology



________________________________
This email may contain confidential information about a Pennsylvania
College of Technology student. It is intended solely for the use of
the recipient. This email may contain information that is considered
an “educational record” subject to the protections of the Family
Educational Rights and Privacy Act Regulations. The regulations may be
found at 34 C.F.R. Part 99 for your reference. The recipient may only
use or disclose the information in accordance with the requirements of
the Federal Educational Rights and Privacy Act Regulations. If you
have received this transmission in error, please notify the sender
immediately and permanently delete the email.
--
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://urldefense.proofpoint.com/v2/url?u=http-3A__lists.midrange.com
_mailman_listinfo_midrange-2Dl&d=DgIGaQ&c=mDGyhZvuvk998Q8jXoZ8lA3z0DKS
1L90j6LdL2xh18c&r=k1NUFTPDWHz_7YCTmYDbACLRD76gjE5KBFabKAAI4bc&m=Vwx_8L
kJYil1lAVUEowM9sfKf2Ip-oOb9vzyOKGg3Qw&s=cHD4uAGpqins26H6nXhiiT5UfXgg_T
DBQlwwhCuZK8Q&e= or email: MIDRANGE-L-request@xxxxxxxxxxxx Before
posting, please take a moment to review the archives at
https://urldefense.proofpoint.com/v2/url?u=http-3A__archive.midrange.com_midrange-2Dl&d=DgIGaQ&c=mDGyhZvuvk998Q8jXoZ8lA3z0DKS1L90j6LdL2xh18c&r=k1NUFTPDWHz_7YCTmYDbACLRD76gjE5KBFabKAAI4bc&m=Vwx_8LkJYil1lAVUEowM9sfKf2Ip-oOb9vzyOKGg3Qw&s=AZuqOYHFyIFLslJMoQ2LP0-SSU2ZzstqJb6_AjhPQsc&e= .

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://urldefense.proofpoint.com/v2/url?u=http-3A__amzn.to_2dEadiD&d=
DgIGaQ&c=mDGyhZvuvk998Q8jXoZ8lA3z0DKS1L90j6LdL2xh18c&r=k1NUFTPDWHz_7YC
TmYDbACLRD76gjE5KBFabKAAI4bc&m=Vwx_8LkJYil1lAVUEowM9sfKf2Ip-oOb9vzyOKG
g3Qw&s=0YwFmVgJxHaxAdJHhukadgy_96EKvHyiJUfHvvYLZe8&e=

--
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://urldefense.proofpoint.com/v2/url?u=http-3A__lists.midrange.com_mailman_listinfo_midrange-2Dl&d=DgIGaQ&c=mDGyhZvuvk998Q8jXoZ8lA3z0DKS1L90j6LdL2xh18c&r=k1NUFTPDWHz_7YCTmYDbACLRD76gjE5KBFabKAAI4bc&m=Vwx_8LkJYil1lAVUEowM9sfKf2Ip-oOb9vzyOKGg3Qw&s=cHD4uAGpqins26H6nXhiiT5UfXgg_TDBQlwwhCuZK8Q&e=
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://urldefense.proofpoint.com/v2/url?u=http-3A__archive.midrange.com_midrange-2Dl&d=DgIGaQ&c=mDGyhZvuvk998Q8jXoZ8lA3z0DKS1L90j6LdL2xh18c&r=k1NUFTPDWHz_7YCTmYDbACLRD76gjE5KBFabKAAI4bc&m=Vwx_8LkJYil1lAVUEowM9sfKf2Ip-oOb9vzyOKGg3Qw&s=AZuqOYHFyIFLslJMoQ2LP0-SSU2ZzstqJb6_AjhPQsc&e= .

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://urldefense.proofpoint.com/v2/url?u=http-3A__amzn.to_2dEadiD&d=DgIGaQ&c=mDGyhZvuvk998Q8jXoZ8lA3z0DKS1L90j6LdL2xh18c&r=k1NUFTPDWHz_7YCTmYDbACLRD76gjE5KBFabKAAI4bc&m=Vwx_8LkJYil1lAVUEowM9sfKf2Ip-oOb9vzyOKGg3Qw&s=0YwFmVgJxHaxAdJHhukadgy_96EKvHyiJUfHvvYLZe8&e=