ADAQnn messages are received from the Adabas Review hub.
Note:
Each of the messages in this section starts with the relevant database
ID.
ADAQ89 | ADAQ90 | ADAQ91 | ADAQ92 | ADAQ93 | ADAQ94 | ADAQ95 | ADAQ96 | ADAQ97 | ADAQ98 | ADAQ99| ADAQ89 | Possible conflict between REVIEW nub and UEX4. RAOSEXIT disabled. |
| Explanation |
The Adabas Review hub was enabled by specifying the REVIEW parameter with a hub ID value in addition to the UEX4 parameter. The user exit 4 module, however, was identified as RAOSEXIT, a Review user exit that is not compatible with the Adabas Review hub. The Adabas nucleus completes its initialization but no calls to user exit 4 are performed by ADALOG. |
| Action: |
If the UEX4 parameter is left over from a previous conversion, remove the parameter. Otherwise, supply the correct user exit 4 module name. |
| ADAQ90 | REVIEW hub inaccessible because REVIEW HUBID was not specified. |
| Explanation |
The REVIEW hub ID value was zero. The Adabas nucleus completes its initialization but no calls are made to the Adabas Review hub. |
| Action: |
Specify the correct REVIEW hub ID value and restart the nucleus. |
| ADAQ91 | module-name monitoring system initialization failed. See error messages. |
| Explanation |
The specified monitoring system component returned a nonzero status. Such a failure is accompanied by error messages displayed by the monitoring system. The Adabas nucleus completes its initialization but no calls are made to the monitoring system. |
| Action: |
Check the monitoring system error messages, correct the cause of the error, and restart the nucleus. |
| ADAQ92 | module-name monitoring system was not loaded. Contact your vendor. |
| Explanation |
The specified monitoring system component could not be loaded. It is possible that the load library containing the expected module was not specified in the job stream of the nucleus. The Adabas nucleus completes its initialization but no calls are made to the monitoring system. |
| Action: |
Correct the cause of the error and restart the nucleus. |
| ADAQ93 | module-name monitoring may be incompleted because ADALOG is not loaded. |
| Explanation |
The command logging module ADALOG was not loaded. The monitoring system cannot process command log records. The Adabas nucleus completes its initialization but no calls are made to the monitoring system. |
| Action: |
Correct the cause of the error and restart the nucleus |
| ADAQ94 | module-name is an incorrect version level. Contact your vendor. |
| Explanation |
The specified module is at an incorrect version level and cannot be used with this version and/or SM-level of Adabas. The Adabas nucleus completes its initialization but no calls are made to the monitoring system. |
| Action: |
Contact your monitoring system vendor to determine if the correct module is being used or supplied. |
| ADAQ95 | module-name does not have the correct PIM. Contact your vendor. |
| Explanation |
The specified module is incompatible with this version and/or SM-level of Adabas. The Adabas nucleus completes its initialization but no calls are made to the monitoring system. |
| Action: |
Contact your monitoring system vendor to determine if the correct module is being used or supplied. |
| ADAQ96 | module-name cannot monitor IOR calls at this time. Unusual error. |
| Explanation |
Adabas cannot give control to the specified monitoring system module for purposes of monitoring I/O activity. The problem is that the Adabas system dependent interface module was not properly loaded. The Adabas nucleus completes its initialization but no calls are made to the monitoring system. |
| Action: |
Note the error message number and module name and call your Software AG technical support for assistance. |
| ADAQ97 | system-name is not a recognized monitor system. Check your parameter. |
| Explanation |
The system setting for the MONITOR parameter (system-name) does not specify a valid monitoring system name. The Adabas nucleus completes its initialization but no calls are made to the monitoring system |
| Action: |
Correct the parameter and restart the nucleus. |
| ADAQ98 | system-name conflicts with REVIEW HUBID parameter. ADABAS REVIEW HUB ASSUMED. |
| Explanation |
The REVIEW parameter with a hub ID value was specified in conjunction with the MONITOR parameter, but the specified monitoring system name was not Adabas Review. Adabas assumes that the monitoring system is Adabas Review and will send its calls to the hub. |
| Action: |
None required if Adabas Review is the desired monitoring system. If the monitoring system is not supposed to be the Adabas Review hub, remove the REVIEW parameter and restart the nucleus. |
| ADAQ99 | REVIEW HUBID = Adabas DBID is not permitted. REVIEW hub inaccessible. |
| Explanation |
The specified REVIEW hub ID value is identical to the value specified for the DBID parameter. The Adabas Review hub cannot have the same target ID as that of the Adabas nucleus. The Adabas nucleus completes its initialization but no calls are made to Adabas Review. |
| Action: |
Correct the REVIEW parameter and restart the nucleus. |
