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.

x distinguishes the events which cause this message to occur.

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 and subcode were 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 REVIEW=hub-id may be used to change the value to 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. W: Wait for nnnnn seconds, after which ADARVU will resend the request to the Adabas Review hub.

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

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

The message displays the number of seconds delay time returned 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 second 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:

The REVIEW parameter is set to “NO”. This message is a consequence of a previous error and is accompanied by a more detailed explanation (e.g. ARVU01).

Correct the issue and reactivate REVIEW.

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.

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.

In the Pulse modules ADAPMT, ADAPSM, and ADAPST a sub code is issued:

In ADAPCS no sub code is issued.

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 and subcode. The report is deactivated.

Identify the problem from the Adabas response code and subcode.

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.

Future records will be sent to the Hub using the command queue instead of Trans-Port. Additional messages are available in the Nucleus and Hub to identify the error.

Correct the error. Restar the Nucleus or Review Hub to reestablish Trans-Port.

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 ARVU14 message appears and the REVIEW parameter is set to NO.

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

Review Local mode has been disabled due to an error when initializing Review. A preceding message will identify the specific error.

Correct the error and restart the nucleus. In some cases it may be possible to use operator commands to assign the nucleus to a Review Hub.

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 when the filtering started or stopped. These messages are informational only.

When the filtering failed, contact your Software AG technical support representative.

Every field which could be processed by REVIEW has an indication (or attribute) whether a particular Adabas buffer (FB, RB, SB, VB, IB, MB, PB, IO, UI) is necessary for REVIEW to process this field. These indications (or attributes) are gathered for each report running and the indications (or attributes) for all running reports are gathered and Adabas is informed which Adabas buffers are requested by REVIEW.

When Adabas sets up a command log record for REVIEW, it checks these indications in order to build the command log record with or without a particular Adabas buffer. During this process Adabas (ADARVU) checks whether the length of the actual Adabas buffer confirms the ADARUN parameter REVLOGMAX. If the value is violated the first time, the ARVU41 message is issued.

Buffers are ignored. If necessary increase the value of REVLOGBMAX or deselect fields which require Adabas buffers.

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.

This message displays shutdown statistics for the Adabas Review components in the Adabas nucleus. ADARVU reports:

• The number of log records processed while in Hub mode

• The number of log records processed while in Local mode

• The number of log records processed while record filtering was active

• The number of log records filtered from Review processing

• The size (in bytes) of largest log record

• The number of successful calls and Trans-Port sends to the Review Hub

• The number of unsuccessful calls and Trans-Port sends to the Review Hub

• The number of records where the HUB was not active

• The number of records where no report was active

• The number the REVIEW subtask was POSTED or not POSTED (because already running or counter/time slice not exceeded)

None required. This message is informational only.

None required. This message is for your information only.

None required. This message is for your information only.

A handshake with the Hub completed successfully.

None required. This message is for information only.

Notify your Software AG technical support representative.

The Hub is no longer active.

If the Hub is remote from the nucleus, check the Net-Work connectivity. Restart the Hub, select another Hub, or change to LOCAL mode.

None required. This message is for your information only.

When a user-defined set is enabled, only the basic information and the values used in reports (running, scheduled, or suspended) are sent to REVIEW (either HUB or local). This action reduces the size of the CLOG record to the vital information units only.

A user-defined set is enabled by setting the INPUT parameter to MODE=V52 and CLOGDATA=USED.

When the user-defined set is discarded or enabled, no action is required. These messages are informational only.

When the user-defined set fails, contact your Software AG technical support representative.

The first form is issued when a Handshake message is not properly formatted. The second form is issued when a valid handshake message is received. The second segment of the second form is not issued when the Nucleus received the handshake directly from the Hub. The second segment indicates the handshake was forwarded from the nucleus that received the handshake directly from the Hub

For the first form, check the target IDs of the Hub and other servers for conflicts.

No action required for the second form. This message is for your information only.

The Review Hub has disconnected from the nucleus as a result of an operator command or stopping the Hub.

None required. This message is for your information only.

The interface (or method) used to send data to REVIEW (either local or HUB ) is controlled by the following parameters:

No action required. This message is for information only.

Records are sent to the Hub using the command queue immediately. Additional messages appear in the Nucleus to identify the error.

The records are not stored temporary in the buffer pool and sent as bulk by the subtask ADARSX.

Correct the error and restart the nucleus.

Records are sent to the Hub using the command queue immediately.

The records are not stored temporary in the buffer pool and sent as bulk by the subtask ADARSX.

In bulk mode, the records are buffered. The buffering the occurs is incompatible with the method used in previous versions.

Upgrade the REVIEW hub or restart the nucleus with ADARUN parameter REVSTHMV=V52.