SAS Scalable Performance Data Server 4.5, Руководство администратора

Страница: 219 / 271

set user/locking anonymou threadid 7;
NOTE: User ANONYMOU connected to record
level proxy operator port with thread=7.
10. Show every LIBNAME for locking user ANONYMOU:
showlibname _all_;
LIBREF(LOCKING):Pathname assigned=/bigdisk/test/qabig1/
LIBREF(LOCKING):ACL Owner=
LIBREF(LOCKING):ACL Defaults(R,W,A,C)=(Y,Y,Y,Y)
11. Show all of the open tables in LIBNAME LOCKING:
showlibname LOCKING/data=_all_;
NOTE: No data sets currently opened for LIBREF LOCKING.
Privileged OPER Commands
You must have ACLSPECIAL access rights (LIBNAME option ACLSPECIAL=YES) to
run privileged OPER commands. With privileged OPER commands, you must first set
yourself as the proxy operator by submitting the following command:
SET MODE OPER;
The SET MODE OPER command sets you as the operator of the user proxy that you are
currently set to. There can be only one operator for a user proxy at any time. If you submit
the SET MODE OPER command when someone is already established as operator of the
user proxy, you get the following message:
ERROR: Operator mode owned by another connection.
Cannot grant this request.
After you have successfully set yourself as the operator, the following commands can be
submitted:
OPER CANCEL [/DUMP];
The OPER CANCEL command cancels and exits the user proxy. If the /DUMP option
is specified for a non-locking user proxy, the proxy exits with an abort() call, which
produces a core file. If you are the operator of a locking user proxy, the /DUMP option
is ignored. The OPER CANCEL command initiates a hard exit of the user proxy. Hard
exits might leave tables opened for UPDATE access, which is an inconsistent and
unusable state. In this case, you can submit the PROC DATASETS REPAIR command
to restore the tables to a usable state.
OPER DISCONNECT;
The OPER DISCONNECT command drops the control socket from the user proxy to
the client. This action causes the user proxy to terminate the next time it tries to
communicate with the client. This termination initiates a hard exit of the user proxy.
Hard exits might leave tables opened for UPDATE access, which is an inconsistent and
Privileged OPER Commands
213