RD/EE Controls<P> EPICURE Software Release Note 131.0<P>
<b> VCS Troubles</b><P>
<b> At least, this particular kind</b>
RD/EE Controls
EPICURE Software Release Note 131.0
VCS Troubles
At least, this particular kind
Debra S. Baddorf
The Symptoms:
You cannot SELECT or CONNECT to a
node because it is
NOT ENABLED. We never manually disable nodes. Therefore, this
should always mean that you need to do the Fix steps which follow. However,
the following are the correct steps to be sure that you really absolutely
cannot enable the node, and thus that this is really the correct fix for
your situation.
- VCS> SELECT WRNQ2
- VCS> Sorry, you can't. It's disabled. (paraphrased)
- VCS> ENABLE WRNQ2
- VCS> Sorry, not enough privilege.
- VCS> SET PRIV
- VCS> Ok. Privilege is on.
- VCS> ENABLE WRNQ2
- VCS> Sorry, you can't. It's permanently disabled.
(emphasis mine)
At this point, you know that you have to stop and restart VCS.
This can happen when the teminal server was disconnected, and VCS
got started up anew without knowing about the nodes on the other side
of the terminal server (perhaps due to a power outage).
The Fix:
- Login as SYSTEM or SYSMANAGER. While you
may personally have the privilege to do the first step (stopping VCS),
the second step involves restarting VCS, and it really needs to be
run under a system UIC.
- $ VCS SHUTDOWN
- $ some text here ... Finally it says it is off.
- $ @SYS_STARTUP:VCS_LOCAL_STARTUP
- $ lots of text here ... You should see it enable three
banks of terminal server lines plus one single spare line on ARDYH.
HYDRA doesn't
use terminal server lines yet. Finally it says it is on.
- Now try your SELECT WRNQ2 again and it should work.
Security, Privacy, Legal
rwest@fsus04.fnal.gov