With the ADARUN parameter ENCRYPTION you specify that Adabas shall support encrypted database container datasets.
| Parameter | Specify... | Possible Values | Default |
|---|---|---|---|
| ENCRYPTION | Whether or not to activate Adabas Encryption | YES | NO | NO |
The ENCRYPTION parameter controls whether Adabas supports encrypted database container datasets.
If ENCRYPTION=YES is specified, any container dataset of the database (ASSO, DATA, WORK, CLOG, PLOG, RLOG, DSIM, SORT, or TEMP) may be encrypted.
Note:
Adabas Encryption requires its own license module (named AEZLIC) or
file (DD-name DDLAEZ), in addition to the standard Adabas license. If the AEZ
license is missing or invalid, the Adabas nucleus will refuse to start.
If ENCRYPTION=NO is specified (the default), Adabas does not support encrypted database container datasets. In this case, if a database container dataset is encrypted, Adabas terminates with an error when it attempts to open the dataset.
Setting ENCRYPTION=YES is required if one or more of the database container datasets accessed by the Adabas nucleus or utility are encrypted. (YES may also be specified if none of the container datasets is encrypted.)
In a cluster, ENCRYPTION is a local, fixed parameter. Still, if ASSO, DATA, or any of the xLOG datasets are encrypted, ENCRYPTION must be set to YES for all nuclei in the cluster.