AREV* - Adabas Review Hub Messages

#### Search Results

Search

# AREV* - Adabas Review Hub Messages

### Overview of Messages

`AREV01 | AREV02 | AREV03 | AREV04 | AREV05 | AREV06 | AREV07 | AREV08 | AREV70 | AREV80 | AREV81 | AREV82 | AREV83 | AREV84 | AREV86 | AREV87 | AREV88 | AREV89 | AREV90 | AREV91 | AREV92 | AREV93 | AREV94 | AREV95 | AREV99`

AREV01 | hub-id ADAREV HUB Vv.r.s COMING UP
Explanation | The Adabas Review hub session initialization is in progress.
Action | None required. This message is for your information only.

AREV02 | hub-id ADAREV HUB IS A C T I V E
Explanation | The Adabas Review hub system has successfully initialized.
Action | None required. This message is for your information only.

AREV03 | hub-id ADAREV HUB IS C L O S E D
Explanation | The Adabas Review hub system has completed its session close processing.
Action | None required. This message is for your information only.

AREV04 | hub-id OPERCOM: command
Explanation | The Adabas Review hub repeats the operator command before continuing.
Action | None required. This message is for your information only.

AREV05 | hub-id OPERCOM COMPLETED
Explanation | The issued command was processed by the Adabas Review hub.
Action | None required. This message is for your information only.

AREV06 | hub-id NO REQUESTS ARE PRESENTLY QUEUED hub-id nnn REQUESTS ARE PRESENTLY QUEUED
Explanation | 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.
Action | None required. This message is for your information only.

AREV07 | hub-id nnn NEXT EXPECTED SEQUENCE NUMBER hub-id cqe-seq-num cqe-job-name cqe-user-id (xxx) cmd ffss
Explanation | 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:
cqe-seq-num | sequence number of the command queue element.
cqe-job-name | job name of the Adabas being monitored.
cqe-user-id (xxx) | user ID of the Adabas being monitored followed by the value in displayable character hex.
cmd | Adabas command used for this request.
ff | CQE status flags in hexadecimal:
x'20' | waiting for 16-call
x'10' | 16-call required
x'08' | attached buffers
x'04' | attached buffers required
ss | more CQE status flags in hexadecimal:
x'80' | in process
x'40' | ready to be selected
Action | None required. This message is for your information only.

AREV08 | hubid ENQUEUE ON HUB hubid SVC svc FAILED
Explanation | 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.
Action | Determine why one Adabas Review hub was started while another hub with the same ID was already running.

AREV70 | hub-id TOTAL CQE USED: uuuuu OF ttttt
Explanation | 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.
Action | None required. This message is for your information only.

AREV80 | hub-id REVIEW PARAMETER IS MISSING
Explanation | An attempt was made to start a hub database, but the hub ID has not been specified in the REVIEW parameter.
Action | Specify the hub ID on the ADARUN REVIEW parameter and restart the hub database.

AREV81 | hub-id MPM-24 CALL FAILED
Explanation | The Adabas Review hub was unable to establish interregion communication. Adabas Review terminates processing.
Action | Identify and correct the error.

AREV82 | hub-id MPM-00 CALL FAILED
Explanation | The Adabas Review hub was unable to establish interregion communication. Adabas Review terminates processing.
Action | Identify and correct the error.

AREV83 | hub-id IDTE FOR THIS HUB IS NO LONGER ACTIVE
Explanation | The ID table element for the hub is no longer marked as being in use by this Adabas Review. It is probable that another target (Adabas, Adabas Review, etc.) was initialized using the same DBID / Adabas Review hub ID with the FORCE=YES parameter. Adabas Review terminates processing.
Action | If another target was inadvertently initialized, quiesce and terminate the target and restart Adabas Review. To prevent such problems, ensure that the FORCE=YES parameter is not used for target initialization unless absolutely necessary.

AREV84 | hub-id USER GONE ON MPM-8 CALL
Explanation | The Adabas Review hub tried to process a request but the addressed data area was not addressable, or no longer contained recognizable data. This error occurred while Adabas Review was receiving the request (router-08 call processing). It is probable that the client nucleus was terminated while it was sending the request to Adabas Review.
Action | None required. Adabas Review cannot process this request so it is cleared from the queue.

AREV86 | hub-id INTERREGION COMMUNICATION COULD NOT BE ESTABLISHED
Explanation | The Adabas Review hub was unable to establish interregion communication due to an unexpected response returned from ADAMPM. Adabas Review terminates processing.
Action | 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.

AREV87 | hub-id OPERATOR COMMUNICATIONS COULD NOT BE ENABLED
Explanation | The Adabas Review hub could not establish operator communications. Adabas Review terminates processing.
Action | Identify and correct the error.

AREV88 | hub-id TIMER SERVICES COULD NOT BE INITIALIZED
Explanation | The Adabas Review hub was unable to establish STIMER services. Adabas Review terminates processing.
Action | Identify and correct the error.

AREV89 | hub-id CORRUPTED CQE ARRIVED
Explanation | A command has arrived at the Adabas Review Hub, but when it was selected for processing it was not in an acceptable state. This indicates a logic error.
Action | Contact your Software AG technical support representative for assistance.

AREV90 | hub-id GETMAIN FAILURE, SIZE= requested-getmain-size
Explanation | The Adabas Review hub was unable to obtain the necessary GETMAIN space to operate. Adabas Review 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.
Action | Increase the region size for Adabas Review and restart.

AREV91 | hub-id MISSING OR INCOMPATIBLE REVIEW COMPONENT
Explanation | The Adabas Review hub could not load the module REVHUB or the REVHUB module that was loaded is not the correct version or SM-level. Adabas Review terminates processing.
Action | Locate the correct REVHUB module, ensure that the module is accessible by Adabas Review, and restart Adabas Review.

AREV92 | hub-id BREAK DETECTED IN SEQUENCE NUMBERS hub-id EXPECTED SEQUENCE NUMBER xxxxx hub-id RECEIVED SEQUENCE NUMBER yyyyy
Explanation | The Adabas Review hub processes the requests in the order that the numbered requests are received. This means that Adabas Review 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. Adabas Review continues processing.
Action | 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.

AREV93 | hub-id ERROR IN REQUEST: command
Explanation | Either the specified operator command was invalid or incorrectly entered. Adabas Review ignores this operator command.
Action | Ensure that the command syntax is valid, and retry the command.

AREV94 | hub-id REVIEW NUCLEUS SESSION OPEN FAILURE
Explanation | The Adabas Review nucleus returned a non-zero status during initialization.
Action | Check all messages displayed by the Adabas Review nucleus, correct any errors, and restart Adabas Review.

AREV95 | hub-id INCOMPATIBLE ADAMPM MODULE, CONTACT SUPPORT CENTER
Explanation | The ADAMPM module is not compatible with this version/release of Adabas Review. It is probable that the wrong Adabas load library, SM-level, or version is being used. Adabas Review terminates processing. It is probable that the wrong Adabas load library is being used.
Action | Locate the correct ADAMPM module, ensure that the module is accessible by Adabas Review, and restart Adabas Review. If the problem persists even with the correct ADAMPM module, contact your Software AG technical support representative.

AREV99 | hub-id ADAREV HUB ABNORMALLY TERMINATED
Explanation | The Adabas Review hub is terminating due to a previous error.
Action | Correct any errors and restart Adabas Review.