Messages and Codes

This section describes the new and changed messages and codes generated by Adabas Encryption. For all other error messages refer to the Adabas messages documentation.

ADAI* - ADAIOR System Messages

Adabas Encryption introduces the following new ADAIOR system messages.

ADAI36 No space for secondary extent on first volume of ddname
Use non-zero primary space allocation for SPACE
parameter in JCL DD statement and rerun the job
Explanation

This message may be issued by ADAFRM when a new dataset is being formatted.

There is no available space on the volume selected by z/OS for allocating the first secondary extent.

Following this message, the job will be terminated with user abend 692.

Action

Specify non-zero primary allocations for the new datasets being formatted and rerun the job.

ADAI37 Encryption buffer pool full
Explanation

An attempt to allocate a buffer for encryption services has failed because there is no available space in the encryption buffer pool.

The job will continue to run but performance may be severely degraded.

Action

Contact your Software AG support representative for information on how to tailor the encryption buffer pool size for your installation.

ADAI45 ddname Open failed - {encryption support not available |
encryption support not available. Insufficient storage |
encryption support not available. Insufficient 64-bit storage |
encryption support not compatible with dataset type}
Explanation

Refer to the table below for description and action:

Message Ending Description Action
‘encryption support not available’ An attempt was made to open an encrypted dataset, but the required support is not available. Ensure that ADARUN parameter ENCRYPTION=YES is specified and that a valid license for the Adabas encryption product has been processed successfully.

If not, correct the error and rerun the job.

If the problem persists, contact your Software AG support representative.
‘encryption support not available. Insufficient storage’ An attempt was made to open an encrypted dataset, but insufficient storage was available for the encryption parameter area. Increase the REGION size and rerun the job.

If the problem persists, contact your Software AG support representative.

‘encryption support not available. Insufficient 64-bit storage’ An attempt was made to open an encrypted dataset, but insufficient storage was available for the encryption buffer area. Ensure that the MEMLIMIT size permits an allocation of 16 MB above the 2 GB bar.

If the problem persists, contact your Software AG support representative.

‘encryption support not compatible with dataset type’ An attempt was made to open an encrypted dataset that is not compatible with the Adabas Encryption product. Ensure that the encrypted dataset was formatted correctly using ADAFRM, with the key label specified on the JCL DD statement (DSKEYLBL) or derived from RACF or SMS.

If the problem persists, contact your Software AG support representative.

Action

See table above.
ADAI47 ddname {read | write | read GCB} encryption error
Return code retcode reason code rsncode | Parameter build error
Explanation

Either the encryption service has returned an error indicated by the return code and reason code, or the encryption parameter list could not be built.

Action

Contact your Software AG support representative.
ADAI81 Unable to complete increase of ddname – extent error
Explanation

When Adabas Cluster Services or Adabas Parallel Services is being used, a request to increase the size of ASSO or DATA in a peer nucleus has not been able to process the new extent information correctly.

This might occur if, for example, additional volumes have been added to the dataset since the nuclei were started.

Action

If new volumes have been added to the dataset since the nuclei were started, the increase will not complete until all participating nuclei are recycled.

If the problem persists, contact your Software AG support representative.

Adabas Encryption amends the following existing ADAIOR system message:

ADAI64 dbid {File ddname | Dataset dsn} is being opened in mode mode
Block size blksize RABN range start-RABN to end-RABN
{File ddname | Dataset dsn} is encrypted
Explanation

The file (ddname) or dynamically allocated data set (dsn) is being opened in the mode (mode) given in the message (CKD, ECKD or zHPF). The file resides on a storage control device that supports count key data (CKD), extended count key data (ECKD) or high performance FICON (zHPF) channel commands. Adabas generates channel programs accordingly.

The block size (blksize) of the data set is given in the message. It contains the blocks with numbers start-RABN through end-RABN.

If the dataset is encrypted, an additional message line is generated to indicate this.

Action

No action is required for this informational message.

ADARUN Statement/Parameter Messages

Adabas Encryption introduces the following new ADARUN error message:

Error-29 Loaded modules do not support ENCRYPTION
Explanation

The Adabas load library is not correct and does not fully support Adabas Encryption, Adabas Auditing or Adabas SAF Security 8.3. Either the ADAIOR/IOS modules do not support Adabas Encryption or some of the required maintenance in the nucleus and utilities is missing.

Action

Review and correct the JOBLIB/STEPLIB concatenation or combined load library, as per the installation instructions for Adabas Encryption. Ensure that all zaps required for Adabas Encryption, Adabas Auditing or Adabas SAF Security 8.3 have been applied.

User Abend Code

Adabas Encryption introduces the following new user abend code. It can be referred to in messages either in decimal notation (for example, ‘U0692’) or in hexadecimal notation (for example, x‘2B4’).

Code Module Explanation
692 ADAIOS Dataset allocation error