The cryptogram (encrypted customer number) should be unique and therefore usable as a file key as well as any other context.
By simply changing the content of the field from customer number to encrypted customer number, the effect ripples throughout all of the resident files as well as copies, backups, etc ,etc. You may even be able to use the cryptogram in many reports/displays as the cryptogram may be sufficient for the business need. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ron Thomas Sent: Tuesday, November 15, 2011 3:53 AM To: [email protected] Subject: Data encrypt Hi Listners, We have go a customer number in applications and this number is currently part of a primary key, we have a requirement to encrypt this number and also should not be used in the tables directly , which means this can not be part of a primary key. pls share your thoughts on the same as to how to take this forward? Regards Ron ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
