ADAF* - Adabas Replication Messages

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

Rectify the Getmain problem and rerun the job.

READONLY=YES is not allowed for an Event Replicator database.

Supply correct parameters and rerun the job.

DTP=TM is not allowed for an Event Replicator database.

Supply correct parameters and rerun the job.

The LRPL must be at least 20,000.

Supply correct parameters and rerun the job.

MODE=SINGLE is not allowed for an Event Replicator database.

Supply correct parameters and rerun the job.

Event Replicator Server module ADARPR could not be loaded.

Ensure that module ADARPR is in the ADABAS load library concatenation and retry the job.

STP=YES not allowed for an Event Replicator database.

Supply correct parameters and rerun the job.

Conflicting parameters - REPLICATION=YES not allowed for this Event Replicator Server database.

Supply correct parameters and rerun the job.

This message can have multiple texts, as listed below:

• xxxxx NT specification too low. NT must be greater than or equal to 15.

• xxxxx LU specification too low, minimum is 164000

  Note:
  This text is used when the Event Replicator Server is running with Adabas 7.4.

• xxxxx LU specification too low, minimum is 167000

  Note:
  This text is used when the Event Replicator Server is running with Adabas 8.

• xxxxx NAB specification too low, minimum is 41

In all cases, the value specified for the named parameter is too low. In some cases the minimum value is given in the message.

Increase the value of the named parameter and rerun the job.

An attempt to load the module listed in the message failed.

Ensure that the module is in the ADABAS load library concatenation and retry the job.

The cause is probably a misspelled keyword.

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

The cause is probably a misspelled keyword.

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 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, 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 JCL; correct the error and rerun the job.

A command (cc) to the target DBID/FNR (ddddd and fffff) identified in the message failed. The response code (rrr) with subcode (sssss) are also given in the message.

If the command is not an S4 command, the text "ISN iiiiiiiii" is appended to this message text, listing the ISN number.

Investigate the reason for the response code subcode on the target database and correct the problem. The command did not complete on the target database.

The cause is probably incorrect parameter input.

Check the parameter input. Supply no more than the maximum number of parameter values permitted, and rerun the job.

The nucleus has terminated with replication data outstanding for the Event Replicator database and files listed in the message.

The nucleus has terminated via a HALT command. If an Event Replicator Server is available, outstanding replication data for this nucleus has been sent to the Event Replicator Server. Check for message ADAF1Q to verify the Event Replicator Server successfully processes all previously sent replication data for this database. If an Event Replicator Server was not available at the time of the HALT, an initial-state request may be used to synchronize a file.

The Event Replicator database listed in the message has disconnected from the nucleus.

No action is required for this informational message.

The nucleus has connected to the Event Replicator database listed in the message.

No action is required for this informational message.

The nucleus has reconnected to the Event Replicator database listed in the message. This may happen if the Event Replicator Server was terminated but the nucleus remained active, and then the Event Replicator Server restarted.

No action is required for this informational message.

The nucleus is waiting for the Event Replicator database listed in the message to finish processing data. When the Event Replicator Server has completed the work, the nucleus will terminate.

Start the Event Replicator Server if it is not currently active.

The nucleus has disconnected from the Event Replicator Server listed in the message.

No action is required for this informational message.

The Event Replicator Server attempted to do a crosscheck for the database listed in the message, but received the response and subcode (rrr/sss) listed in the message during the attempt.

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

The Event Replicator database listed in the message is shutting down.

No action is required for this informational message.

The nucleus tried to communicate with the Event Replicator database listed in the message, but the Event Replicator database is not available.

Start the Event Replicator database.

The Event Replicator Server requires 32,000 bytes of storage from the Adabas work pool to run the crosscheck function.

Increase the LWP parameter setting for Adabas and retry. For more information, read about the ADARUN statement and its LWP parameter in your Adabas operations documentation.

Replication has been deactivated by the Adabas nucleus for the identified file. The reason will be one of the following:

• replication pool overflow

• request from Event Replicator Server

• request via operator command/AOS

If the deactivation reason is "replication pool overflow", consider increasing the value of the LRPL parameter. For other reasons, this message is for information only.

These messages begin when replication pool usage first exceeds the value of ADARUN parameter RPWARNPERCENT. Further messages appear at usage intervals specified by ADARUN parameter RPWARNINCREMENT.

If the usage is not anticipated, you may want to adjust ADARUN parameter LRPL to increase the size of the replication pool. Adjust ADARUN parameters RPWARNPERCENT and RPWARNINCREMENT to control when warning messages are issued.

A number of ADAF1L messages warning of a replication 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, Event Replicator Server will display the number of suppressed message lines and then start printing replication pool usage warning messages again. The number of messages issued before suppression is specified by ADARUN parameter RPWARNMESSAGELIMIT. The suppression interval is specified by ADARUN parameter RPWARNINTERVAL.

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

Event Replicator Server received a message from an input queue but could not process it because some data structure was not correctly interpreted.

<message block> gives additional information:

• URBH - The URBH message header could not be processed

• URBH - Input message truncated

• URBI - The URBI message structure could not be processed

For the memory shortage check if the LRPL needs to be increased. If the input message is truncated, increase the size of the input queue buffer parameter, IQBUFLEN. In the other cases make sure that the input requests are set up correctly.

This message may appear with multiple texts, all relating to an invalid destination setting, as described in the following table:

Make sure that the input request sets up the correct destination for response.

One or more File destination definitions are being used, but the CLOG to which the replication TLOG URBLTDOD records will be routed is not identified in the Event Replicator Server startup JCL. The File destinations are set to "Unavailable" and processing continues.

Identify the CLOG in the Event Replicator Server startup JCL and try again.

The Event Replicator Server has finished processing in-flight transactions for nuclei terminated previously via HALT.

No action is required for this informational message.

The Event Replicator Server has been terminated by a halt request. During termination processing, one or more initial-state requests were found to be active on the database or database and nucleus listed in the message. The request to the nucleus to terminate the initial-state processes failed with Adabas response code and subcode (rrrr/ssss) given in the message.

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

Errors were detected in messages from a target application on an Event Replicator Server input queue. In order to avoid flooding the console, Event Replicator Server starts suppressing messages for approximately one minute after a threshold is reached. When the suppression period has expired, Event Replicator Server will display the number of suppressed message lines and then start printing input transaction error messages again.

This message can have multiple texts, all relating to error message suppression:

• Starting message suppression

• nnnn message lines suppressed

Replication for a file was being deactivated by the Adabas nucleus. Adabas was unable to acquire sufficient resources to notify the associated Event Replicator Server.

Execution continues. This is often the result of a shortage in the replication pool. Increasing the value of the LRPL parameter may alleviate the shortage.

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

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

A replication status or prior-transaction request has an error, and a response code and subcode could not be sent via a URBS status message. The type appearing in the message identifies the request type and will be either "STAT" (replication status) or "TRAN" (prior-transaction). The destination, subscription and number are taken from the URBI for the request. The number will appear only for "TRAN" requests.

The following errors can appear in the message if the request type is either "STAT" or "TRAN":

URBIARC/ACOD/WCOD not zero
URBIRES1/URBIRES2 not zero

The following errors can appear in the message only if the request type is "STAT":

Storage shortage in RPL pool
URBIRNAM undefined/unusable
URBIDNAM and URBISNAM omitted
URBISNAM undefined/unusable
URBIDNAM undefined/unusable
No active destinations

The following errors can appear in the message only if the request type is "TRAN":

RSP0 but URBIRNAM not active
URBIRNAM is unknown
URBIDNAM is unknown
URBISNAM omitted or unknown
URBIDNAM not in URBISNAM
URBISNAM has no resend buffer
URBITRNR not in resend buffer
URBISNAM not active
Invalid transaction in buffer
No active resend destinations
URBILEND not zero
URBIDBID/URBIFNR not zero
URBIINAM not permitted

If the error indicates an RPL storage pool shortage, consider increasing the value of the LRPL parameter.

If the error indicates that an invalid transaction exists in the resend buffer, an internal error has been detected. Notify your Software AG support representative.

If the error indicates that there are no active destinations, this message is for information only.

For all other errors, correct the status request or resend the prior-transaction request.

The Event Replicator Server database listed in the message is active, but the nucleus received the response code and subcode (rrrr/ssss) listed in the message.

Investigate the response code and subcode to identify and correct the problem. For response code 22, subcode 26, ensure that you are trying to connect to another Adabas nucleus and not an Event Replicator Server and try again.

An attempt to send data to the Event Replicator Server database listed in the message failed with the response code and subcode (rrrr/ssss) listed in the message.

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

When the nucleus attempted to disconnect from the Event Replicator Server database listed in the message, the response code and subcode (rrr/sss) listed in the message were received.

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

TLOG logging has been requested, however the CLOG to which TLOG records are written is not active.

Activate the CLOG using the relevant ADARUN parameters in the Event Replicator Server.

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

No action necessary for this informational message.

A record with ISN iiiiiiiiii for destination dddddddd DBID xxxxx FNR fffff with the action (Update, Insert, Delete, or Replace (for Initial State) received Rsp rrrrr Subcode sssss

Investigate the reason for the error and correct. The command did not complete on the target.

The parameter MAXOUTPUTSIZE has an incorrect value specified.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying a DESTINATION NAME parameter, the DASUBSCRIPTION keyword is only valid for DTYPE=ADABAS.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The parameter input has multiple function keywords within a statement, and only one is executed.

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

After reading the parameter input, there has been a close error for DDKARTE.

Investigate the cause of the error; correct it, and rerun the job.

A GETMAIN has failed to acquire memory that the Event Replicator Server requires.

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

The NAME parameter is missing from the Event Replicator Server definition being processed.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying a DESTINATION parameter, there must be a DTYPE equal to ADABAS, ETBROKER, FILE, MQSERIES, or NULL.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The parameter input has DAIFILE specified, and the DTYPE is not equal to ADABAS.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The nucleus has connected to the Event Replicator Server. The DBID or DBID-nucleus ID (dbid/nucid) combination as well as the Adabas and Event Replicator versions (ADAvrm/ARFvrm) 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 nucleus has disconnected from the Event Replicator Server. The DBID or DBID-nucleus ID combination is shown in the message.

No action is required for this informational message.

A Event Replicator Server (the ID is given in the message) has RPLPARMS set to NONE, which will reject any communication from other ADABAS nuclei. The DBID or DBID-nucleus ID combination is shown in the message. This message is output only as an informational message in the Event Replicator Server syslog.

If the Event Replicator Server should be communicating with other ADABAS nuclei, correct the RPLPARMS parameter and recycle the Event Replicator Server. Otherwise, no action is required for this informational message.

These are informational messages about Event Replicator Server crosscheck function processing.

No action is required for these informational messages.

The Event Replicator 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 Event Replicator Server is disconnecting from a noncluster Adabas nucleus. The second instance of this message occurs when the Event Replicator 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 Event Replicator Server disconnecting.

No action is required for this informational message.

The Event Replicator Server has disconnected from the database or nucleus listed in the message.

This message normally follows message ADAF2E and indicates that all replication data for the database has been processed when the Event Replicator Server was terminated by ADAEND. If the Event Replicator 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 Event Replicator Server has disconnected from a noncluster Adabas nucleus. The second instance of this message occurs when the Event Replicator 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 Event Replicator Server attempted to communicate with a database defined via a subscription but found the database is running with a REPLICATION=NO setting.

Execution continues. No replication will occur for the database.

The Event Replicator Server is handling a full replication buffer by removing unprocessed data from the input queue to free storage

Execution continues. The indicated database ID (dbid) will attempt to resend the discarded data. Increasing the value of the LRPL parameter may alleviate the shortage.

The nucleus listed in the message is not currently active.

Start the database.

An Adabas nucleus for the database identified in the message did not recognize some replicated transactions that the Event Replicator Server reported as successfully completed. The number of replicated transactions is also listed in the message.

Generally, once the Event Replicator for Adabas has completed the successful processing of a replicated transaction, it reports the completion to Adabas so that Adabas can release the resources (space in its replication pool) associated with the transaction. In this case, Adabas could not identify the transactions specified by the Event Replicator for Adabas and ignored them.

Take note of any unusual events surrounding the message, keep the job protocols of Adabas database and the Event Replicator Server database, and contact your Software AG technical support representative.

A resource was being deactivated, reactivated, or refreshed by the Event Replicator Server. The Event Replicator Server was unable to acquire sufficient resources to notify the affected destination.

Execution continues. This is often the result of a shortage in the replication pool. Increasing the value of the LRPL parameter may alleviate the shortage.

The replication status for the identified file has changed on Event Replicator Server. The deactivation reason will be one of the following:

• database deactivation

• end of replay process

• file deactivation

• format buffer validation failure

• last destination deactivation

• last subscription deactivation

• permanent error in subscription

• replication pool overflow

• request from ADABAS (RDITYPE=Z)

• request from target application

• request via operator command/AOS

• RPLREFRESH request

• SLOG-related error

• SLOG system file full

• suspension of SLOG input

The reactivation reason will be one of the following:

• request from target application

• request via operator command/AOS

• request from ADABAS (RDITYPE=Y)

• reactivation of destination

• reactivation of subscription

• reactivation of database

• begin of replay process

If the deactivation reason is "replication pool overflow", consider increasing the value of the LRPL parameter. For other reasons, this message is for information only.

The replication status for the identified subscription has changed on Event Replicator Server. See the reason descriptions described for message ADAF2L.

If the deactivation reason is "replication pool overflow", consider increasing the value of the LRPL parameter. For other reasons this message is for information only.

The replication status for the identified destination has changed on Event Replicator Server. See the reason descriptions described for message ADAF2L.

If the deactivation reason is "replication pool overflow", consider increasing the value of the LRPL parameter. For other reasons this message is for information only.

Replication has been reactivated by the Adabas nucleus for the identified file. The reason will be one of the following:

• request from Event Replicator Server

• request via operator command/AOS

• initial-state request

No action is required. This message is for information only.

The replication status for the identified database has changed on Event Replicator Server. See the reason descriptions described for message ADAF2L.

If the deactivation reason is "replication pool overflow", consider increasing the value of the LRPL parameter. For other reasons, this message is for information only.

The database has terminated, but the Event Replicator Server still has active transactions for the database. Execution continues.

Check for Event Replicator Server message ADAF1Q to verify that the Event Replicator Server successfully processes all replication data received from this database.

ADAEND has been issued to the Event Replicator Server with transactions still in progress.

The Event Replicator Server will terminate only after all the transactions that are still in progress have completed.

The files listed in the message have replication turned on, but there are no matching subscriptions in the Event Replicator Server database.

Either add a subscription for the file in the Event Replicator Server database or turn off replication for the files.

An error occurred while attempting to read the Replicator system file. The Event Replicator Server database ID, response code (rc), and command code (cc) are given in the message.

Review the response code to determine why the Replicator 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 files listed in the message have a subscription in the Event Replicator Server database, but replication is not turned on for the files.

Either turn replication on for the files or remove the subscriptions from the Event Replicator Server database..

A resource was being deactivated or reactivated. Event Replicator Server attempted to notify the Adabas nucleus. The command received the unexpected response code and subcode.

If the reason for the response code is not clear, contact your DBA, system support personnel, or Software AG technical support.

The Event Replicator Server attempted to connect to 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.

An attempt to send information about completed transactions from the Event Replicator Server to the Adabas listed in the message (dbid) failed with the response code and subcode (rrrr/ssss) listed in the message.

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

The Event Replicator 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.

An operator command to dynamically alter the level of transaction logging was entered incorrectly. This error is produced because the name of the transaction logging event or the transaction logging level specified in the command were not valid. The event name specified is listed in the message.

Review and correct the command specifications and then rerun it. Valid transaction logging event names and levels are described in TLOG Command.

The DAIFILE is required when DTYPE=ADABAS is specified.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The DAIFILE parameter requires the DAIDBID, DATDBID, and DATFILE parameters be specified as well.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying a DESTINATION, with DTYPE=ETBBROKER, then DETBBROKERID or ETBBROKERID is required.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying a DESTINATION, with DTYPE=MQSERIES, then DMQQMGRNAME or MQQMGRNAME is required.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying a GFORMAT NAME, the GFB parameter is required.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying IQUEUE NAME, then IQTYPE must be ETBROKER or MQSERIES.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying IQUEUE NAME, and IQTYPE=MQSERIES, then IQMQQMGRNAME or MQQMGRNAME is required.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying IQUEUE NAME, and IQTYPE=ETBROKER, then IQETBBROKERID or ETBBROKERID is required.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The Event Replicator Server database is not running with UES option, and it is required for certain parameters, i.e., SARC.

Examine and correct the parameter input or the Event Replicator Server database.

When specifying SUBSCRIPTION, then SDESTINATION or SIDESTINATION is required.

Check the parameter input, correct the error, and restart the Event Replicator Server.

A check was performed on the version of module ADARPD. The version of module ADARPD is incompatible with this Event Replicator Server.

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

The DBID value specified for the given ‘parameter keyword’ exceeds the maximum of 65535.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The system file contains invalid data for destination dest in subscription sub. Only "Y" or "N" are permitted.

Correct the input and restart the Event Replicator Server.

The value entered for the FCOND parameter as part of a filter definition is incorrect. Valid values are listed in the message.

Correct the FCOND parameter value.

The value entered for either the MU or PE value of a filter definition is incorrect. Valid values must range from "1" through "191".

Correct the MU or PE parameter value.

The value entered for either the FSIMAGE or FTIMAGE parameters of a filter definition are incorrect. Valid values are "AI" or "BI".

Correct the FSIMAGE or FTIMAGE parameter value. Descriptions of these parameters are provided in FILTER Settings.

The value entered for the FRECORDS parameter of a filter definition is incorrect. Valid values are "INCLUDE" or "EXCLUDE".

Correct the FRECORDS parameter value. A description of this parameters is provided in FILTER Settings.

The values specified for the TLMAX and TLRESTART parameters are either invalid or are not consistent with each other. Valid values for TLMAX range from 1 through 100, while the TLRESTART setting must be less than the TLMAX setting.

Correct the TLMAX and TLRESTART parameter values so they are valid and consistent. Descriptions of these parameters are provided in Transaction Log (TLOG) Settings.

A parameter that sets the level of transaction logging for a transaction logging event was entered incorrectly. The name of the transaction logging event with the invalid value is listed in the message.

Correct the value specified for the transaction logging event. Valid transaction logging event names and values are described in Transaction Log (TLOG) Settings.

The FTIMAGE, FTPE, FTBEGIN, FTLENGTH, or FTMU parameter was specified without an associated FTARGET parameter in a filter definition.

Provide an FTARGET parameter value. Descriptions of these parameters are provided in FILTER Settings.

A FILTER parameter was specified, but without either the FTARGET or FLIST parameters. Either FTARGET or FLIST is required, but both may not be specified.

Provide either an FTARGET parameter value or an FLIST parameter value. Descriptions of these parameters are provided in FILTER Settings.

An attempt was made to specify the FFIELD parameter separately from a FILTER parameter. FFIELD parameters are not valid outside of FILTER parameters.

Correct the syntax. Descriptions of these parameters are provided in FILTER Settings.

A filter definition (FILTER parameter) was specified, but without at least one filter condition (FFIELD parameter).

Add an FFIELD parameter to the filter definition. Descriptions of these parameters are provided in FILTER Settings.

An incorrect value was specified for the MAXFFIELDS parameter. Valid values are positive integers.

Correct the MAXFFIELDS parameter setting. Read MAXFFIELDS (Maximum Number of FFIELDs) Setting for more information.

An incorrect value was specified for the MAXFLISTSIZE parameter. Valid values range from "1" through "32K".

Correct the MAXFLISTSIZE parameter setting. Read MAXFLISTSIZE (Maximum FLIST Size) Setting for more information.

The transaction filter definition named in the message is specified to be used by an SFILE definition, but no filter definition exists by that name.

Specify the name of a defined filter definition in SFFILTER parameter of the SFILE definition. SFILE definition parameters are described in SUBSCRIPTION Settings and filter definition parameters are described in FILTER Settings.

The data in the Replicator system file indicates that the value associated with the event named in the message for the subscription named in the message is invalid. It must be in the range indicated. This error is caused by invalid data on the Replicator system file.

Contact your Software AG technical support representative for assistance.

The data in the Replicator system file indicates that the value associated with event named in the message for the destination named in the message is invalid. It must be in the range indicated. This error is caused by invalid data on the Replicator system file.

Contact your Software AG technical support representative for assistance.

The DMQCCSID destination parameter is specified for a WebSphere MQ destination definition and no DCLASS or DEXIT parameter has been specified for that destination.

Either add a DCLASS or DEXIT parameter to the WebSphere MQ destination definition or change the DMQCCSID parameter setting to zero.

The keyword SFREPLICATENOTCHANGED was specified for the subscription, database, and file named in the message, but the BI and AI format buffers provided are not identical.

Correct the definition so that the BI and AI format buffers are identical. SFILE definition parameters are described in SUBSCRIPTION Settings.

Invalid data was found in the Replicator system file associated with the filter and field named in the message. This error is caused by invalid data in the Replicator system file.

Contact your Software AG technical support representative for assistance.

There are invalid multiple global setting records in the Replicator system file.

Contact your Software AG technical support representative for assistance.

An attempt was made to specify a retry interval or retry count in a File or Null destination. The DRETRYINTERVAL and DRETRYCOUNT parameters are only valid Adabas, webMethods EntireX, or WebSphere MQ destination definitions.

Remove the DRETRYINTERVAL or DRETRYCOUNT parameters from the File or Null destination definitions.

One of two basic message texts may appear for this message ID:

See the table above for the appropriate action to take, based on the message text that appears with this message ID.

One of two basic message texts may appear for this message ID:

See the table above for the appropriate action to take, based on the message text that appears with this message ID.

An operator command to dynamically alter the level of transaction logging was entered incorrectly. This error is produced because a resource name specified in the command was not valid. The invalid resource type (resource) and its name (name) are given in the message.

Review and correct the command specifications and then rerun it. Valid transaction logging event names and levels are described in TLOG Command.

When specifying SUBSCRIPTION, then sub-parameters SFDBID or DBID are required.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying SUBSCRIPTION, then at least one sub-parameters SFILE is required.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying SUBSCRIPTION, then sub-parameters SFBAI and SGFORMATAI are mutually exclusive. The subscription name, DBID, and file number are given in the message.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying SUBSCRIPTION, then sub-parameters SFBBI and SGFORMATBI are mutually exclusive. The subscription name, DBID, and file number are given in the message.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying SUBSCRIPTION, then sub-parameters SFBKEY and SGFORMATKEY are mutually exclusive. The subscription name, DBID, and file number are given in the message.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying SUBTASKS, the maximum value is 15.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying a parameter, a keyword has been improperly specified and is invalid.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying SUBSCRIPTION, then sub-parameters SFBAI or SGFORMATAI are required. The subscription name, DBID, and file number are given in the message.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The parameter keyword listed in the message only supports YES, NO, or blank, and the input is not matching that.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The parameter SFILE is positioned incorrectly, and not associated with a SUBSCRIPTION.

Check the parameter input, correct the error, and restart the Event Replicator Server.

While performing the session autorestart procedure to recover from the abnormal end of an Adabas nucleus, Adabas found replication data on its Work data set. Adabas is now going to try to recover any replication data that may need to be sent or resent to the Event Replicator Server(s). This message and action occurs only if the ADARUN parameter REPLICATION=YES was specified for both the Adabas nucleus that failed and the nucleus that is performing the session autorestart.

Note that replication data from initial-state processes that were active at the time of the failure is not recovered automatically.

If initial-state processes were active at the time of the failure, check whether any of them need to be rerun. If so, restart them.

During session autorestart. Adabas recovered replication data from the Work data set. After connecting to the Event Replicator Server, Adabas reports:

• how many replicated transactions were recovered that had not been confirmed as successfully processed by the Event Replicator Server before the abnormal end of the previous Adabas session (count1),

• how many of those transactions were confirmed by the Event Replicator Server when Adabas reconnected after the session autorestart (count2),

• how many of those transactions the Event Replicator Server fully received from the previous session (count3), and

• how many recovered transactions Adabas is going to send (or resend) to the Event Replicator Server (count4).

If files in the database are replicated via multiple Event Replicator Servers, Adabas prints one set of these messages for each Event Replicator Server.

No action is necessary for this informational message.

During session autorestart, Adabas detected that one or more Event Replicator Servers had not confirmed the complete processing of one or more older transactions that had already been overwritten on the Work data set in the previous session. It reports which Event Replicator Servers and which replicated files are involved.

Note:
This message is the forerunner of the report of the possible loss of replication data. It indicates that Adabas is unable to recover this replication data because it was already overwritten on the Work data set. However, if the Event Replicator Servers remained active across the outage of Adabas, there is a good chance that the replication data in question is still held or has already been successfully processed by the Event Replicator Servers.

Do not take action to recover from the loss of replication data based on this message alone. The final outcome is reported subsequently in messages ADAF4D or ADAF4E.

If there was no backup of replication data being processed by the Event Replicator Servers at the time of the Adabas failure, consider increasing the value of the ADARUN LP parameter, so that replication data can be held longer on the Work data set.

Replication data that was overwritten on the Work data set, as reported in an earlier ADAF4C message, has not been processed by the Event Replicator Server nor is it still available on the Event Replicator Server side. Adabas and the Event Replicator Server are unable to recover this replication data.

The message indicates which Event Replicator Server and files may be affected, as well as the time period of the missing replication data.

If files in the database are replicated via multiple Event Replicator Servers, Adabas prints one set of these messages for each Event Replicator Server that is implicated in the probable loss of replication data.

Take actions to bring the original data and its replicas back in sync. The extent to which this is necessary depends on the requirements of the application using the replication system.

Replication data that was overwritten on the Work data set, as reported in an earlier ADAF4C message, was still available on the Event Replicator Server side and has been successfully processed by the Event Replicator Server.

If the database contains files being replicated via multiple Event Replicator Servers, Adabas prints one set of these messages for each Event Replicator Server that is not implicated in the loss of replication data.

No action is required for this informational message. The original data and its replicas are in sync even though not all of the replication data could be recovered from the Work data set.

During session autorestart, Adabas found that all replicated transactions from the previous session had already been successfully processed by the Event Replicator Server before the previous session terminated abnormally. There was no replication data that needed to be recovered.

No action required for this informational message. The original data and its replicas are in sync.

TLOG logging processing has used more of the replication pool than the percentage assigned it by the TLMAX.

Determine why TLOG activity is exceeding replication pool limits. Consider adjusting the size of the replication pool or adjusting the TLMAX, as appropriate.

TLOG records have been removed from the replication pool because the replication pool percentage defined by the TLMAX was exceeded. TLOG usage has now fallen below the percentage specified in the TLRESTART and so TLOG processing has resumed.

No action is required for this informational message.

TLOG records have been deleted from the replication pool, due to a replication pool full condition. The number of records that have been deleted is given in the message.

No action is required for this informational message.

An instance of the ADARPL utility has established a session with the Event Replicator 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 ADARPL utility has terminated its session with the Event Replicator Server for the database identified in the message. The token number listed in the message identifies the terminating session. The total number of transactions processed by the ADARPL utility is also given in the message.

No action is required for this informational message.

After an Adabas failure and session autorestart, replication data was recovered for which a matching FDT was no longer available. The FDT had been changed or deleted by a utility operation. Adabas suppressed the record images of the replicated records, because without a matching FDT, the Event Replicator Server could not process them.

This message displays how many record images were suppressed for which files. For each suppressed record image, the Event Replicator Server delivers the replicated record with response code 131, subcode 60 in fields URBRRSP and URBRSUBC of the URBR. Unless these images had already been delivered earlier to the target application, they are lost.

Use application-specific means to determine whether updates to replicated records have been lost and to get the related original data and their replicas back in sync.

One of the following occurred:

• An RPLCLEANUP=ALL operator command was entered, but there were no ADARPL replay operations in progress.

• An RPLCLEANUP=token operator command was entered, but there was no ADARPL replay operation in progress with the specified token.

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

A new RPLREFRESH request has been issued but a previous RPLREFRESH command is still being processed.

Wait for the previous RPLREFRESH command to be processed and reenter the command.

A RPLREFRESH,ABORT command has been issued but no refresh is in progress.

No action is required for this informational message.

An RPLREFRESH,ABORT command has been issued and has been either accepted or rejected (when another RPLREFRESH,ABORT is already scheduled).

No action is required for this informational message.

A replicated transaction was received from Event Replicator Server instance dbid for subscription sub on input queue iqueue, but no subscription definition was found. When unsolicited replication data is received on an input queue, the Event Replicator Server closes the input queue for further processing and message ADAF8G is produced.

Add appropriate subscription, SFILE, and, if necessary, destination definitions to specify how the replication data should be processed. When appropriate definitions have been specified, try again.

An out-of-sequence replicated transaction was received on the input queue iqueue. When this error occurs, the Event Replicator Server closes the input queue for further processing. Message ADAF8G will follow this message to indicate this action.

The exact cause of the error should be determined and appropriate actions should be taken before you try again. Once you have resolved the problem, resume replication processing on the input queue by restarting the Event Replicator Server session from the failing point, using an initial-state definition if required.

A truncated replicated transaction was received on the input queue iqueue. When this error occurs, the Event Replicator Server closes the input queue for further processing. Message ADAF8G will follow this message to indicate this action

Either the IQBUFLEN parameter on the local Event Replicator Server node or the MAXOUTPUTSIZE parameter on the remote Event Replicator Server node needs to be increased and replication processing restarted.

When a request to allocate memory on behalf of an input queue fails because the replication pool is full, the input queue will be closed. The message indicates which input queue has been closed as a result of the over flow. If the replication pool has been allocated with a large enough size, problems like this can happen if there is data backing up in the Event Replicator Server address space.

Investigate why the replication pool has filled up and take appropriate action to avoid this happening into the future.

Unexpected or bad data was received on an input queue so the input queue is closed as the Event Replicator Server is not in a position to deal with the data. The bad-input-data listed in the message can be any of the following:

• URBCLEN is invalid

• No prior transaction for URBC

• URBCSNAM is invalid

• URBCTSNR is invalid

• URBCRSNR is invalid

• URBCDSNR is invalid

• URBT/partial previous trans.

• Insufficient buffer for URBT

• URBTLEN is invalid

• Insufficient buffer for URB*

• Eye-catcher not URBD/URBE/URBR

• Insufficient buffer for URBE

• URBELEN is invalid

• Insufficient buffer after URBE

• URBE not followed by URBT

• Insufficient buffer for URBD

• URBDLENH is invalid

• Insufficient buffer for image

• No record for URBD

• URBDTYP is invalid

• Before image already received

• After image already received

• Insufficient buffer for URBR

• URBRLEN is invalid

• URBRTYP is invalid

To review the Event Replicator DSECTs and the definitions of the DSECT fields listed in thebad-input-data above, read Event Replicator for Adabas Programmer's Reference.

This message is normally the result of a payload being received on an input queue that is not from another Event Replicator Server. It may be another application sending spurious data to a queue which is then picked up by the Event Replicator Server.

To determine what the payload looks like, turn on transaction logging (TLOGing) for "request received" processing using the TLREQRECV system parameter. This will cause the message text to be written to the TLOG. The TLOG information can subsequently be printed using the ADARPP utility. Use the message contents to determine where the spurious data originated. If not, use webMethods EntireX tracing or WebSphere MQ facilities to determine what application is sending these messages to the Event Replicator Server.

For more information about activating transaction logging for the Event Replicator Server, read TLREQRECV Parameter. For information about the ADARPP utility, read ADARPP Utility: Print TLOG Records .

A cluster peer nucleus encountered an error when it attempted to notify the driver nucleus of an "activate file" request.

Reissue the file activation request.

A V1 command to the Event Replicator Server identified in the message (dbid) returned the response code (rsp) and subcode (subcode) given in the message.

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

The parameter GFORMAT NAME=ggggggg exceeds a 7 byte length restriction.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying additional parameter input for the subscription named in the message, a destination is referenced which has not been defined in the Replicator system file or in a DESTINATION initialization parameter.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying additional parameter input for SUBSCRIPTION NAME=ssssssss, a global format is referenced which does not have a corresponding GFORMAT NAME=ggggggg parameter.

Check the parameter input, correct the error, and restart the Event Replicator Server.

This message number is associated with several possible message texts. The following table describes all of the possibilities.

See accompanying messages in DDPRINT for more information.

When specifying additional parameter input for the subscription (subsname), database (dbid), and file (nn) listed in the message, a global format buffer (gfb) is referenced in which the format buffer is for KEY, and is incorrect.

Check the parameter input, correct the error, and restart the Event Replicator Server.

When specifying additional parameter input for the subscription (subsname), database (dbid), and file (nn) listed in the message, a global format buffer (gfb) is referenced in which the format buffer is not for KEY, and is incorrect.

Check the parameter input, correct the error, and restart the Event Replicator Server.

A load was issued for the exit program named in parameter SFSEXIT=eeeeeeee, and it was unsuccessful.

Investigate the cause of the error; correct it and restart the Event Replicator Server.

An Adabas destination is used by more than one subscription. Only one subscription may send data to an Adabas destination.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The Event Replicator Server requested the database listed in the message activate or deactivate the file listed in the message. This request failed due to one of the following reasons:

• The file is an invalid file.

• The file has not been defined for replication

• The file has not been defined for replication for this Event Replicator Server

The response code and subcode (rrrrr / sssss) are given in the message.

Check if the file is correctly defined for replication to this Event Replicator Server. If "invalid file" is indicated, check if the Event Replicator Server subscription references a file number beyond MAXFILES for the database. If a response code is given, investigate the response code and subcode to identify and correct the problem.

The Event Replicator Server successfully processed all replicated transactions.

No action is necessary for this informational message.

Following an event that may cause the loss of replication data (for example, the deactivation of a destination), this message indicates that the Event Replicator server has been unable to track which replicated transactions were processed successfully before the event. This may happen, for example, if the Event Replicator server has not had contact with Adabas between the start of the Event Replicator server and the mentioned event.

If replication data was lost due to the event for which this message was issued, replay the records from the PLOG data sets. During replay processing, be careful to specify a FROMDATE and FROMTIME that covers all replicated transactions that were lost.

Following an event that may cause the loss of replication data (for example, the deactivation of a destination), this message reports the latest known time for which replicated data was processed successfully; in other words any replicated transaction that ended before this time was not lost due to this event. There may or may not be replicated transactions that ended at or after this time which have been lost.

If replication data was lost due to the event for which this message was issued and the lost data is to be replayed from the PLOG data sets, you could use the date and time listed in this message for the FROMDATE and FROMTIME of the replay process.

A replay process was started with the token shown in the message.

No action is required for this informational message.

The replay process referred to in the preceding ADAF4L message ended successfully. The Event Replicator Server returns response code 0 to the disconnecting ADARPL

No action is required for this informational message.

While the replay process referred to in the previous ADAF4L message was running (in synchronized mode), Adabas sent more replication data than the Event Replicator Server was able to hold in its replication pool until the replay process is finished. The Event Replicator Server dropped the new replication data from Adabas and the replay process (ADARPL) proceeded (in replay-only mode).

Run a new replay process for the same subscriptions and destinations to replay the lost replication data that Adabas produced during the first replay process.

The replay process referred to in the preceding ADAF4L message has encountered an error. The response code and subcode shown in the message is returned by Event Replicator Server to ADARPL.

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

When the replay process (in synchronized mode) whose token is shown in the message ended, the Event Replicator Server started delogging and processing the replication data that was sent by Adabas but suspended by the Event Replicator Server while the replay process was running.

No action is required for this informational message.

The Event Replicator Server completed delogging and processing the transactions from Event Replicator Server that it had suspended while a synchronized replay completed. The token for the completed replay process is listed in the message.

No action is required for this informational message.

This informational message indicates that processing is waiting for the completion of all updates to the file referenced in the message.

No action is required for this informational message.

All update transactions active have completed successfully when the file referenced in the message was activated.

No action is required for this informational message.

This is an internal message that occurs as a result of activating the file named in the message.

No action is required for this informational message.

The initial-state definition named in the message has no associated subscriptions, destinations or files.

Correct the initial-state definition and restart the Event Replicator Server.

For DESTINATION NAME=dddddddd, the specified DAIFILE=f#### and DAIDBID=d#### parameters do not have a corresponding SFILE and SFDBID combination in the specified DASUBSCRIPTION=ssssssss.

Check the parameter input, correct the error, and restart the Event Replicator Server.

An attempt was made to define a filter with the name specified in the message more than once. The specified name is not unique.

Change one of the duplicate filter definition names to a different, unique, name.

When a non-zero return code occurs in the execution of ADARPD, then any exits loaded during this execution will be deleted. There was a failure in deleting the exit program eeeeeeee.

Investigate the cause of the error; correct it and restart the Event Replicator Server.

The resend buffer definition name shown in the message is not valid. The name must:

• Be comprised of one to eight uppercase, alphanumeric, and national characters (@,$,#). If the name is less than eight characters, it is automatically padded on the right with blanks.

• Be enclosed in single quotes (') if any national characters are used.

• Not begin with a numeric character or a blank.

• Have no embedded blanks.

• Not begin with the letters "SYS".

Correct the name and try again.

Duplicate names for global format definitions have been found.

Check the parameter input, correct the error, and restart the Event Replicator Server.

There have been duplicate IQUEUE NAME=name statements found.

Check the parameter input, correct the error, and restart the Event Replicator Server.

There have been duplicate DESTINATION NAME=dddddddd found.

Check the parameter input, correct the error, and restart the Event Replicator Server.

In DESTINATION NAME=dddddddd, there are duplicate DAIFILE=f#### and DAIDBID=d#### found..

Check the parameter input, correct the error, and restart the Event Replicator Server.

There have been duplicate SUBSCRIPTION NAME=ssssssss found.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The resend buffer name specified in the SRESENDBUFFER parameter has not been defined.

Either correct the SRESENDBUFFER parameter specification or create a corresponding RESENDBUFFER definition for the resend buffer. Then restart the Event Replicator Server.

An error occurred when reading the Replicator system file for the input queue named in the message.

The Adabas Event Replicator Subsystem can be used to delete and correct the information. If necessary, notify support with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

An error occurred when reading the Replicator system file for the ADABAS destination named in the message.

The Adabas Event Replicator Subsystem can be used to delete and correct the information. If necessary, notify support with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

An error occurred when reading the Replicator system file for the destination named in the message.

The Adabas Event Replicator Subsystem can be used to delete and correct the information. If necessary, notify support with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

An error occurred when reading the Replicator system file for the initial-state definition named in the message.

The Adabas Event Replicator Subsystem can be used to delete and correct the information. If necessary, notify support with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

An error occurred when reading the Replicator system file for the subscription named in the message. The format buffer for this subscription had an incorrect length. The format buffer item is substituted in the message for fmtbuffertype. Possible values are:

• format buffer before image

• format buffer after image

• format buffer key

The Adabas Event Replicator Subsystem can be used to delete and correct the information. If necessary, notify support with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

An error occurred when reading the Replicator system file for the subscription named in the message. An internal structure was found to be invalid.

The Adabas Event Replicator Subsystem can be used to delete and correct the information. If necessary, notify support with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

An error occurred when reading the Replicator system file for the initial-state definition named in the message. The selection criteria has an invalid length.

The Adabas Event Replicator Subsystem can be used to delete and correct the information. If necessary, notify support with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

An error occurred when reading the Replicator system file for the global format definition named in the message. The global format buffer has not been correctly generated.

Regenerate the global format buffer using the Adabas Event Replicator Subsystem or Event Replicator Administration. If the problem persists, contact your Software AG customer support representative with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

An error occurred when reading the Replicator system file for the subscription named in the message

The Adabas Event Replicator Subsystem can be used to delete and correct the information. If necessary, notify support with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

A Event Replicator Server database has ADARUN RPLPARMS=FILE or ADARUN RPLPARMS=BOTH specified but the Replicator file does not exist.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The value of the DACTIVE subparameter must be either "YES" or "NO". DACTIVE is a parameter of the DESTINATION initialization parameter.

Check the parameter input, supply a valid value, and restart the Event Replicator Server.

The value of the SACTIVE subparameter must be either "YES" or "NO". SACTIVE is a parameter of the SUBSCRIPTION initialization parameter.

Check the parameter input, supply a valid value, and restart the Event Replicator Server.

The value of the IRMSGLIMIT initialization parameter must be between 3 and 2, 147,483,647.

Check the parameter input, supply a valid value, and restart the Event Replicator Server.

Valid values for the IRMSGINTERVAL parameter must be between 1 and 2,147,483,647.

Check the parameter input; supply a correct value, and restart the Event Replicator Server.

Valid values for the SINCREMENTIS parameter are "YES" or "NO".

Check the parameter input; supply a correct value, and restart the Event Replicator Server.

Valid values for the IMAXREQ parameter must be between 1 and 2,147,483,647

Check the parameter input; supply a correct value, and restart the Event Replicator Server.

An invalid value was specified for the DLOG subparameter of the DESTINATION NAME parameter. Valid values are "YES" or "NO".

Check the parameter input; supply a correct value, and restart the Event Replicator Server.

An invalid value was specified for the VERIFYMODE parameter in the DDKARTE statements of the Event Replicator Server startup job or for the Verify Mode global value setting in the Replicator system file.

Valid values for the VERIFYMODE parameter are YES or NO, with a default of NO. Valid values for the Verify Mode global value setting are Y or N, with a default of N.

Correct the VERIFYMODE parameter setting or the Verify Mode global value setting, as appropriate for your Event Replicator for Adabas implementation, and try again.

An invalid value has been specified for the FBVALIDATION parameter or in the Format Buffer Validation field.

Correct the input value and restart the Event Replicator Server.

An invalid value was specified for the DBCONNECT parameter.

Specify either "YES" or "NO" as a value for the DBCONNECT parameter or allow DBCONNECT to take the default value of "YES".

You must specify values for both the DATABASE DBCONNECT and ID parameters.

Correct the input values and restart the Event Replicator Server.

Database dbid has been specified more than once either in the DDKARTE input or via one of the online applications in the Replicator system file.

Remove all but one of the definitions for the database and restart the Event Replicator Server.

An error occurred when reading the Replicator system file for the global format buffer definition named in the message (gfb). The global format buffer has not been correctly generated. Possible errors (error) listed in the message are:

• has invalid SubType

• has invalid Header

• Invalid Field type

• FT Buffer too small

Regenerate the global format buffer using the Adabas Event Replicator Subsystem or Event Replicator Administration. If the problem persists, contact your Software AG customer support representative with the information contained in the message. A copy of the Replicator system file may be needed for diagnosis.

This informational message lists information returned from the Event Replicator Server.

No action is necessary for this informational message. Review other associated messages to see if an error occurred.

In SUBSCRIPTION NAME=ssssssss, there are duplicate SFDBID=d#### and SFILE=f#### found.

Check the parameter input, correct the error, and restart the Event Replicator Server.

In SUBSCRIPTION NAME=ssssssss, there is an SDESTINATION='NONE'. "NONE" is a reserved keyword for SIDESTINATION.

Check the parameter input, correct the error, and restart the Event Replicator Server.

In SUBSCRIPTION NAME=ssssssss, there is an SDESTINATION specifying duplicate destinations of sdsdsdsd.

Check the parameter input, correct the error, and restart the Event Replicator Server.

In SUBSCRIPTION NAME=ssssssss, there is an SIDESTINATION specifying duplicate destinations of sisisisi.

Check the parameter input, correct the error, and restart the Event Replicator Server.

In DESTINATION NAME=dddddddd, the DBID/FILE is matching between Input DBID/FILE and Target DBID/FILE.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The parameter SARC has a value not between 0 and 11.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The parameter SIDESTINATION has both NONE and destination names specified.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The list of subscriptions specified in ISUBSCRIPTION parameter or list of destination specified in IDESTINATION parameter is not unique.

Check the parameter input, correct the error, and restart the Event Replicator Server.

IFILE parameter specified without INITIALSTATE keyword.

Check the parameter input, correct the error, and restart the Event Replicator Server.

Both ISNLIST and SELCRIT parameters specified.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The ISNLIST, SELCRIT and IDBID parameters can be specified only with IFILE parameters.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The SELCRIT parameter expression is illegal.

Check the parameter input, correct the error, and restart the Event Replicator Server.

The resend buffer name provided in the RESENDBUFFER parameter has been defined previously. The names must be unique.

Check the parameter input, correct the error, and restart the Event Replicator Server.

Event Replicator for Adabas is running in verify mode, so all destinations are changed to null-type destinations.

This message is generated for every destination that is changed to DTYPE=NULL when VERIFYMODE=YES is specified.

No action is required for this informational message.

A decompression failure occurred during the subscription phase of Event Replicator for Adabas processing. This failure is due to faulty format buffer or key data specified in a subscription definition.

Correct the format buffer or key data and try again.

Decompression during the subscription phase of Event Replicator for Adabas processing was successful; there were no errors.

This message is generated when Event Replicator for Adabas is running in verify mode and decompression is successful in the subscription phase.

No action is required for this informational message.

The value listed in the message does not obey the rules and restrictions governing the use of A() or X() notation as part of FLIST data. For more information, please read Rules for Writing Filter Conditions.

Check the FLIST input, correct the error, and restart the Event Replicator Server.

The list given in the message does not obey the rules and restrictions governing the use of comma characters as part of FLIST data. For more information, please read Rules for Writing Filter Conditions.

Check the FLIST input, correct the error, and restart the Event Replicator Server.

The value listed in the message does not obey the rules and restrictions governing the use of wildcard characters as part of FLIST data. For more information, please read Rules for Writing Filter Conditions.

Check the FLIST input, correct the error, and restart the Event Replicator Server.

The value listed in the message expects to use X() notation but the data between the parentheses does not represent valid hexadecimal data.

Check the FLIST input, correct the error, and restart the Event Replicator Server.

The filter identified by the filter, group and condition listed in the message specifies FLIST data which cannot be evaluated against the FCOND operation specified. For the correct usage, please read Rules for Writing Filter Conditions.

Modify the FLIST input or the FCOND parameter to correct the error. Then restart the Event Replicator Server.

The parameter SELCRIT contains only blanks.

Check the parameter input, correct the error, and restart the Event Replicator Server.

An invalid value was specified for the SDEACTIVATE parameter.

Correct the value and try again.

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.

The initial-state database ID and file number are not unique for the initial-state definition, although they must be.

Correct the initial-state definition so that is includes unique database ID and file number combinations.

An attempt was made to turn on utility replication for a file (DAREPLICATEUTI) in an Adabas destination, without also turning on utility replication for the Adabas destination in general.

Correct the parameter input and restart the Event Replicator Server.

An invalid value was specified for the DREPLICATEUTI parameter. Valid values are "YES" or "NO".

Correct the parameter input and restart the Event Replicator Server.

The initial-state definition named in the message is invalid because the destination specified in the IDESTINATION parameter is not defined in the Replication system file or by a DESTINATION initialization parameter. The destination name is also given in the message.

Correct the destination that is referenced by the IDESTINATION parameter of the initial-state definition or add an appropriate destination definition to the Replicator system file or Event Replicator Server startup job, if necessary. You can add and modify replication definitions using initialization parameters, the Adabas Event Replicator Subsystem, or Event Replicator Administration.

Once the definitions and parameters are correctly specified, restart the Event Replicator Server.

The IFILE parameter of the initial-state definition is incorrect. Either IFILE=0 is specified or the IFILE parameter is omitted.

Correct the initial-state parameter specifications. Once the definitions and parameters are correctly specified, restart the Event Replicator Server.

The initial-state definition named in the message is invalid because the subscription specified in the ISUBSCRIPTION parameter is not defined in the Replication system file or by a SUBSCRIPTION initialization parameter. The subscription name is also given in the message.

One or more subscriptions specified in ISUBSCRIPTION parameter are not defined in SUBSCRIPTION settings.

Correct the subscription that is referenced by the ISUBSCRIPTION parameter of the initial-state definition or add an appropriate subscription definition to the Replicator system file or Event Replicator Server startup job, if necessary. You can add and modify replication definitions using initialization parameters, the Adabas Event Replicator Subsystem, or Event Replicator Administration.

Once the definitions and parameters are correctly specified, restart the Event Replicator Server.

The initial-state definition named in the message is invalid because none of the destinations receive data from the subscription specified in the ISUBSCRIPTION parameter.

Correct the ISUBSCRIPTION parameter to identify the correct subscription or update the associated subscription definition so it sends data to one of the destinations specified in the initial-state definition. You can add and modify replication definitions using initialization parameters, the Adabas Event Replicator Subsystem, or Event Replicator Administration.

Once the definitions and parameters are correctly specified, restart the Event Replicator Server.

The initial-state definition named in the message is invalid because none of the destinations listed in the initial-state definition receive data from the database and file listed in the message.

Correct one or more of the following, as necessary:

• Correct the ISUBSCRIPTION parameter in the initial-state definition to identify the correct subscription.

• Update one or more SFILE definitions within the associated subscription definition so it sends data from the database and file listed in the message.

You can add and modify replication definitions using initialization parameters, the Adabas Event Replicator Subsystem, or Event Replicator Administration.

Once the definitions and parameters are correctly specified, restart the Event Replicator Server.

The parameter DARC has a value that is not between 0 and 3.

Check the parameter value, correct the error, and restart the Event Replicator Server.

Neither IDBID nor DBID specified for IFILE parameter.

Check the parameter input, correct the error, and restart the Event Replicator Server.

This message is issued when an error is encountered while communicating with the Adabas Messaging interface. When the error occurs as a result of a configuration or other expected error, a preceding message will have been issued to give more detailed information as to what the problem may be. If the error is not expected, you will need to use the information in this message along with the documentation from your messaging system to determine what caused the error.

R = Identifies the request that was issued.

Q = Gives 8 bytes of detail about the resource where the problem occurred. In some cases, such as the broker ID or the MQ Manager, only the first 8 bytes are given to indicate what was involved.

RC = Provides the ADABAS Messaging Interface return and reason code and the underlying messaging subsystem return and reason codes respectively to help with error diagnosis.

If the message is preceded by another message indicating what the problem was, proceed based on that message. If the error was unexpected, try to determine from the messaging system response and reason codes what the problem was. If this fails, contact your Software AG technical support representative.

The load of the ADAETB/ADAMQS module has failed. The module name is given as mmmmmmmm.

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

Subtask number nnn has encountered an internal error at address 'aaaaaaaa'. If available, a module name mmmmmmmm and offset oooooo are provided. The register contents at the time of the error are also printed.

The subtask is terminated. Contact Software AG technical support for further assistance.

This message indicates that the attempt to open the indicated destination failed. The reason code indicates why the open attempt failed. This will normally occur if the DESTINATION has not been properly defined.

Determine the reason for the failure based on the supplied reason code and correct the condition. If the reason for the failure is "Unexpected reason code", refer to the codes returned in the subsequent ADAF87 message.

This message is issued when an error is encountered while communicating with the Adabas messaging interface.

xx.xxxx is the name of the queue manager.

zz.zzzz is the reason for the failure. The following reasons can occur due to configuration or resource issues while running Event Replicator Server. If any other reason appears, please contact your local support center.

• Queue name unknown - For WebSphere MQ, the queue name associated with the destination or input queue has not been defined to WebSphere MQ system. For webMethods EntireX, the service name associated with the destination or input queue has not been defined to webMethods EntireX. You must review the parameter definitions associated with the destination or input queue and ensure that the appropriate definitions have been set up correctly in WebSphere MQ or webMethods EntireX.

• Messaging System incorrect - For WebSphere MQ, the queue manager is not known to WebSphere MQ. For webMethods EntireX, the broker ID is not accessible on the system. You must review the parameter definitions associated with the destinations and/or input queues and ensure that the appropriate definitions have been set up correctly in WebSphere MQ or webMethods EntireX.

• Messaging System resource error - There is a resource problem in the WebSphere MQ queue manager or webMethods EntireX being used as the message transport. Review the details of the following message to determine what the resource problems may be.

• Insufficient storage - An attempt to get memory failed. You must review the size of the Event Replicator Server address space.

See listings of failure reasons above.

This message is issued when an error occurs during Event Replicator Server processing of resources associated with the messaging system being used.

The request value in the message is the request that was issued (e.g. INIT, SEND, RECEIVE etc.)

The resource listed in the message is the resource on which the request failed. For example, when a SEND fails to a specific destination, resource will be the name of the destination where the failure occurred.

The reason listed in the message is the reason for the failure. The following reasons can occur due to configuration or resource issues while running Event Replicator Server. If any other reason appears, please contact your local support center.

• Queue name unknown - For WebSphere MQ, the queue name associated with the destination or input queue has not been defined to the WebSphere MQ system. For EntireX broker, the service name associated with the destination or input queue has not been defined to broker. You must review the parameter definitions associated with the destination or input queue and ensure that the appropriate definitions have been set up correctly in WebSphere MQ or EntireX broker.

• Messaging System incorrect - For WebSphere MQ, the queue manager starting with the 8 characters in yyyyyyyy is not known to WebSphere MQ. For webMethods EntireX, the Broker ID starting with the 8 characters in yyyyyyyy is not accessible on the system. You must review the parameter definitions associated with the destinations and/or input queues and ensure that the appropriate definitions have been set up correctly in WebSphere MQ or EntireX broker.

• Messaging System resource error - There is a resource problem in the WebSphere MQ queue manager or webMethods EntireX being used as the message transport. Review the details of the following message to determine what the resource problems may be.

• Insufficient storage - An attempt to get memory failed. You must review the size of the Event Replicator Server address space.

• Destination is full - The destination specified by yyyyyyyy is full. This indicates that the WebSphere MQ Queue Manager or webMethods EntireX has refused to accept any more data. The Event Replicator Server will periodically retry to send the data and, when it successfully manages to send data, will revert back to normal mode and send data as it arrives at the Event Replicator Server. The destination reaches capacity if the data consumer does not remove data from the destination more quickly than the Event Replicator Server can send data to that destination.

See listings of failure reasons above.

An attempt to delete the module yyyyyyyy from storage failed. This should not occur and should be reported to your local support center.

Contact your local support center.

A request has been received to open or close a queue which is already in the process of being opened or closed.

Retry the request after the outstanding open or close request has completed.

A request to open the input queue listed in the message failed because the queue was already open.

Verify that you have specified the correct queue in the request and try again.

The input queue close request completed successfully.

No action is required for this informational message.

The input queue open request either completed successfully or failed, as specified in the message (status). The name of the input queue is given in the message.

No action is required for this informational message.

You have specified DLOG=YES on the definition of one or more destinations, but an SLOG file has not been defined to the Event Replicator for Adabas.

Determine if DLOG=YES is required and, if so, define an SLOG file to Event Replicator Server. For more information, read Setting Up Subscription Logging in Event Replicator for Adabas Administration and Operations Guide.

The SLOG cleanup process has started.

No action is required for this informational message.

One of the following occurred:

• The Event Replicator Server destination identified in the message had data on the SLOG. However, when the Event Replicator Server was initialized, the destination had the SLOG facility turned off, so the data on the SLOG file is deleted.

• In a previous Event Replicator Server session, a replay process that started at the date and time given in the message had data on the SLOG. When the Event Replicator Server was initialized, the replay-related data was deleted from the SLOG file.

The number of transactions deleted from the SLOG file is given in the message.

No action is required for this informational message.

The SLOG cleanup process has finished.

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.

An open or close request was received or rejected for the destination named in the message. This may occur if a previous open or close request is still in progress for the destination.

No action is required for this informational message.

An error occurred with the field, filter, and subscription named in the message. A description of the error is 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 unrecognised

  ---

• Invalid begin byte specified

  ---

• Invalid length specified

  ---

• Invalid or out of range FLIST data: data hex: hex

  ---

• Source field type incompatible with target

  ---

Correct the problem indicated by the error description.

SLOG data has been found for the destination listed in the message, which now has DLOG=NO set. This implies that at some point in the past, DLOG=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.

A destination output user exit requested that the Event Replicator Server terminate.

No action is required for this informational message.

SLOG initialization processing completed successfully.

No action is required for this informational message.

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 Event Replicator Server initialization.

This is an informational message that indicates the result of an open request for the destination listed in the message.

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

A request to open the destination listed in the message failed because the destination was already open.

Verify that you have specified the correct destination in the request and try again.

This is an informational message that indicates the result of a close request for the destination listed in the message.

If the close request failed, review associated messages to determine it failed; then correct the problem. Otherwise, no action is required for this informational message.

A request to close the destination listed in the message failed because the destination was already closed.

Verify that you have specified the correct destination in the request and try again.

No action is required for these informational messages. Once the Event Replicator Server is restarted, this data will be cleared from the SLOG file.

This message is displayed in response to the operator command DRPLPARM. It shows the replication-related parameters.

No action is required for these informational messages.

Event Replicator Server is preparing to attach output subtasks.

None required. This message is for information only.

An error occurred while a Event Replicator Server output subtask was being attached.

Contact your DBA, system support personnel, or Software AG technical support.

All of the Event Replicator Server subtasks of the specified type (input or output) have been successfully attached.

None required. This message is for information only.

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

None required. This message is for information only.

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

Note:
If the message is for input subtask termination, the word "input" is included in the message text. If the word "input" is not included in the message text, the message is for output subtask termination.

No action is required for this informational message.

One or more Event Replicator Server subtasks of the specified type (input or output) 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, read SUBTASKWAIT (Subtask Wait Time) Parameter, in the Event Replicator for Adabas Reference Manual

Evaluate the setting of the SUBTASKWAIT parameter for your Event Replicator 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.

An error occurred while a Event Replicator Server input or output subtask was being detached. The subtask number (nnn) and the error number (eee) are given in the message.

Note:
If the message is for input subtask termination, the word "input" is included in the message text. If the word "input" is not included in the message text, the message is for output subtask termination.

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

The termination of Event Replicator Server input or output subtasks is in progress.

Note:
If the message is for input subtask termination, the word "input" is included in the message text. If the word "input" is not included in the message text, the message is for output subtask termination.

None required. This message is for information only.

This message has multiple texts, as described in the following table.

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.

This message has multiple message texts, as described in the following table.

Ensure the destination or input queue is correctly defined and assigned.

An error has occurred during the processing of output subtask number 'nnn'. 'yyyyyyyyyyy' indicates whether the error occurred during initialization, processing or termination logic on the output subtask. This message is always preceded by a message with more information about where the problem lies.

When this occurs during initialization processing, the subtask will not initialize and Event Replicator Server initialization processing will terminate. When this occurs during termination processing of a subtask, termination processing will continue but one or more resources may be left in an invalid state.

This message will have been preceded by an error messaging indicating the error. Correct the problem based on this preceding error message.

This indicates that an error has occurred during the processing of input subtask number 'nnn'. 'yyyyyyyyyyy' indicates whether the error occurred during initialization, processing or termination logic on the input subtask. This message is always preceded by a message with more information about where the problem lies.

When this occurs during initialization processing, the subtask will not initialize and Event Replicator Server initialization processing will terminate. When this occurs during termination processing of a subtask, termination processing will continue but one or more resources may be left in an invalid state.