Re: Field encryption for a unique key field

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

SQL does all the stuff correctly even with encrtyped key fields - RPG 
I/O does have some issues.

One of the vendors has a solution for this that seems to be working, to 
allow using native I/O even with this issue.

Cheers
Vern

On 12/15/2016 10:47 AM, Charles Wilt wrote:
> Shrug, it's not perfect...not supporting joined logicals is a documented
> limit.
>
> It's better than what we had before, which would require changing the size
> of the field and recompiling the world.
>
> I wouldn't encrypt a key in a new application, but you live with what you
> have.
>
> Charles
>
> On Thu, Dec 15, 2016 at 8:43 AM, Delta - Giduturi, Shankar <
> SGiduturi@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> > 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 ?