KEYLABELCHK control statement

This control statement is optional. The default is KEYLABELCHK=NO.

NO

Does not check the integrity of the key labels associated with the encrypted database data set.

YES

The CRSS checks the integrity of the key labels assigned to the encrypted database data sets.

The CRSS obtains key labels from the RACF data set profile or the SMS data class and compares them against the key labels assigned to the encrypted database data sets. If they are different, the CRSS determines that the database requires a reorganization. When the CRSS obtains key labels, it allocates one work data set for each database data set. The names of work data sets are determined based on the suboption that you specify (PREFIX or FULLNAME).

Notes:

• To specify KEYLABELCHK=YES, you must also specify CONDREORG=YES. If you specify CONDREORG=NO, CONDREORG=YES,REORGDIAG, or CONDREORG=YES,DIAGONLY, the KEYLABELCHK control statement is ignored.
• If KEYLABELCHK=YES is specified with UNLOADONLY=YES, the KEYLABELCHK control statement is ignored.
• If shadow database data sets are allocated before the conditional reorganization job is started, the key labels of the shadow database data sets must match the key labels defined in the RACF data set profile or the SMS data class.
• The key labels of the shadow database data sets, which are specified with the DDEFPDS2 DD statement, must be the same as the key labels defined in the RACF data set profile or the SMS data class.
• Because key labels are not assigned to OSAM data sets, key labels are not checked if the original database data set is OSAM.
• KEYLABELCHK=YES cannot be specified when migrating from an OSAM data set to an OSAM LDS data set or from an OSAM LDS data set to an OSAM data set. If you want to run a reorganization job that involves such migration, specify CONDREORG=NO.
• The integrity of the key labels associated with the indirect list data sets (ILDS) is not checked.

You can specify the following suboptions for KEYLABELCHK=YES:

PREFIX

Specifies that the CRSS allocates work data sets (for obtaining key labels) using the data set name prefix defined with the DSNPREFX parameter of DBRC.

PREFIX is applicable to HALDBs. If specified for a non-HALDB, the Smart Reorg utility uses FULLNAME.

Notes:

• The work data sets for obtaining key labels are allocated with the following size:

  DEFINE CLUSTER (NAME(keylabel.dataset.name) -
         CISZ(80) RECSZ(73 73) REC(1) )  

  If you are using ACS routines that change the SMS data class based on the allocation size, the key label you intended might not be assigned. In such a case, use FULLNAME.
• The SMS data class that is used when allocating the work data sets must be the same SMS data class that is used by the original database data set of the first data set group of the first partition to be processed by the Smart Reorg utility. If the SMS data class is different for each data set, use FULLNAME.

FULLNAME

Specifies that the CRSS allocates work data sets (for obtaining key labels) with the following naming convention:

• Use the same SMS data class as the original database data sets.
• Add one-character suffix to the data set name.

The CRSS allocates one work data set for each database data set that the Smart Reorg utility processes.

Note: If you use a RACF data set profile to manage key labels, you must use a generic profile. If you use a discrete profile that matches the database data set name, the work data set that is used to obtain the key label will be allocated with one-character suffix and, therefore, the intended key label might not be assigned.