The commands in this section of the documentation are used to control the Adabas Review (ADAREV).
The operator commands perform the following general types of operations:
Terminate an Adabas or user session;
Display nucleus or utility information;
Log commands into CLOG;
Change Adabas operating parameters or conditions.
The commands are listed alphabetically.
This document covers the following topics:
The ADAREV operator commands are entered the same way as other Adabas operator commands.
In BS2000 environments, enter each command at the operator console by addressing the Adabas nucleus with its task sequence number (TSN) in the following form:
/INTR TSN,command
For testing purposes, the nucleus may be run as a dialog process. The nucleus may be interrupted by pressing the K2 key, after which the prompt "/" appears. Now an operator command can be sent to the nucleus in the following form:
/INTR command
Note:
In the dialog mode, the nucleus stops as long as the INTR message is
not sent back. The resume statement /RESUME causes the nucleus to resume where
it was interrupted when no operator command is issued.
Operator commands are processed by a STXIT routine.
The remainder of this section of the documentation describes the commands that an Adabas Review operator can enter from the console.
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.
Used to terminate ADAREV immediately; the Review nucleus is abnormally terminated and the job aborts with a user completion code of 253.
DCLIENT={dbid | ALL}
Displays information on the specified client or "ALL" clients. The DCLIENT displays the number of clients currently registered with the 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 hub-id 001 CLIENT(S) LAST-ACT RPT BUF PRTS WBUF LOG-RECORDS REVH13 hub-id 196 03:22:48 Y N 003 000 10,323
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 hub-id 0000000013 NEXT EXPECTED SEQUENCE NUMBER AREV07 hub-id 0000000011 ADASMP ARVU D (C1D9E5E400C40000) PC 2800 AREV07 hub-id 0000000012 ADASMP ARVU D (C1D9E5E400C40000) PC 2800
Used to display the number of queued requests currently in the command queue.
STARTCLIENT={dbid | ALL}
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 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={dbid | ALL}
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).
The following operator commands can be entered to monitor and control Adabas nucleus operation.
Terminate 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 Adabas session immediately. All command processing is immediately suspended. A pending AUTORESTART will be in effect which in turn will cause the AUTORESTART routine to be executed during the initialization of the next Adabas session.