To use Event Replicator for Adabas and customize its processing, you must supply various replication definitions. These definitions can be specified in two ways:
Specified as initialization parameters, which are read from the DDKARTE statements of the Event Replicator Server startup job. For more information, read this document.
Read from the Replicator system file at Event Replicator Server startup. The definitions are maintained in the Replicator system file using the Adabas Event Replicator Subsystem, the provided online menu-driven interface. For more information, read Using the Adabas Event Replicator Subsystem.
Note:
If you use a Replicator system file to store your replication
definitions, you can also use the RPLREFRESH command to refresh resource
definitions in your Event Replicator Server configuration while the
Event Replicator Server is still running. For more information, read
RPLREFRESH
Command.
You can elect to use one or both methods, depending on what works best for you. The method used is controlled by ADARUN parameter RPLPARMS.
This document describes the initialization parameters you can specify in the DDKARTE statements of the Event Replicator Server startup job. Each input record read from DDKARTE must start with the characters ADARPD. In addition, be sure to follow the conventions described in Conventions, when using these initialization parameters.
MAXRECORDSIZE (Maximum Decompressed Record Length) Parameter
MAXVARRECORDSIZE (Maximum Variable Decompressed Record Length) Parameter
By default, Event Replicator for Adabas attempts to connect with any Adabas database encountered during an Event Replicator Server session. You may, however, prefer to control these connection attempts using an Adabas database connection definition. This section describes the syntax and parameters of database connection definitions.
DATABASE ID=dbid
[DBCONNECT={YES|NO}]
This section covers the following DATABASE parameters and subparameters:
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| ID | the database ID of an Adabas database for which you want to control connection attempts. | numeric; 1-65,535 | none |
By default, the Event Replicator Server attempts to connect to every Adabas database it encounters. If you would like to control these connection attempts, use this parameter and a corresponding DBCONNECT parameter.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Database ID parameter in Controlling Connections to Adabas Databases.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DBCONNECT | whether or not the Event Replicator Server specified in the preceding DATABASE parameter should initiate an attempt to connect to the Adabas database at Event Replicator Server startup. | "YES" or "NO" | YES |
If you specify DBCONNECT=YES, the
Event Replicator Server will initiate an attempt to connect to the Adabas
database identified by the preceding DATABASE parameter after the
Event Replicator Server starts.
If you specify DBCONNECT=NO, the
Event Replicator Server will not initiate an attempt to connect to the
Adabas database identified by the preceding DATABASE parameter. The database may
connect with the Event Replicator Server at some point, but the
Event Replicator Server will not initiate the connection at
Event Replicator Server startup.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Connect parameter in Controlling Connections to Adabas Databases.
In the following example, the Event Replicator Server will not initiate a connection to Adabas database 203.
ADARPD DATABASE ID=203 ADARPD DBCONNECT=NO
In the following example, the Event Replicator Server will initiate a connection to Adabas database 203, but not to database 204.
ADARPD DATABASE ID=203,DBCONNECT=YES ADARPD DATABASE ID=204,DBCONNECT=NO
[DBID=dbid]
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DBID | a default database ID. | numeric; 1-65,535 | none |
A default database ID may be specified. The default value is used when subscription-related parameter SFDBID is not specified for a combination of subscription and file.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Replicator Server DBID field in Changing the Event Replicator Server and Replicator System File.
[DBID=database-ID]
The Event Replicator Server supports the following destination types: Adabas, EntireX Broker, File, WebSphere MQ, or Null. Different subparameters are used with the NAME parameter, depending on the destination type.
DESTINATION NAME=destination-name
[DACTIVE={YES|NO}]
[DCLASS=name]
[DCLASSPARM=parmdata]
[DCOMMITTHRESHOLD=5]
[DEXIT=name]
[DEXITWORKSIZE=size]
[DLOG={YES|NO}]
[DMAXOUTPUTSIZE|\=n[K]]
[DOPEN={YES|NO|GLOBAL}]
[DREPLICATEUTI={YES|NO}]
[DRETRYCOUNT={n|GLOBAL}]
[DRETRYINTERVAL={n|GLOBAL}]
[DTLASSIGN={0|1|2|3 }]
[DTLCOMP={0|1|2|3 }]
[DTLSLOGREAD={0|1|2|3 }]
[DTLSLOGWRITE={0|1|2|3 }]
DTYPE={ADABAS|ETBROKER|FILE|MQSERIES|NULL}
The following additional parameter can be used or all destination types supported by Event Replicator for Adabas except Adabas destinations (DTYPE=ADABAS):
[DSTATLOG={YES|NO}]
The following additional parameters are used when DTYPE=ADABAS is used:
[DTLADABAS={0|1|2|3}]
[DAERROR={BACKOUT|ALTACTION|CLOSE}]
DAIFILE=input-file-number
DAIDBID=input-dbid
DATDBID=target-dbid
DATFILE=target-file-number
[DAREPLICATEUTI={YES|NO}]
[DATMETHOD={ISN|KEY}]
[DATKEYSB=search-buffer]
[DATKEYAIO=after-image-key-offset]
[DATKEYAIL=after-image-key-length]
[DATKEYBIO=before-image-key-offset]
[DATKEYBIL=before-image-key-length]
[DATKEYKYO=key-buffer-key-offset]
[DATKEYKYL=key-buffer-key-length]
The following additional parameters are used when DTYPE=ETBROKER is used:
[DARC=architecture-key] [DETBBROKERID=entire-broker-id] [DETBSERVICE=entire-broker-service] [DETBSERVICENAME=entire-broker-service-name] [DETBSERVICECLASS=entire-broker-service-class] [DETBSCONV={YES|NO}] [DETBTOKEN=entire-broker-token] [DETBUSERID=entire-broker-userid] [DEVENTLOG={YES|NO}] [DHBINTERVAL=n] [DQFULLDELAY={n|GLOBAL}]
The following additional parameters are used when DTYPE=MQSERIES is used:
[DARC=architecture-key] [DEVENTLOG={YES|NO}] [DHBINTERVAL=n] [DMQQMGRNAME=mqseries-queue-manager-name] [DMQQNAME=mqseries-queue-name] [DMQDYNQNAME=mqseries-dynamic-queue-name] [DMQFORMAT=format] [DMQCCSID=ccsid] [DQFULLDELAY={n|GLOBAL}]
Note:
If you are running on z/OS using IBM WebSphere MQ Series
definitions for your Event Replicator DESTINATION or IQUEUE definitions,
a S0D3 abend can occur if you run it as a started task and specify the
parameter REUSASID=YES. This is a documented IBM WebSphere MQ Series
issue.
The following additional parameters are used when DTYPE=FILE is used:
[DEVENTLOG={YES|NO}]
The following additional parameters are used when DTYPE=NULL is used:
[DARC=architecture-key
[DEVENTLOG={YES|NO}]
[DHBINTERVAL=n]
This section covers the following topics:
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| NAME | the name of the output destination definition. | alphanumeric; 1-8 characters | none |
Parameter NAME is required and is used to uniquely identify an output destination definition. This value is only referenced within the Event Replicator Server. The value may be used when the Event Replicator Server writes a related message.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Destination Name parameter in Maintaining Destination Definitions. All destination definitions require a name, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DACTIVE | whether the destination should be activated at Event Replicator Server startup. | "YES" or "NO" | YES |
If "YES" is specified, the destination is marked as active at Event Replicator Server startup; if "NO" is specified, the destination is marked as inactive at Event Replicator Server startup (it is inactive).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Destination Active parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DAERROR | the action to be taken when an error occurs during replication to an Adabas destination. | "BACKOUT", "ALTACTION", or "CLOSE" | ALTACTION |
This parameter is valid only when the destination type is Adabas (DTYPE=ADABAS).
Additional actions are taken, based on the value of this DAERROR parameter. These actions are described in the following table:
| Value | Processing |
|---|---|
| ALTACTION | Processing continues with the next
update that is part of the same transaction. Some special processing occurs
when DAERROR=ALTACTION:
For other errors, the record is skipped. |
| BACKOUT | A message is issued indicating that the transaction will be backed out and then ignored. The current transaction is backed out and processing continues with the next transaction to be replicated. |
| CLOSE | A message is issued indicating that the transaction will be backed out and the destination will be closed. The current transaction is backed out and transaction logging (to the SLOG file) will begin, if defined for the destination. |
In all cases (ALTACTION, BACKOUT, and CLOSE), if response 148 is returned and the SLOG system file is available, the destination is closed.
If an insert, update, or delete operation fails because a replicated record already exists or does not exist, an appropriate message is issued. If the transaction fails because of an error, a message containing the two-character Adabas command, the database ID, the file number, the response code and the subcode is written. If the DATMETHOD parameter is set to ISN, the text "ISN" will be appended to this message as well as the ISN value. If the DATMETHOD parameter is set to "KEY", the record key will be written in both hexadecimal and readable formats in a separate message.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Error Action parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DAIDBID | an input database ID associated with a DAIFILE parameter. | numeric; 1-65,535 | none |
For each combination of parameters DAIDBID and DAIFILE, the related subscription must have the same combination of SFDBID and SFILE.
Combinations of parameters DAIDBID and DAIFILE must be unique within a single Adabas destination definition. This implies that the input from a database and file combination can only have a single Adabas target within a specific Adabas destination definition. If you want the input from a database and file combination to go to more than one Adabas target, define multiple Adabas destination definitions.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Input DBID parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DAIFILE | the number of an input file for an Adabas destination definition. | numeric file number | none |
Parameter DAIFILE must be specified at least once when the destination has DTYPE=ADABAS. Parameter DAIFILE may be specified one or more times for a destination with DTYPE=ADABAS. Sub-parameters (DAIDBID, DATDBID, and DATFILE) will be specified for each occurrence of DAIFILE.
For each combination of parameters DAIDBID and DAIFILE, the related subscription must have the same combination of SFDBID and SFILE.
Combinations of parameters DAIDBID and DAIFILE must be unique within a single Adabas destination definition. This implies that the input from a database and file combination can only have a single Adabas target within a specific Adabas destination definition. If you want the input from a database and file combination to go to more than one Adabas target, define multiple Adabas destination definitions.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Input File parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DARC | defines the data architecture for fields in the URB* control structures sent to a webMethods EntireX, WebSphere MQ, or NULL destination. | integer sum of byte order and encoding family (see below) | 2 (byte order 0 + encoding family 2) |
The DARC parameter value is the sum of the following numbers:
| Control Structure Element | Values | Description |
|---|---|---|
| Byte order (b) | 0 | High order byte first |
| 1 | Low order byte first | |
| Encoding Family (e) | 0 | ASCII encoding family |
| 2 | EBCDIC encoding family |
This parameter is not valid for file or Adabas destinations (DTYPE=FILE or DTYPE=ADABAS).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Architecture parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DAREPLICATEUTI | whether Adabas utility change replication should be activated for the target file in the Adabas destination at Event Replicator Server startup. | "YES" or "NO" | NO |
If "YES" is specified, utility replication is activated for the file in and Adabas destination at Event Replicator Server startup; if "NO" is specified, utility replication is not activated for the file.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Replicate Utility parameter in Creating an Adabas Destination Definition.
For more information about replicating utility functions, read Replicating Adabas Utility Functions.
Important:
This parameter is no longer used; it remains only for
compatibility with past versions of Event Replicator for Adabas.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DASUBSCRIPTION | an input subscription name associated with the destination with DTYPE=ADABAS. | subscription name | none |
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATDBID | the target database ID for replication of the input data. | numeric; 1-65,535 | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Target DBID parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATFILE | the target file for replication of the input data. | file name | none |
When DTYPE=ADABAS is specified for the destination, replicated data for the input subscription, input database, and input file number will be applied to the related target Adabas database ID and file number.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Target File parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATKEYAIL | the length (in bytes) of the key to be used in the after image of the data buffer. | 1-32,767 | none |
When the DATMETHOD parameter is set to KEY, this parameter is required. If the DATMETHOD parameter is set to ISN, this parameter may not be specified.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the After Image Key Length parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATKEYAIO | the offset (in bytes) of the key to be used in the after image of the data buffer. | 0 - 2,147,483,646 | 0 |
This optional parameter can only be set if the DATMETHOD parameter is set to KEY; if the DATMETHOD parameter is set to ISN, this parameter may not be specified.
The sum of this parameter and the length of the key to be used in the after image (DATKEYAIL parameter), must be less than or equal to 2,147,483,647 bytes.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the After Image Offset parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATKEYBIL | the length (in bytes) of the key to be used in the before image of the data buffer. | 1-32,767 | none |
This optional parameter can only be set if the DATMETHOD parameter is set to KEY; if the DATMETHOD parameter is set to ISN, this parameter may not be specified.
If the DATKEYBIO parameter is specified, this parameter must also be specified with a value greater than zero.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Before Image Key Length parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATKEYBIO | the offset (in bytes) of the key to be used in the before image of the data buffer. | 0 - 2,147,483,646 | 0 |
This optional parameter can only be set if the DATMETHOD parameter is set to KEY; if the DATMETHOD parameter is set to ISN, this parameter may not be specified.
The sum of this parameter and the length of the key to be used in the before image (DATKEYBIL parameter), must be less than or equal to 2,147,483,647 bytes.
If this parameter is specified, the DATKEYBIL parameter must also be specified with a value greater than zero.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Before Image Offset parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATKEYKYL | the length (in bytes) of the key to be used in the before image of the primary key. | 1-32,767 | none |
This optional parameter can only be set if the DATMETHOD parameter is set to KEY; if the DATMETHOD parameter is set to ISN, this parameter may not be specified.
If the DATKEYKYO parameter is specified, this parameter must also be specified with a value greater than zero.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Key Length parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATKEYKYO | the offset (in bytes) of the key to be used in the before image of the primary key. | 0-32,767 | 0 |
This optional parameter can only be set if the DATMETHOD parameter is set to KEY; if the DATMETHOD parameter is set to ISN, this parameter may not be specified.
The sum of this parameter and the length of the key to be used in the before image (DATKEYKYL parameter), must be less than or equal to 32,767 bytes.
If this parameter is specified, the DATKEYKYL parameter must also be specified with a value greater than zero.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Key Offset parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATKEYSB | the name of a search buffer to be used for keyed replication. | up to 60 alphanumeric characters | none |
When the DATMETHOD parameter is set to KEY, this parameter is required. If the DATMETHOD parameter is set to ISN, this parameter may not be specified.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Search Buffer parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DATMETHOD | the method to be used when searching for a record on the target database. | "ISN" or "KEY" | ISN |
This parameter is valid only when the destination type is Adabas (DTYPE=ADABAS).
When DATMETHOD=KEY is specified, the subparameters DATKEYSB, DATKEYAIO, DATKEYAIL, DATKEYBIO, DATKEYBIL, DATKEYKYO, and DATKEYKYL may also be supplied to indicate where to find the key in the replicated data. All of these subparameters are optional except DATKEYSB and DATKEYAIL.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Replication Method parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DCLASS | the class type for this destination definition. | SAGTARG or SAGTRGB | none |
The DCLASS parameter specifies the destination class. There are two possible values for this parameter: SAGTARG or SAGTRGB. There is no default. You should chose one of these values if the output is to be sent to the Event Replicator Target Adapter for the destination.
When set to SAGTARG the output produced is in an XML format that can be processed by the Event Replicator Target Adapter. If it is set to SAGTRGB the output is in a binary raw data format that can be processed by the Event Replicator Target Adapter.
Otherwise, leave this parameter blank unless otherwise requested by a Software AG support representative.
Notes:
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Destination Class parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DCLASSPARM | up to 120 bytes of character data to be passed to the optional destination output user exit. | any character data | none |
The DCLASSPARM parameter specifies up to 120 bytes of character data to be passed to the optional destination output user exit.
DCLASSPARM cannot be specified for destinations with DTYPE=ADABAS or DTYPE=FILE and can only be specified if a value is set for the DCLASS or DEXIT parameters.
If either DCLASS=SAGTARG or DCLASS=SAGTRGB is
specified to invoke support for the Event Replicator Target Adapter, you may want to specify one or more
of the following keyword parameters:
Note:
These parameter keywords must be specified in uppercase.
- ADA
The ADA keyword is available for use with the
SAGTARGDCLASS exit.Specify the ADA keyword in the DCLASSPARM parameter if the target of the destination requires the Adabas 2-byte short name be included with the schema for all fields.
- NOSPRE
The NOSPRE keyword is available for use with both
SAGTARGandSAGTRGBDCLASS exits.Specify the NOSPRE keyword in the DCLASSPARM parameter if you do not want the subscription name to prefix the names of the tables produced by the Event Replicator Target Adapter. When NOSPRE is specified, the schema file name (Predict view name) alone is used for the table names; when NOSPRE is not specified, the subscription name prefixes the schema file name in the table names.
Note:
Oracle identifiers are limited to 30 characters. If NOSPRE is not specified and an Oracle RDBMS is used by the Event Replicator Target Adapter, the identifier names may exceed 30 characters and errors may occur. We recommend using NOSPRE if an Oracle RDBMS is also used.- SPRE
Specify the SPRE keyword in the DCLASSPARM parameter if you do want the subscription name to prefix the names of the tables produced by the Event Replicator Target Adapter.
The notation is
SPRE=xxxxxxxx. Wherexxxxxxxxcan be a subscription prefix to be used instead of the subscription name used in the job execution. The prefix can be 1 to 8 characters in size.The SPRE keyword is available for use with both
SAGTARGandSAGTRGBDCLASS exits.- OPTIONS
The OPTIONS keyword parameter can be used to specify options for the destination. Specify the OPTIONS keyword parameter, using the syntax
OPTIONS=nnnn. Possible values of the OPTIONS (nnnn) are listed in the following table. However, if you want to combine options, add their values together and enter the total value.For example, if you want to combine option 32 (to send the full image on an update) and option 64 (to set the XML transaction committed time value to local time instead of GMT/UTC), specify
OPTIONS=96(with 96 being the sum of 32 and 64).
Option Value Description 1 Specify OPTIONS=1to send the full image on an insert.2 Specify OPTIONS=2to indicate that long names should be used. This option will cause long names to be sent in place of the default short names used for various elements and attributes. Short names are the default and save on the amount of data being transferred. Long names make for better readability. For example, the short name <F> would appear as <Field> using long names.4 Specify OPTIONS=4to ensure that invalid XML characters found in alphanumeric fields are not translated to spaces.8 Specify OPTIONS=8to ensure that trailing blanks in alphanumeric fields are not removed.16 Specify OPTIONS=16to ensure that characters used by XML are not replaced automatically with predefined entity references. For example, ifOPTIONS=16is set, the ampersand (&) character would not be replaced with the literal "&".32 Specify OPTIONS=32to send the full image on an update. The full before image (if available) and after image of all fields are sent for an update, even if the field values were not changed or are null.Note:
This option is mutually exclusive with option 128. If both options are specified, thenOPTIONS=32will be set andOPTIONS=128ignored.64 Specify OPTIONS=64to set the XML transaction committed time value to local time instead of GMT/UTC.128 Specify OPTIONS=128if the before image is not to be included when a field is updated/changed if the before image data storage records are included. Primary field before images will still be included because the key is needed to find the record that is to be changed.Note:
This option is mutually exclusive with option 32. If both options are specified, thenOPTIONS=32will be set andOPTIONS=128ignored.256 Specify OPTIONS=256to suppress ARMXL004I information messages.- TRACE
The TRACE keyword parameter can be used to specify the contents of the trace. Specify the TRACE keyword parameter using the syntax
TRACE=nnnn. Possible values of the TRACE (nnnn) are listed in the following table. However, if you want to trace multiple control blocks, add their trace values together and enter the total value. For example, to trace the before and after images of the URBD control blocks, you would specifyTRACE=24because the sum of 8 (URBD control block before image) and 16 (URBD control block after image) is 24.Note:
If tracing is enabled using this keyword parameter, be sure to include the following JCL statement in the startup JCL of the Event Replicator Server://DDTRACE1 DD SYSOUT=XSettings for DCLASS=SAGTARG
Trace Value Description 1 Trace the URBS control block. 2 Trace the URBT control block. 4 Trace the URBR control block. 8 Trace the URBD control block before image. 16 Trace the URBD control block after image. 32 Trace the URBF/URBG control block before image. 64 Trace the URBF/URBG control block after image. 128 Trace the send buffer. 256 Trace the URBY control block. 512 Trace the URBO control block. 1024 Trace the output parameters. 2048 Trace the subscription table. Settings for DCLASS=SAGTRGB
Trace Value Description 1 Trace the output buffer. 2 Trace the URBD control block after image. 4 Trace the URBR control block. 8 Trace the URBT control block. 16 Trace the URBH control block. 32 Trace the URBF/URBG control block before image. 64 Trace the URBS control block. 128 Trace the URBY control block. 256 Trace the URBO control block. 512 Trace the URBD AI control blocks 1024 Trace the URBF/G AI control blocks 2048 Trace the subscription table.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Destination Class Parameter Data parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DCOMMITTHRESHOLD |
For destinations defined with DTYPE=ETBROKER, DTYPE=MQSERIES, or DTYPE=NULL, specify a threshold for the number of messages that will be sent to the destination before a commit is performed for those messages. For destinations defined with DTYPE=File, specify the number of URBLTDOD TLOG record bytes that will be written to the CLOG before the buffers are flushed. This parameter may not be specified for a destination defined with DTYPE=ADABAS. |
numeric, within the range 0 through 2,147,483,647 | 5 (except for File destinations) |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Threshold or Commit Threshold parameters in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
For webMethods EntireX, WebSphere MQ, and null destinations, the term commit in this context means that the Event Replicator Server informs the messaging system that all messages sent (since the last commit) should be made permanent. In the case of WebSphere MQ, commit means that the Event Replicator Server will issue an MQCMIT call for the queue.
The actual number of messages sent to the destination prior to the commit call will vary. The number of messages sent prior to the commit may be less than the DCOMMITTHRESHOLD value when all data queued to the destination has been sent. The number of messages sent prior to the commit may be greater than the DCOMMITTHRESHOLD value when a transaction's worth of replicated data must be sent in multiple messages. The commit will only be done after an entire transaction has been sent to the destination.
The replicated transactions occupy space in the Event Replicator Server's replication pool until the commit has been performed. If the commit threshold is set to a high value, the LRPL parameter also must be set to a sufficiently high value, so that the replication pool can accommodate the replicated transactions until they are committed.
The check on the threshold set for File destinations will only occur when a complete transaction has been written. The default value for this threshold is calculated using the following formula:
MAX(MIN(a,b),c)
where
a= 0.9 *
CLOG-block-size *
CLOG-blocks-per-track *
CLOG-tracks-per-cylinder
b= 0.05 *
LRPL-setting
c= The maximum URBL record size that can be written to the TLOG.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DETBBROKERID | defines the webMethods EntireX Broker ID. | up to 32 characters | none |
If this parameter is not specified, the default EntireX Broker ID (specified in parameter ETBBROKERID) will be used.
Broker IDs come in two formats: one for TCP/IP communications and one for Adabas SVC communications. For TCP/IP communications, the format is:
ip-address:port-number:TCP
In this case, the ip-address setting is the TCP/IP IP address and the port-number setting should match the webMethods EntireX PORT parameter.
For Adabas SVC communications in z/OS and VSE environments, the format is:
'broker-id:SVCnnn:NET'
In z/OS and VSE environments, the broker-id setting should match the webMethods EntireX BROKER-ID parameter in the Broker ETBFILE DD. The nnn setting should match either the EntireX Broker ADASVC or ADA5SVC parameters in the Broker PARMS DD statement.
The use of the following parameter form is not recommended in BS2000 environments:
'broker-id: :NET'
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the EntireX Broker ID parameter in Creating an EntireX Broker Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DETBSERVICE | the webMethods EntireX service. | up to 32 characters | none |
This should be the same as the value specified for the SERVICE parameter in webMethods EntireX.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Broker Service parameter in Creating an EntireX Broker Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DETBSERVICECLASS | the webMethods EntireX service class. | up to 32 characters | none |
This should be the same as the value specified for the CLASS parameter in webMethods EntireX.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Service Class parameter in Creating an EntireX Broker Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DETBSCONV | whether or not the destination is to run in single conversation mode for Node to Node support. | YES | NO | NO |
This parameter should be used for high volume destinations.
When this optional parameter is set to "YES" for a destination, all messages are sent using the same EntireX Broker conversation ID.
In the event of a failure, or if the destination is closed, the same conversation ID will be used the next time the destination connection to the EntireX Broker is opened. If there is no active conversation, then a new conversation ID will be established.
The EntireX Broker will only accept the Single Conversation mode if either
the Single Conversation mode is already active or
there are no active conversations for the specified class, server or service.
A switch to Single Conversation mode requires that there are no "old" conversations active (see section about Migration to Single Conversation mode below). A mixture of conversation types is not possible.
A mixture of Single Conversation and non-Single Conversation mode per specified class, server or service is not possible.
To migrate an environment with a Sending Replicator Server, EntireX Broker and Receiving Replicator Server working with multiple Conversations.
The EntireX Broker class, server or service must be empty or drained.
The EntireX Broker must be started and run with EXB970L023 / EXX970L023 or higher.
The Sending Event Replicator Server “Destination” must be modified with the new Single Conversation Parameters, and the Sending Event Replicator Server must be running Event Replicator for Adabas Version 3.5. SP1 or higher.
The Receiving Event Replicator Server “Input Queue” must be modified with the new Single Conversation Parameters, and the Receiving Event Replicator Server must be running Event Replicator for Adabas Version 3.5. SP1 or higher.
Open the Single Conversation Destination and input queue.
If the open is successful, ADAFS0 messages will indicate the destination successfully opened with Single Conversation Mode as shown below.
ADAFS0 36889 ETBBROKER destination OUTPUT1 connected ADAFS0 36889 with single conversation mode set ADAFS0 36889 ETBBROKER Token = REPTOR1 ADAFS0 36889 ETBBROKER Userid = OUT1
If the class, server or service was not empty when the Single Conversation mode opens were attempted, error messages as shown below are received.
ADAF8A 36889 Destination: OUTPUT1 Open failed: Unexpected reason code ADAF87 36889 AMI R=Unexpect Q=OUTPUT1 RC=012/036/0000/0000 ADAF9C 36890 Input Queue: INPUT1 Open failed: Unexpected reason co ADAF87 36890 AMI R=RPIDBG * Q=INPUT1 RC=012/036/0000/0000 ADAF9B 36890 Initialization error in input subtask 001 ADAF8H 36890 Open for input queue INPUT1 failed
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DETBTOKEN | the webMethods EntireX token. | up to 32 characters | REPTOR-DEST- <destination
name> |
This optional parameter can only be specified when DETBSCONV=YES.
Refer to TOKEN in the EntireX Broker ACI for Assembler section of the webMethods EntireX documentation for more information on usage and syntax.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DETBUSERID | the webMethods EntireX user ID. | up to 32 characters | REPTOR--<node>-----<jobname> |
This optional parameter can only be specified when DETBSCONV=YES.
Refer to USER-ID in the EntireX Broker ACI for Assembler section of the webMethods EntireX documentation for more information on usage and syntax.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DETBSERVICENAME | the webMethods EntireX service name. | up to 32 characters | none |
This should be the same as the value specified for the SERVER parameter in webMethods EntireX.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Service Name parameter in Creating an EntireX Broker Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DEVENTLOG | whether or not events should be logged by the Event Replicator and sent to this destination. | YES | NO | NO |
Note:
This parameter is not valid for Adabas destinations.
When this optional parameter is set to "YES" for a destination, Event Replicator Server events are logged to the destination. When DEVENTLOG is set to NO (the default), they are not.
Event Replicator Server events are logged in URBS elements. These URBS elements are sent to destinations related to the event itself. The URBS elements are also sent to any other destinations you have defined with DEVENTLOG=YES. If a related destination also is defined with DEVENTLOG=YES, it will only receive one instance of the URBS element.
To access this log of Event Replicator Server events in the destination queue, you must supply your own application that reads the event URBS elements in the destination queue. If such an application does not exist, the logged events simply sit in the queue.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Event Logging parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DEXIT | the destination output user exit name. | none |
 |
Warning: This parameter is not available for general use. |
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DEXITWORKSIZE | the size of the destination output user exit work area. |
|
Warning: This parameter is not available for general use. |
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DHBINTERVAL | the interval (in seconds) at which the heartbeat should be published to a destination. | 0, 60-86400 | 0 |
Note:
This parameter is to be used with
Replication
Monitoring only.
Use the DHBINTERVAL destination subparameter to set the interval at which heartbeat events are sent to a particular destination. Information for a heartbeat event is collected if at least the defined amount of seconds has passed since a heartbeat event was last sent to the destination. This heartbeat information is inserted into the replication data stream at the exit from the Event Replicator Server (destination processing).
A value of zero (0) indicates that a heartbeat event should not be published for a particular destination.
The DHBINTERVAL parameter is only allowed for destinations defined with DTYPE=ETBROKER, DTYPE=MQSERIES, or DTYPE=NULL.
The DHBINTERVAL parameter is only allowed for destinations defined with DCLASS=SAGTARG.
Note:
The interval between creating heartbeat events may be
slightly longer (e.g. 10 seconds longer) than the interval specified for this
parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DLOG | whether subscription logging should be activated for the destination at Event Replicator Server startup. | "YES" or "NO" | NO |
If "YES" is specified, subscription logging is activated for the destination at Event Replicator Server startup; if "NO" is specified, subscription logging is not activated. For more information about subscription logging, also known as the SLOG facility, read Using the Subscription Logging Facility.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Allow Logging parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DMAXOUTPUTSIZE | the maximum output size (in bytes) for the destination. | 0, 4096 - 2,147,483,647. | 0 |
Note:
You can specify the value for this parameter in a purely
numeric form or use K at the end of the number to specify kilobytes. For
example, DMAXOUTPUTSIZE=4K is the same as DMAXOUTPUTSIZE=4096.
The value for this parameter will be used if it is less than or equal to the maximum output size for the Event Replicator Server (specified using the MAXOUTPUTSIZE global parameter) and less than or equal to the maximum output allowed for the messaging system queue being defined. If this value is larger than the MAXOUTPUTSIZE specification or the maximum output size allowed by the messaging system, the smaller value will be used.
A value of 0 indicates that no specific limit is set for this destination. Instead, the smaller of the MAXOUTPUTSIZE specification or the maximum output size allowed by the messaging system will be used.
Note:
This parameter is not valid for FILE destinations
(DTYPE=FILE). The size of the records written for a destination with DTYPE=FILE
are affected solely by the record size supported by the CLOG data set.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Max Output Size parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DMQCCSID | the destination-specific coded character set ID (CCSID) for the WebSphere MQ destination. | 0 - 2,147,483,647 | 0 |
This optional parameter can only be specified when the DCLASS or DEXIT parameters are specified.
The Event Replicator Server does not attempt to verify the value of this parameter as the character codes may be changed or added to as time goes on. The value for this parameter is simply passed in the appropriate WebSphere MQ request as the CCSID.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the MQSeries Coded Character Set ID parameter in Creating a WebSphere MQ Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DMQDYNQNAME | the WebSphere MQ dynamic queue name | up to 48 characters | (blanks) |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Dynamic Queue Name parameter in Creating a WebSphere MQ Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DMQFORMAT | the optional MQ format name, only if a value for the DCLASS parameter has been specified. | up to eight characters | (blanks) |
Note:
You cannot specify a value for the DMQFORMAT parameter if a
value has not been specified for the DCLASS parameter.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the MQ Format parameter in Creating a WebSphere MQ Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DMQQMGRNAME | defines the WebSphere MQ queue manager name. | up to 48 characters | none |
If this parameter is not specified, the value specified for parameter MQQMGRNAME will be used. This parameter is required if DTYPE=MQSERIES and parameter MQQMGRNAME is not specified.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Queue Manager Name parameter in Creating a WebSphere MQ Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DMQQNAME | the WebSphere MQ queue name. | up to 48 characters | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Queue Name parameter in Creating a WebSphere MQ Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DOPEN | whether or not the destination should be opened at Event Replicator Server startup. | YES | NO | GLOBAL | GLOBAL |
When DOPEN=YES is specified, the destination is opened at Event Replicator Server startup. When DOPEN=NO is specified, the destination is not opened at Event Replicator Server startup.
When DOPEN=GLOBAL is specified, the decision to open the destination at Event Replicator Server startup depends on the setting of the GOPEN global parameter. If GOPEN=YES, the destination is opened at Event Replicator Server startup; if GOPEN=NO, it is not opened.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Open at Startup parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DQFULLDELAY | the number of seconds between retry attempts when resending output transactions to a specific and previously-full webMethods EntireX or MQSeries destination.. | 5 - 300 or "GLOBAL" | GLOBAL |
This parameter specifies the number of seconds between retry attempts to resend output transactions to a specific, previously-full webMethods EntireX or MQSeries destination. If the value GLOBAL is specified, the number seconds between retry attempts is set to the value of the GQFULLDELAY initialization parameter.
Note:
This parameter is valid only for webMethods EntireX and
MQSeries destinations (DTYPE=ETBROKER or DTYPE=MQSERIES).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the QUEUE FULL DELAY parameter in Creating an EntireX Broker Destination Definition or Creating a WebSphere MQ Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DREPLICATEUTI | whether Adabas utility change replication should be activated for a destination at Event Replicator Server startup. | "YES" or "NO" | NO |
If "YES" is specified, utility replication is activated for the destination at Event Replicator Server startup; if "NO" is specified, utility replication is not activated for the destination.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Replicate Util Chgs or Replicate Utility Changes parameters in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
For more information about replicating utility functions, read Replicating Adabas Utility Functions.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DRETRYCOUNT | the number of times that an attempt to open the destination will be retried at the interval specified by DRETRYINTERVAL. | 0 - 2,147,483,647 or "GLOBAL" | RETRYCOUNT parameter setting |
This parameter specifies the number of retry attempts that should occur to open this destination. If the value "GLOBAL" is specified for this parameter, the specification for the global RETRYCOUNT parameter will be used. Any retry attempts will occur at the interval specified by the DRETRYINTERVAL parameter. A value of zero indicates that no retry attempt to open this destination should occur.
Note:
This parameter is not valid for FILE or NULL destinations
(DTYPE=FILE or DTYPE=NULL).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the RETRY COUNT parameter in Creating an Adabas Destination Definition, Creating an EntireX Broker Destination Definition, or Creating a WebSphere MQ Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DRETRYINTERVAL | the default number of seconds between retry attempts to open the destination. | 0, 5 - 2,147,483,647, or "GLOBAL" | RETRYINTERVAL parameter setting. |
This parameter specifies the number of seconds between retry attempts to open the destination. If the value "GLOBAL" is specified for this parameter, the specification for the global RETRYINTERVAL parameter will be used. A value of zero indicates that no retry attempt to open this destination should occur. Except for a specification of zero, the minimum value that can be specified for this parameter is 5 seconds.
Note:
This parameter is not valid for FILE or NULL destinations
(DTYPE=FILE or DTYPE=NULL).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the RETRY INTERVAL parameter in Creating an Adabas Destination Definition, Creating an EntireX Broker Destination Definition, or Creating a WebSphere MQ Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DSTATLOG | whether or not the associated destination should receive interval statistics published by the Event Replicator Server. | YES | NO | NO |
Note:
This parameter is valid for ETBROKER, MQSERIES, or NULL
destinations. This parameter is to be used with
Replication
Monitoring only.
A value of YES indicates that interval statistics should be published to the destination being set up for use with Replication Monitoring; a value of NO indicates they should not.
The Replication Monitoring subsystem will only work if this
Destination is defined and the Global Variable
STATINTERVAL is
greater than zero.
The DEVENTLOG parameter
should be set to YES, if Replication events should be sent to the Adabas
Analytics Collector MF component. If NO is specified, no event information will
be sent.
A destination defined with DSTATLOG=YES
cannot be specified in a subscription.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DTLADABAS | the level of transaction logging that should occur when a transaction for an Adabas destination incurs an error. | 0-3 | 0 |
Valid values range from 0 through 3, as described in the following table:
| Value | Description |
|---|---|
| 0 | No transaction logging should occur. |
| 1 | Log event and Adabas error information. |
| 2 | Log event, Adabas error information, and file and record data. |
| 3 | Log event, Adabas error information, file and record data, and the actual payload. |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Adabas Level parameter in Creating an Adabas Destination Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DTLASSIGN | the level of transaction logging that should occur when a transaction is assigned to a destination for output processing. | "0", "1", "2", or "3" | 0 |
Valid values are "0" (no logging), "1" (log event and output transaction data), "2" (log event, output transaction, and file/record data), or "3" (log event and all available output information for the event).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Assign Level parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DTLCOMP | the level of transaction logging that should occur when a transaction has been successfully output to the messaging system. | "0", "1", "2", or "3" | 0 |
Valid values are "0" (no logging), "1" (log event and output transaction data), "2" (log event, output transaction, and file/record data), or "3" (log event and all available output information for the event).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Completion Level parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DTLSLOGREAD | the level of transaction logging that should occur when a transaction has been successfully read from the SLOG and is about to be queued for output to the destination. | "0", "1", "2", or "3" | 0 |
Valid values are "0" (no logging), "1" (log event and output transaction data), "2" (log event, output transaction, and file/record data), or "3" (log event and all available output information for the event).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the SLOG Read Level parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DTLSLOGWRITE | the level of transaction logging that should occur when a transaction has been successfully written to the SLOG file. | "0", "1", "2", or "3" | 0 |
Valid values are "0" (no logging), "1" (log event and output transaction data), "2" (log event, output transaction, and file/record data), or "3" (log event and all available output information for the event).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the SLOG Write Level parameter in Maintaining Destination Definitions. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| DTYPE | the type of output destination. | ADABAS | ETBROKER | MQSERIES | FILE | NULL | ETBROKER |
Parameter DTYPE defines the type of output destination. Valid values are ADABAS, ETBROKER, MQSERIES, FILE, or NULL. The default value is ETBROKER.
If DTYPE=ADABAS is specified, data is replicated to one or more Adabas files.
If DTYPE=ETBROKER is specified, replicated data is written to the output queue via webMethods EntireX .
If DTYPE=MQSERIES is specified, replicated data is written to the output queue via WebSphere MQ.
Note:
If you are running on z/OS using IBM WebSphere MQ Series
definitions for your Event Replicator DESTINATION or IQUEUE definitions,
an S0D3 abend can occur if you run it as a started task and specify the
parameter REUSASID=YES. This is a documented IBM WebSphere MQ Series
issue.
If DTYPE=FILE is specified, replicated data is written to the CLOG using TLOG URBLTDOD records. You can use these records in the CLOG file to create a sequential output file of the replicated data. For more information, read Creating a Sequential Output File.
Caution:
Be sure that the CLOG is defined in the
Event Replicator Server startup JCL (via one or more
DDCLOGRn DD statements) if you will be using a File
destination definition during Event Replicator for Adabas
processing. If you do not, a warning message will be issued and the File
destination will be set to "Unavailable". For more
information about the CLOG, refer to your Adabas documentation.
If DTYPE=NULL is specified, replication is tested without actually sending the data to a destination.
For additional information about using DTYPE=ADABAS, see Special Information about Destinations with DTYPE=ADABAS.
This parameter can be selected online in Adabas Event Replicator Subsystem (SYSRPTR). SYSRPTR assigns the destination type based on the destination you select to create in SYSRPTR. For more information, read Maintaining Destination Definitions.
The following is an example using the DESTINATION and SUBSCRIPTION parameters to specify that replicated data from DBID 6, file 2 is replicated to DBID 60, file 20:
ADARPD DESTINATION NAME=ADA1 ADARPD DTYPE=ADABAS ADARPD DAIFILE=2,DAIDBID=6,DATDBID=60,DATFILE=20 * ADARPD SUBSCRIPTION NAME=SUB300 ADARPD SDESTINATION='ADA1' ADARPD SFILE=2 ADARPD SFDBID=6 ADARPD SFBAI='AA,BA,BB,BC,BD,CA,CB,CD,CE,CF.'
The destination type ADABAS may be used for replicating data from one Adabas database to another Adabas as long the following conditions are met:
The layout of the target file must be consistent with the format buffer used to decompress the input data from the source file
The ISNs used by the target file must be identical to the ISNs used by the source file (i.e. if record A is stored on ISN 100 in the source file, it must also be stored on ISN 100 in the target file). Insert commands (i.e., N1 or N2) on the source database are applied to the target database via N2 commands. Ensure that the ADALOD LOAD MAXISN setting on the target file is high enough to accommodate all modifications on the source file.
The target Adabas database (the mainframe or open systems Adabas database) must be available to the Event Replicator Server either locally or remotely via Entire Net-Work.
Adabas destinations can be referenced by no more than one subscription.
The following will apply to replication using destination type ADABAS:
The file/ISN will uniquely identify the replicated record.
An insert on the source database/file will result in an insert (using an N2 command) to the same ISN on the target database/file.
An update on the source database/file will result in an update to the same ISN on the target database/file.
A delete on the source database/file will result in a delete of the same ISN on the target database/file.
The format buffer used during an insert or an update will be the after image format buffer defined in the subscription for the related input database/file.
Note:
The format buffer defined in the subscription must
conform to the format buffer rules for both a read and an update.
If the destination target for replicated data is an Adabas mainframe database running Adabas 8.1.3 or later, you can now specify the symbolic notation "C." alone as the global format buffer (GFB parameter) or the after-image format buffer (SFBAI parameter) or after-image global format buffer (SGFORMATAI parameter). This notation will cause the Event Replicator Server to replicate the entire source record to the target mainframe Adabas database.
Caution:
This "C." option may be
used only if the destination target file has been defined with the
same fields in the same order as the fields in the source file; if there are
differences in the definitions of the files, the replication of the data is
likely to incur errors. The only exception to this rule is that the definitions
of the descriptors and superdescriptors in the target and source files may be
different.
The record buffer used during an insert or an update will be the decompressed after image associated with the record.
The following will not be supported on the target database:
A file defined with a cipher code
A file protected with Adabas security
A file defined as a multi-client file
You must set up the target databases and files correctly. Each target file must be sufficiently large (e.g. DSSIZE, UISIZE, NISIZE, MAXISN) to contain all of the data related to the source file. When the user has set up the target file(s) correctly, no errors will be expected when applying the replication data to the target file(s). If one or more errors are received while applying the replication data to the target file(s), information will be printed in the Event Replicator Server to help the user determine the cause of the problem(s).
To make use of this special destination, perform the
following steps:
Load identical files on the source and target.
Note:
The target file could have a subset of the fields in
the source file. Although this is possible, it is up to the user to ensure the
test is set up correctly.
Ensure replication is turned on in the source Adabas nucleus.
Turn replication on for the source file.
Define a subscription that includes the source file and sends output to the destination with type Adabas.
Define a destination of type ADABAS. Define the destination with the source database/file and the target database/file. This destination can be referenced by only one subscription.
Ensure the source nucleus, the target nucleus, and the Event Replicator Server are active.
If you would like to verify that replication is working correctly, you can use an Adabas destination to check it.
To do this, perform the following steps:
Complete Steps 1 - 6 in the procedure above to set up the Adabas destination properly.
Modify the source file with one or more transactions from one or more users.
Wait a sufficient amount of time for replication to complete.
Unload the source and target files in ISN sequence.
Decompress the source file.
Note:
If the target file contains a subset of the fields in
the source file, the FORMAT parameter should be used to ensure the decompressed
source file contains only the fields defined in the target file.
Decompress the target file.
Compare the source and target files. Replication may be considered successful if the two unloaded/decompressed files are identical. Replication may be considered unsuccessful if differences are found and the user has set up the test correctly and no related errors were reported by the Event Replicator Server.
After establishing the correct Network links, it is important to issue a Network "D T" operator command on the Net-work node where the Replication Server resides to confirm:
The target database is seen as a "Translation/UES-enabled database" in the NET0124I message (T Translation / UES-enabled database)
The Replication Server is also seen as a "Translation/UES-enabled database" in the NET0124I message(T Translation / UES-enabled database)
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| ETBBROKERID | a default webMethods EntireX Broker ID destination. | up to 32 characters | none |
This value is used when an webMethods EntireX Broker ID is not specified for a specific webMethods EntireX destination.
Broker IDs come in two formats: one for TCP/IP communications and one for Adabas SVC communications. For TCP/IP communications, the format is:
ip-address:port-number:TCP
In this case, the ip-address setting is the TCP/IP IP address and the port-number setting should match the webMethods EntireX PORT parameter.
For Adabas SVC communications in z/OS and VSE environments, the format is:
'broker-id:SVCnnn:NET'
In z/OS and VSE environments, the broker-id setting should match the webMethods EntireX BROKER-ID parameter in the Broker ETBFILE DD. The nnn setting should match either the EntireX Broker ADASVC or ADA5SVC parameters in the Broker PARMS DD statement.
For Adabas XCOM communications in BS2000 environments, the format is:
'broker-id: :NET'
In BS2000 environments, the broker-id setting should match the webMethods EntireX BROKER-ID parameter in the Broker ETBFILE DD. This file should also contain an IDTNAME parameter in the NET definition section that matches the one in the file in the DDLNKPAR link name. Note also that the Broker ETBFILE link file should contain the parameter TRANSPORT=NET or TRANSPORT=TCP-NET.
[ETBBROKERID=entire-broker-id]
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| ETBBROKERNAME | a default EntireX Broker stub program. | up to 8 characters | BROKER |
This value specifies the name of the EntireX Broker stub program to be used by the Event Replicator Server.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the EntireX Broker Stub Name parameter in Setting Global Values.
Notes:
[ETBBROKERNAME=entirex-broker-stub-program]
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FBVALIDATION | the level of format buffer validation that should occur for subscription definitions. |
ABORT DEAC NONE WARN |
blank (no validation is performed) |
This value specifies the level of format buffer validation that should occur for subscription definitions.
During the subscription phase of transaction processing, all before and after images are decompressed using the format buffers defined for the subscription and its associated SFILE definitions. If an invalid format buffer is specified, this decompression processing fails and a nonzero response code is set in the URBRRSP field of the URBR record. This occurs regardless of the setting of FBVALIDATION initialization parameter. The advantage of the FBVALIDATION initialization parameter is that, when set, format buffer validation occurs before transaction processing uses a subscription.
Format buffer validation set by the FBVALIDATION parameter occurs at Event Replicator initialization for active databases and after the initial handshake for databases that are activated at a later time. In addition, it is performed anytime an updated FDT is received.
If you do not specify the FBVALIDATION parameter (if you leave it blank) or if you specify a value of "NONE" for it, format buffer validation is not performed at Event Replicator Server startup, at the initial handshake for databases, or when an updated FDT is received. If you specify any of the other valid values for FBVALIDATION, format buffer validation is performed, but the action that occurs when the validation fails depends on which value you have selected, as described in the following table:
| FBVALIDATION Value | Action Occurring When Validation Fails |
|---|---|
| ABORT |
If validation errors occur during Event Replicator initialization, the Event Replicator Server is terminated. Validation errors found after successful Event Replicator initialization errors result in warning messages for each format buffer found to be in error. If validation errors occur during refresh processing (RPLREFRESH command), the refresh request fails. |
| DEAC | Warning messages are issued for each
format buffer found to be in error. In addition, the subscription for which
format buffer validation failed is deactivated .
If validation errors occur during refresh processing (RPLREFRESH command), the refresh request fails. |
| WARN | Warning messages are displayed for each format buffer found to be in error. |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Format Buffer Validation parameter in Setting Global Values. SYSRPTR allows you to specify this parameter for all destination definitions, regardless of destination type.
Transaction filter definitions can be used to filter the records used for replication based on the values of fields in those records.
FILTER NAME=filter-name
[FRECORDS=INCLUDE|EXCLUDE]
FFIELD='fieldcode' [ [OR] FFIELD='fieldcode']...
One or more of the following group of subparameters are also specified for the FFIELD parameter:
[FSBEGIN={startbyte | 1}]
[FSLENGTH={length]
[FSIMAGE=AI|BI]
[FSPE=source-pe-number|0]
[FSMU=source-mu-number|0]
[FCOND=EQ|NE|LT|LE|GT|GE]
FLIST=[']value-1[,value-n]...[']
FTARGET='target-fieldcode'
[FTBEGIN={startbyte | 1}]
[FTLENGTH={length ]
[FTIMAGE=AI|BI]
[FTPE=target-pe-number|0]
[FTMU=target-mu-number|0]
This section covers the following FILTER parameters and subparameters:
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| NAME | the name of the transaction filter definition. | alphanumeric; 1-8 characters | none |
Parameter NAME is required and is used to uniquely identify a transaction filter definition. This value is only referenced within the Event Replicator Server. The value may be used when the Event Replicator Server writes a related message.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Transaction Filter Name parameter in Step 2. Specify a Transaction Filter Definition Name and Type.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FCOND | a condition operator code for the filter. |
EQ (equal to) NE (not equal to) LT (less than) LE (less than or equal to GT (greater than) GE (greater than or equal to) |
EQ |
When EQ or NE are specified, multiple target values and target values using wildcards can be tested. For all other condition codes, only single target values without wildcards can be tested (an FLIST subparameter is not valid).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Condition parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
If NE is used to test multiple target values, the record is selected if the field is not equal to any of the listed target values. If EQ is used to test multiple target values, the record is selected if the field is equal to any of the listed target values.
For more information about rules of filter conditions, read Rules for Writing Filter Conditions.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FFIELD | a specific field in the record. Use single quotation marks around the field. This field must be in the format buffer specified for the file in the SFILE definition of the subscription or the subscription will never process the filter. | A valid field code in single quotes. | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Source Field parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
Details of the condition for the named field are specified in the FSBEGIN, FSLENGTH, FSIMAGE, FSPE, FSMU, FCOND, FLIST, FTARGET, FTIMAGE, FTPE, and FTMU subparameters.
If the specified condition is true, the record is selected to be included or excluded from replication, depending on the setting of the FRECORDS parameter.
More than one FFIELD parameter can be specified in a transaction filter definition. The maximum number of FFIELD parameters that can be specified in the DDKARTE statements of the Event Replicator Server startup job is controlled by the MAXFFIELDS parameter setting. If you use the Adabas Event Replicator Subsystem to define transaction filter definitions and their corresponding FFIELD parameters in the Replicator system file, the MAXFFIELDS parameter is not needed as the maximum number of FFIELDs that can be specified is 2500.
When more than one FFIELD parameter is specified in a transaction filter definition, the conditions of all of the FFIELDs must be true for the record to be selected. In other words, the conditions are logically ANDed. However, you can use the OR keyword to group the FFIELD specifications and enforce logical OR processing between the groups. In the following example, condition1, condition2, condition3, and condition4 must all be true for the record to be selected as they are logically ANDed:
FILTER NAME=MYINCLF FRECORDS=INCLUDE FFIELD='field',FCOND=cond1,FTARGET or FLIST values1 FFIELD='field',FCOND=cond2,FTARGET or FLIST values2 FFIELD='field',FCOND=cond3,FTARGET or FLIST values3 FFIELD='field',FCOND=cond4,FTARGET or FLIST values4
But in the following example, either both conditions 1 and 2 OR both conditions 3 and 4 must be true for the record to be selected:
FILTER NAME=MYINCLF FRECORDS=INCLUDE FFIELD='field',FCOND=cond1,FTARGET or FLIST values1 FFIELD='field',FCOND=cond2,FTARGET or FLIST values2 OR FFIELD='field',FCOND=cond3,FTARGET or FLIST values3 FFIELD='field',FCOND=cond4,FTARGET or FLIST values4
For more information about rules of filter conditions, read Rules for Writing Filter Conditions.
If you want to specify only part of a source field for the comparison, specify:
a starting byte number in the FSBEGIN parameter.
optionally, the length of the part to be compared in the FSLENGTH parameter.
Note:
The format of the complete field is used for partial field
comparisons. If the formats of a source field or partial source field and a
target field or partial target field do not match, the comparisons may always
result in an unequal condition. For example, comparing an alphanumeric field to
a packed field will always result in an unequal condition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FLIST | a list of values against which the source field will be compared. | Varies, based on the field identified in the FFIELD parameter | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Target Value n parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
Separate values in the list with commas. Strings that include
blanks should be enclosed in single quotes. Apostrophes in strings must be
doubled (for example: ‘six o”clock’). Each value may consist of either
free-format characters or a mix of elements specified using the
A() or X() notation.
If free-format data consists entirely of numeric data (including an optional leading "+" or "-" character) it is treated as a numeric value.
If a value (or part of a value) is specified using
A() notation, it will be treated as alphabetic data.
Hexadecimal values may be specified using X()
notation.
A value must be specified entirely as free-format data, or
composed of one or more A() or X() subelements. If a
value begins with an A() or X() subelement all
remaining subelements of the value must be so specified. Please refer to
Rules for Writing Filter
Conditions for a full
description of the permissible use of FLIST.
FLIST may specify its list of values spread over many lines, as depicted in the following example:
ADARPD FLIST='value1,value 2, value 3,value 4,value 5,val' ADARPD FLIST='ue 6,value 7,value 8,value ' ADARPD FLIST=' 9'
This example defines the following list of nine string values:
'value1' 'value 2' 'value 3' 'value 4' 'value 5' 'value 6' 'value 7' 'value 8' 'value 9'
Consider the following example, defining eight values:
ADARPD FLIST='J K' ADARPD FLIST='L,M,N,OPQRS' ADARPD FLIST='T,U V,W' ADARPD FLIST='X,Y ,Z' ADARPD FLIST='six o''clock'
The values defined by this example are:
'J KL' 'M' 'N' 'OPQRST' 'U V' 'WX' 'Y ' 'Zsix o'clock'
This parameter is mutually exclusive with the FTARGET subparameter and its related FTIMAGE, FTPE, and FTMU subparameters. You cannot specify values for these subparameters if an FLIST subparameter is specified. Only a value list or a specific field can be used in transaction filter conditions -- not both.
The FLIST parameter may only specify more than one value if the FCOND parameter is set to "EQ" or "NE". In addition, wildcards can only be used in FLIST values if the FCOND parameter is "EQ" or "NE".
Only one value can be specified in the FLIST parameter if the FCOND subparameter is set to "LT", "LE", "GT", or "GE". In addition, wildcard values cannot be specified for these conditions.
For more information about rules of filter conditions, read Rules for Writing Filter Conditions.
The size of the FLIST value list that can be specified in the DDKARTE statements of the Event Replicator Server startup job is controlled by the MAXFLISTSIZE parameter setting. If you use the Adabas Event Replicator Subsystem to define transaction filter definitions and their corresponding FFIELD and FLIST parameters in the Replicator system file, the MAXFLISTSIZE parameter is not needed as the maximum size of the FLIST value list is restricted to the number of bytes on one Replicator system file record (250*8=2000).
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FRECORDS | "INCLUDE" or "EXCLUDE" to indicate whether the records selected by the transaction filter should be included or excluded from replication. | "INCLUDE" or "EXCLUDE" | INCLUDE |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Exclude or Include Records parameter in Step 2. Specify a Transaction Filter Definition Name and Type.
For more information about rules of filter conditions, read Rules for Writing Filter Conditions.
Note:
This parameter can only be specified for fields with
alphanumeric or binary formats.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FSBEGIN | The starting byte number of the partial Adabas source field to be compared. This field is only used if you want to specify a partial field for comparison. | 1 - 32,767 | 1 |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Source Begin parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
For fixed length fields, valid values range from "1" (the start of the field) through the maximum length of the field (the last byte of the field). For variable length fields, valid values range from "1" (the start of the field) to the maximum length allowed for that field type. Counting occurs from left to right beginning with 1 for fields defined with alphanumeric format, and from right to left beginning with 1 for fields defined with binary format.
Note:
The format of the complete field is used for partial field
comparisons. Valid comparisons of different field types are listed in
Field Type
Considerations.
In the following example, four bytes of alphanumeric field AA, starting at byte 2, are compared against the values "A", "BB", "CCC" and "DDDD".
ADARPD GFORMAT NAME=GF1 ADARPD GFB='AA,8,A.' * ADARPD FILTER NAME=MYFILT ADARPD FRECORDS=INCLUDE ADARPD FFIELD='AA',FSIMAGE=AI,FSBEGIN=2,FSLENGTH=4 ADARPD FCOND=EQ ADARPD FLIST='A,BB,CCC,DDDD'
In the following example, four bytes of binary field BB, starting at byte 2, are compared against the values X'C1', X'C2C2', X'C3C3C3', and X'C4C4C4C4'.
ADARPD GFORMAT NAME=GF2 ADARPD GFB='BB,8,B.' * ADARPD FILTER NAME=MYFILT ADARPD FRECORDS=INCLUDE ADARPD FFIELD='BB',FSIMAGE=AI,FSBEGIN=2,FSLENGTH=4 ADARPD FCOND=EQ ADARPD FLIST='X(C1),X(C2C2),X(C3C3C3),X(C4C4C4C4)'
In the following example, four bytes of binary field BB, starting at byte 5, are compared against the after-image of packed field PP using a numeric comparison. If the numbers are equal, the record will be included.
Note:
If field BB had been an alphanumeric field, the comparison
would always result in an unequal condition and the record would not be
included because you cannot compare alphanumeric fields and packed
fields.
ADARPD GFORMAT NAME=GF3 ADARPD GFB='BB,8,B,PP,4,P.' * ADARPD FILTER NAME=MYFILT ADARPD FRECORDS=INCLUDE ADARPD FFIELD='BB',FSIMAGE=AI,FSBEGIN=5,FSLENGTH=4 ADARPD FCOND=EQ ADARPD FTARGET='PP',FTIMAGE=AI
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FSIMAGE | Whether the source field (FFIELD parameter) is in the after image (AI), before image (BI), or the default image of the record. | "AI" "BI" | AI for adds and updates; BI for deletes |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Source Image parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
Note:
This parameter can only be specified for fields with
alphanumeric or binary formats.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FSLENGTH | The numeric length of the partial Adabas source field that should be compared. This field is only used if you want to specify a partial field for comparison. | 1 - 32,767 | see below |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Source Length parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
For fixed length fields, errors will occur if the sum of the values of the FSBEGIN and FSLENGTH parameters exceeds the fixed length of the field. For variable length fields, the sum of the values of the FSBEGIN and FSLENGTH parameters must not exceed the maximum length of the field plus 1. For example, if a variable length field has format "A" with a maximum length of 253 bytes, settings of FSBEGIN=1 and FSLENGTH=253 are valid, but settings of FSBEGIN=2 and FSLENGTH=254 are not.
If FSBEGIN is not specified, the default value is the entire field. If FSBEGIN is specified, the default value is the maximum length of the field minus the value of the FSBEGIN parameter plus 1.
Note:
The format of the complete field is used for partial field
comparisons. Valid comparisons of different field types are listed in
Field Type
Considerations.
Good examples of the FSLENGTH parameter are provided in the description of the FSBEGIN parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FSMU | the index number of the multiple-value field (MU) to which the condition relates if the source field (FFIELD parameter) in this field filter is an MU field. | 0-191 | 0 |
A value of "0" indicates that the source field is not an MU field.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Source MU parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FSPE | the index number (occurrence) of the periodic group (PE) to which the condition relates if the source field (FFIELD parameter) in this field filter is a PE field. | 0-191 | 0 |
A value of "0" indicates that the source field is not a PE field.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Source PE parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
Note:
This parameter can only be specified for fields with
alphanumeric or binary formats.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FTARGET | the two-byte Adabas field code for the target field with which the source field will be compared. Use single quotation marks around the field code. This field must be in the same record as the source field (FFIELD parameter). | A valid field code in single quotes | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Target Field parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
This parameter is mutually exclusive with the FLIST subparameter. You cannot specify values for the FLIST subparameter if this subparameter is specified. Only a value list or a specific field can be used in transaction filter conditions -- not both.
For more information about rules of filter conditions, read Rules for Writing Filter Conditions.
Details regarding the target field are specified in the FTBEGIN, FTLENGTH, FTIMAGE, FTPE, and FTMU subparameters.
If you want to specify only part of a target field for the comparison, specify:
a starting byte number in the FTBEGIN parameter.
optionally, the length of the part to be compared in the FTLENGTH parameter.
Note:
The format of the complete field is used for partial field
comparisons. Valid comparisons of different field types are listed in
Field Type
Considerations.
Note:
This parameter can only be specified for fields with
alphanumeric or binary formats and only if the
FTARGET parameter is also
specified.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FTBEGIN | The starting byte number of the partial Adabas target field at which the comparison should begin. This field is only used if you want to specify a partial field for the comparison. | 1 - 32,767 | 1 |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Target Begin parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
For fixed length fields, valid values range from "1" (the start of the field) through the maximum length of the field (the last byte of the field). For variable length fields, valid values range from "1" (the start of the field) to the maximum length allowed for the field type. Counting occurs from left to right beginning with 1 for fields defined with alphanumeric format, and from right to left beginning with 1 for fields defined with binary format.
Note:
The format of the complete field is used for partial field
comparisons. Valid comparisons of different field types are listed in
Field Type
Considerations.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FTIMAGE | Whether the target field (FTARGET subparameter) is in the after image (AI), before image (BI), or the default image of the record. | "AI" "BI" | AI for adds and updates; BI for deletes |
This subparameter can only be specified if the FTARGET subparameter is also specified.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Target Image parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
Note:
This parameter can only be specified for fields with
alphanumeric or binary formats and only if the
FTARGET parameter is also
specified.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FTLENGTH | The numeric length of the partial Adabas target field that should be used for the comparison. This field is only used if you want to specify a partial field for the comparison. | 1 - 32,767 | see below |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Target Length parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
For fixed length fields, errors will occur if the sum of the values of the FTBEGIN and FTLENGTH parameters exceeds the fixed length of the field. For variable length fields, the sum of the values of the FTBEGIN and FTLENGTH parameters must not exceed the maximum length of the field plus 1. For example, if a variable length field has format "A" with a maximum length of 253 bytes, settings of FTBEGIN=1 and FTLENGTH=253 are valid, but settings of FTBEGIN=2 and FTLENGTH=254 are not.
If FTBEGIN is not specified, the default value is the entire field. If FTBEGIN is specified, the default value is the maximum length of the field minus the value of the FTBEGIN parameter plus 1.
Note:
The format of the complete field is used for partial field
comparisons. Valid comparisons of different field types are listed in
Field Type
Considerations.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FTMU | the index number of the multiple-value field (MU) to which the condition relates if the target field (FTARGET subparameter) in this field filter is an MU field. | 0-191 | 0 |
This subparameter can only be specified if the FTARGET subparameter is also specified. A value of "0" indicates that the target field is not an MU field.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Target MU parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| FTPE | the index number (occurrence) of the periodic group (PE) to which the condition relates if the target field (FTARGET subparameter) in this field filter is a PE field. | 0-191 | 0 |
This subparameter can only be specified if the FTARGET subparameter is also specified. A value of "0" indicates that the target field is not a PE field.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Target PE parameter in Step 3. Add Filter Conditions to the Transaction Filter Definition.
When more than one FFIELD parameter is specified in a transaction filter definition, the conditions of all of the FFIELDs must be true for the record to be selected. In other words, the conditions are logically ANDed. However, you can use the OR keyword to group the FFIELD specifications and enforce logical OR processing between the groups.
In the following example, condition1, condition2, condition3, and condition4 must all be true for the record to be selected (they are logically ANDed):
FILTER NAME=MYINCLF FRECORDS=INCLUDE FFIELD condition1 FFIELD condition2 FFIELD condition3 FFIELD condition4
But in the following example, either both conditions 1 and 2 OR both conditions 3 and 4 must be true for the record to be selected:
FILTER NAME=MYINCLF FRECORDS=INCLUDE FFIELD condition1 FFIELD condition2 OR FFIELD condition3 FFIELD condition4
For more information about rules of filter conditions, read Rules for Writing Filter Conditions.
The following filter not replicate any updates in which fields CA, CB, and CC do not change. In other words, the update will only be replicated when fields CA, CB or CC are changed.
FILTER NAME=SAG1
FRECORDS=EXCLUDE
FFIELD=’CA’,FSIMAGE=BI
FCOND=EQ
FTARGET=’CA’,FTIMAGE=AI
FFIELD=’CB’,FSIMAGE=BI
FCOND=EQ
FTARGET=’CB’,FTIMAGE=AI
FFIELD=’CC’,FSIMAGE=BI
FCOND=EQ
FTARGET=’CC’,FTIMAGE=AI
The following filter will replicate all updates in which the values of fields CA, CB, or CC are increased. If any of these field values are increased, the update will be replicated.
FILTER NAME=SAG2
FRECORDS=INCLUDE
FFIELD=’CA’,FSIMAGE=BI
FCOND=LT
FTARGET=’CA’,FTIMAGE=AI
OR
FFIELD=’CB’,FSIMAGE=BI
FCOND=LT
FTARGET=’CB’,FTIMAGE=AI
OR
FFIELD=’CC’,FSIMAGE=BI
FCOND=LT
FTARGET=’CC’,FTIMAGE=AI
The following filter will replicate records in which field BA contains the characters "J", "K", "L", "M" or "NO", or in which field BB is set to a value ending in 30 consecutive "P" characters and field BC is set to contain the strings "ALPHABETIC", "STRINGS" or any string containing 15 consecutive "Q" characters.
FILTER NAME=SAG3
FRECORDS=INCLUDE
FFIELD=’BA’,FSIMAGE=AI
FCOND=EQ
FLIST=’J,K,L,M,NO’
OR
FFIELD=’BB’,FSIMAGE=AI
FCOND=EQ
FLIST=’*PPPPPPPPPPPPPPPPPPPPPPPPPPPPPP’
FFIELD=’BC’,FSIMAGE=AI
FCOND=EQ
FLIST=’ALPHABETIC,*QQQQQQQQQQQQQQQ*,STRINGS’
The following example replicates records for which the second MU (FSMU=2) within PEs "1", "2", or "3" of field BA are set equal to the contents of field AA.
FILTER NAME=SAG4
FRECORDS=INCLUDE
FFIELD=’BA’,FSMU=2,FSPE=1
FCOND=EQ
FTARGET=’AA’
FFIELD=’BA’,FSMU=2,FSPE=2
FCOND=EQ
FTARGET=’AA’
FFIELD=’BA’,FSMU=2,FSPE=3
FCOND=EQ
FTARGET=’AA’
A global format buffer definition may be used for decompression of replication data from a specific DBID/file. Once a global format buffer definition is defined, it can be used by one or more subscriptions.
GFORMAT NAME=format-name
GFB='format-buffer'
The NAME subparameter defines the name of the global format buffer.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| NAME | the global format buffer name. | alphanumeric; 1 - 7 characters | none |
The format name must be unique across all defined global formats. Subparameter GFB is also required when GFORMAT is specified.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the GFB Name parameter in Adding GFB Definitions.
A global format may be used for decompression of replication data from a specific DBID/file for one or more subscriptions. The following may be defined in the definition of a global format: 1) Global format name 2) Format buffer.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| GFB | the global format buffer | varies | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the blank lines below the GFB Name parameter in Adding GFB Definitions.
The format buffer specified in the GFB parameter must conform to the format buffer requirements (for read commands) documented in the Adabas command reference documentation. Subparameter NAME is also required when GFORMAT is specified.
If the destination target for replicated data is
an Adabas mainframe database running Adabas 8.1.3 or later, you can specify the
symbolic notation "C." alone as the GFB parameter
value (for example, GFB=’C.’). This notation will cause the
Event Replicator Server to replicate the entire source record to the
target mainframe Adabas database.
PE and MU fields cannot use the range notation 1-N in format buffers for a subscription that is sent to a destination that has specified the replication initialization parameter DCLASS=SAGTARG. The SAGTARG application invoked requires that the range of occurrences specified are contained in the record buffer even if they are empty occurrences. 1-N results in a range of 1-191, but unless there are 191 occurrences containing data, space in the record buffer is not allocated for any empty occurrences, resulting in incorrect field positioning when processing the record.
Caution:
This "C." option may be used
only if the destination target file has been defined with the same
fields in the same order as the fields in the source file; if there are
differences in the definitions of the files, the replication of the data is
likely to incur errors. The only exception to this rule is that the definitions
of the descriptors and superdescriptors in the target and source files may be
different.
In the following example, the first and second GFB subparameters define the global format buffer of the global format definition named "G1". The third through fifth GFB subparameters define the global format buffer of the global format definition named "G2".
ADARPD GFORMAT NAME=G1 ADARPD GFB='AA,8,A,' ADARPD GFB='AB,8,A.' * ADARPD GFORMAT NAME=G2 ADARPD GFB='CC,8,A,' ADARPD GFB='CD,8,A,' ADARPD GFB='CE,8,A.' *
The GLOBALS parameter allows you to specify global settings for the Event Replicator Server. All of these global settings have defaults, so none of them are required.
GLOBALS [NUMSFILE=number-of-SFILE-groups] [MAXFFIELDS=n] [MAXFLISTSIZE=n]
This section covers the following GLOBALS parameters and subparameters:
The NUMSFILE subparameter specifies the number of SFILE groups to be allowed for a SUBSCRIPTION. Once set, all subsequent subscriptions will allow up to NUMSFILE number of SFILE groups.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| GLOBALS NUMSFILE | the maximum number of SFILE groups allowed. | Minimum value of 1 Maximum value is dependent on available memory | 10 |
In the following example, subsequent subscriptions will allow up to 30 SFILE parameter groups.
GLOBALS NUMSFILE=30
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| MAXFFIELDS | the number of FFIELD definitions that can be specified in a single FILTER definition. | Minimum value of 1 Maximum value is dependent on available memory | 32 |
The Event Replicator Server will getmain storage to accommodate the number of FFIELD parameters allowed by this parameter and based on the maximum size of the FLIST specifications allowed by the MAXFLISTSIZE parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| MAXFLISTSIZE | the maximum size allowed for the FLIST subparameter. Values are expressed in bytes or kilobytes (if you add a K after the value). | 1-32768 | 128 bytes |
The Event Replicator Server will getmain storage to accommodate the size specified by this parameter and based on the number of FFIELD specifications allowed by the MAXXFIELDS parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| GOPEN | whether or not destinations with DOPEN=GLOBAL and input queues with IQOPEN=GLOBAL specified in their definitions should be opened at Event Replicator Server startup. This parameter specifies the global policy determining whether destinations with DOPEN=GLOBAL settings are opened at Event Replicator Server startup. | YES | NO | YES |
When GOPEN=YES is specified, any destinations with DOPEN=GLOBAL or input queues with IQOPEN=GLOBAL specified in their definitions are opened at Event Replicator Server startup. When GOPEN=NO is specified, any destinations with DOPEN=GLOBAL or input queues with IQOPEN=GLOBAL specified in their definitions are not opened at Event Replicator Server startup.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Open at Start parameter in Setting Global Values.
GOPEN={ YES | NO }
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| GQFULLDELAY | the number of seconds between retry attempts when resending output transactions to a previously-full webMethods EntireX or MQSeries destination. | 5-300 | 60 |
This is a global parameter.
Note:
This parameter only affects webMethods EntireX and MQSeries
destinations (DTYPE=ETBROKER or DTYPE=MQSERIES).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR) in both the webMethods EntireX and MQSeries destinations as well as as a global parameter. For more information, read about the Queue Full Delay parameter in Step 2. Specify General and TLOG EntireX Broker Destination Parameters, Step 2. Specify General and TLOG WebSphere MQ Destination Parameters, and Setting Global Values.
GQFULLDELAY=n
The INITIALSTATE parameter and its subparameters define an initial-state process that may be requested from the Event Replicator Server. Each initial-state process is identified by its name. Different initial-state processes must have different names.
Note:
At least one subscription (ISUBSCRIPTION), destination
(IDESTINATION), or file (IFILE) must be specified in an initial-state
definition.
INITIALSTATE NAME=init-state-name
[ISUBSCRIPTION='subscription-name-list']
[IDESTINATION='destination-name-list']
[IMAXREQ=n]
Zero, one or more of the following group of sub-parameters will be specified:
[IFILE=file-number]
[IDBID=database-id]
[ISNLIST | SELCRIT='search-buffer']
This section covers the following INITIALSTATE parameters and sub-parameters:
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| NAME | an initial-state process that may be requested from the Event Replicator Server. | alphanumeric; 1-8 characters | none |
Each initial-state process is identified by its name. Different initial-state processes must have different names.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Initial-State Name parameter in Step 2. Supply a Name for the Initial-State Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| ISUBSCRIPTION | the subscriptions for which initial-state data is to be delivered. | alphanumeric list of up to 32 subscription names | none |
Zero, one, or more subscription names (up to 32 names) can be specified. If one or more IFILE parameters are specified, the ISUBSCRIPTION parameter restricts the delivery of initial-state data to the specified subscriptions. If no IFILE parameter is specified, ISUBSCRIPTION also defines the set of files for which initial-state data is to be delivered (see below).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about selecting subscriptions in Select Subscriptions for the Initial-State Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IDESTINATION | the destinations to which initial-state data is to be delivered. | alphanumeric list of destination names | none |
Zero, one, or more destination names can be specified. If one or more IFILE parameters are specified, the IDESTINATION parameter restricts the delivery of initial-state data to the specified destinations. If neither IFILE nor ISUBSCRIPTION is specified, IDESTINATION also defines the set of files for which initial-state data is to be delivered (see below).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about selecting destinations in Select Destinations for the Initial-State Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IMAXREQ | number of concurrent initial-state requests that can occur in a given instance of this initial-state definition. | numeric; 1-2,147,483,647 | 1 |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Num of Concurrent Initial State Requests field in Step 3. Specify the Number of Concurrent Initial-State Requests Possible for the Initial-State Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IFILE | the files from which initial-state data is to be delivered. | numeric file number | none |
Zero, one or more file numbers can be specified.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about selecting files in Select Files for the Initial-State Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IDBID | the database containing the specified file (for each IFILE parameter). | numeric; 1-65,535 | none |
If IDBID is not specified, the default DBID is assumed. This parameter may only be specified when the IFILE parameter is specified.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about selecting files in Select Files for the Initial-State Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| ISNLIST or SELCRIT | data selection (filtering) method. | MAX 60 byte search buffer for SELCRIT | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the selection criteria in Select Files for the Initial-State Definition.
The optional keyword parameters ISNLIST and SELCRIT are mutually exclusive and may only be specified when the IFILE parameter is specified.
The ISNLIST parameter specifies that only the records with the ISNs provided in the actual initial-state request will be delivered. The alternative optional SELCRIT parameter, which takes an Adabas Search Buffer as its argument, specifies that only those records that satisfy a search criterion will be delivered. The search criterion consists of the specified Search Buffer and the Value Buffer provided in the actual initial-state request.
If you elect to use an ISN list, be sure to supply an ISN list when you submit the initial-state request. The ISN list can be specified using the Adabas Event Replicator Subsystem (read Populating a Database With Initial-State Data) or in the client request (read ISN List Format).
If one or more file numbers are specified, initial-state data will be delivered for the specified files, subject to selection (filtering) via the ISNLIST or SELCRIT parameters. The data will be delivered only for the specified subscriptions and destinations. If no subscriptions or destinations are specified, the data will be delivered for each subscription that includes any of the specified files. It will be delivered to all destinations defined in these subscriptions.
If no file numbers are specified and one or more subscriptions names are specified, initial-state data will be delivered for all files defined in any of the specified subscriptions. The data will be delivered to the specified destinations. If no destination is specified, the data will be delivered to all destinations defined in any of the specified subscriptions.
If no file numbers and no subscription names are specified, initial-state data will be delivered for all files defined in any subscription that is delivered to any of the specified destinations.
An initial-state definition with the SELCRIT option may not be used for a file with spanned Data Storage record support.
Note:
Initial-state processes that replicate all records may be
used for a file with spanned Data Storage record support. In addition,
initial-state processes that replicate records matching an ISN list may also be
used for a file with spanned Data Storage record support.
One or more input queues may be defined. The Event Replicator Server will listen on each of its defined queues. Defined input queues should match queues used by target applications when sending requests to an Event Replicator Server.
An input queue is defined with the following parameters:
IQUEUE NAME=input-queue-name
[IQBUFLEN={nnnn|2048}]
[IQOPEN={GLOBAL|NO|YES}
[IQRETRYCOUNT={n|GLOBAL}
[IQRETRYINTERVAL={n|GLOBAL}
[IQTYPE={ETBROKER|MQSERIES}]
The following parameters are used when IQTYPE=MQSERIES is used:
[IQMQQMGRNAME=mqseries-queue-manager-name] [IQMQQNAME=mqseries-queue-name]
Note:
If you are running on z/OS using IBM WebSphere MQ Series
definitions for your Event Replicator DESTINATION or IQUEUE definitions,
a S0D3 abend can occur if you run it as a started task and specify the
parameter REUSASID=YES. This is a documented IBM WebSphere MQ Series
issue.
The following parameters are used when IQTYPE=ETBROKER is used:
[IQETBBROKERID=entire-broker-id]
[IQETBSERVICE=entire-broker-service]
[IQETBSERVICENAME=entire-broker-service-name]
[IQETBSERVICECLASS=entire-broker-service-class]
[IQETBSCONV={YES|NO}]
[IQETBTOKEN=entire-broker-token]
[IQETBUSERID=entire-broker-userid]
This section covers the following IQUEUE parameters and subparameters:
The IQUEUE NAME defines an input queue name. It is used to uniquely identify an input definition. This value is only referenced within the Event Replicator Server. The value may be used when the Event Replicator Server writes a message related to an input queue.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| NAME | the input queue to which messages are to be written. | alphanumeric, 1-8 characters | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Input Queue Name parameter in Creating an EntireX Broker IQUEUE Definition and Creating a WebSphere MQ IQUEUE Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQBUFLEN | the length, in bytes, of the input buffer associated with this input queue. | 2048 - 2,147,483,647 | 2048 |
The maximum value of the input queue buffer length is restricted by the amount of virtual storage available in the Event Replicator address space. In addition, if you enter a value less than "2048", "2048" will be used.
The IQBUFLEN value should be set to a value greater than or equal to the largest message that will be received by the input queue. When the input queue will receive data as a part of node-to-node replication, the largest message will be limited by the minimum of the following Event Replicator Server settings: MAXOUTPUTSIZE parameter, DMAXOUTPUTSIZE parameter (if specified for the destination), or the message limit imposed by the messaging system.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Input Queue Buffer Length parameter in Creating an EntireX Broker IQUEUE Definition and Creating a WebSphere MQ IQUEUE Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQOPEN | whether the input queue should be opened automatically when the Event Replicator Server starts up or when an RPLREFRESH command is run. | GLOBAL | NO | YES | GLOBAL |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Open Queue at Start parameter in Creating an EntireX Broker IQUEUE Definition and Creating a WebSphere MQ IQUEUE Definition.
Valid values for IQOPEN are:
GLOBAL (the default): This setting indicates that the decision about automatically opening the input queue should be based on the setting of the GOPEN global parameter. If the GOPEN global parameter is set to "YES", the input queue is opened; if GOPEN is set to NO, the input queue is not opened.
NO: This setting indicates that the input queue should never be opened automatically when the Event Replicator Server starts up or when an RPLREFRESH command is run.
YES: This setting indicates that the input queue should always be opened automatically when the Event Replicator Server starts up or when an RPLREFRESH command is run.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQRETRYCOUNT | the number of times that an attempt to open the input queue will be retried at the interval specified by IQRETRYINTERVAL. | 0 - 2,147,483,647 or "GLOBAL" | RETRYCOUNT parameter setting |
This parameter specifies the number of retry attempts that should occur to open the input queue identified by this definition. If the value "GLOBAL" is specified for this parameter, the specification for the global RETRYCOUNT parameter will be used. Any retry attempts will occur at the interval specified by the IQRETRYINTERVAL parameter. A value of zero indicates that no retry attempt to open this input queue should occur.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Retry Count parameter in Creating an EntireX Broker IQUEUE Definition and Creating a WebSphere MQ IQUEUE Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQRETRYINTERVAL | the default number of seconds between retry attempts to open the input queue. | 0, 5 - 2,147,483,647, or "GLOBAL" | RETRYINTERVAL parameter setting. |
This parameter specifies the number of seconds between retry attempts to open the input queue identified by this definition. If the value "GLOBAL" is specified for this parameter, the specification for the global RETRYINTERVAL parameter will be used. A value of zero indicates that no retry attempt to open this input queue should occur. Except for a specification of zero, the minimum value that can be specified for this parameter is 5 seconds.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Retry Interval parameter in Creating an EntireX Broker IQUEUE Definition and Creating a WebSphere MQ IQUEUE Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQTYPE | the type of input queue. | ETBROKER | MQSERIES | ETBROKER |
If IQTYPE=ETBROKER, the input queue will be accessed via EntireX Broker. If IQTYPE=MQSERIES, the input queue will be accessed via WebSphere MQ.
Note:
If you are running on z/OS using IBM WebSphere MQ Series
definitions for your Event Replicator DESTINATION or IQUEUE definitions,
a S0D3 abend can occur if you run it as a started task and specify the
parameter REUSASID=YES. This is a documented IBM WebSphere MQ Series
issue.
This parameter can be selected online in Adabas Event Replicator Subsystem (SYSRPTR). SYSRPTR assigns the input queue type based on the input queue you select to create in SYSRPTR. For more information, read Maintaining Input Queue (IQUEUE) Definitions.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQMQQMGRNAME | the WebSphere MQ queue manager name. A maximum of 48 characters can be specified. | Check with your WebSphere MQ development staff and the WebSphere MQ documentation. | none |
If this parameter is NOT specified, the value specified for parameter MQQMGRNAME will be used. This parameter is required if IQTYPE=MQSERIES and parameter MQQMGRNAME is NOT specified. Up to 48 characters may be specified for this parameter.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Queue Manager Name parameter in Creating a WebSphere MQ IQUEUE Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQMQQNAME | the WebSphere MQ queue name. A maximum of 48 characters can be specified. | Check with your WebSphere MQ development staff and the WebSphere MQ documentation. | IQUEUE NAME |
If this parameter is NOT specified, the value specified for parameter IQUEUE NAME will be used.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the MQ Queue Name parameter in Creating a WebSphere MQ IQUEUE Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQETBBROKERID | the webMethods EntireX Broker ID. A maximum of 32 characters can be specified. | Check with your webMethods EntireX Broker development staff and the webMethods EntireX Broker documentation. | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Broker ID parameter in Creating an EntireX Broker IQUEUE Definition.
If this parameter is not specified, the default EntireX Broker ID (specified in parameter ETBBROKERID) will be used.
Broker IDs come in two formats: one for TCP/IP communications and one for Adabas SVC communications. For TCP/IP communications, the format is:
ip-address:port-number:TCP
In this case, the ip-address setting is the TCP/IP IP address and the port-number setting should match the webMethods EntireX PORT parameter.
For Adabas SVC communications in z/OS and VSE environments, the format is:
'broker-id:SVCnnn:NET'
In z/OS and VSE environments, the broker-id setting should match the webMethods EntireX BROKER-ID parameter in the Broker ETBFILE DD. The nnn setting should match either the EntireX Broker ADASVC or ADA5SVC parameters in the Broker PARMS DD statement.
The use of the following parameter form is not recommended in BS2000 environments:
'broker-id: :NET'
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQETBSERVICE | the webMethods EntireX service. A maximum of 32 characters can be specified. | Check with your webMethods EntireX Broker development staff and the webMethods EntireX Broker documentation. | none |
This should be the same as the value specified for the SERVICE parameter in webMethods EntireX.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Broker Service parameter in Creating an EntireX Broker IQUEUE Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQETBSERVICENAME | the webMethods EntireX service name. A maximum of 32 characters can be specified. | Check with your webMethods EntireX Broker development staff and the webMethods EntireX Broker documentation. | none |
This should be the same as the value specified for the SERVER parameter in webMethods EntireX.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Service Name parameter in Creating an EntireX Broker IQUEUE Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQETBSERVICECLASS | the webMethods EntireX service class. A maximum of 32 characters can be specified. | Check with your webMethods EntireX Broker development staff and the webMethods EntireX Broker documentation. | none |
This should be the same as the value specified for the CLASS parameter in webMethods EntireX.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Service Class parameter in Creating an EntireX Broker IQUEUE Definition.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQETBSCONV | whether or not the input queue is to run in single conversation mode for Node to Node support. | YES | NO | NO |
This parameter should be used for high volume input queues. At this time only one destination may connect to an input queue that has this parameter set to yes. If more than one were to connect and send messages, a message out of sequence error can occur and the input queue will be closed.
When this optional parameter is set to "YES", it will only accept messages from a destination that also has single conversation mode set to "YES".
In the event of a failure or if the input queue is closed, no DEREGISTER or LOGOFF is issued, thus preserving the conversation ID that was in effect.
The EntireX Broker will only accept the Single Conversation mode if either
the Single Conversation mode is already active or
there are no active conversations for the specified class, server or service.
A switch to Single Conversation mode requires that there are no "old" conversations active (see section about Migration to Single Conversation mode below). A mixture of conversation types is not possible.
A mixture of Single Conversation and non-Single Conversation mode per specified class, server or service is not possible.
To migrate an environment with a Sending Replicator Server, EntireX Broker and Receiving Replicator Server working with multiple Conversations.
The EntireX Broker class, server or service must be empty or drained.
The EntireX Broker must be started and run with EXB970L023 / EXX970L023 or higher.
The Sending Event Replicator Server “Destination” must be modified with the new Single Conversation Parameters, and the Sending Event Replicator Server must be running Event Replicator for Adabas Version 3.5. SP1 or higher.
The Receiving Event Replicator Server “Input Queue” must be modified with the new Single Conversation Parameters, and the Receiving Event Replicator Server must be running Event Replicator for Adabas Version 3.5. SP1 or higher.
Open the Single Conversation Destination and input queue.
If the open is successful, ADAFS0 messages will indicate the destination successfully opened with Single Conversation Mode as shown below.
ADAFS0 36889 ETBBROKER destination OUTPUT1 connected ADAFS0 36889 with single conversation mode set ADAFS0 36889 ETBBROKER Token = REPTOR1 ADAFS0 36889 ETBBROKER Userid = OUT1
If the class, server or service was not empty when the Single Conversation mode opens were attempted, error messages as shown below are received.
ADAF8A 36889 Destination: OUTPUT1 Open failed: Unexpected reason code ADAF87 36889 AMI R=Unexpect Q=OUTPUT1 RC=012/036/0000/0000 ADAF9C 36890 Input Queue: INPUT1 Open failed: Unexpected reason co ADAF87 36890 AMI R=RPIDBG * Q=INPUT1 RC=012/036/0000/0000 ADAF9B 36890 Initialization error in input subtask 001 ADAF8H 36890 Open for input queue INPUT1 failed
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQETBTOKEN | the webMethods EntireX token. | up to 32 characters | IQIN<input queue name> |
This optional parameter can only be specified when IQETBSCONV=YES.
Refer to TOKEN in the EntireX Broker ACI for Assembler section of the webMethods EntireX documentation for more information on usage and syntax.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IQETBUSERID | the webMethods EntireX user ID. | up to 32 characters | REPTOR--<node>-----<jobname> |
This optional parameter can only be specified when IQETBSCONV=YES.
Refer to USER-ID in the EntireX Broker ACI for Assembler section of the webMethods EntireX documentation for more information on usage and syntax.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IRMSGINTERVAL | the interval during which the message limit specified by the IRMSGLIMIT parameter applies. | 1 - 2,147,483,647 | 60 |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Input Request Msg Interval parameter in Setting Global Values.
IRMSGINTERVAL=n
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| IRMSGLIMIT | the maximum number of input request error messages issued by the Event Replicator Server during the interval specified by the IRMSGINTERVAL parameter | 3 - 2,147,483,647 | 10 |
This optional parameter can be used to limit the number of input request error messages issued by the Event Replicator Server in the interval specified by the IRMSGINTERVAL parameter. These error messages relate to invalid information sent to a WebSphere MQ or EntireX Broker input queue. Use of this parameter allows you to prevent the console from being overrun with error messages when invalid data is sent to these input queues.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Input Request Msg Limit parameter in Setting Global Values.
IRMSGLIMIT=n
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| LOGINPUTTRANSACTION | whether and when database-related input transactions are written to the SLOG system file. | ALL | NO | 1-99 | NO |
You can reduce the risk of Event Replicator Server replication pool overflows by requesting that the Event Replicator Server temporarily write replication transactions received from the Adabas nucleus to the SLOG system file. These transactions are commonly referred to as database-related input transactions. Once database-related input transactions have been written to the SLOG system file, the Event Replicator Server then 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 for the LOGINPUTTRANSACTION parameter are described below:
| Valid Value | Description |
|---|---|
| ALL |
Specify ALL if you want SLOG system file usage to always be active for database-related input transactions. When ALL is specified, database-related input transactions from the Adabas nucleus are written to the SLOG system file. |
| NO |
Specify NO if you do not want to activate SLOG system file usage for database-related input transactions from the Adabas nucleus. In this case, the transactions will be processed, as usual, using the Event Replicator Server replication pool. This is the default setting. |
| 1-99 |
Specify an integer from 1 to 99 to set a percentage threshold for Event Replicator Server replication pool usage. If this threshold is exceeded, database-related input transactions will be stored in and processed from the SLOG system file. When the threshold is no longer exceeded and all database-related input transactions have been processed, database-related input transactions from the Adabas nucleus are stored in and processed from the replication pool. The value is specified as a percentage of the setting of the LRPL parameter (which specifies the size of the replication pool). |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Log Input Transaction parameter in Setting Global Values.
LOGINPUTTRANSACTION=[ALL | NO | nn]
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| LOGOUTPUTTRANSACTION | whether and when output items are written to the SLOG system file. | ALL | NO | 1-99 | NO |
Valid values for the LOGOUTPUTTRANSACTION parameter are described below:
| Valid Value | Description |
|---|---|
| ALL |
Specify ALL, if you want SLOG processing to always be turned on for destinations defined with DLOG=YES. |
| NO |
Specify NO, if you want SLOG processing to be turned off for a destination related to space used in the Event Replicator Server replication pool. This is the default setting. |
| 1-99 |
Specify an integer from 1 to 99 to set a percentage threshold for Event Replicator Server replication pool usage. SLOG processing will be turned on for a destination when:
|
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Log Output Transaction parameter in Setting Global Values.
LOGOUTPUTTRANSACTION=[ALL | NO | nn]
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| MAXOUTPUTSIZE | the maximum output message size, in bytes or KB. | 32,768 - 2,147,483,647 bytes | 100,000 |
MAXOUTPUTSIZE may be specified in bytes or it may be specified with the suffix K to indicate kilobytes. The maximum value for MAXOUTPUTSIZE 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.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Max Output Size parameter in Setting Global Values.
MAXOUTPUTSIZE=n[K]
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| MAXRECORDSIZE | the maximum length (in bytes) of any decompressed record that can be processed by the Event Replicator Server. | 1 - 32,767 bytes (Adabas 7 installations)
1-32,767 or 50% of the LRPL setting, whichever is larger (Adabas 8 installations) |
32,767 bytes |
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.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Max Record Size parameter in Setting Global Values.
MAXRECORDSIZE=n
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| MAXVARRECORDSIZE | the maximum length (in bytes) of variable decompressed records that can be processed by the Event Replicator Server. | 1 - MAXRECORDSIZE setting | 32,767 bytes |
The value specified for MAXVARRECORDSIZE must be less than or equal to the setting of the MAXRECORDSIZE setting.
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.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Max Variable Record Size parameter in Setting Global Values.
MAXVARRECORDSIZE=n
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| MQQMGRNAME | the default WebSphere MQ queue manager name. | MAX 48 characters | none |
This parameter is used when a WebSphere MQ queue manager name is not specified for a specific WebSphere MQ destination.
MQQMGRNAME=mqseries-queue-manager-name
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| NPADACALLS | the maximum number of parallel Adabas calls that can be made. | 1 - 50 | 3 |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Num Parallel Adabas Calls parameter in Setting Global Values.
Use this parameter to improve throughput of data replication to your Adabas destinations.
For example, assume a subscription sends its output to 5 Adabas destinations, each applying data to a file on a separate target database. Suppose a user issues the following commands for the one DBID/file combination in the subscription: A1 (Update), A1, ET (End Transaction). If NPADACALLS is set to "1", the Event Replicator Server will send the following commands using a single Adabas user:
OP (open)
A1,A1,ET for the first Adabas destination
A1,A1,ETfor the second Adabas destination
A1,A1,ET for the third Adabas destination
A1,A1,ET for the fourth Adabas destination
A1,A1,ET for the fifth Adabas destination
CL (close)
However, if NPADACALLS is set to "5", the Event Replicator Server will send the following commands using five concurrent Adabas users to the five destinations: OP,A1,A1,ET,CL.
Note:
If NPADACALLS is set to a value greater than
"1", you should make sure that the following ADARUN
parameters are set appropriately for the target Adabas nucleus, ensuring the
target nucleus can handle updates by multiple concurrent users:
LBP, LDEUQP,
LFIOP, LFP,
LP,
LWP, NAB,
NC,
NH,
NT,
and NU.
NPADACALLS=n
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| RECORDPLOGINFO | whether or not PLOG information should be saved in the Replicator system file. Valid values are "YES" (store the information) or "NO" (do not store the information). | YES | NO | NO |
If this parameter is set to "NO", PLOG information is not saved by the Reptor when the nucleus processes the SYNP checkpoint created by ADARES PLCOPY. The PLOG information screens in the Adabas Event Replicator Subsystem will either not display any PLOG data set information or will display outdated information on the screens. Replicator system file.
If you plan on using the automated replay facility provided with Event Replicator, you must set this parameter to "YES". The related information is collected when the source Adabas nucleus processes the SYNP checkpoint created by ADARES PLCOPY.
For more information about the PLOG information screens, read Reviewing and Managing the PLOG Data Set List.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Record PLOG Information parameter in Setting Global Values.
RECORDPLOGINFO={ YES | NO }
The Event Replicator Server can provide a circular buffer to expedite retransmission of a transaction. A single resend buffer can be shared among multiple subscriptions. Resend buffers are defined using the RESENDBUFFER initialization parameter.
RESENDBUFFER initialization parameters use the following syntax:
RESENDBUFFER NAME=name
RSIZE={buffersize|32K}
This section covers the following topics:
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| NAME | the unique name for the resend buffer definition. | alphanumeric; 1-8 characters (see constraints below) | none |
There are some constraints on the name. It must:
Be comprised of one to eight uppercase, alphanumeric characters and can include the special characters "@", "$", or "#". If the name is less than eight characters, it is automatically padded on the right with blanks.
Not begin with a numeric character or a blank.
Have no embedded blanks.
Not begin with the letters "SYS".
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Resend Buffer Name parameter in Adding Resend Buffer Definitions.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| RSIZE | the amount of storage allocated to the resend buffer. Values may be specified in bytes or kilobytes (specify K after the value). | 32K - 2,097,151K | 32K |
If a resend buffer is defined for a subscription that delivers data to multiple destinations, multiple copies of the sent data may be saved, one copy for each destination. The specification of RSIZE must be large enough to accommodate these multiple copies of the data.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Resend Buffer Size parameter in Adding Resend Buffer Definitions.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| RETRYCOUNT | the default number of times that an attempt to retry opening a destination or input queue will be attempted at the interval specified by the RETRYINTERVAL parameter. | 0 - 2,147,483,647 | 10 |
This global parameter specifies the number of attempts to retry opening any destination or input queue for which no specific retry count has been specified. A value of zero indicates that no retry processing should occur for any affected destinations or input queues.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Retry Count parameter in Setting Global Values.
RETRYCOUNT=n
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| RETRYINTERVAL | the default number of seconds between attempts to retry opening a destination or input queue. | 0 - 2,147,483,647 | 0 |
This global parameter specifies the number of seconds between attempts to retry opening any destination or input queue for which no specific retry interval has been specified. A value of zero indicates that no retry processing should occur for any affected destinations or input queues.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Retry Interval parameter in Setting Global Values.
RETRYINTERVAL={n|GLOBAL}
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SLOGCHECKINTERVAL | the interval (in minutes) between checks of the Associator and Data file space usage. | 0, 5 - 2880 | 0 |
The SLOGCHECKINTERVAL is an optional
parameter. If it is not specified, a value of zero (0) is assumed, indicating
that no threshold monitoring should occur. If it is specified, valid values are
zero (0) or any numbers in the range from 5 to 2880 minutes (48 hours).
Once a value is specified, the settings of the thresholds
specified by the ASSOTHRESHOLD,
DATATHRESHOLD,
SLOGACTHRESHOLD,
SLOGNITHRESHOLD,
SLOGUITHRESHOLD, and
SLOGDSTHRESHOLD initialization parameters are used to
evaluate your system’s Adabas and SLOG Associator and Data file space usage. If
the thresholds are met or reached, warning messages are issued to the console
and DDPRINT.
This section covers the following topics:
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
ASSOTHRESHOLD |
the percentage of the Event Replicator database Associator space that can be used before threshold warning messages are issued. Associator space usage must meet or exceed this threshold value to trigger the warning messages. | 0 - 100 | 80 |
The ASSOTHRESHOLD is an optional
parameter. If it is not specified, a default of 80% is assumed.
If the percentage of space used meets or exceeds the setting of this parameter, warning messages are issued to the console.
If zero (0) is specified for this parameter, no threshold monitoring will occur for the Event Replicator database Associator space.
Note:
If the SLOGCHECKINTERVAL
initialization parameter is not specified, no Event Replicator database Associator space
threshold monitoring will occur, regardless of the setting of this
parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
DATATHRESHOLD |
the percentage of the Event Replicator database Data space that can be used before threshold warning messages are issued. Data space usage must meet or exceed this threshold value to trigger the warning messages. | 0 - 100 | 80 |
The DATATHRESHOLD is an optional
parameter. If it is not specified, a default of 80% is assumed.
If the percentage of space used meets or exceeds the setting of this parameter, warning messages are issued to the console.
If zero (0) is specified for this parameter, no threshold monitoring will occur for the Event Replicator database Data space.
Note:
If the SLOGCHECKINTERVAL
initialization parameter is not specified, no Event Replicator database Data space
threshold monitoring will occur, regardless of the setting of this
parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
SLOGACTHRESHOLD |
the percentage of the SLOG address converter space that can be used before threshold warning messages are issued. Address converter space usage must meet or exceed this threshold value to trigger the warning messages. | 0 - 100 | 70 |
The SLOGACTHRESHOLD is an optional
parameter. If it is not specified, a default of 70% is assumed.
If the percentage of space used meets or exceeds the setting of this parameter, warning messages are issued to the console. To determine if the address converter threshold has been reached, the percentage used is calculated using the following formula:
(TOPISN-MINISN+1)/(MAXISN-MINISN+1)
If zero (0) is specified for this parameter, no threshold monitoring will occur for the SLOG address converter space.
Note:
If the SLOGCHECKINTERVAL
initialization parameter is not specified, no SLOG address converter space
threshold monitoring will occur, regardless of the setting of this
parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
SLOGDSTHRESHOLD |
the percentage of the SLOG Data Storage space that can be used before threshold warning messages are issued. Data Storage space usage must meet or exceed this threshold value to trigger the warning messages. | 0 - 100 | 70 |
The SLOGDSTHRESHOLD is an optional
parameter. If it is not specified, a default of 70% is assumed.
If the percentage of space used meets or exceeds the setting of
this parameter, warning messages are issued to the console. To determine if the
Data Storage threshold has been reached, the percentage used is calculated
using the following formula, where acyl represents the number of
allocated cylinders, uncyl represents the number of unused
cylinders, and unbytes represents the number of unused bytes (per
the DSST):
(acyl - uncyl - unbytes) / acyl
If zero (0) is specified for this parameter, no threshold monitoring will occur for the SLOG Data space.
Note:
If the SLOGCHECKINTERVAL
initialization parameter is not specified, no SLOG Data Storage space threshold
monitoring will occur, regardless of the setting of this parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
SLOGNITHRESHOLD |
the percentage of the SLOG normal index space that can be used before threshold warning messages are issued. Normal index space usage must meet or exceed this threshold value to trigger the warning messages. | 0 - 100 | 70 |
The SLOGNITHRESHOLD is an optional
parameter. If it is not specified, a default of 70% is assumed.
If the percentage of space used meets or exceeds the setting of
this parameter, warning messages are issued to the console. To determine if the
normal index threshold has been reached, the percentage used is calculated
using the following formula, where acyl represents the number of
allocated cylinders and ucyl represents the number of used
cylinders:
(ucyl / acyl)
If zero (0) is specified for this parameter, no threshold monitoring will occur for the SLOG normal index space.
Note:
If the SLOGCHECKINTERVAL
initialization parameter is not specified, no SLOG normal index space threshold
monitoring will occur, regardless of the setting of this parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
SLOGUITHRESHOLD |
the percentage of the SLOG upper index space that can be used before threshold warning messages are issued. Upper index space usage must meet or exceed this threshold value to trigger the warning messages. | 0 - 100 | 70 |
The SLOGUITHRESHOLD is an optional
parameter. If it is not specified, a default of 70% is assumed.
If the percentage of space used meets or exceeds the setting of
this parameter, warning messages are issued to the console. To determine if the
upper index threshold has been reached, the percentage used is calculated using
the following formula, where acyl represents the number of
allocated cylinders and ucyl represents the number of used
cylinders:
(ucyl / acyl)
If zero (0) is specified for this parameter, no threshold monitoring will occur for the SLOG upper index space.
Note:
If the SLOGCHECKINTERVAL
initialization parameter is not specified, no SLOG upper index space threshold
monitoring will occur, regardless of the setting of this parameter.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| STATINTERVAL | the interval (in seconds) at which Event Replicator statistics should be published by the Event Replicator Server. | 0, 60-86400 | 0 |
Note:
This parameter is to be used with
Replication
Monitoring only.
The STATINTERVAL initialization parameter
must be set to a value greater than zero to activate
Replication
Monitoring. This will result interval statistics being
generated by the Event Replicator Server.
A value of zero (0) indicates that interval statistics should not be published and Replication Monitoring will be deactivated.
When the value of the STATINTERVAL is
greater than zero, a Destination with a DSTATLOG setting
of YES must be setup. See the DSTATLOG parameter for
more details.
One or more subscriptions will be defined in the replication definitions. A subscription defines a set of rules to be applied to the replicated data. Each subscription defines the following:
The output alpha code used during decompression.
The output architecture key used during decompression.
One or more output destinations.
The version ID of the subscription.
The output wide-code used during decompression.
One or more combinations of database ID and file denoting the input replication data to be processed for the subscription.
In addition, the following is defined for each combination of database ID and file:
The format buffer used when decompressing the data storage after image.
The format buffer used when decompressing the data storage before image.
The format buffer used when decompressing the key related before image.
An optional subscription exit name.
The following parameters are used to define a SUBSCRIPTION:
SUBSCRIPTION initialization parameters use the following syntax:
SUBSCRIPTION NAME='subscription-name'
[SACODE={user-data-alpha-key|0}]
[SACTIVE=YES|NO]
[SARC=architecture-key|2]
[SDEACTIVATE=YES|NO]
[SDESTINATION='destination-name-list']
[SINCREMENTIS=YES|NO]
[SIDESTINATION='NONE' | 'destination-name-list']
[SRESENDBUFFER=resendbuffer-name]
[STLFILTER={0 | 1 | 2 | 3 }]
[STLIGNORE={0 | 1 | 2 }]
[STLINPUT={0 | 1 | 2 | 3 }]
[STLMATCH={0 | 1 | 2 }]
[STLNOMATCH={0 | 1 | 2 }]
[STLOUTPUT={0 | 1 | 2 | 3 }]
[SVERSION=subscription-version-indicator]
[SWCODE=user-data-wide-key]
One or more of the following group of subparameters are also specified:
SFILE='file-num'
{SFBAI='format-buffer-used-with-data-storage-after-image'|SGFORMATAI=global-format-name}
[SFBBI='format-buffer-used-with-data-storage-before-image'|SGFORMATBI=global-format-name]
[SFBKEY='format-buffer-used-key-before-image'|SGFORMATKEY=global-format-name]
[SFDBID=database-id|DBID-parm-value]
[SFDEFAULTACODE=file-alpha-EBCDIC-key]
[SFFILTER=transaction-filter-name]
[SFFILTERGFBAI=global-format-name]
[SFFILTERGFBBI=global-format-name]
[SFREPLICATEDELETE=YES|NO|UPDATE]
[SFREPLICATEINSERT=YES|NO]
[SFREPLICATENOTCHANGED=YES|NO]
[SFREPLICATEUPDATE=YES|NO]
[SFSECURITYFILE=YES|NO]
[SFSEXIT=subscription-exit-name]
This section covers the following topics:
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| NAME | the unique name for the subscription definition. | alphanumeric; 1-8 characters | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Subscription Name parameter in Step 2. Supply General Subscription Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SACODE | the desired output character encoding. This can only be set when the Event Replicator Server has been started with Universal Encoding Support (UES) enabled. | numeric | 0 (zero) |
The A (alpha) field key code is documented in the record buffer section of the OP command in the Adabas command reference documentation. A value of zero means that no UES translation will be done.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the User Data Alpha Key parameter in Step 2. Supply General Subscription Information.
The subscription data sent to the Event Replicator Target Adapter is wrapped in XML messages. By, default the data is assumed to be encoded in US-EBCDIC (SACODE=37) and is converted to Unicode by the Event Replicator Target Adapter for interpretation. EBCDIC values for alphanumeric characters X’40’ thru X’FF’ are sent unchanged; EBCDIC values for alphanumeric fields under X’40’ are translated to spaces.
If the source data is in a different code page, the parameter SACODE must be specified. The SACODE is sent with the subscription data so that the Event Replicator Target Adapter can convert it correctly. Not all source encodings can be specified because of conflicts with the Event Replicator Target Adapter protocol. Only SACODE settings of 37, 424, 813, 912, 915, 920, 922, 923, 1006, 1112, 1140, 1256, and 4091 are valid. The following table lists the single byte EBCDIC source encodings and their possible subscription encodings. If a specified encoding is not supported, a warning message will be printed and encoding 37 (EBCDIC) will be used.
Note:
For double-byte host encodings, SACODE should be set to 4091
(UTF-8). If you want to use UTF-8 character encoding, you must verify that your
field lengths are increased as required to accommodate UTF-8 character
encoding.
| Source Encoding | Description | SACODE Setting |
|---|---|---|
| 37 | IBM037: USA, Canada, etc. (EBCDIC) | 37 |
| 273 | IBM273: Austria, Germany (EBCDIC) | |
| 277 | IBM277: Denmark, Norway (EBCDIC) | |
| 278 | IBM278: Finland, Sweden (EBCDIC) | |
| 280 | IBM280: Italy (EBCDIC) | |
| 284 | IBM284: Spanish (EBCDIC) | |
| 285 | IBM285: United Kingdom (EBCDIC) | |
| 290 | EBCDIC Japanese Katakana | 4091 |
| 297 | IBM297: France (EBCDIC) | 37 |
| 420 | IBM420 Arabic (presentation shapes) (EBCDIC) | 1256 |
| 424 | IBM424 Hebrew (EBCDIC) | 424 |
| 500 | IBM500: Belgium, Canada, Swiss International | 37 |
| 803 | Old Hebrew EBCDIC ibm-803_P100-1999 | 424 |
| 836 | Simplified Chinese Host Extended SBCS (EBCDIC) | |
| 870 | IBM870 Multilingual: Latin-2 (EBCDIC) | 912 |
| 871 | IBM871 CECP: Iceland (EBCDIC) | 37 |
| 875 | Greek (EBCDIC) | 813 |
| 918 | IBM918 Urdu (EBCDIC) | 1006 |
| 924 | IBM00924: Latin-15, Belgium, Canada, Swiss, International | 923 |
| 1025 | Cyrillic Multilingual (EBCDIC) | 915 |
| 1026 | IBM1026 Turkey Latin-5 (EBCDIC) to ISO-8859-9 | 920 |
| 1027 | Japanese Latin Host Extended SBCS (EBCDIC) | 4091 |
| 1047 | EBCDIC Latin 1 Open Systems | 37 |
| 1112 | Baltic, Multilingual (EBCDIC) | 1112 |
| 1122 | Estonia (EBCDIC) | 922 |
| 1140 | IBM01140: USA, Canada, (Euro) | 1140 |
| 1141 | IBM01141: Austria, Germany (EBCDIC Euro) | |
| 1142 | IBM01142: Denmark, Norway (EBCDIC Euro) | |
| 1143 | IBM01143: Finland, Sweden (EBCDIC Euro) | |
| 1144 | IBM01144: Italy (EBCDIC Euro) | |
| 1145 | IBM01145: Spanish (EBCDIC Euro) | |
| 1146 | IBM01146: United Kingdom (EBCDIC Euro) | |
| 1147 | IBM01147: France (EBCDIC Euro) | |
| 1148 | IBM01148: Belgium Canada Swiss (EBCDIC Euro) | |
| 1149 | IBM01149: Iceland (EBCDIC Euro) | |
| 3585 | DF.03 International CCSN:EDF03IRV | 37 |
| 3586 | DF.03 CCSN:EDF03 Austria, Germany | |
| 3587 | DF.03 CCSN:EDF03 Austria, Germany | |
| 3588 | DF.04-DRV LATIN 1, Austria, Germany | |
| 3589 | DF.04-1 LATIN 1, International | |
| 3709 | IBM28709: Trad. Chinese Host Ext. SBCS (EBCDIC) | |
| 4094 | Old TS default EBCDIC |
In the following example, IBM424 Hebrew (EBCDIC) encoding is requested for replicated data via the SACODE=424 parameter. Because the source database is not UES-enabled in this case, the SFDEFAULTACODE=803 parameter specifies the encoding of the source data (in this case, Old Hebrew EBCDIC).
ADARPD SUBSCRIPTION NAME=EMPLOYEE ADARPD SDESTINATION='OUT4' ADARPD SACODE=424 <- target encoding *) ADARPD SFILE=11,SFDBID=10006,SFDEFAULTACODE=803 <- source encoding **)
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SACTIVE | whether the subscription definition should be activated once it is loaded. | "YES" or "NO" | YES |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Subscription Active parameter in Step 2. Supply General Subscription Information.
If "YES" is specified, the subscription definition is loaded and activated at Event Replicator Server startup; if "NO" is specified, the definition is loaded but not activated at Event Replicator Server startup (it is inactive).
Only activated subscription definitions can be used during replication. If you need to activate an inactive subscription definition after Event Replicator Server startup, use the Replicator Activate/Deactivate screen of the Adabas Online System. For more information, read Adabas Online System Features Supporting Event Replicator for AdabasAdabas Online System Features Supporting Event Replicator for Adabas.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SARC | the desired output architecture key. This can only be set when the Event Replicator Server has been started with Universal Encoding Support (UES) enabled. | 0-11 | 2 |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Architecture Key parameter in Step 2. Supply General Subscription Information.
The architecture key is an integer that is calculated as the sum of the following numbers (this is the same as is documented in the record buffer section of the OP command in the Adabas Command Reference Guide):
| byte order | b=0 | high-order byte first |
|---|---|---|
| b=1 | low-order byte first | |
| encoding family | e=0 | ASCII encoding family |
| e=2 | EBCDIC encoding family (default for local calls) | |
| floating-point format | f=0 | IBM370 floating-point format |
| f=4 | VAX floating-point format | |
| f=8 | IEEE floating-point format |
If UES has not been enabled, leave this parameter set to "2".
Note:
If you want to transfer replicated and initial-state data to
a relational database using the Event Replicator Target Adapter (in otherwords the
DCLASS
parameter is set to "SAGTARG"), set the
SARC parameter to "2" -- regardless of the location
of your relational database.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SDEACTIVATE | whether the subscription should be deactivated when one or more of the files assigned to it are deactivated. | "YES" or "NO" | YES |
If "YES" is specified, the subscription is deactivated when one or more of the files assigned to it are deactivated; if "NO" is specified, the subscription is not deactivated when one of its files is deactivated.
While this is an optional feature, we recommend that you use the default or specify SDEACTIVATE=YES to ensure that the integrity of your replicated data is maintained when a file becomes deactivated. If the subscription is deactivated because one of its files is deactivated, any other files referenced by this subscription are also deactivated unless they are also referenced by another active subscription.
If replication for this file in the subscription is unrelated to the replication for other files in the same subscription, the integrity of the replicated data may not be at risk. In this case, SDEACTIVATE=NO might be specified.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Deactivate if file deactivated parameter in Step 2. Supply General Subscription Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SDESTINATION | the name or names of the destination definitions used by the subscription. | alphanumeric; 1-8 characters | none |
This parameter is required. A matching destination name must be defined through the DESTINATION parameter (and its sub-parameters). Data processed for the subscription will be sent to this destination. This parameter can be specified more than once for one subscription.
At least one destination must be specified (and a maximum of 32 destinations may be specified) in the SDESTINATION or SIDESTINATION parameters.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about specifying destinations for the subscription in Step 3. Specify One or More Destinations for the Subscription.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFBAI | the format buffer used when decompressing the data storage after image. | Valid Adabas format buffer up to 40 characters | none |
| SGFORMATAI | the name of the global format buffer definition to be used when decompressing the data storage after image. The global format definition must be defined through the parameters GFORMAT and GFB. | Valid global format buffer definition name (maximum of seven characters) | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the After Image FB and After Image GFB Name parameters in Step 2. Specify SFILE Definition Information.
Format buffers for data storage after images must conform to the format buffer rules (for a read command) documented in the Adabas command reference documentation.
Parameters SFBAI and SGFORMATAI are mutually exclusive. One of these parameters must be specified for a specific input DBID/file.
Note:
The maximum length of a format buffer specified in parameter
SFBAI is 40. This is a temporary restriction. If a longer format buffer is
needed, take the following steps:
Specify the longer format buffer in the GFORMAT and GFB parameters.
Specify SGFORMATAI to use the related global format.
PE and MU fields cannot use the range notation 1-N in format buffers for a subscription that is sent to a destination that has specified the replication intialization parameter DCLASS=SAGTARG. The SAGTARG application invoked requires that the range of occurrences specified are contained in the record buffer even if they are empty occurrences. 1-N results in a range of 1-191, but unless there are 191 occurrences containing data, space in the record buffer is not allocated for any empty occurrences, resulting in incorrect field positioning when processing the record.
If the destination target for replicated data is an Adabas
mainframe database running Adabas 8.1.3 or later, you can specify the symbolic
notation "C." alone as the SFBAI parameter value
(for example, SFBAI=’C.’). This notation will cause the
Event Replicator Server to replicate the entire source record to the
target mainframe Adabas database. Likewise, the SGFORMATAI parameter can
reference a GFB that uses this symbolic notation.
Caution:
This "C." option may be used
only if the destination target file has been defined with the same
fields in the same order as the fields in the source file; if there are
differences in the definitions of the files, the replication of the data is
likely to incur errors. The only exception to this rule is that the definitions
of the descriptors and superdescriptors in the target and source files may be
different.
If you are using the Event Replicator Target Adapter, the value used for the SGFORMATAI parameter and the SGFORMATBI parameter must be the same. In addition, the key image global format buffer specified in the SGFORMATKEY parameter must have been built from a Predict user view with the same name as the user view used to build the before and after images, but with the suffix "-KEY" on the end. (Likewise, if you use the Data Mapping Tool, the SGFORMATKEY GFB should be built from a DDM with the same name as the DDM used to build the before and after image GFBs.) Event Replicator processing strips off the "-KEY" to ensure that any delete is associated with the before and after image file name that was used to build the table(s) in the RDBMS.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFBBI | the format buffer used when decompressing the data storage before image. | Valid Adabas format buffer up to 40 characters | none |
| SGFORMATBI | the name of the global format buffer definition to be used when decompressing the data storage before image. The global format definition must be defined through the parameters GFORMAT and GFB. | Valid global format buffer definition name (maximum of seven characters) | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Before Image FB and Before Image GFB Name parameters in Step 2. Specify SFILE Definition Information.
Format buffers for data storage before images must conform to the format buffer rules (for a read command) documented in the Adabas command reference documentation.
The SFBBI and SGFORMATBI parameters are mutually exclusive. If neither of these parameters is specified, the parameter specified for the after image (for example, SFBAI or SGFORMATAI) will be used.
Note:
The maximum length of a format buffer specified in parameter
SFBBI is 40. This is a temporary restriction. If a longer format buffer is
needed, take the following steps:
Specify the longer format buffer in the GFORMAT and GFB parameters.
Specify SGFORMATBI to use the related global format.
PE and MU fields cannot use the range notation 1-N in format buffers for a subscription that is sent to a destination that has specified the replication intialization parameter DCLASS=SAGTARG. The SAGTARG application invoked requires that the range of occurrences specified are contained in the record buffer even if they are empty occurrences. 1-N results in a range of 1-191, but unless there are 191 occurrences containing data, space in the record buffer is not allocated for any empty occurrences, resulting in incorrect field positioning when processing the record.
If you are using the Event Replicator Target Adapter, the value used for the SGFORMATAI parameter and the SGFORMATBI parameter must be the same. In addition, the key image global format buffer specified in the SGFORMATKEY parameter must have been built from a Predict user view with the same name as the user view used to build the before and after images, but with the suffix "-KEY" on the end. (Likewise, if you use the Data Mapping Tool, the SGFORMATKEY GFB should be built from a DDM with the same name as the DDM used to build the before and after image GFBs.) Event Replicator processing strips off the "-KEY" to ensure that any delete is associated with the before and after image file name that was used to build the table(s) in the RDBMS.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFBKEY | the format buffer used when decompressing the key-related before image. | Valid Adabas format buffer up to 40 characters | none |
| SGFORMATKEY | the name of the global format buffer definition to be used when decompressing the key-related before image. The global format definition must be defined through the parameters GFORMAT and GFB. | Valid global format buffer definition name (maximum of seven characters) | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Key-Related Before Image FB and Key-Related GFB Name parameters in Step 2. Specify SFILE Definition Information.
Format buffers for key-related before images must conform to the format buffer rules (for an L9 command) documented in the Adabas command reference documentation.
The SFBKEY and SGFORMATKEY parameters are mutually exclusive. If a key-related before image is received and SFBKEY/SGFORMATKEY have not been specified, the field name followed by a period will be used for the format buffer.
If you are using the Event Replicator Target Adapter, the value used for the SGFORMATAI parameter and the SGFORMATBI parameter must be the same. In addition, the key image global format buffer specified in the SGFORMATKEY parameter must have been built from a Predict user view with the same name as the user view used to build the before and after images, but with the suffix "-KEY" on the end. (Likewise, if you use the Data Mapping Tool, the SGFORMATKEY GFB should be built from a DDM with the same name as the DDM used to build the before and after image GFBs.) Event Replicator processing strips off the "-KEY" to ensure that any delete is associated with the before and after image file name that was used to build the table(s) in the RDBMS.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFDBID | the DBID associated with the SFILE parameter. | Valid database ID | The value of the DBID parameter. |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the DBID parameter in Step 2. Specify SFILE Definition Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFDEFAULTACODE | a default, at the subscription file level, for the file’s alpha character encoding. The encoding must belong to the EBCDIC encoding family; that is, the space character must be X’40’.’. This can only be set when the Event Replicator Server has been started with Universal Encoding Support (UES) enabled. | alpha character code page number | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Default Code parameter in Step 2. Specify SFILE Definition Information.
This parameter is meant to be used when all of the following conditions are met:
The Event Replicator Server is UES-enabled,
The source database is not UES-enabled
The subscription definition requests UES translation (i.e. parameter SACODE is specified)
The data in the source database file is stored in a code page other than the default alpha encoding.
At the time a before or after image is decompressed and translated in the Event Replicator Server, the file encoding is taken as follows:
from the source FCB;
if the encoding is not set above, from the GCB of the source database;
if the encoding is not set above, from the value set for this parameter (SFDEFAULTACODE);
if the encoding is not set above, from the GCB of the Event Replicator Server.
Note that if the source database is UES-enabled, the file encoding will be taken from either 1 or 2 above.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFFILTER | a transaction filter definition that should be used by the SFILE definition. | Valid transaction filter name | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Transaction Filter parameter in Step 2. Specify SFILE Definition Information.
Transaction filter definitions specify filter conditions for specific fields within the SFILE record. When the conditions are met, the record is selected either to be included in replication processing or to be excluded from replication processing, depending on the FRECORDS setting in the transaction filter definition. Transaction filter definitions are defined by the FILTER initialization parameter and its related parameters and subparameters.
Note:
Any filter field specified in a transaction filter definition
used by a subscription file (SFILE) definition must also be included in either
the format buffers for the SFILE definition (SFBAI, SGFORMATAI, SFBBI, and SGFORMATBI parameters) or in filter format buffers
for the SFILE definition (SFFILTERGFBAI and
SFFILTERGFBBI parameters).
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFFILTERGFBAI | the name of the global format buffer definition (GFB) to be used when filtering the data storage after image as described by the SFFILTER parameter. The global format definition must be defined through the parameters GFORMAT and GFB. | Valid global format buffer definition name (maximum of seven characters) | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Filter After Image FB parameter in Step 2. Specify SFILE Definition Information.
The SFFILTERGFBAI parameter specifies the after image filter format buffer for a subscription file (SFILE) definition. Ordinarily it is optional. It is only required if both of the following conditions are met:
A transaction filter definition is specified in the SFFILTER parameter of the SFILE definition.
The format buffer or global format buffer specified for the data storage after image in the SFILE definition does not contain one or more of the fields defined in the filter.
For example, suppose the SFFILTER parameter identifies a
transaction filter that filters the data storage after image for the field AA.
But suppose the normal after image format buffer for the SFILE definition does
not include field AA (it might be 'C.' or some other format
buffer). Normally, this combination of specifications will not work. However,
if you include an SFFILTERGFBAI parameter that specifies a global format buffer
that includes field AA, after image records are processed as described by the
filter and the associated after image filter format buffer.
This parameter can be used to improve the performance of Event Replicator processing. For example, if most records for a large format buffer are being rejected due to a filter based on the contents of a small number of fields, it may help to specify the key fields in a filter format buffer so that, for most records, only the fields required to make acceptance/rejection decisions are decompressed instead of the entire buffer.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFFILTERGFBBI | the name of the global format buffer (GFB) definition to be used when filtering the data storage before image as described by the SFFILTER parameter. The global format definition must be defined through the parameters GFORMAT and GFB. | Valid global format buffer definition name (maximum of seven characters) | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Filter Before Image FB parameter in Step 2. Specify SFILE Definition Information.
The SFFILTERGFBBI parameter specifies the before image filter format buffer for a subscription file (SFILE) definition. Ordinarily it is optional. It is only required if both of the following conditions are met:
A transaction filter definition is specified in the SFFILTER parameter of the SFILE definition.
The format buffer or global format buffer specified for the data storage before image in the SFILE definition does not contain one or more of the fields defined in the filter.
For example, suppose the SFFILTER parameter identifies a
transaction filter that filters the data storage before image for the field AA.
But suppose the normal before image format buffer for the SFILE definition does
not include field AA (it might be 'C.' or some other format
buffer). Normally, this combination of specifications will not work. However,
if you include an SFFILTERGFBBI parameter that specifies a global format buffer
that includes field AA, before image records are processed as described by the
filter and the associated before image filter format buffer.
This parameter can be used to improve the performance of Event Replicator processing. For example, if most records for a large format buffer are being rejected due to a filter based on the contents of a small number of fields, it may help to specify the key fields in a filter format buffer so that, for most records, only the fields required to make acceptance/rejection decisions are decompressed instead of the entire buffer.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFILE | the file number of input data processed by the subscription. | Valid file number | none |
The combination of SFDBID and SFILE is used to determine whether or not input data is processed for the subscription. One or more combinations of SFDBID and SFILE (along with the related subparameters) may be specified for a subscription. The number of SFILEs allowed for a given subscription depends on the GLOBALS NUMSFILE setting.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the File Number parameter in Step 2. Specify SFILE Definition Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFREPLICATEDELETE | whether replication should occur if an input record for the database file is for a delete. | "YES", "NO", or "UPDATE" | YES |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Replicate for Delete parameter in Step 2. Specify SFILE Definition Information.
Note:
IF SFREPLICATEDELETE is set to UPDATE, a value must be
specified for the SFSEXIT parameter. In addition, the format buffer before and
after images must be identical.
If SFREPLICATEDELETE=NO is specified and an input record for the DBID/file is for a delete, the input record will NOT be processed for this subscription. If SFREPLICATEDELETE=YES and an input record for the DBID/file is for a delete, the input record will be processed for this subscription.
If SFREPLICATEDELETE=UPDATE is specified and an input record for the DBID/file is for a delete, the before and after images of the input record will be passed to your subscription user exit. Therefore, if SFREPLICATEDELETE=UPDATE is specified, a subscription user exit name must be specified in the SFSEXIT parameter. In addition, the subscription before and after image format buffers must be identical and no primary key should be defined to the file (to ensure that the before image is a copy of data storage). The purpose of the UPDATE value of this parameter is to allow your subscription user exit to process replicated physical delete transactions on your target database as you choose. Your subscription user exit 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.
For more information about using the subscription user exit with SFREPLICATEDELETE=UPDATE, read Controlling Delete Transaction Processing (SFREPLICATEDELETE=UPDATE Processing).
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFREPLICATEINSERT | whether replication should occur if an input record for the database file is for an insert. | "YES" or "NO" | YES |
If SFREPLICATEINSERT=NO is specified and an input record for the DBID/file is for an insert, the input record will NOT be processed for this subscription. If SFREPLICATEINSERT=YES and an input record for the DBID/file is for an insert, the input record will be processed for this subscription.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Replicate for Insert parameter in Step 2. Specify SFILE Definition Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFREPLICATENOTCHANGED | whether an update request should be replicated if the after image (AI) is the same as the before image (BI). | "YES" or "NO" | YES |
If SFREPLICATENOTCHANGED=YES is specified and the AI and BI record images are the same, the record will be replicated, subject to any transaction filters that may be specified for the SFILE file. If SFREPLICATENOTCHANGED=NO is specified and the AI and BI record images are the same, no further processing will occur for the record.
Note:
The format buffer used for the AI and BI record images must
be the same as the comparison to determine if they are identical is simply done
against the decompressed records.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Include Identical Records parameter in Step 2. Specify SFILE Definition Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFREPLICATEUPDATE | whether replication should occur if an input record for the database file is for an update. | "YES" or "NO" | YES |
If SFREPLICATEUPDATE=NO is specified and an input record for the DBID/file is for an update, the input record will NOT be processed for this subscription. If SFREPLICATEUPDATE=YES and an input record for the DBID/file is for an update, the input record will be processed for this subscription.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Replicate for Update parameter in Step 2. Specify SFILE Definition Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFSECURITYFILE | whether replication of the security definitions should occur. The setting of this parameter allows you to define a subscription file (SFILE) definition specifically for security definitions in the Adabas security file on the database. | "YES" or "NO" | NO |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Replicate Security File parameter in Step 2. Specify SFILE Definition Information.
Notes:
When SFSECURITYFILE=NO is specified, replication of the security definitions does not occur and replication processing proceeds normally.
When SFSECURITYFILE=YES is specified for a subscription file definition, replication of the security definitions in the Adabas security file will occur. In addition, the following parameter settings are required:
A format buffer may not be specified. This means that no values may be specified for the SFBAI, SFBBI, SFBKEY, SGFORMATTAI, SGFORMATBI, or SGFORMATKEY parameters.
No value may be specified for the SDEFAULTACODE parameter.
A transaction filter definition may not be specified. This means that no value may be specified for the SFFILTER parameter.
The default value of YES must be specified for the SFREPLICATEDELETE, SFREPLICATEINSERT, SFREPLICATENOTCHANGED, and SFREPLICATEUPDATE parameters.
A subscription exit may not be specified. This means that no value may be specified for the SFSEXIT parameter.
When you specify SFSECURITYFILE=YES, you indicate that the file specified in the SFILE parameter is the file number of the security file for the source database identified by the SFDBID parameter. Therefore, if SFSECURITYFILE=YES is specified for other subscription SFILE definitions using the same source database (with the same SFDBID setting), the same value must be set for each of the SFILE parameters in the SFILE definition. In other words, it is invalid for a source database (SFDBID setting) to have different file numbers specified for the security file in different subscriptions. For example, source database 10 cannot have the security file specified as both file 15 in one SFILE definition and 20 in another SFILE definition.
If SFSECURITYFILE=YES is specified for a source database (SFDBID parameter), then any Adabas destination definitions with same database specified as the destination input database (SFDBID setting equals the DAIDBID setting), must also specify identical file numbers for both the DAIFILE (input file) and DATFILE (target file) parameters.
Note:
Any security file you identify in an SFILE definition cannot
also be used in an initial-state definition. In other words,
Event Replicator for Adabas does not support the use of security
files in initial-state definitions. If you want to populate a target database
with an initial snapshot of the security definitions, read
Initial-State Processing of
Security Definitions.
For complete information about replicating security definitions, read Replicating Security Definitions.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SFSEXIT | the name of a subscription exit | Valid subscription exit name | none |
If a subscription exit is specified, it will be called when replication data is processed for one file/ISN for this subscription, database ID, and file number.
For more information about using the subscription user exit with SFREPLICATEDELETE=UPDATE, read Controlling Delete Transaction Processing (SFREPLICATEDELETE=UPDATE Processing).
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Subscription User Exit parameter in Step 2. Specify SFILE Definition Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SIDESTINATION | a destination name list for the subscription. It specifies where initial-state data is to be sent for the subscription. | Valid destination definition names in single quotes or NONE in single quotes. | The same list as specified for the SDESTINATION parameter |
A matching destination name must be defined via parameter
DESTINATION (and its subparameters)
for each name in the list. If SIDESTINATION is specified, all initial-state
data will be sent to each destination. If SIDESTINATION is NOT specified, the default is
the same list of destinations specified for parameter
SDESTINATION, that is, all data
processed for the subscription, including initial-state data, will be sent to
each destination. If SIDESTINATION='NONE' is specified, no
initial-state process can be performed for the subscription.
At least one destination must be specified (and a maximum of 32 destinations may be specified) in SDESTINATION or SIDESTINATION.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about specifying destinations for the subscription in Step 3. Specify One or More Destinations for the Subscription.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SINCREMENTIS | whether the transaction sequence number should be incremented if an initial-state request is occurring. | "YES" or "NO" | NO |
If "YES" is specified, the transaction sequence number is incremented if an initial-state request is occurring; if "NO" is specified, the transaction sequence number is not incremented.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Increment Initial State Count parameter in Step 2. Supply General Subscription Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SRESENDBUFFER | the name of the resend buffer to be associated with the subscription | Valid resend buffer definition name | none |
A RESENDBUFFER initialization parameter with a corresponding name must be defined.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Resend Buffer Name parameter in Step 2. Supply General Subscription Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| STLFILTER | the transaction logging level when a record in a transaction is being excluded from replication due to extended subscription processing or the subscription user exit. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event, filter reason, and transaction information), "2" (log event, filter reason, transaction, and file/record information), or "3" (log event, filter reason, transaction information, file/record information, and payload data of available images).
This is the equivalent of specifying the Filter Level field in the Adabas Event Replicator Subsystem subscription definition screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Filter Level parameter in Step 5. (Optional) Modify the Transaction Logging Values for the Subscription, as Necessary.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| STLIGNORE | the transaction logging level when a filter condition cannot be evaluated. | 0, 1, or 2 | 0 |
Valid values are "0" (no logging), "1" (log event and filter information), or "2" (log event, filter information, and payload data or available field values).
This is the equivalent of specifying the Filter Ignored field in the Adabas Event Replicator Subsystem subscription definition screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Filter Ignored parameter in Step 5. (Optional) Modify the Transaction Logging Values for the Subscription, as Necessary.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| STLINPUT | the transaction logging level when a transaction is selected for subscription processing. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and input transaction data), "2" (log event, input transaction, and file/record data), or "3" (log event and all available input transaction data for the event).
This is the equivalent of specifying the Input Level field in the Adabas Event Replicator Subsystem subscription definition screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Input Level parameter in Step 5. (Optional) Modify the Transaction Logging Values for the Subscription, as Necessary.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| STLMATCH | the transaction logging level when a filter condition is true. | 0, 1, or 2 | 0 |
Valid values are "0" (no logging), "1" (log event and filter information), or "2" (log event, filter information, and payload data or available field values).
This is the equivalent of specifying the Filter Matched field in the Adabas Event Replicator Subsystem subscription definition screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Filter Matched parameter in Step 5. (Optional) Modify the Transaction Logging Values for the Subscription, as Necessary.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| STLNOMATCH | the transaction logging level when a filter condition is false. | 0, 1, or 2 | 0 |
Valid values are "0" (no logging), "1" (log event and filter information), or "2" (log event, filter information, and payload data or available field values).
This is the equivalent of specifying the Filter Not Matched field in the Adabas Event Replicator Subsystem subscription definition screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Filter Not Matched parameter in Step 5. (Optional) Modify the Transaction Logging Values for the Subscription, as Necessary.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| STLOUTPUT | the transaction logging level when a transaction is to be output on behalf of a subscription. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and output transaction data), "2" (log event, output transaction, and file/record data), or "3" (log event and all available output information for the event).
This is the equivalent of specifying the Output Level field in the Adabas Event Replicator Subsystem subscription definition screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Output Level parameter in Step 5. (Optional) Modify the Transaction Logging Values for the Subscription, as Necessary.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SVERSION | a user-specified subscription version indicator. | Up to 2 characters | blanks |
The SVERSION parameter has no meaning to the Event Replicator Server. The subscription version indicator will be passed as a part of the header information sent to the output destination. Its use allows the target application to handle changes in the subscription definition.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Subscription Version parameter in Step 2. Supply General Subscription Information.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SWCODE | the desired output-wide code. This can only be set when the Event Replicator Server has been started with Universal Encoding Support (UES) enabled. | numeric | none |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the User Data Wide Key parameter in Step 2. Supply General Subscription Information.
The W (w-char) field key code is documented in the record buffer section of the OP command in the Adabas Command Reference documentation.
Wide-character fields sent to Event Replicator Target Adapter are translated to hexadecimal. However, support for UTF-8 encoding is available for internationalization purposes. To send wide-character fields to Event Replicator Target Adapter using UTF-8 format, make sure the SWCODE parameter is set to "4091" in the Event Replicator subscription definition used for Event Replicator Target Adapter processing.
Below is an example using the DESTINATION and SUBSCRIPTION parameters to specify that replicated data from DBID 6, file 2 is replicated to DBID 60, file 20:
ADARPD DESTINATION NAME=ADA1 ADARPD DTYPE=ADABAS ADARPD DAIFILE=2,DAIDBID=6,DATDBID=60,DATFILE=20 * ADARPD SUBSCRIPTION NAME=SUB300 ADARPD SDESTINATION='ADA1' ADARPD SFILE=2 ADARPD SFDBID=6 ADARPD SFBAI='AA,BA,BB,BC,BD,CA,CB,CD,CE,CF.'
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SUBTASKS | the number of output subtasks in the Event Replicator Server. | integer, 0-15 | 3 |
A specific destination will be handled by only one output subtask at a time.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Subtasks parameter in Setting Global Values.
SUBTASKS=n
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| SUBTASKWAIT | the number of seconds the Event Replicator Server will wait for the successful initialization of an input or output subtask. | 1 - 3600 | 10 |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Subtask Activation Wait parameter in Setting Global Values.
SUBTASKWAIT=n
Global transaction log settings can be specified using the following parameters:
[TLCOMP={0|1 }]
[TLINPUT={0|1|2|3 }]
[TLISTATE={0|1|2|3 }]
[TLISTATECOMP={0|1|2|3 }]
[TLMAX=[n|50 ]
[TLNOSUB={0|1|2|3 }]
[TLQCOMP={0|1|2|3 }]
[TLREQERR={0|1|2|3 }]
[TLREQRECV={0|1|2 }]
[TLREQREJECT={0|1|2|3 }]
[TLRESTART=[{n|40 ]
[TLRETRANS={0|1|2|3 }]
[TLSTATUS={0|1|2|3 }]
Transaction log settings can also be specified for specific destination and subscription definitions. For information on those TLOG settings, read DESTINATION Settings and SUBSCRIPTION Settings, elsewhere in this documentation.
This section covers the TLOG settings:
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLCOMP | 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. | 0 or 1 | 0 |
Valid values are "0" (no logging) or "1" (log event and input transaction data).
This is the equivalent of specifying the Completion Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Completion Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLINPUT | the level of transaction logging that should occur when a transaction is taken off the input queue and put on the transaction assignment queue. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and input transaction data), "2" (log event, input transaction, and file/ record information), and "3" (log event and all available input information for the event.
This is the equivalent of specifying the Input Queue Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Input Queue Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLISTATE | the level of transaction logging that should occur when a user request for initial-state information for a file has started. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI), or "3" (log event, URBS, and URBI).
This is the equivalent of specifying the I-State Start Request Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the I-State Start Request Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLISTATECOMP | the level of transaction logging that should occur when an initial-state information request has completed. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI, if available), or "3" (log event, URBS, and URBI, if available).
This is the equivalent of specifying the I-State Completion Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the I-State Completion Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLMAX | the maximum percentage of the Event Replicator replication pool that can be used for transaction log (TLOG) processing. | 1 - 100 | 50 |
The setting for this parameter must always be greater than the setting for the TLRESTART parameter.
This is the equivalent of specifying the Maximum RPL Usage global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Maximum RPL Usage parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLNOSUB | the level of transaction logging that should occur when a transaction is not queued to any subscription in the Event Replicator Server. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and input transaction data), "2" (log event, input transaction, and file/record information), or "3" (log event and all available input information for the event).
This is the equivalent of specifying the No Match Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the No Match Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLQCOMP | the level of transaction logging that should occur prior to a transaction being assigned to the completion queue. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and input transaction data, "2" (log event, input transaction, and file/record information), or "3" (log event and all input information available for the event).
This is the same as specifying the Queue Completion Level global value directly in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Queue Completion Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLREQERR | the level of transaction logging that should occur when a user request is rejected due to an error in carrying out the request. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI), or "3" (log event, URBS, and URBI).
This is the equivalent of specifying the Request Error Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Request Error Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLREQRECV | the level of transaction logging that should occur when a user request has been received. | 0, 1, or 2 | 0 |
Valid values are "0" (no logging), "1" (log event but no data), or "2" (log event and the entire input buffer before and after translation if appropriate).
This is the equivalent of specifying the Request Received Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Request Received Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLREQREJECT | the level of transaction logging that should occur when a user request is rejected due to an error in interpreting the request. | 0, 1, or 2 | 0 |
Valid values are "0" (no logging), "1" (log event but no data), or "2" (log event, error code, and entire input buffer).
This is the equivalent of specifying the Request Rejected Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Request Rejected Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLRESTART | the amount of available Event Replicator replication pool storage that must be available before transaction logging (TLOG logging) can restart. | 0 - 99 | 40 |
The setting for this parameter must always be less than the setting for the TLMAX parameter.
This is the equivalent of specifying the Restart RPL Usage Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Restart RPL Usage parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLRETRANS | the level of transaction logging that should occur when a user request to retransmit a specific transaction has been processed. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI), or "3" (log event, URBS, and URBI).
This is the equivalent of specifying the Retransmit Request Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Retransmit Request Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| TLSTATUS | the level of transaction logging that should occur when a user request for status on an Event Replicator Server resource has been processed. | 0, 1, 2, or 3 | 0 |
Valid values are "0" (no logging), "1" (log event and URBS), "2" (log event and URBI), or "3" (log event, URBS, and URBI).
This is the equivalent of specifying the Status Request Level global value in the Adabas Event Replicator Subsystem screens.
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the Status Request Level parameter in Setting Global Values.
| Parameter | Specify . . . | Possible Values | Default |
|---|---|---|---|
| VERIFYMODE | whether the Event Replicator for Adabas should run in verify (test) mode or not. | YES | NO | NO |
This parameter can be maintained online in Adabas Event Replicator Subsystem (SYSRPTR). For more information, read about the VERIFYMODE parameter in Setting Global Values.
When VERIFYMODE=YES is specified during
Event Replicator Server startup, Event Replicator for Adabas
assumes that it is in test mode and performs the following processing:
All of the non-null destinations specified in the Replicator system file or as DDKARTE statements in the Event Replicator Server startup job are first changed to null destinations to ensure that data is not actually written to the destinations. A message is sent to the job log for each changed destination.
Event Replicator for Adabas runs, testing all of its definitions as it does so, without actually writing any data to the destinations.
When errors occur during subscription decompression, a related message is sent to the job log for the first occurrence of the error for a given subscription-SFILE-image definition combination. (Decompression failures are always noted in the DRPLPARM output, regardless of the setting of the VERIFYMODE parameter.)
If no errors occur during subscription decompression, a
related messages is sent to the job log for the first successful decompression
of a given subscription-SFILE-image definition combination. In addition,
successful decompression attempts are noted in the DRPLPARM output when
VERIFYMODE=YES.
VERIFYMODE=[YES | NO]