Hub System Messages

The Adabas Review hub was enabled by specifying a hub ID on the ADARUN REVIEW parameter. The ADARUN UEX4 parameter was also specified and the user exit 4 module was identified as RAOSEXIT, an Adabas 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.

If the UEX4 parameter is left over from a previous conversion, remove the parameter. Otherwise, supply the correct user exit 4 module name.

The value specified for the Adabas Review hub was invalid. The Adabas nucleus completes its initialization but no calls are made to the Adabas Review hub.

Specify the correct Adabas Review hub ID value and restart the nucleus.

The specified monitoring system component returned a nonzero status. Any failure of this sort should be accompanied by error messages displayed by the monitoring system. The Adabas nucleus completes its initialization but no calls are made to the monitoring system.

Check the monitoring system error messages, correct the cause of the error, and restart the nucleus.

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 nucleus' job stream. The Adabas nucleus completes its initialization but no calls are made to the monitoring system.

Correct the cause of the error and restart the nucleus.

The command logging module ADALOG was not loaded. The monitoring system will not be able to process any command log records. The Adabas nucleus completes its initialization but no calls are made to the monitoring system.

Correct the cause of the error and restart the nucleus

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.

Contact your monitoring system vendor to determine if the correct module is being used or supplied.

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.

Contact your monitoring system vendor to determine if the correct module is being used or supplied.

Adabas cannot give control to the specified monitoring system module for purposes of monitoring I/O activity. 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.

Note the error message number and module name and call your Software AG technical support for assistance.

The parameter MONITOR=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

Correct the parameter and restart the nucleus.

The REVIEW parameter specified a hub ID. The MONITOR parameter was also specified, but the monitoring system name was not Adabas Review. Adabas assumes that the monitoring system is Adabas Review and sends its calls to the hub.

None required if Adabas Review is the desired monitoring system. If the monitoring system is not supposed to be the Adabas Review hub, reset the REVIEW parameter and restart the nucleus.

The specified Adabas 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.

Correct the hub ID value on the REVIEW parameter and restart the nucleus.

The Adabas Review hub session initialization is in progress.

None required. This message is for your information only.

The Adabas Review hub system has successfully initialized.

None required. This message is for your information only.

The Adabas Review hub system has completed its session close processing.

None required. This message is for your information only.

The Adabas Review hub repeats the operator command before continuing.

None required. This message is for your information only.

The issued command was processed by the Adabas Review hub.

None required. This message is for your information only.

This message is displayed in response to the DNC operator command. nnn indicates the number of command queue elements queued for processing by the Adabas Review hub.

This message is also displayed in response to a DCQ operator command in the event that there are no command queue elements waiting to be processed.

None required. This message is for your information only.

This message is displayed in response to the DCQ operator command. The first message displays the expected sequence number nnn that shows which numbered command queue element is in line to be processed next. The following information is displayed for each command queue element:

None required. This message is for your information only.

An Adabas Review hub is started with the hub ID and SVC listed in the message, but another hub with that hub ID and SVC is already running. The new Adabas Review hub comes down.

Determine why one Adabas Review hub was started while another hub with the same ID was already running.

This message is displayed when the Adabas Review hub is terminated. uuuuu is the total number of CQEs used by the hub; ttttt is the total number of CQEs allocated by the hub.

None required. This message is for your information only.

An attempt was made to start a hub database, but the hub ID has not been specified in the REVIEW parameter.

Specify the hub ID on the ADARUN REVIEW parameter and restart the hub database.

ADAREV was unable to establish interregion communication. ADAREV terminates processing.

Identify and correct the error.

ADAREV was unable to establish interregion communication. ADAREV terminates processing.

Identify and correct the error.

The ID table element for ADAREV is no longer marked as being in use by this ADAREV. It is probable that another target (Adabas, ADAREV, etc.) was initialized using the same DBID / Adabas Review hub ID with the FORCE=YES parameter. ADAREV terminates processing.

If another target was inadvertently initialized, quiesce and terminate the target and restart ADAREV. To prevent such problems, ensure that the FORCE=YES parameter is not used for target initialization unless absolutely necessary.

ADAREV tried to process a request but the addressed data area was not addressable, or no longer contained recognizable data. This error occurred while ADAREV was receiving the request (router-08 call processing). It is probable that the client nucleus was terminated while it was sending the request to ADAREV.

None required. ADAREV cannot process this request so it is cleared from the queue.

ADAREV was unable to establish interregion communication due to an unexpected response returned from ADAMPM. ADAREV terminates processing.

Check for system messages from ADAMPM that could identify the error. If the error cannot be identified, keep all dumps, messages, and other related information and contact your Software AG support representative.

ADAREV could not establish operator communications. ADAREV terminates processing.

Identify and correct the error.

ADAREV was unable to establish STIMER services. ADAREV terminates processing.

Identify and correct the error.

ADAREV was unable to obtain the necessary GETMAIN space to operate. ADAREV 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.

Increase the region size for ADAREV and restart.

ADAREV could not load the module REVHUB or the REVHUB module that was loaded is not the correct version or SM-level. ADAREV terminates processing.

Locate the correct REVHUB module, ensure that the module is accessible by ADAREV, and restart ADAREV.

ADAREV processes the requests in the order that the numbered requests are received. This means that ADAREV always knows the next number in sequence that should be received. If there is a discrepancy, this message is displayed along with the expected sequence number and the sequence number actually received. A skipped or missing sequence number can indicate that a request has been dropped by the router. ADAREV continues processing.

Lost requests may indicate that the hub is overloaded. Check the client nuclei for nonzero response codes received from the hub. In some cases, the number of commands (NC) parameter needs to be increased to accommodate the load from the client nuclei. Otherwise, divide up the Adabas Review monitoring work load on multiple hubs.

Either the specified operator command was invalid or incorrectly entered. ADAREV ignores this operator command.

Ensure that the command syntax is valid, and retry the command.

The Adabas Review nucleus returned a non-zero status during initialization.

Check all messages displayed by the Adabas Review nucleus, correct any errors, and restart ADAREV.

The ADAMPM module is not compatible with this version/release of ADAREV. It is probable that the wrong Adabas load library, SM-level, or version is being used. ADAREV terminates processing. It is probable that the wrong Adabas load library is being used.

Locate the correct ADAMPM module, ensure that the module is accessible by ADAREV, and restart ADAREV. If the problem persists even with the correct ADAMPM module, contact your Software AG technical support representative.

ADAREV is terminating due to a previous error.

Correct any errors and restart ADAREV.

A request for storage in the Adabas nucleus failed.

Either determine what is using so much storage in the Adabas nucleus and correct the problem; or increase the available storage.

The Adabas nucleus was unable to attach the subtask ADARST. STRS is the ADAIOR response code.

Probably, the module ADARST is missing.

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.

One of the buffers may be too big. For instance, you may set LOGRB=NO.

The subtask ADARST was not attached, but was reattached sucessfully. The database will send data to the Adabas Review hub again.

No action is required for this informational message.

A request for storage in the Adabas nucleus subtask ADARST failed.

Either determine what is using so much storage in the Adabas nucleus and correct the problem; or increase the available storage.

The specified module cannot be loaded.

Probably, the requested load module is missing.

This message displays ADARST shutdown statistics.

None required. This message is for information only.

An abend occurred in the ADARST subtask of an Adabas nucleus. The abend did occur in the Adabas Review Trans-port routine. To avoid subsequent failures, the ADARUN REVIEW parameter is switched from a hub ID to "NO." The Adabas Review hub is no longer active for the Adabas nucleus.

Check the abend and contact your Software AG technical support representative. If necessary, try switching the ADARUN REVIEW parameter to a hub ID again.

An abend occurred in the ADARST subtask of an Adabas nucleus. The abend did not occur in the Adabas Review Trans-port routine. To avoid subsequent failures, the ADARUN REVIEW parameter is switched from a hub ID to "NO". The Adabas Review hub is no longer active for the Adabas nucleus.

Check the abend and contact your Software AG technical support representative. If necessary, try switching the ADARUN REVIEW parameter to a hub ID again.

The subtask ADARST was detached for one of the following reasons:

• An error occurred when accessing the Adabas Review hub

• The Adabas Review hub returned Adabas response code 148 (not active)

As long as the subtask is not attached, this database will not send data to the Adabas Review hub.

If the reason for the detachment is an unjustified Adabas response code 148, contact your Software AG technical support representative for assistance.

ADARVU was unable to obtain the necessary GETMAIN space to operate. ADARVU 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.

Increase the region size for Adabas and restart the nucleus.

A non-zero Adabas response was received from the Adabas Review hub with the specified target ID when ADARVU sent one of the following requests:

Identify the problem from the Adabas response code. If the problem is parameter settings in the hub, i.e., attached buffer size or command queue size, then the Adabas Review hub must be cycled to reset the parameters. If the Adabas response 148 was received, the Adabas Review hub may have been terminated.

The target ID specified on the REVIEW parameter is not an Adabas Review hub. The target may be another Adabas nucleus. The Adabas nucleus completes its initialization but no calls are made to the Adabas Review hub.

Ensure that the REVIEW parameter specifies the correct target ID of an Adabas Review hub and restart the nucleus.

The operator command REVIEWHUBID=hub-id may be used to change the value to a another target ID.

ADARVU received a response 148 on a request call to the Adabas Review hub. This message is displayed in conjunction with the AREV02 message.

Start the appropriate Adabas Review hub.

On any error condition, ADARVU calls user exit 5 if present. User exit 5 may return one of three possible service requests:

1. Wait for nnnnn seconds, after which ADARVU will resend the request to the Adabas Review hub.

2. Ignore the non-zero response received from the Adabas Review hub and to continue processing.

3. Immediately resend the request to the Adabas Review hub.

The message displays the service request received from the user exit 5. If an unknown request is received from the user exit, the request is ignored and processing continues.

None required, unless the fourth message is displayed. The INVALID REQ message indicates a problem with the user exit 5. Correct the problem and restart the Adabas nucleus, when possible.

This message is displayed in conjunction with the AREV02 message in the event that the non-zero response received by ADARVU is not a RSP 148.

None required. This message is for your information only.

The specified module was not found in the load library and could not be loaded. The Adabas nucleus completes its initialization but no calls are made to the Adabas Review hub.

Ensure that the correct load libraries are specified for the Adabas job and restart the Adabas nucleus.

Whenever an unexpected response is received by ADARVU, the count of the number of non-zero responses is incremented and this message is displayed.

None required. This message is for your information only.

During session initialization, ADARVU checks if a user exit 5 has been loaded. This message displays whether the user exit 5 was located or not.

None required. This message is for your information only.

During session initialization, ADARVU issues a call to the specified Adabas Review hub. When a successful connection is established, this message is displayed.

None required. This message is for your information only.

The Adabas Review hub notified the client nucleus that it changed the monitoring or reporting status of the client nucleus. ADARVU then displays this message accompanied by the ARVU13 message set.

None required. This message is for your information only.

ADARVU detected that the hub-id specified in the REVIEW parameter was changed dynamically by an operator command.

None required. This message is for your information only.

Possible message texts:

• dbid {NO | count } REVIEW REPORT(S) STARTED ARVU13 dbid {NO | count } REPORT(S) REQUIRING BUFFERS
  In conjunction with the ARVU11 message, these messages indicate the status of information transmitted from the client nucleus to the hub. If no Adabas Review report(s) are started, ADARVU does not send data to the hub. If there is at least one report started, then ADARVU transmits the command log data to the hub.

  If at least one report requires buffers, ADARVU transmits the requested Adabas control buffer data in addition to the command log data. The count indicates the number of started reports and/or the number of reports requiring buffers.

  No action required. This message is for your information only.

• dbid TRANSPORT INITIALIZED, MEMORY mmmmmmmm
  BS2000: The nucleus accessed the hub through the Adabas Review Trans-port and uses the common memory defined by mmmmmmmm.

  No action required. This message is for your information only.

• dbid RTPSSPC, REVIEW HUB COULD NOT BE FOUND IN IDT
  BS2000: The nucleus tried to access a hub with a DBID that is unknown to the system. The IDT is a table of databases or nodes still active in the system.

  Use the Utility IDTLOOK to check for active IDs in the table. Check also on the use of the GROUPS=NO/YES parameter. Otherwise, contact SAG support.

• dbid RTPSSPC, HEADER HAS xxxxxxxx AND DBID dddddddd
  BS2000: The stored Adabas Review Trans-port header has an ID that is different from the one in the request. This header exists in a common memory pool and should have an eyecatcher of ADAPCTRA and the Hub's dbid. This doesn't check.

  Contact Software AG Support with dump and protocol information.

• dbid RTPSSPC, REVIEW HUB hubid HAS BEEN REMOVED FROM THE IDT
  BS2000: The hub ID requested is no longer active.

  Use the Utility IDTLOOK to check for active IDs in the table. Check also on the use of the GROUPS=NO/YES parameter. Otherwise contact SAG support.

• dbid REVIEW HUB TRANSPORT INITIALIZED, MEMORY mmmmmmmm
  BS2000: The hub started Adabas Review Trans-port with the memory mmmmmmmm.

  No action Required. This message is for your information only.

• dbid RTPINIT, REVIEW HUB COULD NOT BE FOUND IN IDT
  BS2000: The hub has not successfully registered with the ID Table. The IDT is a table of databases or nodes still active in the system.

  Check in the output protocol for other error messages from the Adabas MPM. Otherwise contact SAG support.

• dbid RTPINIT, CANNOT GET HEADER, SIZE ssssssss, MEMORY mmmmmmmm
  BS2000: The hub cannot acquire an Adabas Review Trans-port header of size ssssssss using memory mmmmmmmm.

  Check memory allocation parameters in use in the Adabas Review Hub. Otherwise contact SAG Support.

• dbid RTPINIT, COULD NOT ESTABLISH EXIT FOR RTPTERM - RC rrrrrrrr
  BS2000: The RTPTERM exit module could not be established in the Hub's task.

  Send Hub output protocol to SAG Support.

ADARVU received a change order from an Adabas Review hub that is not the hub to which ADARVU is currently sending data. The may happen if another hub is initialized that has started reports for the client nucleus. ADARVU ignores the change order.

Find out what has issued the strange change order.

An ABEND occurred in the Adabas Review Trans-port interface routine. An SVC dump is taken. Adabas Review Trans-port is disabled, but records continue to be logged to Adabas Review hub from the client nucleus.

Retain all dumps, messages, and other related information; contact your Software AG technical support representative.

The Adabas Review hub accepts buffered CLOG records from the client nucleus as a way of reducing the number of cross-memory calls from the client nucleus to the hub.

None required. This message is for your information only.

The Adabas Review hub is not accepting buffered CLOG records from the client nucleus.

Check the job log of the Adabas nucleus and the Adabas Review hub, why the Adabas Review hub refuses to accept buffered CLOG records.

z/OS only. The Adabas nucleus runs with the Adabas Review Trans-port feature when sending CLOG records to the Adabas Review hub.

None required. This message is for your information only.

BS2000 and z/OS only. The Adabas Review Trans-port feature is not installed.

If this Adabas nucleus should run with the Adabas Review trans-port feature, check the job log of the Adabas nucleus and the job log of the Adabas Review hub why trans-port is not installed.

ADARUN LOGCLEX=YES has been specified, but no Adabas Review modules are available. The Adabas nucleus changed the LOGCLEX parameter to ADARUN LOGCLEX=NO. The extended information is made available for the purpose of running Adabas Review in batch mode.

Please make the Adabas Review modules available in the STEPLIB.

A request to the Adabas ADAIOR interface by the Pulse failed.

Retain all dumps, messages, and other related information; contact your Software AG technical support representative.

A request for storage by the Pulse failed. The report is not started.

Increase the region size for Adabas and restart the nucleus.

An internal error has occurred in the given Pulse module. The report is not started.

Retain all dumps, messages, and other related information; contact your Software AG technical support representative.

The Pulse has determined that Cluster Services statistics reporting is not possible. The report is not started.

Ensure that Cluster Services is active.

The Pulse has encountered the given Adabas non-zero response code. The report is deactivated.

Identify the problem from the Adabas response code.

The Pulse subtask has encountered an error and will attempt to recover.

None.

The Pulse subtask attempt at error recovery failed. The report is deactivated.

Retain all dumps, messages, and other related information; contact your Software AG technical support representative.

The Pulse subtask could not be attached. The report is deactivated.

Retain all dumps, messages, and other related information; contact your Software AG technical support representative.

The Pulse has stopped or started.

None.

The Pulse detected an invalid timer interval. The acceptable range is from 1 to 1440 minutes. The default interval of 15 minutes is used.

Restart the report with a valid timer value.

The Pulse detected three non-zero Adabas response codes. The report is deactivated.

Correct the cause of the non-zero response codes and restart the report.

The length of CLOG and CLOG extension exceeds 65K. The CLOG extension is not attached. This message is only issued one time.

An internal error occurred. Contact Software AG support.

There are no valid Adabas modules available which can convert CLOGLAYOUT=8 records for Adabas Review.

Specify an Adabas load library from version 8.1.3 or later in your Adabas nucleus job.

The status of record filtering has changed. When filtering is stopped, the number of command log records processed thus far by the filter is printed, as well as the number of records filtered from Review processing.

None required. This message is informational only.

The length of buffer is greater than the value of the ADARUN parameter REVLOGBMAX. xx = FB, RB, SB, VB, IB, IO. This message is only issued one time.

The relevant buffer is truncated.

The length of the REVIEW command log buffer is bigger than the value of the ADARUN parameter REVLOGMAX. This message is only issued one time.

Buffers are ignored.

When a client nucleus initializes, the nucleus sends a call to the hub specified on the ADARUN parameter REVIEW to determine whether an Adabas Review hub is active. When it receives the call, the Adabas Review hub displays this message identifying the DBID of the client nucleus. If the client nucleus is a member of an ADASMP or Adabas sysplex cluster, then the corresponding nucleus ID is also displayed.

None required. This is for your information only.

When a client nucleus is closing, the nucleus calls the hub identified on the ADARUN REVIEW parameter. When it receives the call, the hub displays this message identifying the DBID of the client nucleus. If the client nucleus is a member of an ADASMP or Adabas sysplex cluster, then the corresponding nucleus ID also displayed.

None required. This is for your information only.

The specified client nucleus was deleted from the hub's registered client list.

None required. This is for your information only.

When there is a change in the monitoring or reporting status of a client nucleus by Adabas Review, the hub sends a notification to the client nucleus. This message is displayed when the notification is sent to the client nucleus.

None required. This is for your information only.

These messages are displayed in conjunction with the REVH10 message and indicate the status of information transmitted to the client nucleus by the hub.

count indicates the number of started reports and/or the number of reports requiring buffers.

None required. This message is for your information only.

This message is displayed at the completion of a notification call to a client nucleus identified by dbid. A response code of zero indicates that the message was successfully received.

None required. This is for your information only.

This message is displayed in response to the DCLIENT operator command. For each client nucleus registered with the hub, the following information is displayed:

None required. This is for your information only.

This message is displayed in response to an operator command that requested a service for a nonexistent client nucleus. The requested client nucleus could not be found in the hub's registered client list.

Ensure that the correct client nucleus ID is properly specified and reenter the operator command.

An operator command requested a service or status and there are no client nuclei presently listed in the hub's registration list.

None required. This is for your information only.

To use the Transport feature of the Adabas Review hub under z/OS, the load library needs to be APF-authorized.

APF-authorize the load library if you want to use the Transport feature.

The reason is provided in the previous message.

The Transport feature is not available in z/VSE environments. To use the Transport feature in other supported operating environments, refer to the previous message.

The hub received a call from an unknown client. The hub ignores the request.

None required. This is for your information only.

The hub was unable to insert a new client into its registration list. The client is given a non-zero response to prevent further communication. The hub continues processing and the registration of the new client is ignored.

Enter a DCLIENT=ALL operator command and review the list of clients. If there is a possibility of deleting a non-active client, then enter the STOPCLIENT=dbid operator command to stop the client from sending data, followed by a DELCLIENT=dbid to release the space in the registration list. To initiate the registration of the previously rejected client, start an Adabas Review report for that client.

The hub was unable to obtain space from the Adabas Review buffer. The hub is forced to slow its processing until the Adabas Review nucleus can process the work already in the queue.

During the slowdown, incoming data from the client(s) is further queued. It is possible that the client(s) will receive response 151 (command queue full) and/or response 255 (attached buffer full). The non-zero responses to the client would be detected and user exit 5 driven in ADARVU.

If the hub parameters NC (command queue size) and NAB (number of attached buffers) are set sufficiently high, the temporary slowdown should not affect the acquisition and recording of Adabas Review data. However, to prevent future occurrences of this type, increase the Adabas Review buffer size the next time the hub is cycled.

The Adabas Review nucleus terminated abnormally. The hub can no longer process Adabas Review data and will terminate.

Check all messages from Adabas Review to determine the cause of the abnormal termination of the Adabas Review nucleus. Correct the problem and restart ADAREV.

The hub incurred a shortage of REVIEW buffers. The value for the available storage can be determined by the BUFFER-SEGMENTS parameter of the INPUT statement

See the Adabas Review User documentation.

For diagnostic purposes, a handshake trace from the Adabas Review hub to the databases is activated. The Adabas Review hub issues a handshake command to a database because a report for this database is started, changed, or stopped. When the Adabas Review hub is brought down via ADAEND, the handshake command for the databases is also issued.

No action is required for this informational message.

For diagnostic purposes, a handshake trace from the Adabas Review hub to the databases is activated. An Adabas X'1C' call with UB was sent to a database by the Adabas Review hub and message REVH26 was issued. UBRSP=8 means the call was successful, UBRSP=4 means the call was not finished, an Adabas X'10' call is required and will wait to be posted, and UBRSP=0 means the call was not finished, no Adabas X'10' call is required.

Note:
UBRSP=8, ACBRSP=148 means the call was successful and the database was not active.

No action is required for this informational message.

For diagnostic purposes, a handshake trace from the Adabas Review hub to the databases is activated. An Adabas X'1C' call with UB was sent to a database by the Adabas Review hub and messages REVH26 and REVH27 were issued, with UBRSP=4. The Adabas Review hub does not issue an Adabas X'10' call which is required normally in this case. Instead, the Adabas Review hub issues this message and ignores the Adabas call, because a hang situation may occur.

No action is required for this informational message.