Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!HNYKUN53.BITNET!SCHOMAKE
From: SCHOMAKE@HNYKUN53.BITNET (Lambert Schomaker)
Newsgroups: comp.os.vms
Subject: VS2000 questions.
Message-ID: <8805282023.AA12726@ucbvax.Berkeley.EDU>
Date: 27 May 88 11:41:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 33

Hurray!
    Finally we have received our VS2000 stations. Naturally I am very
pleased with such an enormous increase in functionality on my desktop.
But, as is invariably the case, there are some annoyances.

(1) One major gripe is that for several harmless features, one needs
SYSPRV privilege to activate them (e.g. DEF/SYS VT_ENABLE_OSC_STRINGS TRUE).
Furthermore, the system manager defines the set of fonts that can be loaded
by the user. What if I am very curious about the non-loaded fonts (some of the
WT fonts from UIS$SELECT_FONT are not too impressive), but I am no system
manager? Also, once, my BANNER got stuck in an RWAST state and I had
to ask the system manager to remove the process and restart it. Customizing
the BANNER also requires SYSPRV/SYSNAM privilege. Does anybody know why they
set it up like this?

(2) Probably related to (1). Is there any way to change the WT window title
from "VT220 Terminal" into something more informative, like a string containing
f$log("sys$node") and f$directory() ?

(3) We have 6 VS2000, all 4 MB +disk, local paging+swapping, in a cluster with
a VAX 750, 7 MB, 1xRA81, VMS 4.7. On the 750, the average number of users is 9,
working sets are (L/Q/E) 150,700,3000. Paging file 32k blocks. The 750 also
runs PSIACP and jNET and Alisatalk processes (about 15 total).
Since installation of the cluster, users on the 750 start complaining about
deteriorated response. Last week, the system "hung" in a strange way:
NULL took still 50%cpu, no excessive paging, swapping, topdio or topbio, only
"Mutex & Misc Resource Wait" was high (25) in MONITOR STATES. Eventually,
logging in or even breaking execution with ^Y was impossible on any terminal.
On the other hand, RA81 access from the satellites was not impaired in any way
during these problems, so workstation users didn't notice until they did a
SET HOST to the 750. We had to reboot, and did not experience big problems
since then. Who has any clues, given this limited system description?

Lambert Schomaker, SCHOMAKER@HNYKUN53.BITNET