Version 8.1.4
 —  System Operator Command Functions  —

Stop User(s)

Selecting option "S" (Stop Users) from the Session Opercoms menu displays the Stop Users menu:

10:22:02         *****  A D A B A S   BASIC  SERVICES  *****       2008-07-14
                               -  Stop Users   -                    PACIS02

                      Code  Service
                      ----  -----------------------
                       F    Stop users using file
                       I    Stop inactive users
                       J    Stop users by jobname
                       U    Stop a selected user
                       ?    Help
                       .    Exit
                      ----  -----------------------
    Code ............. _
    File Number ...... _____
    Last Activity .... ________ (elapsed time in seconds)
    Job Name ......... ________
    Purge UQE(s) ..... N
    Selected Userid ..
    Database ID ...... 105   (RD-105)

Command ==>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help     Disp UQ   Exit      Clear UID                            Menu

You can stop a specific user, all users from a specific job, all users using a specific file, or all inactive users. Any open transactions of the stopped users are backed out. When the Purge UQE(s) field is set to "Y", the stopped users are also deleted. Note that EXF and UTI users are not stopped or deleted.

The following table describes what each of the screen options allows you to do and how to use them effectively:

Code This option allows you to...
F stop all users who are using a specific file. When you use this option, specify the file number in the File Number field.

The nucleus backs out all open transactions of any users of the file. If the Purge UQE(s) field is set to "Y", the stopped users are also deleted. If the Purge UQE(s) field is set to "N" or Adabas is running with ADARUN OPENRQ=YES, a stopped user who returns (by sending a command) will receive response code 9.

Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are not required to issue an OP as the first command of the session), select this option with the Purge UQE(s) field set to "Y" only if you are certain that the users to be deleted are no longer active. If a user with an open transaction is deleted, but then returns (by sending a command), no indication is given about the transaction backout. If the user continues the transaction, logical inconsistencies in the database could occur.

I stop all users who have not executed a command during a specific time interval. When you use this option, specify the inactivity time (in seconds) in the Last Activity field.

The nucleus backs out all open transactions of the affected users. If the Purge UQE(s) field is set to "Y", the stopped users are also deleted. If the Purge UQE(s) field is set to "N" or Adabas is running with ADARUN OPENRQ=YES, a stopped user who returns (by sending a command) will receive response code 9.

Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are not required to issue an OP as the first command of the session), select this option with the Purge UQE(s) field set to "Y" only if you are certain that the users to be deleted are no longer active. If a user with an open transaction is deleted, but then returns (by sending a command), no indication is given about the transaction backout. If the user continues the transaction, logical inconsistencies in the database could occur.

J stop and delete all users from a specific job. When you use this option, specify the job name in the Job Name field.

The nucleus backs out any open transactions from the job and deletes the users (purges their user queue elements), regardless of the setting of the Purge UQE(s) field.

Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are not required to issue an OP as the first command of the session), select this option only if you are certain that the users to be deleted are no longer active. If a user with an open transaction is deleted, but then returns (by sending a command), no indication is given about the transaction backout. If the user continues the transaction, logical inconsistencies in the database could occur.

U stop and delete a specific user. When you use this option, specify the user ID of the user you want to stop in the Selected Userid field. You can do this by selecting a user from the current user queue (select PF2 on this screen).

The nucleus backs out any open transaction of the user and deletes the user (purges the user queue element), regardless of the setting of the Purge UQE(s) field.

Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are not required to issue an OP as the first command of the session), select this option only if you are certain that the user to be deleted is no longer active. If a user with an open transaction is deleted, but then returns (by sending a command), no indication is given about the transaction backout. If the user continues the transaction, logical inconsistencies in the database could occur.

? access online help for this screen.
. exit this screen.

The following table describes the use of the fields on this screen:

Field Description
Code Specify the code of the function you wish to perform, as described in the table above.
File Number When selecting the "F" code (stop users of a specific file), specify the file number; all users of the file will be stopped.
Last Activity When selecting the "I" code (stop inactive users), specify the inactivity time of the users (in seconds); users who have not executed a command during the specified time interval will be stopped.
Job Name When selecting the "J" code (stop and delete users from a specific job), specify the job name; all users from that job will be stopped and deleted.
Purge UQE(s) When selecting the "F" or "I" codes specify (with "Y" or "N") whether the user queue elements (UQEs) of the stopped users should be purged. Users stopped via the "J" or "U" codes are always purged.

Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are not required to issue an OP as the first command of the session), select this option only if you are certain that the users to be deleted are no longer active. If a user with an open transaction is deleted, but then returns (by sending a command), no indication is given about the transaction backout. If the user continues the transaction, logical inconsistencies in the database could occur.

Selected Userid Lists the selected user ID. To change the user ID, press the PF2 key and select a new user ID from the current user queue. To clear a user ID from this field, press the PF4 key. If no specific user is listed in this field, all users are assumed. This field is used only when the "U" Code (stop a specific user) is selected.
Database ID Specify the database ID of the database for which the users are stopped.

The following special function keys are also available for use on this screen:

An equivalent direct command is:

STOP USERS

Top of page