The following log shows
part of the server administrator's log for PROC OPERATE. The log reports
client/server transactions for users John and Maria, who are working
on a server named SHARE1.
For information
about interpreting server logs that are generated by users, see Interpreting SAS/SHARE Server Log Messages.
Administrator's Log for the OPERATE Procedure
LOG
Command ===>
1 proc operate serverid=share1;
======================================================================
2 display user _all_;
NUMBER OF
USER ID STATUS LIBRARIES
----------------------------------
john(1) ACTIVE 1
maria(2) ACTIVE 2
myid(3) ACTIVE 0
======================================================================
3 stop user maria;
User maria(2) stopped from active state.
User maria is now disallowed from connecting to server SHARE1.
======================================================================
4 display user maria;
NUMBER OF
USER ID STATUS LIBRARIES
----------------------------------
maria(2) STOPPED 0
======================================================================
5 quiesce user 1;
User john(1) quiesced from active state.
======================================================================
6 display user 1;
NUMBER OF
USER ID STATUS LIBRARIES
----------------------------------
john(1) QUIESCED 1
User john(1) is accessing these libraries:
USER LIBREF SERVER LIBREF LIBRARY NAME
-------------------------------------------------------------
DATALIB SYSUSE
<SAS-library-name>
User john(1) is accessing these data sets:
USER LIBREF SERVER LIBREF MEMBER TYPE OPEN MODE
--------------------------------------------------------------------
DATALIB SYSUSE USAGE CATALOG UPDATE
======================================================================
7 start user maria;
User maria started from stopped state and therefore has become unknown
to server SHARE1.
======================================================================
8 quit;
1PROC OPERATE executes commands 2 through 8 (shown in the preceding
output).
2The DISPLAY USER command requests general information about all users
who are currently accessing SHARE1. The users are listed by user
ID, current status, and the number of library assignments to the server.
3The STOP USER command immediately disconnects user MARIA(2) from
the server. If Maria is using the FSEDIT procedure to update an observation
when the STOP command is issued, she loses the updates on her display,
but she does not lose previous updates. The STOP USER command terminates
all attachments to that server, and she is prohibited from accessing
that server until the administrator issues a START USER command.
4The DISPLAY USER command shows Maria's current status. No libraries
are listed for Maria because the STOP USER command released them.
5The QUIESCE USER command gradually terminates user JOHN(1), which
allows John to finish work in the data sets that he currently has
open.
6The subsequent DISPLAY USER command reports that John is still accessing
member USAGE in library DATALIB. When John closes USAGE in that library,
the server releases the library and disconnects John. Because John's
session was quiesced by its connect number, John can reconnect to
the server when he wants to. He receives a new connection number at
that time.
7The START USER command allows Maria to access the server again. Note
that the START USER command does not establish a communication path
between the server and Maria. It only enables Maria to re-establish
a path by using a LIBNAME statement or an SQL CONNECT TO statement.
She must explicitly re-access the server.
8The QUIT statement terminates PROC OPERATE.