Encryption of Sequential Datasets

#### Search Results

Search

# Encryption of Sequential Datasets

The Adabas nucleus and utilities use the following sequential datasets:

Dataset type | Associated DD name(s)
--- | ---
Job input parameters | DDCARD, DDKARTE Often provided via the JES spool (for example, ‘DD *’)
Job output protocol | DDPRINT, DDDRUCK Often directed to the JES spool (for example, ‘DD SYSOUT=*’)
Payload input data | For example: DDEBAND for ADALOD LOAD DDREST1-8 for ADASAV RESTORE
Payload output data | For example: DDSAVE1-8 for ADASAV SAVE DDSIAUS1-2 for ADARES PLCOPY

Adabas reads and writes these sequential datasets using standard system interfaces (BSAM or QSAM). They may be encrypted if the encryption (for output) and decryption (for input) takes place at that system interface level or below.

Adabas itself is not involved in the encryption and decryption of sequential datasets. It supports the use of encrypted sequential datasets for nucleus and utility executions with or without the add-on Adabas Encryption.

With z/OS Dataset Encryption, encrypted basic format and large format sequential datasets on DASD need 8 bytes more space per block than unencrypted sequential datasets. In Adabas, the calculation of the default block and record sizes (BLKSIZE & LRECL) for sequential output datasets on DASD has been adjusted to take this extra space into account. This avoids the wasting of DASD space.

Note
Zaps AO852011, AO851020, AO843024, and AO842016 adjust the default block size calculation for extended format and encrypted sequential datasets. They are recommended for all installations.