Messages and Codes

This section describes the error messages that can result when using Adabas Auditing.

For all other error messages refer to the Adabas for Mainframes documentation > Messages and Codes.


Adabas Nucleus Auditing Start-up and Run-time Messages

The following messages may be issued by an Adabas nucleus running with ADARUN AUDITING=YES.

Overview of Messages

PARM-ERROR 130 | ADAAE4 | ADAAE5 | ADAAE6 | ADAAEG | ADAAEW
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 AUDITING = YES.


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.


ADAAE6 yyyy.mm.dd hh.mm.ss No connection attempts will be made as a
yyyy.mm.dd hh.mm.ss result of the AUDCONNECT request
Explanation

This message is printed as a result of the AUDCONNECT operator command (issued to an Adabas nucleus). The message is printed when no connection attempts will be made as a result of the AUDCONNECT operator command.

Action

Analyze the AUDCONNECT operator command you issued for invalid Auditing Server IDs that might have been specified.


ADAAEG yyyy.mm.dd hh.mm.ss A connection will be attempted
yyyy.mm.dd hh.mm.ss with server id
Explanation

This message is printed as a result of the AUDCONNECT operator command (issued to an Adabas nucleus). The message is printed for each Auditing Server ID for which the nucleus attempts a connection.

Action

No action is required for this informational message.


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).


Adabas Audit Server Messages

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.

Overview of Messages

ADAA01 | ADAA0G | ADAAJ2 | ADAAK2 | ADAAK3 | ADAAK4 | ADAAK8 | ADAALA | ADAALB | ADAALC | ADAALD | ADAALE | ADAALJ | ADAALK | ADAALL | ADAALM | ADAALP | ADAA18 | ADAA2D | ADAA2E | ADAA2F | ADAA2G | ADAA2H | ADAA2Q | ADAA1Q | ADAA1R | ADAA14 | ADAA15 | ADAA16 | ADAA19
ADAA01 yyyy.mm.dd hh.mm.ss No connection attempts will be made as a
yyyy.mm.dd hh.mm.ss result of the AUDCONNECT request
Explanation

This message is printed as a result of the AUDCONNECT operator command (issued to an Auditing Server). The message is printed when no connection attempts will be made as a result of the AUDCONNECT operator command.

Action

Analyze the AUDCONNECT operator command you issued for invalid Adabas database IDs that might have been specified.


ADAA0G yyyy.mm.dd hh.mm.ss A connection will be attempted
yyyy.mm.dd hh.mm.ss with database id
Explanation

This message is printed as a result of the AUDCONNECT operator command (issued to an Auditing Server). The message is printed for each Adabas database for which the Auditing Server attempts a connection.

Action

No action is required for this informational message.


ADAAJ2 The value 'x' is invalid in subscription subs-id
DBID/FNR = nnnnn/nnnnn for phrase1
Valid values are phrase2
Explanation

A value read from the subscription subs-id defined in the ALA system file is incorrect. The value is listed as ‘x’ above, the DBID/FNR is identified, and the name of the incorrect value is listed, i.e. phrase1 might be “send insert data image”. An expected valid value is listed, phrase2, an example being ’Y’ or ‘N’.

Action

Using the AMN or SYSALA editor for the ALA system file, verify the subscription, dbid/fnr, and the name of the incorrect value (phrase1). Correct if necessary (phrase2 values). Also contact your Software AG support representative with the contents of the message.


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 subs-id 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 subs-id database dbid file nn. before|after|key image uses global format buffer gfb. This global format buffer is also used by subscription subs-id 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 ID 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-id, 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:

  • Request format buffer

  • Client-Info format buffer

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-id 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-id DBID dbid file fnr. filter filter-id 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:

  • Begin byte or length not supported for field format

  • Begin byte plus length greater than field length

  • Field, PE or MU instance not found in Format buffer

  • Field specified cannot be used in field level filter

  • Field type unrecognized

  • Invalid begin byte specified

  • Invalid length specified

  • Invalid or out of range FLIST data: data

    hex: hex

  • Source field type incompatible with target

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-id. 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:

  • no FCB

  • no FDT

  • record too big

  • decompress error

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.


ADAA1Q SLOG turned on for destination dest-name
Explanation

SLOG processing has been turned on for the destination listed in the message (dest-name).

Action

No action is required for this informational message.


ADAA1R SLOG turned off for destination dest-name
Explanation

SLOG processing has been turned off for the destination listed in the message (dest-name).

Action

No action is required for this informational message.


ADAA14 Destination destination deactivated due to reason
Explanation

The status for the identified destination has changed on the Audit Server.

The deactivation reason will be one of the following:

  • auditing pool full

  • request from ADADBS

  • request via operator command/AOS

  • SLOG-related error

  • SLOG system file full

Action

If the deactivation reason is "auditing pool full", consider increasing the value of the LAP parameter. For other reasons this message is for information only.


ADAA15 Subscription subscription deactivated due to reason
Explanation

The deactivation reason will be one of the following:

  • deactivation of last destination

  • error in subscription processing

  • request from ADADBS

  • request via operator command/AOS

Action

No action is required for this informational message.


ADAA16 Subscription subscription activated due to reason
Explanation

The activation reason will be one of the following:

  • request from ADADBS

  • request via operator command/AOS

Action

No action is required for this informational message.


ADAA19 SLOG cleanup process {started|aborted|completed|halted}
Explanation

The SLOG cleanup process has started, aborted, completed or halted.

Action

No action is required for this informational message.


ADADBS Utility Messages

Overview of Messages

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-265
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 DESTINATION was missing.

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 DESTINATION or SUBSCRIPTION was missing.

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 (ADARUN AUDITING=YES).

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 NUCID= parameter was specified for a non-cluster Adabas database.

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.


ERROR-265 Invalid value for parameter AUDCONNECT
Explanation

Only valid DBIDs, auditing server IDs, or ALL are allowed.

Action

Supply the correct parameter value and rerun the job.


Adabas Response Codes

Overview of Messages

Response 136
Response 136
Origin Mainframe systems only
Explanation

This response code is used for communication with Adabas utilities and Adabas Audit Administration (SYSALAA) or Adabas Online System (AOS). The system returns this error because the requested function could not be performed on the Adabas system and its files, or because an error occurred in a SYSALAA/AOS or utility function.

Action

For SYSALAA/AOS, a subcode is displayed in the error message or a descriptive message indicates the error that occurred. For utility functions, the subcodes may be described within the message text or a descriptive message indicates the error that occurred. If you do not understand the action to take, note the subcode and the function that caused the response code and call your Software AG technical support representative for assistance.