Copying Database Container Datasets

#### Search Results

Search

# Copying Database Container Datasets

Non-Adabas programs are not as versatile in copying encrypted Adabas database container datasets as they are with unencrypted container datasets.

Encrypted database container datasets cannot be copied using non-Adabas programs that read the datasets record by record, such as:

- IEBGENER, ICEGENER

- IDCAMS REPRO

- ISPF 3.3

- SORT MERGE with FIELDS=COPY

- Any program that uses BSAM or QSAM to read the dataset

Even if the user running the program has the authorization to use the dataset’s encryption key label, BSAM and QSAM cannot decrypt Adabas container datasets. Trying to open an encrypted Adabas container dataset with BSAM or QSAM results in system abend 219 with return code 99.

In contrast, encrypted Adabas database container datasets can still be copied using non-Adabas programs that read and write the datasets track by track, such as:

- DFSMSdss COPY

- FlashCopy®, Concurrent Copy®, and so on.

These programs copy the data as is, without decrypting and re-encrypting it. They do not need the authorization to access the encryption key label either.

For instance, a procedure like the following also works if the database container datasets are encrypted:

1. ADADBS TRANSACTIONS SUSPEND,TTSYN=…,TRESUME=…

2. Copy the database container datasets using FlashCopy, Concurrent Copy, or a similar program

3. ADADBS TRANSACTIONS RESUME