ARBIN001I | ARBIN002I | ARBIN003E | ARBIN004W | ARBIN005I | ARBIN006I | ARBIN007E | ARBIN008E
ARBIN001I | Binary TA Exit Startup for dest-name - Version n.n.n.n Built: yyyymmdd |
Explanation |
Event Replicator Target Adapter initialization processing for destination dest-name has been started. The Event Replicator Target Adapter version (n.n.n.n) and the date (yyyymmdd) the Event Replicator Target Adapter code was built are also given in the message. |
Action |
No action is required for this informational message. |
ARBIN002I | Binary TA Exit dest-name Terminating |
Explanation |
Event Replicator Target Adapter termination processing for destination dest-name has been started. |
Action |
No action is required for this informational message. |
ARBIN003E | Required field table information missing for subscription subs-name |
Explanation |
Required field table information was missing for subscription
subs-name during Event Replicator Target Adapter processing. This information
is required by the Event Replicator Target Adapter in order to process the raw data being generated by
the A key image was received for a delete of a record in an Adabas file defined with a primary key for Replication, RPLKEY parameter, and there was no key image defined for the subscription. |
Action |
Verify that you have generated a global format buffer (GFB) for the subscription. If you do not generate a global format buffer using the tools provided in the Adabas Event Replicator Subsystem or if you elect to code a GFB by hand, the required field table information is not constructed for use by the Event Replicator Target Adapter. Check for decompression error messages on the console. If the record cannot be decompressed, the data will not be included with the output and will not be able to be processed by the Event Replicator Target Adapter. For more information, read Generating a GFB in Using the Adabas Event Replicator Subsystem. For more information about correctly activating Event Replicator Target Adapter processing, read Activating Event Replicator Target Adapter Processing. Correct the problem and either run the replay utility for the subscriptions, destinations, and files affected by this error or an initial state for each of the files affected in order to get the files on the target destination back in sync. If the problem persists, contact your Software AG support representative. |
ARBIN004W | Key image for primary key missing for Subscription=xxxxxxxx, DBID=nnnnn, FNR=nnnn |
Explanation |
Required field table information was missing for subscription subs-name during Event Replicator Target Adapter processing. This information is required by the Event Replicator Target Adapter in order to process the raw data being generated by the SAGTRGB destination class exit. |
Action |
Verify that you have generated a key global format buffer (GFB) for the subscription. If a file was defined in ADABAS with the parameter RPLKEY, primary key for replication, defined, then when a delete of a record occurs or an update to the primary key occurs, the before image of the primary key only is sent to the Event Replicator Server nucleus. If the Event Replicator Target Adapter application is the receiver it may not be able to process the record correctly without the key global format buffer. If you do not generate a key global format buffer using the tools provided in the Adabas Event Replicator Subsystem or if you elect to code a key GFB by hand, the required field table information is not constructed for use by the Event Replicator Target Adapter. Check for decompression error messages on the console. If the record cannot be decompressed, the data will not be included with the output and will not be able to be processed by the Event Replicator Target Adapter. For more information, read Generating a GFB in Using the Adabas Event Replicator Subsystem. For more information about correctly activating Event Replicator Target Adapter processing, read Activating Event Replicator Target Adapter Processing. If the problem persists, contact your Software AG support representative. |
ARBIN005I | Destination xxxxxxxx no subscription prefix set |
Explanation |
The destination DCLASSPARM parameter NOSPRE was specified. The parameter indicates you do not want the subscription name to prefix the names of the tables produced by the Event Replicator Target Adapter. |
Action |
No action is required for this informational message. |
ARBIN006I | Destination xxxxxxxx subscription prefix = xxxxxxxx |
Explanation |
The destination DCLASSPARM parameter SPRE was specified. This parameter defines a subscription prefix to be used instead of the subscription name as a prefix for the names of the tables produced by the Event Replicator Target Adapter. |
Action |
No action is required for this informational message. |
ARBIN007E | Destination xxxxxxxx DCLASSPARM subscription prefix parameter invalid and ignored |
Explanation |
The subscription prefix parameter, SPRE, was specified and found to be invalid and will be ignored. |
Action |
Verify that the value for the destination DCLASSPARM subscribtion prefix parameter SPRE is at least 1 character and not more than 8 characters in length. If the problem persists, contact your Software AG support representative. |
ARBIN008E | The DCLASSPARM parameters SPRE and NOSPRE for destination xxxxxxxx are mutually exclusive |
Explanation |
The destination DCLASSPARM no subscription prefix parameter (NOSPRE) and subscription prefix parameter (SPRE) were both specified for the destination and are mutually exclusive. Both parameters are ignored. |
Action |
Remove one of the destination DCLASSPARM subscription prefix parameters. |