Version 8.2.5
 —  Messages and Codes  —

ARF* - Adabas Event Replicator Subsystem Messages

Overview of Messages

ARF00001 | ARF00002 | ARF00003 | ARF00004 | ARF00006 | ARF00007 | ARF00008 | ARF00009 | ARF00010 | ARF00011 | ARF00012 | ARF00013 | ARF00014 | ARF00015 | ARF00016 | ARF00017 | ARF00018 | ARF00019 | ARF00020 | ARF00021 | ARF00022 | ARF00024 | ARF00025 | ARF00026 | ARF00027 | ARF00028 | ARF00029 | ARF00030 | ARF00031 | ARF00032 | ARF00033 | ARF00034 | ARF00035 | ARF00036 | ARF00038 | ARF00041 | ARF00043 | ARF00044 | ARF00045 | ARF00046 | ARF00047 | ARF00048 | ARF00049 | ARF00050 | ARF00051 | ARF00052 | ARF00053 | ARF00054 | ARF00055 | ARF00056 | ARF00057 | ARF00058 | ARF00059 | ARF00060 | ARF00061 | ARF00062 | ARF00063 | ARF00064 | ARF00065 | ARF00066 | ARF00067 | ARF00068 | ARF00069 | ARF00070 | ARF00071 | ARF00072 | ARF00073 | ARF00074 | ARF00075 | ARF00076 | ARF00077 | ARF00078 | ARF00079 | ARF00080 | ARF00083 | ARF00084 | ARF00085 | ARF00086 | ARF00087 | ARF00088 | ARF00089 | ARF00090 | ARF00091 | ARF00092 | ARF00093 | ARF00101 | ARF00102 | ARF00103 | ARF00104 | ARF00105 | ARF00106 | ARF00107 | ARF00108 | ARF00109 | ARF00110 | ARF00111 | ARF00112 | ARF00113 | ARF00114 | ARF00115 | ARF00116 | ARF00117 | ARF00118 | ARF00119 | ARF00120 | ARF00121 | ARF00122 | ARF00123 | ARF00124 | ARF00125 | ARF00126 | ARF00127 | ARF00128 | ARF00130 | ARF00131 | ARF00132 | ARF00133 | ARF00134 | ARF00135 | ARF00136 | ARF00137 | ARF00138 | ARF00139 | ARF00140 | ARF00141 | ARF00142 | ARF00143 | ARF00144 | ARF00145 | ARF00146 | ARF00147 | ARF00148 | ARF00149 | ARF00150 | ARF00151 | ARF00152 | ARF00153 | ARF00154 | ARF00155 | ARF00156 | ARF00158 | ARF00159 | ARF00160 | ARF00161 | ARF00162 | ARF00163 | ARF00164 | ARF00165 | ARF00166 | ARF00167 | ARF00168 | ARF00169 | ARF00171 | ARF00172 | ARF00173 | ARF00174 | ARF00175 | ARF00178 | ARF00179 | ARF00180 | ARF00181 | ARF00182 | ARF00183 | ARF00185 | ARF00186 | ARF00187 | ARF00188 | ARF00189 | ARF00190 | ARF00191 | ARF00192 | ARF00193 | ARF00194 | ARF00195 | ARF00196 | ARF00197 | ARF00198 | ARF00199 | ARF00200 | ARF00201 | ARF00202 | ARF00203 | ARF00204 | ARF00205 | ARF00206 | ARF00207 | ARF00208 | ARF00209 | ARF00210 | ARF00211 | ARF00212 | ARF00213 | ARF00214 | ARF00215 | ARF00216 | ARF00217 | ARF00218 | ARF00219 | ARF00220 | ARF00221 | ARF00222 | ARF00223 | ARF00224 | ARF00225 | ARF00226 | ARF00227 | ARF00228 | ARF00229 | ARF00230 | ARF00231 | ARF00232 | ARF00233 | ARF00234 | ARF00235 | ARF00236 | ARF00237 | ARF00238 | ARF00239 | ARF00240

ARF00001 Default broker name was inserted
Explanation

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

Action

No action is required for this informational message.


ARF00002 Broker Service must be provided
Explanation

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

Action

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


ARF00003 Cannot enter a GFB if a format buffer is in use
Explanation

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.

Action

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


ARF00004 Cannot save in read-only mode
Explanation

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.

Action

Edit the definition and try again.


ARF00006 Description must not be blank
Explanation

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

Action

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


ARF00007 Do not select blank entries
Explanation

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

Action

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


ARF00008 Duplicate entry not allowed
Explanation

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.

Action

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


ARF00009 Entire Broker ID must be provided
Explanation

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

Action

Supply a valid webMethods EntireX ID.


ARF00010 Existing Destination Updated
Explanation

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

Action

No action is required for this informational message.


ARF00011 Invalid name
Explanation

An invalid name was supplied.

Action

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


ARF00012 Invalid selection character
Explanation

An invalid character was specified in the SEL column.

Action

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.


ARF00013 Invalid value
Explanation

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

Action

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


ARF00014 Invalid Architecture value (valid: 0-2)
Explanation

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

Action

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.


ARF00015 Invalid MAXOUTPUT value (valid: 32768-2147483647)
Explanation

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

Action

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.


ARF00016 Invalid Subtasks value (valid: 0-15)
Explanation

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

Action

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.


ARF00017 MQ Queue Name must be provided
Explanation

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

Action

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


ARF00018 Name is required
Explanation

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

Action

Specify a valid name for the definition.


ARF00019 Name must be provided
Explanation

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

Action

Specify a valid name for the definition.


ARF00020 New destination info added
Explanation

The destination definition has been successfully added.

Action

No action is required for this informational message.


ARF00021 New destination saved
Explanation

The destination definition has been successfully saved.

Action

No action is required for this informational message.


ARF00022 New GFB added
Explanation

The GFB definition has been successfully added.

Action

No action is required for this informational message.


ARF00024 Queue Manager Name must be provided
Explanation

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

Action

Supply a valid WebSphere MQ queue manager name.


ARF00025 Queue Name must be provided
Explanation

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

Action

Supply a valid WebSphere MQ queue name.


ARF00026 Service Class must be provided
Explanation

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

Action

Supply a valid webMethods EntireX service class name.


ARF00027 Service Name must be provided
Explanation

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

Action

Supply a valid webMethods EntireX service name.


ARF00028 Subscription not defined
Explanation

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

Action

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. When you create the subscription later on, the destination definition is automatically updated and the "pending" status is removed.


ARF00029 Subscription saved/updated
Explanation

The subscription definition was successfully updated and saved.

Action

No action is required for this informational message.


ARF00030 Subscription Name is required
Explanation

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.

Action

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. When you create the subscription later on, the destination definition is automatically updated and the "pending" status is removed.


ARF00031 Subscription name must not be blank
Explanation

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

Action

Specify a valid subscription name.


ARF00032 There are currently no SFILEs - Press PF4 to add
Explanation

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

Action

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


ARF00033 Zero entry not allowed
Explanation

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.

Action

Specify a valid database ID or file number.


ARF00034 PFnn not defined
Explanation

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

Action

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


ARF00035 Cannot enter a format buffer if GFB is in use
Explanation

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.

Action

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


ARF00036 GFB is not defined
Explanation

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

Action

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


ARF00038 Duplicate destinations not allowed
Explanation

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.

Action

Specify a unique destination definition name.


ARF00041 Missing or invalid destination flags
Explanation

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.

Action

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


ARF00043 Invalid DBID value
Explanation

An invalid database ID was specified in an SFILE definition.

Action

Specify a valid database ID.


ARF00044 Invalid FILE value
Explanation

An invalid file number was specified in an SFILE definition.

Action

Specify a valid file number.


ARF00045 Default info updated
Explanation

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

Action

No action is required for this informational message.


ARF00046 GFB not saved
Explanation

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

Action

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


ARF00047 IQUEUE definition deleted
Explanation

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

Action

No action is required for this informational message.


ARF00048 Subscription deleted
Explanation

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

Action

No action is required for this informational message.


ARF00049 IQUEUE definition updated
Explanation

The IQUEUE definition was successfully updated.

Action

No action is required for this informational message.


ARF00050 IQUEUE definition saved
Explanation

The IQUEUE definition was successfully saved.

Action

No action is required for this informational message.


ARF00051 Initial State definition deleted
Explanation

The initial-state definition was successfully deleted.

Action

No action is required for this informational message.


ARF00052 Initial-State definition saved
Explanation

The initial-state definition was successfully saved.

Action

No action is required for this informational message.


ARF00053 Initial-State definition updated
Explanation

The initial-state definition was successfully updated.

Action

No action is required for this informational message.


ARF00054 SFILE deleted
Explanation

The SFILE definition was successfully deleted.

Action

No action is required for this informational message.


ARF00055 Select A,I or enter selection criteria
Explanation

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.

Action

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.


ARF00056 "I" Field must be blank for selection criteria
Explanation

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.

Action

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


ARF00057 IDBID cannot be zero
Explanation

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

Action

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


ARF00058 IFile cannot be zero
Explanation

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

Action

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


ARF00059 Object not copied - Already exists
Explanation

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

Action

Specify a new unique definition name when copying definitions.


ARF00060 Destination of another type and same name exists
Explanation

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

Action

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


ARF00061 Input DBID must be 1-65535
Explanation

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

Action

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


ARF00062 Target DBID must be 1-65535
Explanation

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

Action

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


ARF00063 Input DBID/FNR and target DBID/FNR cannot be the same
Explanation

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.

Action

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


ARF00064 Destination does not exist
Explanation

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

Action

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


ARF00065 MESSAGE number NOT FOUND
Explanation

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

Action

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.


ARF00066 Invalid message number
Explanation

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

Action

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.


ARF00067 DBID/FNR is not a valid Replicator file
Explanation

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

Action

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


ARF00068 Existing resend buffer updated
Explanation

The resend buffer definition was successfully updated.

Action

No action is required for this informational message.


ARF00069 Invalid buffer size (VALID: 32-2097151)
Explanation

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

Action

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


ARF00070 Invalid buffer name
Explanation

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

Action

Specify the name of a previously defined resend buffer definition.


ARF00071 Resend buffer definition does not exist
Explanation

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

Action

Specify the name of a previously defined resend buffer definition.


ARF00072 Subscription no longer available
Explanation

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

Action

Try saving it again.


ARF00073 Subscription already exists, cannot save
Explanation

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

Action

Specify a unique name for each subscription definition you define.


ARF00074 New resend buffer saved
Explanation

The resend buffer definition has been successfully saved.

Action

No action is required for this informational message.


ARF00075 GFB replaced
Explanation

The GFB definition was successfully altered and saved.

Action

No action is required for this informational message.


ARF00076 Invalid Message Limit value (valid: 3-2147483647)
Explanation

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

Action

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


ARF00077 GFB is used by subscription name -- Not deleted
Explanation

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

Action

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.


ARF00078 Subscription name cannot be changed
Explanation

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.

Action

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.


ARF00079 Invalid num of concurrent requests - (valid 1-2147483647)
Explanation

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

Action

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


ARF00080 Invalid Message Interval value - (valid 1-2147483647)
Explanation

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

Action

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


ARF00083 Subscription not deleted --- Used by Initial State name
Explanation

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.

Action

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


ARF00084 Subscription not deleted --- Used by Destination name
Explanation

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.

Action

Delete the destination definition prior to deleting the subscription.


ARF00085 Destination not deleted --- Used by subscription name
Explanation

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.

Action

Delete the subscription definition prior to deleting the destination.


ARF00086 Destination not deleted --- Used by Initial State name
Explanation

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.

Action

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


ARF00087 GFB not deleted --- Used by subscription name
Explanation

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.

Action

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


ARF00088 LFILE allocation error
Explanation

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

Action

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


ARF00089 Natural error eeee occurred at line nnnn of program pppppppp
Explanation

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.

Action

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


ARF00090 Cannot save due to syntax errors
Explanation

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

Action

Correct the parameters and try to save the definition again.


ARF00091 Filter not allowed if using UES conversion
Explanation

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

Action

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


ARF00092 Input FILE must be 1-5000
Explanation

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

Action

Specify a valid file number for the Input File field.


ARF00093 Target FILE must be 1-5000
Explanation

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

Action

Specify a valid file number for the Target File field.


ARF00101 A maximum of n entries can be selected
Explanation

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

Action

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


ARF00102 Transaction filter name does not exist
Explanation

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.

Action

Try saving the transaction filter definition again.


ARF00103 Transaction filter name cannot be changed
Explanation

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.

Action

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.


ARF00104 No value allowed if target field empty
Explanation

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

Action

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


ARF00105 Invalid record for filter name in linenumber
Explanation

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.

Action

Try saving the transaction filter definition again.


ARF00106 Value length 0 or exceeds 254
Explanation

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

Action

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


ARF00107 Transaction filter saved/updated
Explanation

The transaction filter definition was successfully updated and saved.

Action

No action is required for this informational message.


ARF00108 Only one value allowed for condition
Explanation

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.

Action

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


ARF00109 Odd number of quotation marks
Explanation

A syntactical error exists in the transaction filter definition.

Action

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.


ARF00110 Transaction filter deleted
Explanation

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

Action

No action is required for this informational message.


ARF00111 Transaction filter not deleted --- Used by subscription name
Explanation

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.

Action

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


ARF00112 Quotation marks in strings have to be doubled
Explanation

A syntactical error exists in the transaction filter definition.

Action

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.


ARF00113 Invalid Adabas field name
Explanation

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.

Action

Correct the field name.


ARF00114 Possible condition values: EQ, NE, LT, LE, GT or GE
Explanation

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

Action

Correct the condition value.


ARF00115 Transaction filter not saved
Explanation

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

Action

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


ARF00116 New Transaction filter added
Explanation

The transaction filter definition has been successfully added.

Action

No action is required for this informational message.


ARF00117 Transaction filter replaced
Explanation

The transaction filter definition was successfully altered and saved.

Action

No action is required for this informational message.


ARF00118 Enter either a target field or a value
Explanation

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

Action

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


ARF00119 Number of conditions exceeds 2500 at line number of program name
Explanation

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.

Action

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


ARF00120 Total value length exceeds 2000
Explanation

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.

Action

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


ARF00121 You must create the AI format buffer first
Explanation

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.

Action

Provide an after image format buffer first.


ARF00122 AI and BI buffers must be identical
Explanation

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.

Action

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


ARF00123 No object found
Explanation

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

Action

Check the entity and name specifications and try again.


ARF00124 Cannot save with errors present
Explanation

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

Action

Correct the errors and try again.


ARF00125 AI GFB must be entered first
Explanation

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

Action

Define the after image GFB first.


ARF00126 Transaction Filter is not defined
Explanation

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

Action

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


ARF00127 Cannot mix local and global format buffers
Explanation

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

Action

Do not mix local and global format buffers.


ARF00128 BI format buffer must be deleted first
Explanation

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

Action

Delete the before image format buffer first.


ARF00130 Maximum length of parameter-name is nnn characters
Explanation

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.

Action

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.


ARF00131 Resend buffer definition deleted
Explanation

The resend buffer definition was successfully deleted.

Action

No action is required for this informational message.


ARF00132 Format buffer generated successfully
Explanation

The Predict function has been completed successfully.

Action

No action is required for this informational message.


ARF00133 Required Predict version: 4.4.1; installed: vrsp
Explanation

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.

Action

Verify your environment and install the required version of Predict.


ARF00134 Global Format Buffer name must not be blank
Explanation

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.

Action

Specify a valid global format buffer name.


ARF00135 Format Buffer must be provided
Explanation

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

Action

Supply a format buffer and try again.


ARF00136 LFILE has not been set
Explanation

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

Action

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


ARF00137 LFILE has been set successfully
Explanation

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

Action

No action is required for this informational message.


ARF00138 Replicator system file not found
Explanation

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.

Action

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


ARF00139 Replicator system file must be available to continue
Explanation

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.

Action

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


ARF00140 Field field-name (Adabas short name) already defined as primary key
Explanation

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

Action

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


ARF00141 Resulting format buffer is empty
Explanation

The generated format buffer does not contain any field.

Action

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


ARF00142 Predict Generation Information unlinked
Explanation

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

Action

No action is required for this informational message.


ARF00143 Replicator system file not available - RSP=148
Explanation

Adabas response code 148 (ADARSP148) 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.

Action

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


ARF00144 Database ID deleted
Explanation

The database ID entry was successfully deleted.

Action

No action is required for this informational message.


ARF00145 GFB deleted
Explanation

The GFB entry was successfully deleted.

Action

No action is required for this informational message.


ARF00146 Possible values are ...
Explanation

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

Action

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


ARF00147 Replay process initiated - Token=nnnnn
Explanation

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

Action

No action is required for this informational message.


ARF00148 Insufficient space in the replication pool
Explanation

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

Action

Increase the size of the LRPL parameter and try again.


ARF00149 Replay request for undefined database
Explanation

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

Action

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


ARF00150 Invalid (undefined/outdated) replay token
Explanation

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

Action

Specify a valid replay token.


ARF00151 Requested replay in conflict with existing replay
Explanation

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

Action

Request replay processing for a different DBID and file number.


ARF00152 DATE/TIME format or value incorrect
Explanation

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

Action

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


ARF00153 Incorrect replay parameters
Explanation

The specified replay parameters are incorrect.

Action

Check and correct the replay parameters and try again.


ARF00154 Replay destination without SLOG closed
Explanation

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

Action

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


ARF00155 Invalid replay status transition
Explanation

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

Action

Notify your Software AG technical support representative.


ARF00156 Response nnn Subcode nnn Received from replicator
Explanation

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

Action

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


ARF00158 Subscription is required
Explanation

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

Action

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


ARF00159 Initial-State name is required
Explanation

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

Action

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


ARF00160 Initial-State definition not found
Explanation

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

Action

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


ARF00161 Initial-State subscription does not match screen
Explanation

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

Action

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


ARF00162 Initial-State DBID/FNR does not match screen
Explanation

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.

Action

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


ARF00163 Subscription does not contain a valid AI GFB
Explanation

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.

Action

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


ARF00164 Subscription not found
Explanation

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

Action

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


ARF00165 GFB not found
Explanation

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

Action

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


ARF00166 GFB does not contain field table
Explanation

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.

Action

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.


ARF00167 Request successful
Explanation

The Event Replicator Target Adapter request was successfully submitted.

Action

No action is required for this informational message.


ARF00168 Response code nnn subcode nnn received from request
Explanation

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

Action

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


ARF00169 A timeout occurred while running Synchronized Replay
Explanation

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.

Action

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


ARF00171 There is insufficient space in the nucleus pool
Explanation

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

Action

Increase the LRPL size of the nucleus and try again.


ARF00172 Subscription specified in a status request is undefined
Explanation

The subscription specified in a status request is undefined.

Action

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


ARF00173 The initial-state name specified was not found
Explanation

The specified initial-state name was not found.

Action

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


ARF00174 End date must be greater than start date
Explanation

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

Action

Correct the dates and try again.


ARF00175 End time must be greater than start time
Explanation

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

Action

Correct the times and try again.


ARF00178 Destination name not found
Explanation

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

Action

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


ARF00179 Subscription name not found
Explanation

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

Action

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


ARF00180 Destination is not active
Explanation

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

Action

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


ARF00181 Subscription not active
Explanation

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

Action

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


ARF00182 File is not active
Explanation

The file requested for replay processing is not active.

Action

Activate the file. Then try again.


ARF00183 No files for subscription
Explanation

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

Action

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


ARF00185 Destination does not receive data
Explanation

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.

Action

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


ARF00186 Subscription does not reference any destination
Explanation

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

Action

Complete the subscription definition and try again.


ARF00187 Data from file does not flow to any destination
Explanation

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.

Action

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


ARF00188 No data flow for destination
Explanation

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

Action

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


ARF00189 Input queue with same name already exists
Explanation

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

Action

Change the input queue definition name and try again.


ARF00190 PLOG records deleted
Explanation

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

Action

No action is required for this informational message.


ARF00191 Duplicate destinations not allowed
Explanation

A replay request included duplicate destination names.

Action

Review the destinations you specified and remove the duplicates.


ARF00192 Duplicate subscriptions not allowed
Explanation

A replay request included duplicate subscription names.

Action

Review the subscriptions you specified and remove the duplicates.


ARF00193 Restart RPL Usage must be less than Maximum RPL Usage
Explanation

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

Action

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


ARF00194 File-related info not deleted --- Used by Initial-State is-def
Explanation

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.

Action

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


ARF00195 IDBID/IFILE deleted
Explanation

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

Action

No action is required for this informational message.


ARF00196 Start Date/Time must be less than or equal to From Date/Time
Explanation

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

Action

Correct the times and try again.


ARF00197 Destination Class must be present to enter data
Explanation

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.

Action

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


ARF00198 GFB must be generated by Predict
Explanation

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 .

Action

Supply a GFB that was generated by Predict.


ARF00199 Initial-State not found
Explanation

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

Action

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


ARF00200 Only type I (ISN) files can be edited
Explanation

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.

Action

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


ARF00201 You must enter data before submitting
Explanation

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.

Action

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.


ARF00202 Entered ISN data is not contiguous
Explanation

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.

Action

Remove any blanks from the ISN list.


ARF00203 Invalid characters in ISN data
Explanation

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.

Action

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

ARF00204 Unbalanced parentheses
Explanation

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

Action

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.


ARF00205 Two values are required for a range
Explanation

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

Action

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.


ARF00206 Comma missing after range
Explanation

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

Action

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

ARF00207 ISN ranges must be in ascending order
Explanation

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.

Action

Correct the ISN range specification.


ARF00208 Initial-state name not found
Explanation

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

Action

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


ARF00209 Wrong ISN list
Explanation

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

Action

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.


ARF00210 Selection data not allowed for type A initial-state
Explanation

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

Action

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


ARF00211 Initial-State request received after ADAEND or HALT
Explanation

An initial-state request was issued to an 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.

Action

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


ARF00212 Num of concurrent initial-state requests exceeded
Explanation

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

Action

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


ARF00213 ISN entry too long
Explanation

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.

Action

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


ARF00214 Data missing after last comma
Explanation

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.

Action

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.


ARF00215 Values cannot be specified for METHOD=ISN
Explanation

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.

Action

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.


ARF00216 Do not specify both "*" and destination names
Explanation

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.

Action

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.


ARF00217 Do not specify both "*" and subscription names
Explanation

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.

Action

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.


ARF00218 Value buffer length must be entered
Explanation

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.

Action

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


ARF00219 Duplicate source DBID/FILE combinations are not allowed
Explanation

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

Action

Remove the duplicate.


ARF00220 Only valid entries can be marked
Explanation

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

Action

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


ARF00221 Duplicate DBid and File exist -- invalid {add|change}
Explanation

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.

Action

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


ARF00222 Request rejected, a related file is not active
Explanation

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.

Action

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.


ARF00223 Only the first {destination|subscription} may have an asterisk
Explanation

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

Action

Correct your specifications.


ARF00224 Asterisk is only allowed in the first cell
Explanation

Only the first entry may contain an asterisk.

Action

Correct your specifications.


ARF00225 Predict not available for edit
Explanation

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

Action

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.


ARF00226 Destination destname does not exist in a subscription
Explanation

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

Action

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.


ARF00227 Destination destname in subsc subsname does not send i-s data
Explanation

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

Action

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.


ARF00228 Subsc subsname has no matching dest in i-s dest list
Explanation

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

Action

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


ARF00229 Subsc subsname has no i-s data flow for dest destname
Explanation

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

Action

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.


ARF00230 User exit required when Replicate for Delete = U
Explanation

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.

Action

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


ARF00231 Dest. found in Subsc. subsname w/o matching DBid dbid File fn
Explanation

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.

Action

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


ARF00232 xxxxxx begin + length > 32767
Explanation

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.

Action

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


ARF00233 Replic.for fx=N invalid when Replic.security file=Y
Explanation

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.

Action

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


ARF00234 Incl.Identical Records=N invalid when Replic.security file=Y
Explanation

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.

Action

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


ARF00235 Default Code=nnnn invalid when Replic.security file=Y
Explanation

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.

Action

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


ARF00236 Subscription user exit invalid when Replic.security file=Y
Explanation

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.

Action

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


ARF00237 Transaction filter invalid when Replic.security file=Y
Explanation

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.

Action

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


ARF00238 FBs or GFBs are invalid when Replic.security file=Y
Explanation

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.

Action

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


ARF00239 Format buffer exceeds length of 32756, is = nnnnn
Explanation

A Predict global format buffer (a generated GFB) is exceeding the maximum length of 32756, and will be trunicated. The length of the format buffer is given in the message (nnnnn).

Action

Modify the GFB to fit the maximum length.


ARF00240 No flow for dbid/fnr xxxxx yyyyy in is-subscr
Explanation

A verification process has found that the subscription specified by the the initial-state definition (is-subscr) does not have a correct definition for the DBID/file number combination (xxxxx/yyyyy) given in the message.

Action

Correct the initial-state, destination, or subscription definitions and try again.


Top of page