ADAA* Auditing Messages

Getmain for Auditing area failed or there was insufficient storage available.

Rectify the Getmain problem and rerun the job.

Getmain for Auditing area failed or there was insufficient storage available. Requested and acquired values are given.

Rectify the Getmain problem and rerun the job.

The LAP value must be at least 100,000.

Supply correct parameters and rerun the job.

These messages begin when auditing pool usage first exceeds the value of ADARUN parameter GAPWARNPERCENT. Further messages appear at usage intervals specified by ADARUN parameter GAPWARNINCREMENT.

If the usage is not anticipated, you may want to adjust ADARUN parameter LAPL to increase the size of the auditing pool. Adjust ADARUN parameters GAPWARNPERCENT and GAPWARNINCREMENT to control when warning messages are issued.

A number of ADAAAD messages warning of an auditing pool shortage have been issued. In order to avoid flooding the console, additional messages are suppressed for a period after a threshold is reached. When the suppression period has expired, the Auditing Server will display the number of suppressed message lines and then start printing auditing pool usage warning messages again. The number of messages issued before suppression is specified by ADARUN parameter GAPWARNMESSAGELIMIT. The suppression interval is specified by ADARUN parameter GAPWARNINTERVAL.

No action is required for these informational messages. If needed, adjust the ADARUN parameters GAPWARNMESSAGELIMIT and GAPWARNINTERVAL to control message traffic.

There was not enough free storage in the Auditing pool to satisfy a request.

Execution continues. Increasing the value of the LAP parameter may alleviate the shortage.

Conflicting parameters – AUDITING=YES is not allowed for an Auditing Server.

Supply correct parameters and rerun the job.

An error occurred while attempting to read the Auditing server system file. The command return code (rc), response code (rp) and command code (cc) are given in the message.

Review the response code to determine why the Auditing server system file could not be read. Then take appropriate actions to correct the error. If the problem persists, contact your Software AG technical support representative for assistance.

The Auditing Server has disconnected from the database or nucleus listed in the message. This message normally follows message ADAA0J and indicates that all auditing data for the database has been processed when the Auditing Server was terminated by ADAEND. If the Auditing Server has been terminated via a HALT request, there is no guarantee that all data has been processed. The first instance of this message occurs when the Auditing Server has disconnected from a noncluster Adabas nucleus. The second instance of this message occurs when the Auditing Server has disconnected from an Adabas cluster nucleus (for example, an Adabas Cluster Services or an Adabas Parallel Services nucleus).

No action is required for this informational message.

The nucleus listed in the message is not currently active.

Start the database.

ADAEND has been issued to the Auditing Server with auditing data still in progress.

The Auditing Server will terminate only after all the auditing data that are still in progress have completed.

The Auditing Server attempted to communicate with a database defined via a subscription but found the database is running with an AUDITING=NO setting, or has AUDITING=YES, however, no data is sent to this Auditing Server. Communication is suspended between the Auditing Server and the database.

Execution continues. No auditing will occur for the database and this Auditing Server.

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.

No action is required for this informational message.

The Auditing Server attempted to disconnect from the database listed in the message, but received the response code and subcode (rrr/sss) listed in the message during the attempt.

Investigate the response code and subcode to identify and correct the problem.

The Auditing Server attempted to connect from the database listed in the message, but received the response code and subcode (rrr/sss) listed in the message during the attempt.

Investigate the response code and subcode to identify and correct the problem.

The Auditing Server is in the process of disconnecting from the database or nucleus listed in the message. The first instance of this message occurs when the Auditing Server is disconnecting from a noncluster Adabas nucleus. The second instance of this message occurs when the Auditing Server is disconnecting from an Adabas cluster nucleus (for example, an Adabas Cluster Services or an Adabas Parallel Services nucleus). In this second instance, the Adabas cluster itself ensures that all nuclei in the cluster are informed about the Auditing Server disconnecting.

No action is required for this informational message.

This message is displayed in response to the operator command DAUDSTAT. It shows the auditing-related statistics for a database.

No action necessary for this informational message.

An unexpected error occurred related to the data storage RABN listed in the message.

Identify and fix the problem from the response code (rc) and data storage RABN listed in the message or contact your Software AG technical support representative for assistance.

There was insufficient work pool space available to the Auditing Server.

Increase the setting of the ADARUN LWP parameter for the Auditing Server. Then stop and restart the Auditing Server.

You have specified ‘SLOG allowed=YES’ for the SYSALA destination definition, but an SLOG file has not been defined to the Auditing Server for Adabas.

Determine if ‘SLOG allowed=YES’ is required and, if so, define a SLOG file to the Auditing Server.

UTIONLY=YES is not allowed for an Auditing Server.

Supply correct parameters and rerun the job.

SLOG data has been found for the destination listed in the message, which now has ‘SLOG allowed=NO’ set. This implies that at some point in the past, ‘SLOG allowed=YES’ was set and was subsequently changed. Be aware that this message indicates that previously logged data is now lost.

If logging should not be active for the destination, this can be ignored. However, if it should be active, determine why the configuration was changed.

SLOG initialization processing has encountered data on the SLOG system file for the destination listed in the message. However, the destination is not defined in the current configuration. All SLOG data related to the destination will be deleted.

If the destination should be defined, determine why it was omitted from the configuration.

SLOG initialization processing completed successfully.

No action is required for this informational message.

Use of the SLOG system file for storing and processing database-related input transactions from the Adabas nucleus has been disabled for the listed destination. This may occur when SLOG processing of the database-related input transactions is suspended and a subsequent error occurred while attempting to delete the transactions from the SLOG system file.

Review earlier messages to determine the cause of the problem.

An unexpected error occurred during SLOG processing. The details of the error are provided in the second line of the message, as described in the following table. The response code and reason code are also provided in the message.

Investigate the response and reason codes to determine the cause of the problem and correct it. If you get the "Workpool storage request failed for CQE" message text, verify that sufficient storage is available for Auditing Server initialization.

This message is printed as a result of the DAUDPARM operator command. The Auditing definitions for this Adabas are printed.

No action necessary for this informational message.

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.

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

DTP=TM or DTP=RM is not allowed for an Auditing Server.

Supply correct parameters and rerun the job.

MODE=SINGLE is not allowed for an Auditing Server.

Supply correct parameters and rerun the job.

READONLY=YES is not allowed for an Auditing Server.

Supply correct parameters and rerun the job.

An attempt to close a destination dddddddd was performed. The destination was already closed.

No action is required for this informational message.

An attempt to open a destination dddddddd was performed. The destination was already open.

No action is required for this informational message.

An action listed was performed for destination dddddddd, due to the request from ADADBS/AOS.

No action is required for this informational message.

The destination listed in the message (dddddddd) was deactivated, due to the reason specified.

No action is required for this informational message, if it was expected. If it is unexpected, investigate the reason or any additional messages to identify and correct the problem.

The subscription listed in the message (ssssssss) was deactivated, due to the reason specified.

No action is required for this informational message, if it was expected. If it is unexpected, investigate the reason or any additional messages to identify and correct the problem.

The subscription listed in the message (ssssssss) was activated, due to the reason specified.

No action is required for this informational message, if it was expected. If it is unexpected, investigate the reason or any additional messages to identify and correct the problem.

One or more Auditing Server subtasks could not be started successfully. One possible reason for this might be that the default subtask wait time is insufficient for your system. Reference SYSALA Global Definitions, for "Subtask Activation Wait Time" to increase the parameter if needed.

Investigate the reason why this failed or any additional messages, to identify and correct the problem.

A UQE is required for processing subscription ssssssss. A User Queue Element is used to store pointers to the internal format buffers and other information and could not be acquired. The response code (rc) and subcode (sc) are given in the message.

Investigate the response code and subcode to identify and correct the problem.

The SLOG cleanup process status message.

No action is required for this informational message.

STP=YES is an invalid parameter setting.

Supply correct parameters and rerun the job.

REPLICATION=YES is an invalid parameter setting.

Supply correct parameters and rerun the job.

The NT value must be at least 15.

Supply correct parameters and rerun the job.

The LU value must be at least 167,000.

Supply correct parameters and rerun the job.

The NAB value must be at least 41.

Supply correct parameters and rerun the job.

The nucleus has connected to the Auditing Server. The DBID or DBID-nucleus ID (dbid/nucid) combination as well as the Adabas and the Auditing for Adabas versions (ADAvrm/ALAvrm) are shown in the message. In addition, the database is identified as a local or a remote database in the message.

No action is required for this informational message.

The Auditing server, has determined the module ADAASP is incompatible with ADAASF.

Ensure that all recent updates have been applied and that the load module versions in use are as delivered by Software AG. Investigate, correct the problem and rerun the job. If the problem persists, contact your Software AG support representative for assistance.

The Adabas or Auditing for Adabas version running in the Adabas nucleus is incompatible with the Adabas or Auditing for Adabas version running in the Auditing Server nucleus. The software level in the Auditing Server must be greater than or equal to the software level in the source nucleus.

Analyze the use of the Adabas and Auditing Server nucleuses to determine which versions should be used on each. Then update the software as appropriate. Contact your Software AG technical support representative if you need assistance.

During session startup, one or more errors were found in the auditing definitions.

Examine the Auditing server output for the error information, make the necessary corrections, and rerun the job.

An error occurred while attempting to process auditing parameters. The return code is given in the message.

Review the return code to determine why the error occurred. Then take appropriate actions to correct the error. If the problem persists, contact your Software AG technical support representative for assistance.

The destination name dddddddd is not available.

Ensure the destination is correctly defined and assigned.

The Auditing Server initializing messages process has failed with Adabas response code and subcode (rrr/sss) given in the message.

Investigate the response code and subcode to identify and correct the problem.

The destination identified in the message (dddddddd) will not be opened. The destination was either defined with SYSALA Destination parameter "Open at Startup = N" or "Open at Startup = G" and the SYSALA Global Definitions parameter "Open at Start = NO".

No action is required for this informational message.

The nucleus has disconnected from the Auditing Server. The DBID or DBID-nucleus ID combination is shown in the message.

No action is required for this informational message.

An operator command DAUDPARM was issued, and the listed destination or subscription was not found. This error is produced because a resource name specified in the command was not valid. The invalid resource name (Destination dddddddd or Subscription ssssssss) are given in the message.

Review and correct the command specifications and then rerun it.

SLOG processing has been turned on for the destination listed in the message (dddddddd).

No action is required for this informational message.

SLOG processing has been turned off for the destination listed in the message (dddddddd).

No action is required for this informational message.

An open request was either successful, partially successful, or failed for the destination listed in the message (dddddddd).

No action is required for this informational message if successful. If there was any type of failure, investigate any additional messages to identify and correct the problem.

A close request was either successful, partially successful, or failed for the destination listed in the message (dddddddd).

No action is required for this informational message if successful. If there was any type of failure, investigate any additional messages to identify and correct the problem.

During the Auditing Server shutdown processing, nnn output subtasks were detached.

No action is required for this informational message.

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

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

The termination of the output subtasks is in progress.

No action is required for this informational message.

This message indicates the number nnn of subtasks that will be attached.

No action is required for this informational message.

An attempt to close a destination definition occurred for which pending open retries are still outstanding. The pending open retries are dropped.

No action is required for this informational message.

A Close/Open request, for a destination dddddddd , has an action xxxxxxxx of received, rejected or invalid.

If the Close/Open request failed, review associated messages to determine why it failed; then correct the problem if needed. Otherwise, no action is required for this informational message.

The number of transactions deleted from the SLOG file during cleanup processes for the destination dddddddd.

No action is required for this informational message.

An unexpected error occurred related to the data storage RABN listed in the message.

Identify and fix the problem from the response code and data storage RABN listed in the message or contact your Software AG technical support representative for assistance.

A GETMAIN failure occurred during connection from Adabas DBid xxxxx.

Identify and fix the problem from the response code subcode rc sc or contact your Software AG technical support representative for assistance.

A Format buffer error occurred during processing of subscription ssssssss.

Identify and fix the problem from the response code subcode rc sc or contact your Software AG technical support representative for assistance.

An open of file destination dddddddd failed as the ALOG is unavailable.

Investigate why the ALOG is unavailable. If needed, contact your Software AG technical support representative for assistance.

An open destinations failed as the ALOG is unavailable.

Investigate why the ALOG is unavailable. If needed, contact your Software AG technical support representative for assistance.

Subscription filter list encoding or user encoding to set conversion attributes failed for the Dbid/file listed.

Investigate the failure using the response code rc and reason code rrrrr. If needed, contact your Software AG technical support representative for assistance.

Subscription filter error has occurred for the Dbid/file listed, giving the filter, group, condition and field. One of four types of errors follows on the next line.

Investigate the failure and correct as necessary. If needed, contact your Software AG technical support representative for assistance.

A status of the SLOG is listed in the message.

No action is required for this informational message, if it was expected. If it is unexpected, investigate the reason or any additional messages to identify and correct the problem.

A status of the SLOG is listed in the message.

No action is required for this informational message, if it was expected. If it is unexpected, investigate the reason or any additional messages to identify and correct the problem.

A status of the SLOG is listed in the message.

No action is required for this informational message, if it was expected. If it is unexpected, investigate the reason or any additional messages to identify and correct the problem.

A status of the SLOG is listed in the message.

No action is required for this informational message, if it was expected. If it is unexpected, investigate the reason or any additional messages to identify and correct the problem.

A status of the SLOG is listed in the message.

No action is required for this informational message, if it was expected. If it is unexpected, investigate the reason or any additional messages to identify and correct the problem.

The parameter "LOG INPUT" in SYSALA Global Defitions is set to ALL or 1-99, and the SLOG system file is not defined.

If a SLOG file is required, define a SLOG file or change the parameter to NO.

A Data status of the SLOG is listed in the message.

No action is required for this informational message, if it was expected. If it is unexpected, investigate the reason or any additional messages to identify and correct the problem.

The subscription listed in the message (ssssssss) had an error during processing.

Investigate the response code rc, subcode sc for the field name listed. Identify and correct the problem.

An instance of the ADAARP utility has established a session with the Auditing Server for the database identified in the message. The token number it has been assigned is also listed in the message and can be used to track the session.

No action is required for this informational message.

An instance of the ADAARP utility has terminated its session with the Auditing Server for the database identified in the message. The token number is also listed in the message and identifies the terminating session. The total number of transactions processed by the ADAARP utility is also given in the message.

No action is required for this informational message.

The replay process referred to in the preceding ADAA2S message ended successfully. The Auditing Server returns response code 0 (ADARSP000) to the disconnecting ADAARP.

No action is required for this informational message.

The replay process referred to in the preceding ADAA2S message has encountered an error. The response code and subcode shown in the message is returned by the Auditing Server to ADAARP.

Investigate the cause of the error, correct it, and run a new replay job.

There are two possible reasons for this message. Either you entered an AUDCLEANUP=ALL operator command and there were no ADAARP replay operations in progress, or you entered an AUDCLEANUP=token operator command and there was no ADAARP replay operation in progress with the specified token.

Supply a token for a replay operation that is in progress or start some ADAARP replay operations. The operator command DAUDSTAT can be used to identify active ADAARP replay tokens.

The Adabas nucleus has responded to an operator command of ‘DAUDSTAT,GLOBALS’. There may be extensions to the DAUDSTAT command, that has additional information to be displayed.

No action is required for these informational messages. Reference the ‘DAUDSTAT Command against an Adabas Nucleus’ documentation for additional information.

The Adabas nucleus deactivated auditing for the listed file, for the specified reason, if it was available.

Investigate the informational error message if it was unexpected. Correct it and rerun the job.

Auditing was activated for file nnnnn due to the specified reason.

No action is required for this informational message. If it was unexpected, investigate the reason.

The Adabas nucleus has responded to an operator command of "DAUDSTAT,F=ALL" or "DAUDSTAT,F=nnnnn". There may be extensions to the DAUDSTAT command, that has additional information to be displayed.

No action is required for these informational messages. Reference the "DAUDSTAT Command against an Adabas Nucleus" documentation for additional information.

The Adabas nucleus ADAANP input for the listed file has FACCDS=FIELDS for access commands. Field XX is specified for parameter FACCFIELDS and is not defined in the file.

Correct your ADAANP parameters FACCDS and FACCFIELDS as required, for the listed file number and rerun the job.

The Adabas nucleus ADAANP input for the listed file, has FUPDAI|FUPDBI =FIELDS for update commands. Field XX is specified for parameter FUPDFIELDS and is not defined in the file or is a special descriptor.

Correct your ADAANP parameters FUPDAI|FUPDBI and FUPDFIELDS as required, for the listed file number and rerun the job.

The Adabas nucleus has responded to an operator command of "AUDCONNECT=ALL" or "AUDCONNECT=nnnnn" and that attempt has failed.

Examine the prior console log for additional messages. If it is an unexpected message, reference the AUDCONNECT Command operator command documentation for additional information.

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.

No action is required for this informational message.

The Adabas nucleus ADAANP input for the listed file, has FACCDS=FIELDS for access commands, however there are no fields specified for parameter FACCFIELDS.

Correct your ADAANP parameters FACCDS and FACCFIELDS as required, for the listed file number.

The Adabas nucleus ADAANP input, does not have the Auditing server DBid of nnnnn for GSERVERID or DSERVERID, or for a specific file FSERVERID, thus the connection is refused.

Correct your ADAANP parameters, or correct SYSALA Subscription parameters for the Auditing server nnnnn and rerun the job.

The Adabas nucleus has AUDITING=NO, has received a connection request from the listed Auditing server, and refused that connection.

Verify and correct your parameter input for the Adabas nucleus and/or SYSALA subscriptions for the Auditing server, if this was an unexpected message. Rerun jobs as required.

The Adabas nucleus, while processing the ADAANP input, has found an error(s), and listed out one or more of the above messages.

Correct your ADAANP parameters as needed per the messages and rerun the job.

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

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.

The field name xx in filter xxxxxxxx has an invalid keyword value as reported in the message.

Investigate the cause of the error, correct it, and restart the Audit Server.

The notation was specified incorrectly.

Investigate the cause of the error, correct it, and restart the Audit Server.

The wildcharacter notation was specified incorrectly.

Investigate the cause of the error, correct it, and restart the Audit Server.

The Global Format xxxxxxxx length is invalid. Maximum size is 32767.

Investigate the cause of the error, correct it, and restart the Audit Server.

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.

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.

The format xxxxxxxx defined for Subscription xxxxxxxx was not found in the format definitions.

Investigate the cause of the error, correct it, and restart the Audit Server.

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.

Correct the subscription so that the GFB field table is used for a single combination of database ID and file number.

A global format buffer (GFB) definition is used by a subscription for the same file number on different databases. This is not allowed.

Correct the subscription so that the GFB is used properly.

Duplicate names for global format definitions have been found.

Check the parameter input, correct the error, and restart the Audit Server.

A global or a local format may be specified, but not both.

Check the parameter input, correct the error, and restart the Audit Server.

The hexadecimal value was invalid.

Investigate the cause of the error, correct it, and restart the Audit Server.

A value list cannot be used with the specified condition.

Investigate the cause of the error, correct it, and restart the Audit Server.

The filter format ID xxxxxxxx does not match a global format.

Investigate the cause of the error, correct it, and restart the Audit Server.

The subscription xxxxxxxx was deactivated because of an error.

Ensure the Audit Server is running with an ALOG defined if you wish to use destinations of type AUDIT.

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.

Correct the filter to use a value as the target of the compare.

All the files specified in the FLIST parameter were invalid and will not be use.

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

The file definition xxxxx does not have a server ID. The file definition will be discarded.

Specify the server ID for the file definition and rerun the job.

The file nnnnn is specified in both of the listed definitions. The definition zzzzz will be used for file nnnnn.

Check the parameter input, correct the error, and rerun the job as needed.

The parameter listed is improperly misplaced for database parameter(s) processing.

Check the parameter input, correct the error, and rerun the job.

The parameter DSERVERID has an invalid value specified.

Check the parameter input, correct the error, and rerun the job.

The parameter DSERVERID has an invalid value specified.

Check the parameter input, correct the error, and rerun the job.

An internal error occured while processing the ADAANP input parameters. The Register information is output in the message text.

Check the JCL and job log for other errors. Contact your Software AG representative with the information provided.

The cause is probably a misspelled keyword or file name.

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

The cause is probably a misspelled keyword or file name.

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

The cause is probably a misspelled keyword.

Check the parameter input, correct the error, and rerun the job.

The cause is probably a missing separator or a misspelled keyword.

Check the parameter input, correct the error, and rerun the job.

The cause is probably incorrect parameter input.

Check the parameter input, correct the error, and rerun the job.

The cause is probably incorrect parameter input.

Check the parameter input, supply the correct keyword in full length, and rerun the job.

The cause is probably a misspelled keyword.

Check the parameter input, correct the error, and rerun the job.

The cause is probably a misspelled keyword.

Check the parameter input, correct the error, and rerun the job.

Getmain for a specified area failed or there was insufficient storage available.

Rectify the Getmain problem and rerun the job.

The cause is probably a misspelled keyword or file name.

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

The cause is probably a misspelled keyword or file name.

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

The parameter listed is improperly misplaced for file parameter(s) processing.

Check the parameter input, correct the error, and rerun the job.

The parameter listed is improperly misplaced for global parameter(s) processing.

Check the parameter input, correct the error, and rerun the job.

The parameter listed has an invalid value specified. Only YES or NO are valid values.

Check the parameter input, correct the error, and rerun the job.

The parameter listed has an invalid value specified. Only YES or NO or FIELDS are valid values.

Check the parameter input, correct the error, and rerun the job.

The parameter listed has an invalid Adabas field name xx specified.

Check the parameter input, correct the error, and rerun the job.

The parameter FSERVERID has an invalid value specified.

Check the parameter input, correct the error, and rerun the job.

The parameter GAPWARNINCREMENT has an invalid value specified.

Check the parameter input, correct the error, and rerun the job.

The parameter GAPWARNINTERVAL has an invalid value specified.

Check the parameter input, correct the error, and rerun the job.

The parameter GAPWARNMESSAGELIMIT has an invalid value specified.

Check the parameter input, correct the error, and rerun the job.

The parameter GAPWARNPERCENT has an invalid value specified.

Check the parameter input, correct the error, and rerun the job.

The parameter FSERVERID has an invalid value specified.

Check the parameter input, correct the error, and rerun the job.

The parameter FLIST has an invalid file number specified. The range defaults to the listed values.

Check the parameter input, correct the error, and rerun the job.

The parameter FLIST is required for the file parameters definition.

Check the parameter input, correct the error, and rerun the job.

Getmain for a specified area failed or there was insufficient storage available.

Rectify the Getmain problem and rerun the job.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

Contact your local support center.