REVH* - Adabas Review Hub Messages

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.

No action is required for this informational message.

When client reporting 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 job name of the client nucleus.

No action is required for this informational message.

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.

No action is required for this informational message.

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.

No action is required for this informational message.

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 the database ID (dbid) or nucleus ID (nucid) given in the message. In cluster environments, a nucleus ID is listed; in all other environments, a database ID is listed. A response code of zero indicates that the message was successfully received.

No action is required for this informational message.

This message is displayed in response to the DCLIENT operator command. A title that reads " hubid Dbid Nucid Last-act Rpts Buffers Log-records" appears as the first REVH13 message. Thereafter, the following information is supplied under the corresponding column titles for each client nucleus registered with the hub:

The last line of the message lists the number of client reports running in the hub.

No action is required for this informational message.

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 Trans-port 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 Trans-port feature.

The reason is provided in the previous message.

The Trans-port feature is not available in z/VSE environments. To use the Trans-port 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 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 Adabas Review.

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. UBRSP=8 indicates that the command is immediately complete and a 16-call is not required. UBRSP=4 indicates that the call is not complete and a 16-call is required.

Either a database ID (dbid) or nucleus ID (nucid) is given in the message. In cluster environments, a nucleus ID is listed; in all other environments, a database ID is listed.

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. A 16-call was issued (if required) and the command completed with the indicated response code and subcode.

Note:
ACBRSP=148 most likely means the database was not active.

Either a database ID (dbid) or nucleus ID (nucid) is given in the message. In cluster environments, a nucleus ID is listed; in all other environments, a database ID is listed.

No action is required for this informational message.

The hub attempted to send a command to the indicated client but found that its internal pool of UBs was exhausted.

This may be a transient condition if the hub is servicing many clients in a very busy system. Issue the STARTCLIENT operator command to reinitiate handshaking. If this does not resolve the error, contact your Software AG technical support representative.

A command sent from the hub to a client was thought to be complete, but the 16-call did not mark it as complete. This is normally a logic error, but it might also occur during hub termination if the client was unresponsive..

Contact your Software AG technical support representative if this does not relate to an unresponsive client during hub termination.

The Adabas Review hub can only run in storage key 0 or 8.

Start the Adabas Review hub again under storage key 0 or storage key 8.