This section describes the error messages that can result when using Adabas Auditing.
For all other error messages refer to the Adabas Messages documentation.
The following messages may be issued by an Adabas nucleus running
with ADARUN AUDITING=YES
.
PARM-ERROR 130 | ADAAEW | ADAAE4 | ADAAE5
PARM-ERROR 130 | Auditing initialization error - detected during system open |
Explanation |
Once AUDITING is turned on, the only option allowed for the AUDITING parameter is YES. |
Action |
Set |
ADAAEW | Collection of auditing data for xxxxxx commands for file nnnnn will not be controlled by field names |
Explanation |
The value of xxxxx will be either access or update. If the value is "access", then one of the ADAANP parameters FACCACBX, FACCDS, or FACCINFO is set to FIELDS and there was no field list provided in FACCFIELDS. In this case, FACCACBX, FACCDS, and FACCINFO are changed to NO. If the value is "update", then one of the ADAANP parameters FUPDACBX, FUPDAI, FUPDBI or FUPDINFO is set to FIELDS and there was no field list provided in FUPDFIELDS. In this case, FUPDACBX, FUPDAI, FUPDBI, and FUPDINFO are changed to NO. |
Action |
Provide a field list (FACCFIELDS or FUPDFIELDS) or set the data collection parameters to a value other than FIELDS (YES or NO). |
ADAAE4 | Warning during FACCFIELDS validation: Field xx is not defined in file nnnn |
Explanation |
The field name xx in the list of fields in ADAANP parameter FACCFIELDS is not a valid field for file nnnn. |
Action |
Ensure that the field xx is correct for this file. For the FACCFIELDS ADAANP parameter, each field should be in the FDT or SDT. This is a warning only. The field xx for file nnnn will be ignored. |
ADAAE5 | Warning during FUPDFIELDS validation: Field xx is not defined in file nnnnn or is a special descriptor |
Explanation |
The field name xx in the list of fields in ADAANP parameter FUPDFIELDS is not a valid field for file nnnn. |
Action |
Ensure that the field xx is correct for this file. For the FUPDFIELDS ADAANP parameter, each field should be in the FDT. Fields defined in the SDT (special descriptors) are invalid. This is a warning only. The field xx for file nnnn will be ignored. |
The following messages may be issued by the Adabas Audit Server.
Most messages are written to the console using WTO. Some are noted as being written to file DDAUDERR instead. Messages on DDAUDERR are formatted similarly to a multi-line WTO: the message number and DBID appear on only the first line of the message. Each line is prefixed with the Julian date and local time.
ADAAK2 | ADAAK3 | ADAAK4 | ADAAK8 | ADAALA | ADAALB | ADAALC | ADAALD | ADAALE | ADAALJ | ADAALK | ADAALL | ADAALM | ADAALP | ADAA18 | ADAA2D | ADAA2E | ADAA2F | ADAA2G | ADAA2H | ADAA2Q
ADAAK2 | Filter xxxxxxxx source field name xx. Invalid value '/X’xxxxxxxx' for keyword |
Explanation |
The field name xx in filter xxxxxxxx has an invalid keyword value as reported in the message. |
Action |
Investigate the cause of the error, correct it, and restart the Audit Server. |
ADAAK3 | Misuse of A( ) or X( ) notation |
Explanation |
The notation was specified incorrectly. |
Action |
Investigate the cause of the error, correct it, and restart the Audit Server. |
ADAAK4 | Misuse of wildcharacter in value |
Explanation |
The wildcharacter notation was specified incorrectly. |
Action |
Investigate the cause of the error, correct it, and restart the Audit Server. |
ADAAK8 | Global Format xxxxxxxx has an invalid length |
Explanation |
The Global Format xxxxxxxx length is invalid. Maximum size is 32767. |
Action |
Investigate the cause of the error, correct it, and restart the Audit Server. |
ADAALA | For Subscription xxxxxxxx. Format xxxxxxxx not found in format definitions |
Explanation |
The format xxxxxxxx defined for Subscription xxxxxxxx was not found in the format definitions. |
Action |
Investigate the cause of the error, correct it, and restart the Audit Server. |
ADAALB | Subscription subsname database dbid file nn. before|after|key image uses global format buffer gfb. This global format buffer contains field table information. It may not be used by more than one combination of database and file. |
Explanation |
A global format buffer (GFB) definition contains a field table and is used for more than one combination of database ID and file number. This is not allowed. |
Action |
Correct the subscription so that the GFB field table is used for a single combination of database ID and file number. |
ADAALC | Subscription subsname database dbid file nn. before|after|key image uses global format buffer gfb. This global format buffer is also used by subscription subsname database dbid file nn. |
Explanation |
A global format buffer (GFB) definition is used by a subscription for the same file number on different databases. This is not allowed. |
Action |
Correct the subscription so that the GFB is used properly. |
ADAALD | GFORMAT xxxxxxxx is not unique |
Explanation |
Duplicate names for global format definitions have been found. |
Action |
Check the parameter input, correct the error, and restart the Audit Server. |
ADAALE | Subscription xxxxxxxx Global and Local format buffers are mutually exclusive |
Explanation |
A global or a local format may be specified, but not both. |
Action |
Check the parameter input, correct the error, and restart the Audit Server. |
ADAALJ | Invalid hexadecimal input for X( ) notation |
Explanation |
The hexadecimal value was invalid. |
Action |
Investigate the cause of the error, correct it, and restart the Audit Server. |
ADAALK | Filter xxxxxxxx, Group xxxx, Condition xxxx inconsistent with value list |
Explanation |
A value list cannot be used with the specified condition. |
Action |
Investigate the cause of the error, correct it, and restart the Audit Server. |
ADAALL | Global filter format xxxxxxxx not found in Global format definitions |
Explanation |
The filter format name xxxxxxxx does not match a global format. |
Action |
Investigate the cause of the error, correct it, and restart the Audit Server. |
ADAALM | Subscription xxxxxxxx has been deactivated |
Explanation |
The subscription xxxxxxxx was deactivated because of an error. |
Action |
Ensure the Audit Server is running with an ALOG defined if you wish to use destinations of type AUDIT. |
ADAALP | Filter xxxxxxxx; target field not allowed |
Explanation |
For a request or client filter, the target can only be one or more values. The target cannot be a field. The subscription is deactivated. |
Action |
Correct the filter to use a value as the target of the compare. |
ADAA18 | Unable to acquire a UQE for subscription Response rrrrr, subcode sssss |
Explanation |
The subscription is deactivated. This message appears in file DDAUDERR and is not displayed on the console. |
Action |
Increase the value specified for the ADARUN NU parameter, and restart the Audit Server. |
ADAA2D | Format buffer error Subscription subscription-name, error-description Response code rrrrr, subcode sssss {field name ff|Additions2 x’aaaa’} |
Explanation |
An error occurred processing a format buffer of a command for the subscription named in the message. The response code and subcode are shown in the message. When a field name is available it is shown, otherwise the contents of either ACBAdd2 bytes 0:1 or ACBXErrB are shown in hex. Possible error descriptions are:
This message appears in file DDAUDERR and is not displayed on the console. |
Action |
Correct the error in the format buffer indicated by the error description. |
ADAA2E | Open of File destination name failed as ALOG is not active |
Explanation |
A command was issued to open an Audit destination, but a command log was not defined in the Audit Server. |
Action |
Ensure the Audit Server is running with an ALOG defined if you wish to use Adabas Auditing. |
ADAA2F | One or more Audit destinations are defined but ALOG is not active |
Explanation |
One or more Audit destination definitions are being used, but the ALOG is not defined in the Audit Server start-up JCL. The AUDIT destinations are set to "Unavailable" and processing continues. |
Action |
Identify the ALOG in the Audit Server start-up JCL and try again. |
ADAA2G | Failed to set conversion attributes to subscription flist encoding for subscription subscription-name DBID dbid file fnr. Failed to set conversion attributes to user encoding |
Explanation |
An error occurred processing a command for the subscription named in the message. A description of the error, the response code, and subcode are also listed in the message. This message appears in file DDAUDERR and is not displayed on the console. |
Action |
Correct the conversion attribute problem indicated by the error description. |
ADAA2H | Subscription subscription-name DBID dbid file fnr. filter filter-name group group-name condition nnnnn field xx error: error-description |
Explanation |
An error occurred with the field, filter, and subscription named in the message. A description of the error, the database ID, file number, and condition are also listed in the message. Possible error descriptions are:
This message appears in file DDAUDERR and is not displayed on the console. |
Action |
Correct the problem indicated by the error description. |
ADAA2Q | Error during subscription processing: error-description.Subscription subscription-name. Response code rrrrr, subcode sssss |
Explanation |
An error occurred processing a command for the subscription named in the message. A description of the error, the response code, and subcode are also listed in the message. Possible error descriptions are:
This message appears in file DDAUDERR and is not displayed on the console. |
Action |
Investigate the cause of the error. The error may be an internal error. If you are unable to determine the cause, contact Software AG technical support. |
ERROR-242 | ERROR-243 | ERROR-245 | ERROR-246 | ERROR-247 | ERROR-248 | ERROR-249 | ERROR-250 | ERROR-251 | ERROR-252 | ERROR-253 | ERROR-254 | ERROR-255 | ERROR-257 | ERROR-258 | ERROR-259 | ERROR-260
ERROR-242 | Invalid FILE number specified for auditing |
Explanation |
The ADADBS AUDITING function is only valid for files participating in auditing (are included in an ADAANP FILE group). |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-243 | The specified FILE was already active|inactive |
Explanation |
The database detected the file identified in the message was already active or inactive. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-245 | AUDITSERVER function only allowed for use with the Audit Server |
Explanation |
The ADADBS AUDITSERVER function is only valid for an Audit Server. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-246 | The specified destination destination was not found |
Explanation |
The destination identified in the message is not defined to the Audit Server. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-247 | The specified subscription subscription was not found |
Explanation |
The subscription identified in the message is not defined to the Audit Server. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-248 | The specified destination destination was already active|inactive |
Explanation |
The Audit Server detected the destination identified in the message was already active or inactive. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-249 | The specified subscription subscription was already active|inactive |
Explanation |
The Audit Server detected the subscription identified in the message was already active or inactive. |
Action |
Investigate the cause of the error. Correct it and, rerun the job. |
ERROR-250 | Missing parameter: DESTINATION required |
Explanation |
ADADBS detected that the required parameter
|
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-251 | Missing parameter: DESTINATION or SUBSCRIPTION required |
Explanation |
ADADBS detected that the required parameter
|
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-252 | SUBSCRIPTION parameter not allowed for OPEN or CLOSE: only DESTINATION |
Explanation |
ADADBS detected invalid parameter SUBSCRIPTION with OPEN or CLOSE. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-253 | The specified subscription subscription was not activated|deactivated |
Explanation |
The Audit Server detected an unexpected response code from an attempt to activate or deactivate the subscription identified in the message. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. If the cause of the error cannot be determined, contact your Software AG technical support representative. |
ERROR-254 | Auditing not active for Adabas |
Explanation |
The database is not an auditing database ( |
Action |
Investigate the cause of the error. Correct it and rerun the job. |
ERROR-255 | NUCID specified for a non-cluster Adabas DBID |
Explanation |
The |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-257 | {CLOSE | OPEN} failed for specified destination destination |
Explanation |
ADADBS detected that the Audit Server could not CLOSE or OPEN the destination identified in the message. |
Action |
Investigate the cause of the error. The Audit Server job log will provide more details on why the request failed. |
ERROR-258 | The specified destination destination cannot be activated.Data still exists on the SLOG system file for this inactive destination. |
Explanation |
An attempt was made to activate the destination identified in the message while items for the destination still exist on the SLOG system file from the last time it was active. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-259 | The specified destination destination was already open|closed |
Explanation |
The Audit Server detected the destination identified in the message was already open or closed for all tasks. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. |
ERROR-260 | The specified destination destination was not activated|deactivated |
Explanation |
The Audit Server detected an unexpected response code from an attempt to activate or deactivate the destination identified in the message. |
Action |
Investigate the cause of the error. Correct it, and rerun the job. If the cause of the error cannot be determined, contact your Software AG technical support representative. |