statements or have a recorded encryption key for the library to make any modifications
to the encrypted data sets. For and example, see “Example 16: Changing a Metadata-
Bound Library to Require AES Encryption When Existing Data Sets Are Encrypted with
Different Encryption Keys” on page 160.
For more information, see “TABLES Statement” on page 129.
CAUTION:
For AES-encrypted data sets that are referentially related to one another, follow
these best practices to ensure that the data does not become inaccessible:
Store the encryption key in the library’s metadata. You can modify the stored key,
but do not remove the key from metadata and do not unbind ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month, and much more.