Version 4.6.2
 —  Messages and Codes  —

REVH* - Adabas Review Hub Messages

Overview of Messages

REVH03 | REVH04 | REVH06 | REVH07 | REVH10 | REVH11 | REVH12 | REVH13 | REVH14 | REVH15 | REVH16 | REVH17 | REVH21 | REVH22 | REVH24 | REVH25 | REVH26 | REVH27 | REVH29 | REVH30 | REVH31

REVH03 hub-id CLIENT dbid [ - nuc-id ] HAS REGISTERED IN
Explanation

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.

Action

No action is required for this informational message.


REVH04 hub-id CLIENT MONITORING jobname HAS REGISTERED IN
Explanation

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.

Action

No action is required for this informational message.


REVH06 hub-id CLIENT {dbid|nucid} HAS CHECKED OUT
Explanation

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.

Action

No action is required for this informational message.


REVH07 hub-id CLIENT dbid WAS DELETED
Explanation

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

Action

None required. This is for your information only.


REVH10 hub-id CLIENT dbid WAS SENT A MESSAGE
Explanation

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.

Action

No action is required for this informational message.


REVH11 hub-id { NO | count } REVIEW REPORT(S) STARTED.
hub-id { NO | count } REPORT(S) REQUIRING BUFFERS.
Explanation

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.

Action

None required. This message is for your information only.


REVH12 hub-id OUTBOUND MESSAGE TO CLIENT {dbid|nucid} RECEIVED RSP rsp/subcode
Explanation

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.

Action

No action is required for this informational message.


REVH13 hubid Dbid Nucid Last-act Rpts Buffers Log-records
hubid dbid nucid last-act-time globrpts/dbrpts buffers log-recs
hubid CL jobname last-act-time clientrpts/dbrpts ------- log-recs
Explanation

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:

buffers The buffers requested for this client are displayed in the following format frsvtom, where:
  • f: An"F" appears here if a format buffer was requested.

  • r: An "R" appears here if a record buffer was requested.

  • s: An "S" appears here if a search buffer was requested.

  • v: A "V" appears here if a value buffer was requested.

  • i: An "I" appears here if an ISN buffer was requested.

  • o: An "O" appears here if an I/O list buffer was requested.

  • m: An "M" appears here if a multifetch buffer was requested

If a buffer type was not requested, a dash ("-") appears in the appropriate location above.

Note:
In the case of the client report line in this message (the line starting with CL), there are no buffers, so dashes will appear in this section.

clientrpts The number of client reports running.
dbid The database ID of the client nucleus.
dbrpts The number of database-specific reports running for this client.
globrpts The number of DBID=ALL reports running for this client.
hubid The Adabas Review hub ID.
jobname The job name of the client reporting client.
last-act-time The time of last activity or the time when the last command log record was received from the client nucleus, in hh:mm:ss format.
log-recs The number of command log records received from the client nucleus. For client report entries, this is the number of all command log records received from the client address space identified by the job name given in the message (jobname).
nucid If the client nucleus represents an Adabas Parallel Services or Adabas Cluster Services database, the number of the nucleus within the cluster is also displayed.

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

Action

No action is required for this informational message.


REVH14 hub-id CLIENT dbid IS NOT REGISTERED
Explanation

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.

Action

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


REVH15 hub-id NO CLIENTS REGISTERED
Explanation

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

Action

None required. This is for your information only.


REVH16 hub-id THE REVIEW HUB IS NOT RUNNING APF AUTHORIZED
Explanation

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

Action

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


REVH17 hub-id TRANS-PORT IS DISABLED
Explanation

The reason is provided in the previous message.

Action

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.


REVH21 hub-id A CLIENT ATTEMPTED TO REGISTER WITHOUT A DBID
Explanation

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

Action

None required. This is for your information only.


REVH22 hub-id CLIENT dbid UNABLE TO ALLOCATE LIST SPACE
Explanation

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.

Action

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.


REVH24 hub-id REVIEW NUCLEUS TERMINATED, REVIEW HUB ABORTING
Explanation

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

Action

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.


REVH25 hub-id REVIEW BUFFER SHORTAGE, INCREASE VALUE FOR BUFFER-SEGMENTS
Explanation

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

Action

See the Adabas Review User documentation.


REVH26 hubid HANDSHAKE COMMAND FOR DATA BASE {dbid|nucid} ISSUED UBRSP=ubrsp
Explanation

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.

Action

No action is required for this informational message.


REVH27 hubid HANDSHAKE COMMAND FOR DATA BASE {dbid|nucid} HAS COMPLETED
hubid RSP=acbrsp/acbsubcode, ACBRSP=acbrsp
Explanation

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.

Action

No action is required for this informational message.


REVH29 hubid NO UB AVAILABLE FOR COMMAND TO CLIENT dbid
Explanation

There are not sufficient user blocks to add or communicate with a new client. The Adabas Review hub abends.

Action

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, try decreasing the number of clients or increasing the number of user blocks. The number of user blocks can be increased by an optional zap which increases the value HUBMXCL is increased. For more information, or if this does not resolved the error, contact your Software AG technical support representative.


REVH30 hubid LOGIC ERROR COMPLETING COMMAND TO CLIENT dbid
Explanation

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..

Action

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


REVH31 hubid INVALID STORAGE KEY x
Explanation

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

Action

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


Top of page