Version 8.2.5
 —  Messages and Codes  —

ARXM* - Event Replicator for Adabas Messages for Event Replicator Target Adapter

Overview of Messages

ARXML001I | ARXML002I | ARXML003I | ARXML004I | ARXML005S | ARXML006I | ARXML008S

ARXML001I XML 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.


ARXML002I XML 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.


ARXML003I Destination dest-name now active for jobname
Explanation

Event Replicator Target Adapter processing for destination dest-name has been activated. The job name (jobname) of the Event Replicator Server is also given in the message.

Action

No action is required for this informational message.


ARXML004I Received code event for dest-name
Explanation

Event Replicator Target Adapter processing received the internal event code (code) listed in the message for destination dest-name.

Action

No action is required for this informational message.


ARXML005S 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 for building the XML messages used in Event Replicator Target Adapter processing.

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 in Event Replicator Administration, 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. For more information, read one of the following sections:

  • Generating a GFB using the Adabas Event Replicator Subsystem

  • Generating a GFB using Event Replicator Administration.

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.


ARXML006I Schema generation for subs-name triggered
Explanation

An internal schema is being generated by Event Replicator Target Adapter, based on the field information provided in subscription subs-name. This internal schema maps the replicated data that the Event Replicator Target Adapter then transforms and applies to your relational database.

Action

No action is required for this informational message.


ARXML008S Unsupported code page=acode, default to CP037
Subscription=subname, DBID=dbid, FNR=fnr
Explanation

The code page (acode) listed in the message for the subscription (subname), DBID (dbid), and FNR (fnr) is not supported.

Code page Cp037 will be used for the XML tags and as the code page identifier sent to Event Replicator Target Adapter. Event Replicator Target Adapter will process the data as if it were code page 37, so the data loaded into the RDBMS table(s) may be corrupted. This message is displayed once per combination of incompatible subscription, DBID, file, and code page values.

Action

If use of code page Cp037 is valid, no action is required for this message.

However, if use of code page Cp037 is invalid, you will also want to verify that the data in your RDBMS table is not corrupted and correct it if it is. Then specify the correct code page in the SACODE parameter and try again.


Top of page