Adabas Event Replicator Subsystem Messages

No default webMethods EntireX stub name was supplied on the Global Values screen. The default stub name, BKIMBTSO, is inserted.

No action is required for this informational message.

No webMethods EntireX service was provided in a webMethods EntireX destination definition. One is required.

Specify a valid webMethods EntireX service ID for this destination definition.

During editing of an SFILE definition, an attempt was made to specify both a format buffer and a GFB definition name for the before image, after image, or key-related before image of the SFILE. You cannot specify a format buffer if you have already specified a GFB definition name; likewise, you cannot specify a GFB definition name if you have already specified a format buffer.

Specify either a format buffer or a GFB definition name, but not both.

An attempt was made to save a definition in the Event Replicator Server Parameter Subsystem, but the record being edited was in read-only mode. You cannot save a definition you have not explicitly edited.

Edit the definition and try again.

At least one destination must be specified for a subscription definition.

Specify a destination definition to be associated with this subscription definition.

An attempt was made to select a blank line on the List of Destinations screen in the Adabas Event Replicator Subsystem

Select a line that is not blank but that has a destination name listed.

While defining an Adabas destination definition, an attempt was made to specify a database ID and file combination twice in either the Input DBID and Input File fields or in the Target DBID and Target File fields. This is not allowed.

Specify unique database ID and file combinations on the Adabas Destination Definition screen.

An attempt was made to save a webMethods EntireX destination definition when no webMethods EntireX ID was supplied.

Supply a valid webMethods EntireX ID.

The existing definition was updated in the Event Replicator Server Parameter Subsystem.

No action is required for this informational message.

An invalid name was supplied.

Correct the name in the field that the Adabas Event Replicator Subsystem identifies as invalid.

An invalid character was specified in the SEL column.

Refer to the help for the specific screen to determine what values can be specified for the field in question and then specify a valid value.

An invalid value was supplied in one of the fields on the Event Replicator Server Parameter Subsystem screen.

Correct the value in the field that the Adabas Event Replicator Subsystem identifies as invalid.

An invalid value was specified for the Architecture field on the screen. Valid values range from "0" through "2".

Refer to the help for the specific screen to determine what values can be specified for the field in question and then specify a valid value.

An invalid value was specified in the Max Output Size field on the Global Values screen.

Refer to the help for the specific screen to determine what values can be specified for the field in question and then specify a valid value.

An invalid value was specified for the Subtasks field on the Global Values screen.

Refer to the help for the specific screen to determine what values can be specified for the field in question and then specify a valid value.

A WebSphere MQ queue name must be specified in the MQ Queue Name field when creating a WebSphere MQ IQUEUE definition.

Specify a valid WebSphere MQ queue name in the MQ Queue Name field.

An attempt was made to save a definition when no name was specified. A name must be provided for the definition.

Specify a valid name for the definition.

An attempt was made to save a definition when no name was specified. A name must be provided for the definition.

Specify a valid name for the definition.

The destination definition has been successfully added.

No action is required for this informational message.

The destination definition has been successfully saved.

No action is required for this informational message.

The GFB definition has been successfully added.

No action is required for this informational message.

An attempt was made to save a WebSphere MQ destination definition but a WebSphere MQ queue manager name was not supplied.

Supply a valid WebSphere MQ queue manager name.

An attempt was made to save a WebSphere MQ destination definition but a WebSphere MQ queue name was not supplied.

Supply a valid WebSphere MQ queue name.

An attempt was made to save a webMethods EntireX destination definition but a webMethods EntireX service class name was not supplied.

Supply a valid webMethods EntireX service class name.

An attempt was made to save a webMethods EntireX destination definition but a webMethods EntireX service name was not supplied.

Supply a valid webMethods EntireX service name.

The subscription selected for an Adabas destination definition has not yet been defined.

No action is required immediately. You can save the destination definition with the invalid subscription specification, but the destination definition is marked as "pending" in the Event Replicator Server database. When you create the subscription later on, the destination definition is automatically updated and the "pending" status is removed.

The subscription definition was successfully updated and saved.

No action is required for this informational message.

An attempt was made to save an Adabas destination definition when no subscription name (even a name for an as-yet undefined subscription) has been specified. A subscription definition is required for an Adabas destination definition.

Specify a subscription name for the Adabas destination definition. You can press PF6 on this screen to select a subscription name from a list of the currently defined subscription definitions.

In addition, you can specify the name of a subscription that has not yet been defined. In this case, the destination definition is marked as "pending" in the Event Replicator Server database. When you create the subscription later on, the destination definition is automatically updated and the "pending" status is removed.

An attempt was made to save a subscription definition when no subscription name was specified. A name is required for a subscription definition.

Specify a valid subscription name.

There are no SFILE definitions currently defined in the Event Replicator Server database.

Press PF4 to access screens that allow you to add an SFILE definition.

A zero was entered for a database ID or file number in an Adabas destination definition. Zero values are not allowed in database IDs or file numbers.

Specify a valid database ID or file number.

A function (PF) key was pressed that is not valid for the screen.

Review the function keys listed at the bottom of the screen and select a valid one for that screen.

During editing of an SFILE definition, an attempt was made to specify both a format buffer and a GFB definition name for the before image, after image, or key-related before image of the SFILE. You cannot specify a format buffer if you have already specified a GFB definition name; likewise, you cannot specify a GFB definition name if you have already specified a format buffer.

Specify either a format buffer or a GFB definition name, but not both.

The GFB definition specified for an SFILE definition is not defined in the Event Replicator Server database.

Specify the name of a GFB definition that has been previously defined in the Event Replicator Server database.

An attempt was made to assign the same destination definition to a subscription more than once. Every destination definition specified for a subscription definition must be unique.

Specify a unique destination definition name.

While assigning a destination definition to a subscription definition, no values were supplied for the N (normal replicated data) or the I (initial-state replicated data) flags.

Specify values for the I and N fields on the screen. Refer to help for the screen to review the valid values.

An invalid database ID was specified in an SFILE definition.

Specify a valid database ID.

An invalid file number was specified in an SFILE definition.

Specify a valid file number.

The default values specified on the Global Values screen of the Adabas Event Replicator Subsystem have been successfully updated and saved.

No action is required for this informational message.

Changes were made to a GFB definition, but the GFB definition has not been saved.

Save and replace the existing GFB definition or alter the GFB definition name and save it under the new name.

The selected IQUEUE definition has been successfully deleted from the Event Replicator Server database.

No action is required for this informational message.

The selected subscription definition has been successfully deleted from the Event Replicator Server database.

No action is required for this informational message.

The IQUEUE definition was successfully updated.

No action is required for this informational message.

The IQUEUE definition was successfully saved.

No action is required for this informational message.

The initial-state definition was successfully deleted.

No action is required for this informational message.

The initial-state definition was successfully saved.

No action is required for this informational message.

The initial-state definition was successfully updated.

No action is required for this informational message.

The SFILE definition was successfully deleted.

No action is required for this informational message.

This informational message informs you to specify "A" or "I" in the I field on this screen or leave the I field blank and specify selection criteria instead.

In the I field on the Initial-State Definition screen, specify "A" (no filter), "I" (filter by initial-state ISN specification), or a blank (filter by selection criteria). If you specify a blank, you must also specify some selection criteria in the Selection Criteria field on the screen.

An attempt was made to specify a value for the I and Selection Criteria fields on the Initial-State Definition screen. If you want to specify selection criteria, the I field must be blank.

Specify a valid value in the I field or specify selection criteria in the Selection Criteria field, but not both.

An attempt was made to save an initial-state definition for which no values for the IDBID field were specified.

Specify at least one input database ID in the IDBID field for the initial-state definition.

An attempt was made to save an initial-state definition for which no values for the IFile field were specified.

Specify at least one input file number in the IFile field for the initial-state definition.

While attempting to copy a Event Replicator Server definition, a duplicate name was specified.

Specify a new unique definition name when copying definitions.

An attempt was made to define two destination definitions with the same name, but of different types. This is not allowed.

Specify a unique name each time you add a destination name to the Event Replicator Server database.

An invalid value was specified for the Input DBID field on the Adabas Destination Definition screen.

Specify a valid database ID for the Input DBID field. Valid values range from "1" to "65535".

An invalid value was specified for the Target DBID field on the Adabas Destination Definition screen.

Specify a valid database ID for the Target DBID field. Valid values range from "1" to "65535".

In an Adabas destination definition, the database ID and file number combination specified for the Input DBID and Input File fields were the same as those specified for the Target DBID and Target File fields. The DBID/file combinations for the input fields must be different than those specified for the target fields.

Specify unique DBID/file combinations for the input and target fields of an Adabas destination definition.

In a subscription definition, the name of a destination that has not yet been defined was specified on the Destination List screen.

Specify the name of a previously defined destination definition for the subscription.

No help could be found for the message number you specified.

Verify that you have specified the correct number. To get help for Adabas Event Replicator Subsystem messages, enter:

msg nn

at the Command prompt. Specify the two-digit message number (omit the leading zeros) for nn.

If you have specified a valid message number and the error persists, contact your Software AG technical support representative.

The message value specified during a message help request was not in a format that the Adabas Event Replicator Subsystem recognized.

Request message help using a valid message number format. To get help for Adabas Event Replicator Subsystem messages, enter:

msg nn

at the Command prompt. Specify the two-digit message number (omit the leading zeros) for nn.

If you have specified a valid message number and the error persists, contact your Software AG technical support representative.

The database ID and file number combination specified on the Set LFILE Parameters screen were not for a Event Replicator Server database.

Specify the database ID and file number combination of a Event Replicator Server database.

The resend buffer definition was successfully updated.

No action is required for this informational message.

An invalid buffer size was specified for a resend buffer definition.

Specify a valid buffer size. Refer to help for this screen for a range of valid values.

The resend buffer definition name specified in the subscription definition is for a resend buffer definition that has not yet been defined.

Specify the name of a previously defined resend buffer definition.

The resend buffer definition specified for the subscription definition has never been defined.

Specify the name of a previously defined resend buffer definition.

The subscription definition was deleted somehow (probably by somebody else) while you were working on it.

Try saving it again.

An attempt was made to create a new subscription definition with the same name as an existing subscription definition.

Specify a unique name for each subscription definition you define.

The resend buffer definition has been successfully saved.

No action is required for this informational message.

The GFB definition was successfully altered and saved.

No action is required for this informational message.

An invalid value was specified for the Input Request Message Limit field of the Global Values screen.

Refer to help for this screen to review the valid values for this field. Then specify a valid value.

An attempt was made to delete a GFB definition that is used by a subscription definition. The deletion attempt fails.

No action is required. However, if you really need to delete the GFB definition, edit the subscription definition, specify a different GFB definition for the subscription, save the subscription definition, and try the delete attempt again.

An attempt was made to change the name of an existing subscription definition on the Subscription Definition screen. Once defined, the name of a subscription definition cannot be changed.

This limitation is designed to protect you from accidental replication problems, To get around this limitation, copy the subscription definition to a new name and delete the original subscription (with the original name) on the Available Subscriptions screen.

An invalid value was specified for the Num of Concurrent Initial State Requests field on the Initial-State Definition screen.

Refer to the help for this screen for a description of the valid values for this field. Then specify a valid value.

An invalid value was specified for the Input Request Message Interval field on the Global Values screen.

Refer to the help for this screen for a description of the valid values for this field. Then specify a valid value.

A request to delete a subscription was canceled because an initial-state definition makes reference to it. The name of the initial-state definition is given in the message.

Delete the initial-state definition prior to deleting the subscription.

A request to delete a subscription was canceled because a destination definition makes reference to it. The name of the destination definition is given in the message.

Delete the destination definition prior to deleting the subscription.

A request to delete a destination was canceled because a subscription definition makes reference to it. The name of the subscription definition is given in the message.

Delete the subscription definition prior to deleting the destination.

A request to delete a destination was canceled because an initial-state definition makes reference to it. The name of the initial-state definition is given in the message.

Delete the initial-state definition prior to deleting the destination.

A request to delete a GFB definition was canceled because a subscription definition makes reference to it. The name of the subscription definition is given in the message.

Delete the GFB reference in the subscription definition prior to deleting the GFB definition.

An attempt was made to set the LFILE parameters using the Adabas Event Replicator Subsystem's Set LFILE Parameters screen, but the attempt failed.

Enter Natural using the LFILE=(89,nnnnn,nnnn) session parameter where nnnnn,nnnn are the DBID and file number of the Replicator system file.

A Natural error occurred. The Natural error number (eeee), the possible line number within the program (nnnn). and the program name (pppppppp) that encountered the error are given in the message.

Read about the Natural error in the Natural documentation and follow the instructions described for that error.

The definition could not be saved because parameters in the definition were not specified correctly.

Correct the parameters and try to save the definition again.

An attempt was made to supply a filter definition for a subscription that allows UES conversion. In other words, its architecture key (SARC parameter) is not "2" and a value other than "0" has been set for the user data alpha and wide settings (SACODE and SWCODE parameters). At this time, filters are only allowed on subscriptions that do not allow UES conversion. So the architecture key (SARC) must be set to "2" and the user data alpha and wide settings (SACODE and SWCODE) must be set to "0".

Change the subscription definition. Either remove the filter definition specification or reset the UES field values.

An invalid value was specified for the Input File field on the Adabas Destination Definition screen. Valid values range from "1" through "5000".

Specify a valid file number for the Input File field.

An invalid value was specified for the Target File field on the Adabas Destination Definition screen. Valid values range from "1" through "5000".

Specify a valid file number for the Target File field.

More than n transaction filter definitions have been selected for the SFILE definition. The maximum that can be selected is listed in the message.

Select the correct number of transaction filter definitions for the SFILE definition.

This error may occur if there are concurrent updates on the same transaction filter definition. For example, if one user is modifying a definition at the same time as another user deletes it, this error occurs. The name of the transaction filter definition is given in the message.

Try saving the transaction filter definition again.

An attempt was made to change the name of an existing transaction filter definition on the Transaction Filter screen. Once defined, the name of a transaction filter definition cannot be changed.

This limitation is designed to protect you from accidental replication problems, To get around this limitation, copy the transaction filter definition to a new name and delete the original transaction filter (with the original name) on the List of Transaction Filters screen.

If no target field is specified, no target PE, target MU, or target image can be specified.

Specify a target field prior to specifying a target PE, MU, or image.

This error may occur if there are concurrent updates on the same transaction filter definition. For example, if one user is modifying a definition at the same time as another user deletes it, this error occurs.

Try saving the transaction filter definition again.

Either no values were specified in the target value list for the transaction filter definition or more than 254 characters were specified.

Review the target value list for the transaction filter definition. If more than 254 characters were specified, change the list to specify fewer characters. If you intend to specify a blank for the target value list, make sure a blank character is coded between the quotation marks (' ').

The transaction filter definition was successfully updated and saved.

No action is required for this informational message.

More than one value was specified for an LT, LE, GT, or GE condition. Only one value is allowed for these conditions, although more than one value may be specified for the EQ and NE conditions.

Specify only one value for the condition or change the type of condition.

A syntactical error exists in the transaction filter definition.

Review the Event Replicator for Adabas documentation and the help provided with the Adabas Event Replicator Subsystem for the correct syntax of transaction filter definitions. Correct the syntactical error and try again.

The selected transaction filter definition has been successfully deleted from the Event Replicator Server database.

No action is required for this informational message.

A request to delete a transaction filter definition was canceled because a subscription definition makes reference to it. The name of the subscription definition is given in the message.

Delete the transaction filter definition reference in the subscription definition prior to deleting the transaction filter definition.

A syntactical error exists in the transaction filter definition.

Review the Event Replicator for Adabas documentation and the help provided with the Adabas Event Replicator Subsystem for the correct syntax of transaction filter definitions. Correct the syntactical error and try again.

An invalid Adabas field name was specified. The field name must be two characters long with the first character alphabetic and the second character either alphabetic or numeric. No special characters are permitted.

Correct the field name.

An invalid condition value was specified. Valid values are listed in the message.

Correct the condition value.

Changes were made to a transaction filter definition, but the definition has not been saved.

Save and replace the existing transaction filter definition or alter the definition name and save it under the new name.

The transaction filter definition has been successfully added.

No action is required for this informational message.

The transaction filter definition was successfully altered and saved.

No action is required for this informational message.

Neither a target field or a target value list was specified. One of these is required for the transaction filter definition.

Specify either a target field or a target value list for the transaction filter definition.

Over 2500 conditions were specified for the transaction filter definition. The maximum number of conditions you can specify for a transaction filter definition is 2500. The line number and program name are given in the message.

Remove conditions from the transaction filter definition so that no more than 2500 are specified and try again.

Over 2000 characters were specified in the target value list for the transaction filter definition. The maximum length of all target value lists is 2000 characters.

Specify fewer values in the target value list and try again.

While defining file-related parameters, an attempt was made to create a before image format buffer when an after image format buffer does not exist. The after image format buffer must be defined first.

Provide an after image format buffer first.

While defining file-related parameters, if Include Identical Records is specified as "N", then the before image format buffer must be identical to the after image format buffer.

Either remove the before image format buffer or make it identical to the after image format buffer.

During unload processing, no object was found with the entity and name combination specified.

Check the entity and name specifications and try again.

A request to save an object failed because errors were found in the object.

Correct the errors and try again.

An attempt was made to specify a before image global format buffer (GFB) definition, but the after image GFB definition must be defined first. This is only true if the value for the Include Identical Records field is specified as "N".

Define the after image GFB first.

A transaction filter name was specified but the transaction filter has not been defined.

Define the transaction filter first or specify the name of a currently defined filter.

An attempt was made to combine the use of local and global format buffers. This is not allowed if the value for the Include Identical Records field is specified as "N".

Do not mix local and global format buffers.

An attempt was made to delete an after image format buffer when a before image format buffer still exists.

Delete the before image format buffer first.

The number of characters for the RPLOD or RPULD utility parameter named in the message has been exceeded. The maximum number of characters possible for the parameter is also listed in the message.

Correct the parameter specification and try the load or unload function again. For complete information on the RPLOD and RPULD utility parameters, read RPLOD and RPULD Utilities.

The resend buffer definition was successfully deleted.

No action is required for this informational message.

The Predict function has been completed successfully.

No action is required for this informational message.

The version of Predict required to run the selected function is given in the message. The message also indicates which version of Predict is installed in the current environment: vrsp identifies the Predict version, release, SM level, and service pack number. If Predict is not installed in the current environment, a remark is shown for vrsp.

Verify your environment and install the required version of Predict.

An attempt was made to save a global format buffer definition when no global format buffer name was specified. A name is required for a global format buffer definition.

Specify a valid global format buffer name.

An attempt was made to save a global format buffer definition when no format buffer was supplied.

Supply a format buffer and try again.

Errors occurred while attempting to save LFILE parameters on the Set LFILE Parameters screen.

Supply a correct database ID and file number and try again.

This confirms that the LFILE settings were successfully saved or updated on the Set LFILE Parameters screen.

No action is required for this informational message.

The Replicator system file specified on the Set LFILE Parameters screen cannot be found. Possible reasons are:

• No file was loaded.

• The LFILE parameters are incorrect.

Verify that a file is specified and that the LFILE settings are correct.

The Replicator system file specified on the Set LFILE Parameters screen is not available. The only function you can perform using the Adabas Event Replicator Subsystem is option "L" on the System Functions menu, which directs you to the Set LFILE Parameters screen, where you can fix the problem.

Navigate to the Set LFILE Parameters screen and correct the LFILE settings. Otherwise, make the Replicator system file available and try again.

Only one field can be marked as the primary key. The message shows the already-defined primary key field.

To define another field as the primary key, remove the existing primary key flag first.

The generated format buffer does not contain any field.

Check the Predict file name and the field definitions for this file in Predict.

The Predict Generation Information has been successfully unlinked (removed) from the GFB definition.

No action is required for this informational message.

Adabas response 148 was received while trying to communicate with the Event Replicator Server. The Natural LFILE setting points to a Replicator system file that is currently not available.

Correct the LFILE setting or insure that the Replicator system file is available.

The database ID entry was successfully deleted.

No action is required for this informational message.

The GFB entry was successfully deleted.

No action is required for this informational message.

An invalid value was supplied in one of the fields on the Adabas Event Replicator Subsystem screen.

Correct the value in the field that the Adabas Event Replicator Subsystem identifies as invalid.

This confirms a replay operation was initiated and informs you of the token number associated with the replay process.

No action is required for this informational message.

There is insufficient space in the Event Replicator server replication pool. In other words, the value specified by LRPL has been exceeded.

Increase the size of the LRPL parameter and try again.

A replay request was issued for a database not defined to the Event Replicator server.

Correct the DBID in the replay request or define the database to the Event Replicator server.

The replay token is invalid. Either it is not defined or it is outdated.

Specify a valid replay token.

Replay processing for the same DBID and file number combination is already running.

Request replay processing for a different DBID and file number.

The value specified for the date or time is not in the correct format or is an invalid value.

Check the syntax of the specified date and time values. Do not specify future date and time values.

The specified replay parameters are incorrect.

Check and correct the replay parameters and try again.

A replay destination that was defined without an SLOG was closed at the beginning of replay processing or while the replay was running.

Reopen the closed destination and rerun the replay process for the destination.

An invalid replay status transition occurred. Events that change the status of a replay process occurred in an unexpected order.

Notify your Software AG technical support representative.

The response code and subcode listed in the message were received from the Event Replicator.

Review your Adabas documentation for the exact meaning of the listed response code and subcode. Take appropriate action, based on that description.

A subscription is required to submit a request to the Event Replicator Target Adapter.

Supply a valid subscription definition name for the Event Replicator Target Adapter request and try again.

An initial-state definition must be specified for populate requests to the Event Replicator Target Adapter.

Supply a valid initial-state definition name for the Event Replicator Target Adapter request and try again.

The initial-state definition specified for the Event Replicator Target Adapter populate request cannot be found.

Verify that the initial-state definition specified for the Event Replicator Target Adapter populate request is valid and spelled correctly. Then try again.

The subscription specified in the Event Replicator Target Adapter populate request must match one of the subscriptions specified in the initial-state definition.

Specify a subscription that is used by the initial-state definition. Then try again.

The DBID and file number specified in the Event Replicator Target Adapter populate request do not match a DBID and file number combination specified in the initial-state definition.

Specify a DBID and file number combination that is used by the initial-state definition. Then try again.

The subscription specified for the Event Replicator Target Adapter request does not include a valid after-image global format buffer. Any subscription used in an Event Replicator Target Adapter request must include a generated global format buffer and field table. Global format buffers and field tables can be generated by the Event Replicator for Adabas using appropriate Predict file definitions.

Specify a subscription that includes a generated global format buffer and field table or add one to the subscription. Then try again.

The subscription definition specified for the Event Replicator Target Adapter request cannot be found.

Verify that the subscription definition specified for the Event Replicator Target Adapter request is valid and spelled correctly. Then try again.

The global format buffer (GFB) specified by the subscription used in the Event Replicator Target Adapter request cannot be found.

Verify that the GFB definition name specified in the subscription is valid and spelled correctly. Then try again.

The global format buffer (GFB) specified by the subscription used in the Event Replicator Target Adapter request does not include a field table. This means that the GFB definition was not generated. Only when the GFB is generated will the field table also be generated.

Global format buffers and field tables can be generated by the Event Replicator for Adabas using appropriate Predict file definitions.

Specify a subscription for that request that uses a generated GFB and field table or generate a GFB and field table for the subscription in the request.

The Event Replicator Target Adapter request was successfully submitted.

No action is required for this informational message.

The response code and subcode listed in the message were received from the Event Replicator Target Adapter request.

Review your Adabas documentation for the exact meaning of the listed response code and subcode. Take appropriate action, based on that description.

A timeout occurred while the Event Replicator Server was waiting for the end of a synchronization process after reactivating replication for a file in Adabas. The synchronization process ends when all transactions have finished that had updated the file before it was reactivated.

Wait until the Event Replicator Server reports the activation of the file (ADAF2L message). Then run a new replay job.

There is insufficient space in the nucleus replication pool. In other words, the value specified by LRPL has been exceeded.

Increase the LRPL size of the nucleus and try again.

The subscription specified in a status request is undefined.

Correct the subscription specified in the status request and try again.

The specified initial-state name was not found.

Correct the initial-state name or create an initial-state definition by that name. Then try again.

The end date specified for the request must be later than the start date.

Correct the dates and try again.

The end time specified for the request must be later than the start time.

Correct the times and try again.

One of the destinations requested for replay processing could not be found.

Verify that the names of the destination definitions in the destination list are specified accurately. Then try again.

One of the subscriptions requested for replay processing could not be found.

Verify that the names of the subscription definitions in the subscription list are specified accurately. Then try again.

One of the destinations listed in the destination list for replay processing is not active.

Either activate the destination definition or remove it from the list for replay processing. Then try again.

One of the subscriptions listed in the subscription list for replay processing is not active.

Either activate the subscription definition or remove it from the list for replay processing. Then try again.

The file requested for replay processing is not active.

Activate the file. Then try again.

No files were found for a subscription specified in the subscription list for replay processing.

Check the subscriptions requested for replay processing and verify that they are complete and include SFILE definitions. Then try again.

One of the destinations specified in the destination list for a replay run does not receive replication data. No data can replayed for this destination.

Review the list of destinations specified for replay and alter it as necessary.

A subscription definition in the subscription list for replay processing does not reference any destination definition. It is incomplete.

Complete the subscription definition and try again.

A file specified for replay is not processed by any subscription, so replicated data from the file does not flow to any destination. Data for the file could not be found in the PLOG.

Add the file to a subscription definition, let replication processing run for a while, and then try again.

A destination definition requested for replay is not referenced by any subscription. No PLOG data exists for the destination.

Add the destination to a subscription definition, let replication processing run for a while, and then try again.

An input queue definition with the same name already exists Each input queue definition name must be unique.

Change the input queue definition name and try again.

A request to delete the selected PLOG information record and all prior PLOG information records has completed.

No action is required for this informational message.

A replay request included duplicate destination names.

Review the destinations you specified and remove the duplicates.

A replay request included duplicate subscription names.

Review the subscriptions you specified and remove the duplicates.

The value specified for the Restart RPL Usage global parameter setting is greater than the Maximum RPL Usage global parameter setting.

Reduce the setting for the Restart RPL Usage global parameter or increase the value for the Maximum RPL Usage global parameter.

A request to delete file-related information from a subscription was canceled because an initial-state definition makes reference to it. The name of the initial-state definition is given in the message.

Remove references to the subscription from the initial-state definition and try again.

An IDBID/IFILE specification in an initial-state definition was successfully deleted.

No action is required for this informational message.

The start time specified for the replay request must be earlier or the same as the from time specified for the replay request.

Correct the times and try again.

Data was entered in the Destination Class Parameter Data field, but no value was specified for the Destination Class field. You cannot supply a value for the Destination Class Parameter Data field without first supplying a Destination Class value.

Supply a value in the Destination Class field or delete the data in the Destination Class Parameter Data field.

A subscription references a destination that has a Destination Class of SAGTARG. When this condition is true, any GFB specified in the subscription must be generated by Predict. For more information on how to generate your GFBs, readGenerating a GFB using the Adabas Event Replicator Subsystem or Generating a GFB using Event Replicator Administration .

Supply a GFB that was generated by Predict.

The initial-state definition you selected to populate a database could not be found in the Replicator system file.

Specify an existing initial-state definition, or add one and then select it.

Only files that require an ISN list as a filter can be edited on the Perform Initial-State screen. An attempt was made to edit a file that does not require an ISN list filter.

Do not type an "E" next to any files that do not have a filter type of "I" (check the I column on the screen).

An attempt was made to submit the initial-state definition for processing, but it failed because one of the files requires an ISN list filter or a value buffer that has not yet been specified.

Enter an "E" next to every file on the Perform Initial-State screen that has a filter type of "I" or "S". Another Adabas Event Replicator Subsystem screen appears on which you can specify ISNs or a value buffer for the file.

The ISN list on the Specify ISNs screen is not specified correctly. There are blanks in the ISN list. The only characters allowed are numbers, commas, and parentheses.

Remove any blanks from the ISN list.

The ISN list on the Specify ISNs screen is not specified correctly. There are invalid characters in the ISN list. The only characters allowed are numbers, commas, and parentheses.

Correct the ISN list. Separate multiple ISNs with commas (no blanks). If you want to specify a range of ISNs, specify them in parentheses. For example, the following ISN list selects ISNs 111 and 222, all the ISNs between 333 and 666, and ISN 9999.

111,222,(333,666),9999

The ISN list on the Specify ISNs screen is not specified correctly. An uneven number of open and closed parentheses are specified.

Verify that both an open and closed parenthesis are provided if you are specifying an ISN range. The following example correctly specifies a range of ISNs falling between 333 and 555.

(333,555)

If you are not specifying an ISN range, remove parentheses from the ISN list.

The ISN list on the Specify ISNs screen is not specified correctly. An ISN range is indicated, but using only one number.

Verify that two numbers are provided if you are specifying an ISN range. The following example correctly specifies a range of ISNs falling between 333 and 555.

(333,555)

If you are not specifying an ISN range, remove the parentheses from the ISN list. Parentheses indicate that an ISN range is being specified.

The ISN list on the Specify ISNs screen is not specified correctly. A comma is missing.

Correct the use of commas in the ISN list. Commas should be used to separate individual ISNs in the list and any ISN range specifications from the rest of the list. Note the use of commas in the following correct ISN list that selects ISNs 111 and 222, all the ISNs between 333 and 666, and ISN 9999.

111,222,(333,666),9999

The ISN list on the Specify ISNs screen is not specified correctly. A range in the ISN list is not specified in ascending order.

When specifying a range in the ISN list, you must be sure that the lowest ISN of the range is listed first, followed by the highest ISN in the range.

Correct the ISN range specification.

The initial-state definition you selected to populate a database could not be found in the Replicator system file.

Specify an existing initial-state definition, or add one and then select it.

The ISN list on the Specify ISNs screen is not the correct ISN list.

Verify that the ISN list filters on the Specify ISN screens are specified correctly, as required for each file on the Perform Initial-State screen.

Filter data is not allowed for the initial-state definition of filter type A records (see the I column on the Perform Initial-State screen).

Do not type an "E" next to any files that do not have a filter type of "I" (check the I column on the screen).

An initial-state request was issued to a Event Replicator Server address space that was terminating as a result of an ADAEND or HALT command. An initial-state request may only be issued when the Event Replicator Server is active.

Reissue the initial-state request after the Event Replicator Server has been started.

The number of active concurrent initial-state requests exceeded the IMAXREQ parameter setting. For more information about the IMAXREQ parameter, read IMAXREQ.

Increase the IMAXREQ setting or reduce the number of active concurrent initial-state requests.

The ISN list on the Specify ISNs screen is not specified correctly. An ISN in the list is longer than nine characters. An ISN in the list can be a maximum of nine characters long.

Correct the ISN list. If your ISN is really larger than nine characters in length, contact your Software AG technical support representative for assistance.

The ISN list on the Specify ISNs screen is not specified correctly. A continuation in the list is indicated by a comma, but no additional ISN data is provided.

Either remove the comma (if there are no additional ISNs or ISN ranges to specify) or complete the ISN list. The ISN list should not end with a comma.

In an Adabas destination definition, the Replication Method specified was ISN for a given DBID/file combination's file-related parameters. If this parameter is set to ISN, no other file-related parameters for that DBID/file combination can be specified.

Do not enter values for the other file-related parameters if the Replication Method is set to ISN. If you set the Replication Method to KEY, you may specify the other parameters.

An automated replay request was made using an asterisk specified in the first destination space of the Destination Name List field. This includes all destinations definitions in the request. If you use an asterisk to select all destinations for the replay request, you cannot also add another specific destination or select one from a list.

To add a specific destination or select one from a list, remove the asterisk from the first destination space of the Destination Name List field.

An automated replay request was made using an asterisk specified in the first subscription space of the Subscription Name List field. This includes all subscription definitions in the request. If you use an asterisk to select all subscriptions for the replay request, you cannot also add another specific subscription or select one from a list.

To add a specific subscription or select one from a list, remove the asterisk from the first subscription space of the Subscription Name List field.

A value buffer length was not specified on the Specify Value Buffer screen while you were trying to perform an initial-state. If a DBID/file combination includes a search buffer, a value buffer and the length of the value buffer must be specified.

Enter a valid value for the length of the value buffer.

The same DBID/file combination was defined for more than one target in an Adabas destination definition.

Remove the duplicate.

You have selected a blank line of input and target DBIDs and files on the Adabas Destination Definition panel.

Select a line that has input and target DBIDs and files specified or supply input and target DBIDs and files on the selected line.

When specifying an SFILE definition for a subscription, you tried to add a new DBID/file combination or change a DBID/file combination but specified a combination that already exists for this subscription.

Specify a unique DBID/file combination for each SFILE definition within a subscription.

After requesting that an initial-state be performed (by selecting the Perform Initial-State option on the Administration panel), the returned response and subcodes indicate that a file related to the initial-state definition you attempted to run is not active.

Examine the error and current status of the file and determine why the file is not active. If the problem persists, contact your Software AG support representative for assistance.

When selecting a destination or subscription, only the first entry may contain an asterisk.

Correct your specifications.

Only the first entry may contain an asterisk.

Correct your specifications.

The global format buffer (GFB) you have selected to edit was created with Predict, but predict is not available in this Natural environment.

Either install Predict in this Natural environment or edit the GFB in a Natural environment in which Predict is already installed and then import the GFB into the original Natural environment.

The initial-state definition includes references to both destination and subscription definitions. The destination identified in the message (destname) does not exist in the subscriptions of the initial-state definition being defined or modified. The Event Replicator Server detects this inconsistency and produces an error condition at startup or when an RPLREFRESH is attempted for the initial-state definition. The destinations specified in an initial-state definition must also exist in one of the subscriptions referenced by the initial-state definition.

When both destination and subscription definitions are specified in an initial-state definition, the destinations must correlate to destinations specified by the subscriptions. Likewise, at least one destination specified by each subscription must be referenced by the initial-state definition. In addition, any destinations referenced in the initial-state definition must be identified as able to send initial-state data (using the I field on the Destination List panel within the subscription definition).

Make sure that all of the destinations used by your initial-state definition also exist in one of the subscription destinations referenced by your initial-state definition. Then try again.

The initial-state definition includes references to both destination and subscription definitions. The destination listed in the message (destname) was found in the subscription listed in the message (subsname), but it is not marked in the subscription definition as being able to send initial-state data. The Event Replicator Server detects this inconsistency and produces an error condition at startup or when an RPLREFRESH is attempted for the initial-state definition.

When both destination and subscription definitions are specified in an initial-state definition, the destinations must correlate to destinations specified by the subscriptions. Likewise, at least one destination specified by each subscription must be referenced by the initial-state definition. In addition, any destinations referenced in the initial-state definition must be identified as able to send initial-state data (using the I field on the Destination List panel within the subscription definition).

Make sure that any destinations used by your initial-state definition and included in the associated subscription definitions are marked as able to send initial-state data. This setting is specified by setting the I field to "Y" on the Destination List panel line associated with the destination in the subscription definition. Then try again.

The initial-state definition includes references to both destination and subscription definitions. None of the destinations specified by the subscription listed in the message (subsname) are included in the initial-state definition, as is required. The Event Replicator Server detects this inconsistency and produces an error condition at startup or when an RPLREFRESH is attempted for the initial-state definition. The destinations specified by a subscription (that is included in an initial-state definition) must also be included in the initial-state definition.

When both destination and subscription definitions are specified in an initial-state definition, the destinations must correlate to destinations specified by the subscriptions. Likewise, at least one destination specified by each subscription must be referenced by the initial-state definition. In addition, any destinations referenced in the initial-state definition must be identified as able to send initial-state data (using the I field on the Destination List panel within the subscription definition).

Make sure to include in the initial-state definition any destinations specified by any subscriptions included in the initial-state. Then try again.

The initial-state definition includes references to both destination and subscription definitions. The destination listed in the message (destname) was found in the subscription listed in the message (subsname), but the destination is not marked in the subscription definition as being able to send initial-state data. The Event Replicator Server detects this inconsistency and produces an error condition at startup or when an RPLREFRESH is attempted for the initial-state definition.

When both destination and subscription definitions are specified in an initial-state definition, the destinations must correlate to destinations specified by the subscriptions. Likewise, at least one destination specified by each subscription must be referenced by the initial-state definition. In addition, any destinations referenced in the initial-state definition must be identified as able to send initial-state data (using the I field on the Destination List panel within the subscription definition).

Make sure that any destinations used by your initial-state definition and included in the associated subscription definitions are marked as able to send initial-state data. This setting is specified by setting the I field to "Y" on the Destination List panel line associated with the destination in the subscription definition. Then try again.

When the Replicate for Delete field is set to "U" in an SFILE definition, a subscription user exit name must be supplied in the Subscription User Exit field. The subscription user exit can then process replicated physical delete transactions on your target database as you choose. It can decide if the physical delete transaction should be:

• physically deleted from your target database

• converted to an update

• ignored and not sent at all.

Specify a subscription user exit name or change the setting of the Replicate for Delete field.

An input DBID/file combination was added to a destination definition, but a subscription that references the destination definition does not include a comparable SFILE definition for the DBID/file combination. You will not be able to save the destination definition until the problem is resolved.

Add the SFILE definition for the new DBID/file combination first. Then update the destination definition.

When setting Source Begin and Length values or Target Begin and Length values, the sum of these values cannot exceed 32767. You will not be able to save the transaction filter until the problem is resolved.

Examine and correct the values for the appropriate Begin and Length fields. Then save or update the transaction filter definition.

When the Replicate Security File field is set to "Y", the Replicate for Delete, Replicate for Insert, and Replicate for Update fields must also be set to "Y". The Replicate Security File field specifies the value of the SFSECURITYFILE parameter.

Examine and correct the values for the appropriate field. Then save or update the definition.

When the Replicate Security File field is set to "Y", the Include Identical Records field must also be set to "Y". The Replicate Security File field specifies the value of the SFSECURITYFILE parameter.

Examine and correct the values for the appropriate field. Then save or update the definition.

When the Replicate Security File field is set to "Y", the Default Code field must be null. The Replicate Security File field specifies the value of the SFSECURITYFILE parameter.

Examine and correct the values for the appropriate field. Then save or update the definition.

When the Replicate Security File field is set to "Y", the Subscription User Exit field must be null. The Replicate Security File field specifies the value of the SFSECURITYFILE parameter.

Examine and correct the values for the appropriate field. Then save or update the definition.

When the Replicate Security File field is set to "Y", the Transaction Filter field must be null. The Replicate Security File field specifies the value of the SFSECURITYFILE parameter.

Examine and correct the values for the appropriate field. Then save or update the definition.

When the Replicate Security File field is set to "Y", no format buffers or global format buffers can be specified. The values of the Before Image FB, After Image FB, Key-Related Before Image FB, Before Image GFB Name, After Image GFB Name, and Key-Related GFB Name must be null. The Replicate Security File field specifies the value of the SFSECURITYFILE parameter.

Examine and correct the values for the appropriate field. Then save or update the definition.