Version 4.3.2
 —  Installation and Operations for z/OS  —

Operator Commands (Hub Mode Only)

Note: The commands described in this document are used only in hub mode.

The commands in this document are used to control Adabas Review (ADAREV) in hub mode. The operator commands perform the following general types of operations:

In this document, the commands are listed alphabetically.


Entering Operator Commands

The ADAREV operator commands are entered the same way as other Adabas operator commands.

Start of instruction setTo enter operator commands in OS/390 or z/OS environments:

Top of page

Operator Command Overview

The remainder of the section describes the commands that an Adabas Review operator can enter from the console.

ADAEND

Used to terminate an ADAREV session normally; the Review nucleus is terminated normally. No new monitoring commands are accepted and all currently queued requests are dropped.

CANCEL

Used to terminate ADAREV immediately; the Review nucleus is abnormally terminated and the job aborts with a user completion code of 253.

DCLIENT

graphics/review_dclient.png

Displays information on the specified client or "ALL" clients. The DCLIENT displays the number of clients currently registered with the Review hub plus the individual status of each client, including the client's DBID, time of last activity, whether the client has any active reports and if buffers are required from the client, the number of reports (and of these, how many reports require buffer information), and the total number of monitoring data records received from the client. The following is an example of the message output:

REVH13 hubid  001 CLIENT(S) 	LAST-ACT RPT BUF PRTS WBUF LOG-RECORDS
REVH13 hubid      96         03:22:48	Y	   N  003  000   10,323

DCQ

Used to display the entire list of queued requests. The DCQ displays the sequence number, client's job name, client's user ID, request code, and status flags for each queued request.

Note:
If a large value was set for NC (as is recommended), the DCQ request may incur delays in the Review hub processing if a large number of queue elements must be displayed. Also, the display on the operator console may fill the console's buffers causing further system delays.

The following is an example of the message output:

AREV07 hubid  0000000013 NEXT EXPECTED SEQUENCE NUMBER
AREV07 hubid  0000000011 ADASMP    ARVU D   (C1D9E5E400C40000)  PC 2800
AREV07 hubid  0000000012 ADASMP    ARVU D   (C1D9E5E400C40000)  PC 2800  

DNC

Used to display the number of queued requests currently in the command queue.

STARTCLIENT

graphics/review_startclient.png

Used to initiate a change order command to the specified client or "ALL" clients informing the client(s) to begin sending monitoring data to the Review hub. The change order is only sent to registered clients (clients that appear on the DCLIENT operator command display).

Note:
A change order changes a client's operation only if the monitoring status has been changed. This occurs only in cases where a previous STOPCLIENT operator command had been issued.

STOPCLIENT

graphics/review_stopclient.png

Initiate a change order command to the specified client or "ALL" clients informing the client(s) to stop sending monitoring data. The change order is only sent to registered clients (clients that appear on the DCLIENT operator command display).

Adabas Operator Commands

The following operator commands can be entered to monitor and control Adabas nucleus operation.

ADAEND

Terminate the Adabas session normally. No new users are accepted after this command has been issued. ET logic updating is continued until the end of the current logical transaction for each user. After all activity has been completed as described above, the Adabas session is terminated.

CANCEL

Terminate the Adabas session immediately. All command processing is immediately suspended. A pending autorestart is in effect, which in turn causes the autorestart routine to be executed during the initialization of the next Adabas session.

Top of page