ARMT01 | ARMT02 | ARMT03 | ARMT04 | ARMT05| ARMT01 | dbid GETMAIN FAILURE, SIZE requested-getmain-size |
| Explanation |
A request for storage in the Adabas nucleus failed. |
| Action |
Either determine what is using so much storage in the Adabas nucleus and correct the problem; or increase the available storage. |
| ARMT02 | dbid ATTACH ADARST FAILURE, STRS nn |
| Explanation |
The Adabas nucleus was unable to attach the subtask ADARST. STRS is the ADAIOR response code. |
| Action |
Probably, the module ADARST is missing. |
| ARMT03 | dbid CLOG TOO BIG, CLOG NOT SENT |
| Explanation |
When an ADABAS nucleus runs Adabas Review in hub mode, the CLOG inclusive CLOG extension and control information may be bigger than around 32K. This CLOG record is not sent to the Adabas Review hub. This message is only issued one time. |
| Action |
One of the buffers may be too big. For instance, you may set LOGRB=NO. |
| ARMT04 | dbid ATTACH OF ADARST SUCCESSFUL |
| Explanation |
The subtask ADARST was attached successfully. The database will send data to the Adabas Review hub. |
| Action |
No action is required for this informational message. |
| ARMT05 | dbid DETACH OF ADARST SUCCESSFUL |
| Explanation |
The subtask ADARST was detached successfully. |
| Action |
Once you have corrected the error that led to detachment of ADARST, you can reactivate the subtask using the ADARUN parameter REVIEW=hubid. The successful ATTACH will be acknowledged with message ARMT04. A restart of the database is in this case not necessary. If the subtask abends a second time, it will be deactivated completely and message ARST10 will be given. |
