You can set the following global values in the Replicator system file using the Event Replicator Administration screens.
To set global values in the Replicator system file using the
Event Replicator Administration:
Select an Event Replicator Server in tree-view as described in Selecting Event Replicator Databases.
Click on Replication Definitions in tree-view under the selected database.
A table listing the global value settings in the Replicator system file appears in detail-view.
Click on the button at the bottom of the detail-view.
The global value parameters you can modify become editable in detail-view.
Update the global parameters in detail-view as described in the following table.
| Parameter Name | Specify | Default |
|---|---|---|
| Subtask (SUBTASKS parameter) | The number of subtasks in the Event Replicator Server. | 0 |
| Maximum Output Size (MAXOUTPUTSIZE parameter) | The maximum output message size for the Event Replicator for Adabas.
The minimum value you can specify for this field is 32768.
This parameter may be specified in bytes or it may be specified with the suffix K to indicate kilobytes. The maximum value is 2,147,483,647 bytes. The practical maximum is limited by the region size of the Event Replicator Server. One output buffer is acquired for each output task. |
32768 |
| EntireX Broker Stub Name (ETBBROKERNAME parameter) | The default webMethods EntireX Broker stub name to be used by the Event Replicator Server if no other name is specified. webMethods EntireX Broker is a component of webMethods EntireX. | BKIMBTSO |
| Input Request Message Limit (IRMSGLIMIT parameter) | The maximum number of input request error messages issued by the Event Replicator Server during the interval set by the Input Request Message Interval field (also on this screen). | 3 |
| Input Request Message Interval (IRMSGINTERVAL parameter) | The interval during which the message limit specified by the Input Request Message Limit field applies. | 1 |
| Verify Mode (VERIFYMODE parameter) | Whether the Event Replicator for Adabas should run in verify (test) mode or not. Valid values are "Yes" (run in verify mode) or "No" (do not run in verify mode). | No |
| Format Buffer Validation (FBVALIDATION parameter) | Indicates the level of format buffer validation
that should occur for subscriptions. Valid values are a blank,
"Abort Reptor...", "Deactivate
subscription and print warning", "no initial format
buffer validation", or "Print warning
message".
|
no initial format buffer validation |
| Record PLOG Information (RECORDPLOGINFO parameter) | Indicates whether or not PLOG information is
saved in the Replicator system file. Valid values are
"Yes" (store the information) or
"No" (do not store the information).
Note: |
No |
| Retry Count (RETRYCOUNT parameter) |
The default number of times that an attempt to open a destination or input queue will be attempted at the interval specified by the Retry Interval parameter. This is the equivalent of specifying the RETRYCOUNT parameter in the Event Replicator Server startup job. Valid values range from 0 through 2,147,483,647. A value of zero indicates that no retry processing should occur for any affected destinations. |
10 |
| Retry Interval (RETRYINTERVAL parameter) |
The default number of seconds between retry attempts that will be performed for any destination or input queue for which no specific retry interval has been specified. This is the equivalent of specifying the RETRYINTERVAL parameter in the Event Replicator Server startup job. Valid values range from 0 through 2,147,483,647. A value of zero indicates that no retry processing should occur for any affected destinations. |
0 |
| Maximum Decompress Record Length (MAXRECORDSIZE parameter) | The maximum length (in bytes) of any
decompressed record that can be processed by the Event Replicator Server. This is the
equivalent of specifying the MAXRECORDSIZE parameter directly in the
startup job.
The minimum value you can specify for this field is 1. For an Event Replicator Server running with Adabas 7, the maximum value that can be specified for MAXRECORDSIZE is 32,767 bytes. However, in Adabas 8 systems, this limit has been lifted; the size of a decompressed record may be much larger than 32,767 bytes. Therefore, for an Event Replicator Server running with Adabas 8, the maximum value that can be specified for MAXRECORDSIZE is the larger of either 32,767 bytes or 50% of the setting of the ADARUN LRPL parameter. |
32,767 bytes |
| Maximum Variable Record Length (MAXVARRECORDSIZE parameter) | The maximum length (in bytes) of variable
decompressed records that can be processed by the Event Replicator Server. This is the
equivalent of specifying the MAXVARRECORDSIZE parameter directly in
the startup job.
The value specified for MAXVARRECORDSIZE must be less than or equal to the setting of the MAXRECORDSIZE setting. The minimum value you can specify for this field is 1. For an Event Replicator Server running with Adabas 7, the maximum value that can be specified for MAXRECORDSIZE or MAXVARRECORDSIZE is 32,767 bytes. However, in Adabas 8 systems, this limit has been lifted; the size of a decompressed record may be much larger than 32,767 bytes. Therefore, for an Event Replicator Server running with Adabas 8, the maximum value that can be specified for MAXRECORDSIZE or MAXVARRECORDSIZE is the larger of either 32,767 bytes or 50% of the setting of the ADARUN LRPL parameter. |
32,767 bytes |
| Subtask Activation Wait Time(SUBTASKWAIT parameter) | The number of seconds that can be used to override the default time to wait for a subtask to finish initialization and activate. Valid values are from 1 to 3600 seconds. This is the equivalent of specifying the SUBTASKWAIT parameter in the Event Replicator Server startup job. | 60 |
| Log Input Transactions (LOGINPUTTRANSACTION parameter) | Whether or not the Event Replicator should use its SLOG
system file as a temporary storage location for incoming compressed replication
transactions, before they are queued for processing. Once transactions have
been written to the SLOG system file, the Event Replicator Server processes them using a
throttling mechanism so that only a limited amount of Event Replicator Server replication pool
space is used at a time. Valid values are ALL (indicating that input
transactions will always will be written to the SLOG system file), NO (the
default, indicating that input transaction will not be written to the SLOG
system file, or an integer in the range from 1 to 99. The integer setting
specifies a threshold percentage of the LRPL (Event Replicator Server replication pool space)
that can be used before triggering the writing of input transaction to the SLOG
system file.
This is the equivalent of specifying the LOGINPUTTRANSACTION directly in the Event Replicator Server startup job. |
All |
| Global OPEN Value(GOPEN parameter) | Indicates whether or not destinations with
Open at Start (DOPEN) set to
"Global" in their definitions should be opened at
Event Replicator Server startup. This parameter specifies the global policy for determining
whether destinations with Opened at Start set
to "Global" are opened at Event Replicator Server startup. Valid
values are "Yes" or "No",
with "Yes" as the default.
When this parameter is set to "Yes", any destinations with Opened at Start set to "Global" in their definitions are opened at Event Replicator Server startup. When this parameter is set to "No", any destinations with Opened at Start set to "Global" in their definitions are not opened at Event Replicator Server startup. This is the equivalent of specifying the GOPEN directly in the Event Replicator Server startup job. |
Yes |
| Maximum RPL Usage (TLMAX parameter) | The maximum percentage of the Event Replicator replication pool that can be used for transaction log (TLOG) processing. Valid values range from "0" through "100". | 40 |
| Restart RPL Usage (TLRESTART parameter) | The amount of available Event Replicator replication pool storage that must be available before transaction logging (TLOG logging) can restart. Valid values range from "0" through "99". | 50 |
| Input Queue Level (TLINPUT parameter) | The level of transaction logging that should occur when a transaction is taken off the input queue and put on the transaction assignment queue. Valid values are "no logging", "log event and input transaction data", "log event, input transaction, and file/ record data", or "log event and all available input information for the event". | no logging |
| No Match Level (TLNOSUB parameter) | The level of transaction logging that should occur when a transaction is not queued to any subscription in Event Replicator. Valid values are "no logging", "log event and input transaction data", "log event, input transaction, and file/record data", or "log event and all available input information for the event". | no logging |
| Queue Completion Level (TLQCOMP parameter) | The level of transaction logging that should occur prior to a transaction being assigned to the completion queue. Valid values are "no logging", "log event and input transaction data", "log event, input transaction, and file/record data", or "log event and all available input information for the event". | no logging |
| Completion Level (TLCOMP parameter) | The level of transaction logging that should occur when a transaction has been fully processed and Adabas has been informed that the transaction was successfully replicated. Valid values are "no logging", "log event and input transaction data", or "log event, input transaction, and file/record data". | no logging |
| Request Received Level (TLREQRECV parameter) | The level of transaction logging that should occur when a user request has been received. Valid values are "no logging", "log event but no data", or "log event and the entire input buffer before and after translation if appropriate". | no logging |
| Request Rejected Level (TLREQREJECT parameter) | The level of transaction logging that should occur when a user request is rejected due to an error in interpreting the request. Valid values are "no logging", "log event but no data", or "log event, error code, and entire input buffer". | no logging |
| Request Error Level (TLREQERR parameter) | The level of transaction logging that should occur when a user request is rejected due to an error in carrying out the request. Valid values are "no logging", "log event and URBS", "log event and URBI", or "log event, URBS, and URBI". | no logging |
| Status Request Level (TLSTATUS parameter) | The level of transaction logging that should occur when a user request for status on an Event Replicator resource has been processed. Valid values are "no logging", "log event and URBS", "log event and URBI", or "log event, URBS, and URBI". | no logging |
| I-State Start Request Level (TLISTATE parameter) | The level of transaction logging that should occur when a user request for initial-state information for a file has started. Valid values are "no logging", "log event and URBS", "log event and URBI", or "log event, URBS, and URBI". | no logging |
| I-State Completion Level (TLISTATECOMP parameter) | The level of transaction logging that should occur when an initial-state information request has completed. Valid values are "no logging", "log event and URBS", "log event and URBI, if available", or "log event, URBS, and URBI, if available". | no logging |
| Retransmit Request Level (TLRETRANS parameter) | The level of transaction logging that should occur when a user request to retransmit a specific transaction has been processed. Valid values are "no logging", "log event and URBS", "v", or "log event, URBS, and URBI". | no logging |
When all specifications have been made to your satisfaction, click to save the global values or click to cancel your updates..
