ARMX01 | ARMX02 | ARMX03 | ARMX04 | ARMX05 | ARMX06 | ARMX07 | ARMX08 | ARMX97 | ARMX98 | ARMX99
ARMX01 | dbid GETMAIN failure (x), size=requested-getmain-size. |
Explanation |
ADARMX was unable to obtain the necessary GETMAIN space to operate. ADARMX terminates processing. It is probable that the specified region size is too small, or the default region size is too small.
SIZE is the requested GETMAIN size that could not be obtained. The Adabas nucleus completes its initialization, but no calls are made to the Adabas Review hub using the ADARMX interface. |
Action |
Increase the region size for Adabas and restart the nucleus. |
ARMX02 | dbid ATTACH ADARSX FAILURE, STRS nn |
Explanation |
The Adabas nucleus was unable to attach the subtask ADARSX. STRS is the ADAIOR response code. |
Action |
The ADARSX module might not be available. |
ARMX03 | dbid ADARSX stopped, try to re-attach. |
Action |
No action required. This message is for information only. |
ARMX04 | dbid Attach of ADARSX successful. |
Action |
No action required. This message is for information only. |
ARMX05 | dbid Detach of ADARSX successful. |
Action |
No action required. This message is for information only. |
ARMX06 | dbid Review suspended, buffer unavailable. REVIEW parameter is set to NO. |
Explanation |
ADARMX is experiencing a temporary buffer shortage. The ADARUN parameter REVIEW is set to NO when the subtask ADARSX is out of service. |
Action |
To activate Review, change the ADARUN REVIEW parameter. |
ARMX07 | dbid Review resumed, nn CLOG records skipped. |
Explanation |
Buffers have become available after the shortage noted by message ARMX06. (nn) is the number of CLOG records skipped during the shortage. |
Action |
No action required. This message is for information only. |
ARMX08 | dbid Review suspended, subtask unable to initialize. REVIEW parameter is set to NO. |
Explanation |
The subtask ADARSX did not initialize. ADARSX is detached and the message ARMX05 appears. All Adabas Review processing from this nucleus is suspended. |
Action |
After you correct the error that led to the initialization failure of ADARSX, you can reactivate the subtask using the operator command REVIEW=hubid. The successful ATTACH will be acknowledged with message ARMX04. In this case, a restart of the database is not necessary. Otherwise, contact your Software AG technical support representative. |
ARMX97 | dbid ADARSX statistics: dbid CLOGs received: dbid CLOGs processed: dbid CLOG send as bulk: dbid CLOG send single: dbid wake up by POST: dbid TIMER pop ups: dbid UEX5 calls: |
Explanation |
The following statistics of subtask ADARSX are reported at session termination:
|
Action |
No action required. This message is for information only. |
ARMX98 | dbid ADARMX statistics: dbid CLOGs received: dbid CLOGs skipped: dbid Storage allocation: dbid allocation failed: dbid buffer flush: dbid WAIT for ADARSX: dbid POST ADARSX: dbid ATTACH ADARSX: dbid ATTACH ADARSX failed: dbid re_ATTACH ADARSX: dbid DETACH ADARSX: dbid DETACH ADARSX failed: |
Explanation |
The following statistics of subtask ADARMX are reported at session termination:
|
Action |
No action required. This message is for information only. |
ARMX99 | dbid REVIEW HUB bulk interface is initializing: dbid ADARMX built V vrs YYYY-MM-DD HH:MM |
Action |
No action required. This message is for information only. |