Start of change

Encrypting log, catalog, and directory data sets with z/OS DFSMS data set encryption

To encrypt the Db2 log, catalog, and directory by using z/OS DFSMS data set encryption, set a key label for their underlying data sets.

Procedure

  1. Set a key label for the RACF data set profile or the DFSMS data class used to protect the archive log, catalog, and directory data sets.
    DFSMS encrypts the data set when Db2 allocates new data sets that match the RACF data set profile for the following types of data sets:
    • Archive log data sets on disk
    • Catalog data sets
    • Directory data sets
  2. Run the REORG TABLESPACE utility against the catalog and directory table spaces.
    DSNDB01.SYSUTILX cannot be encrypted by running the REORG TABLESPACE utility.
  3. Encrypt the DSNDB01.SYSUTILX directory table space by running the RECOVER utility followed by REBUILD INDEX(ALL).
  4. Allocate new active log data sets as encrypted.

    The user who allocates the active log data sets must specify a key label that Db2 has permission to use. However, the user who allocates the active log data set is not required to have access to that key label. For details, see Data Set Encryption.

  5. Identify the encrypted data sets as the new active log using one of the following methods:
    • Issue the -STOP DB2 command, run the DSNJU003 NEWLOG statement, and restart Db2 to enable the use of encrypted active log data sets.
    • Issue the -SET LOG NEWLOG command. The active log data set is immediately available for use without recycling Db2.
End of change