When one turns on pervasive encryption for Tables in VSAM LDS Areas, obviously the records get encrypted. But what about the primary and secondary keys in the index? Do they reflect their native value or do they reflect an encrypted value? If the keys are encrypted, don't they have to be decrypted before they can be utilized by SQL or CBS for set processing? Wouldn't the sequence also be altered as well?
z/OS
Datacom 15.1
Here in VSAM Linear Datasets with Media Manager we document:
Index Areas and Data Areas can be assigned a "keylabel", which makes the dataset available for IBM Pervasive Encryption.
IBM Media Manager Performs encryption/decryption transparently for Pervasive Encryption
So with pervasive encryption turned on on the index VSAM LDS , the key value stored in the index is encrypted.