ADAA* Adabas Auditing Messages

Note:
Each of the messages in this section starts with the relevant database ID.

Overview of Messages

ADAA01 | ADAA0G | ADAA1U | ADAA1V | ADAA1W | ADAA1X | ADAA17 | ADAAE2 | ADAAE4 | ADAAE5 | ADAAE6 | ADAAEG | ADAAEW | ADAAKX | ADAAPM | ADAAPN | ADAAPO | ADAAPP | ADAAPQ | ADAAPR | ADAAPS | ADAAPT | ADAAPU | ADAAPV | ADAAPW | ADAAPX | ADAAPY | ADAAP0 | ADAATA | ADAATB | ADAATC | ADAATF | ADAATG | ADAATH

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.


ADAA1U nnn output subtasks have been detached
Explanation

The Analytics Server output subtask termination process has completed. The total number of subtasks that have been terminated is given in the message (nnn).

Action

No action is required for this informational message.


ADAA1V Subtask nnn detach error eee occurred
Explanation

An error occurred while an Analytics Server output subtask was being detached. The subtask number (nnn) and the error number (eee) are given in the message.

Action

Analytics Server termination continues. Contact your DBA, system support personnel, or Software AG technical support for assistance.


ADAA1W Waiting for the termination of analytics server output subtasks
Explanation

The termination of Analytics Server output subtasks is in progress.

Action

No action is required for this informational message.


ADAA1X nnn output subtasks to be attached
Explanation

The Analytics Server is preparing to attach output subtasks.

Action

No action is required for this informational message.


ADAA17 All output subtasks could not be initialized
Explanation

One or more Adabas Analytics Server output subtasks could not be started successfully. One possible reason for this might be that the default subtask wait time (or the time specified by the SUBTASKWAIT parameter) is insufficient for your system.

For more information about the SUBTASKWAIT parameter, refer to SUBTASKWAIT (Subtask Wait Time) Parameter, in the Adabas Analytics documentation.

Action

Evaluate the setting of the SUBTASKWAIT parameter for your Adabas Analytics Server and consider increasing it (or setting it if it has not been set). If you still need assistance or the problem persists, contact your DBA, system support personnel, or Software AG technical support.


ADAAE2 Analytics activated for file nnnnn
due to request from ADADBS/AOS
Explanation

Analytics was activated for file nnnnn. The second message only appears if the reason code indicates the request was from ADADBS or AOS.

Action

No action is required for this informational message.


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


ADAAKX Requested storage exceeds maximum GETMAIN of 2,147,483,647 bytes
Explanation

A GETMAIN storage request would have exceeded the maximum amount that can be requested. Review the global definition settings for Subtasks and Maximum output size. The number of Subtasks + 1 for the main task is multiplied by the Maximum output size.

In addition, storage for additional control blocks related to the number of Subtasks, is added to the total and the result is used in the GETMAIN storage request.

Action

Either reduce the size of the Maximum output size or reduce the number of Subtasks, so that the GETMAIN size is less than the maximum size allowed.


ADAAPM The parameter xxxxxxxxxx must be in a group of file parameters
Explanation

The parameter must be proceeded by an ADAANP FILE statement.

Action

Check the parameter; correct the error and rerun the job.


ADAAPN The parameter xxxxxxxxxx must be in a group of global parameters
Explanation

The parameter must be proceeded by an ADAANP GLOBAL statement.

Action

Check the parameter; correct the error and rerun the job.


ADAAPO Only YES or NO are valid values for parameter xxxxxxxxxx
Explanation

Only YES or NO are valid values for this parameter.

Action

Check the parameter; correct the error and rerun the job.


ADAAPP Only YES, NO, or FIELDS are valid values for parameter xxxxxxxxxx
Explanation

Only YES, NO or FIELDS are valid values for this parameter.

Action

Check the parameter; correct the error and rerun the job.


ADAAPQ Invalid Adabas field name xx contained in parameter xxxxxxxxxx
Explanation

The Adabas field name does not conform to Adabas field name standards and will not be included in the list of field names.

Action

Check the parameter; correct the error and rerun the job.


ADAAPR Parameter FSERVERID | GSERVERID must be in the range 1 - 65535
Explanation

Only numbers in the range from 1 through 65535 are allowed.

Action

Check the parameter; correct the error and rerun the job.


ADAAPS Parameter GAPWARNINCREMENT must be in the range 1 - 99
Explanation

Only numbers in the range from 1 through 99 are allowed.

Action

Check the parameter; correct the error and rerun the job.


ADAAPT Parameter GAPWARNINTERVAL must be non-zero
Explanation

Only a non-zero value is allowed.

Action

Check the parameter; correct the error and rerun the job.


ADAAPU Parameter GAPWARNMESSAGELIMIT must be non-zero
Explanation

Only a non-zero value is allowed.

Action

Check the parameter; correct the error and rerun the job.


ADAAPV Parameter GAPWARNPERCENT must be in the range 1 - 99
Explanation

Only numbers in the range from 1 through 99 are allowed.

Action

Check the parameter; correct the error and rerun the job.


ADAAPW Parameter FSERVERID | GSERVERID must not be equal to the current database ID
Explanation

The value cannot be equal to the current database ID.

Action

Check the parameter; correct the error and rerun the job.


ADAAPX Parameter FLIST contains invalid file number nnnnnnnnnn
Parameter FLIST contains invalid file range nnnnnnnnnn - nnnnnnnnnn
From file number will be set to 1
To file number will be set to maximum file number nnnnn
Explanation

The parameter contains an invalid file number or range.

An invalid file number will not be included in the file list.

If both numbers in a file range are invalid and the FROM value is not 0, the file range will not be included in the file list

If the FROM value is 0 it will be set to 1, the lowest possible value.

If the TO value is greater than the maximum file number and the FROM value is 0 or a valid value, the TO value will be set to the maximum file number.

Action

Check the parameter; correct the error and rerun the job.


ADAAPY Required FLIST parameter is missing from the group of file parameters
The group of file definitions will not be used
Explanation

The FLIST parameter is required and missing from the group of file parameters. The group of file parameters will not be used.

Action

Check the parameter; correct the error and rerun the job.


ADAAP0 All files within the FLIST parameter are invalid
The group of file definitions will not be used
Explanation

All the files specified in the FLIST parameter were invalid. The group of file definitions will not be used.

Action

Check the parameter; correct the error and rerun the job.


ADAATA Load failed for mmmmmmmm
Explanation

The load of the ADAABK/ADAAMT module has failed. The module name is given as mmmmmmmm.

Action

Ensure the given module is available to the Analytics Server. Contact your DBA, system support personnel, or Software AG technical support if further assistance is needed.


ADAATB YYYYYY INIT call failed
Explanation

An error occurred during the initialization phase of YYYYYY. Where YYYYYY is either ADAABK or ADAAMQ and the text is followed by either 'GETMAIN failed' or the return code and reason code.

Action

Determine the reason for the failure based on the supplied reason code and correct the condition. Contact your DBA, system support personnel, or Software AG technical support if further assistance is needed.


ADAATC Connect failed Error info
Explanation

The Connect to the messaging system failed. The second line contains the Broker ID or the MQSeries queue manager name. The third line contains the error information.

Action

Determine the reason for the failure based on the supplied reason code and correct the condition. Contact your DBA, system support personnel, or Software AG technical support if further assistance is needed.


ADAATF Disconnect failed Error info
Explanation

The Disconnect to the messaging system failed. The second line contains the Broker ID or the MQSeries queue manager name. The third line contains the error information.

Action

Determine the reason for the failure based on the supplied reason code and correct the condition. Contact your DBA, system support personnel, or Software AG technical support if further assistance is needed.


ADAATG YYYYYY TERM call failed
Explanation

An error occurred during the termination phase of YYYYYY. Where YYYYYY is either ADAABK or ADAAMQ and the text is followed by return code and reason code.

Action

Determine the reason for the failure based on the supplied reason code and correct the condition. Contact your DBA, system support personnel, or Software AG technical support if further assistance is needed.


ADAATH Delete failed for YYYYYY
Explanation

An attempt to delete the module YYYYYY from storage failed. Where YYYYYY is either ADAABK or ADAAMQ. This should not occur and should be reported to your local support center.

Action

Contact your local support center.