ARVU* - Adabas Review Interface Messages

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 code 148 (ADARSP148) 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 response code 148 (ADARSP148) 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
  dbid {NO | count } REPORT REQUIRES 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.

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.

This message is issued when the CPU ID of the Adabas nucleus and the CPU ID of the Adabas Review hub are different. When this happens, CLOG records to the Adabas Review hub cannot be sent via the Trans-port PC call, but must be sent via the Adabas router. The performance of the Adabas router sending mechanism is slower than the performance of Trans-port.

No action is required for this informational message.

The ADARUN parameters DBID and REVIEW specify equivalent DBID values. The REVIEW parameter is set to NO.

Specify the correct REVIEW parameter. This can be done online.

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.

During session initialization, ADARVU issues a call to the specified Adabas Review hub, running with version Vnn. This version is not supported; the version number is either too low or too high. The handshake command to the hub did not work, so Adabas Review will not collect any data.

Start the Adabas Review hub with the appropriate version. For information about version compatibility, read Adabas and Adabas Review Version Compatibility, in the Adabas Review Release Notes.

The storage keys of the Adabas nucleus and of the Adabas Review hub are different. Both address spaces must run under storage keys 0 or storage keys 8.

Start Adabas nucleus and Adabas Review hub under the same key, i.e. storage key 0 or storage key 8.