🚀 go-pugleaf

well, I do not like the digest format so much, since it is usually easier for
me to do a DIR in MAIL to see the subjects I am interested in than to look
within the mail messages themselves. I wish there is a way in VMS Mail to
burst the message, but...

even so, this message is kind of a digest of comments/replies since I only
want to send out one message (and not get too many Failed Mail messages back
later on)

>
>It seems that swing is a great program, except that users in the same root
>directory can swing to each others directories and delete whole trees! This
>is even more compunded by a problem of a user doing set defaulkt to syslib
>or some other such area and deleting the whole structure. Isn't there some
>owner prot/id routine in SWING? I see a problem here...

if the file protection and user privileges
allow such action, then I think it is not really a problem with the program but
a problem with the user having too much privilege and not careful about what
he is doing. Same goes for user files within a same Root directory, do they
have the same UIC or are in the same GROUP?

>in my logout procedure I delete all .JOU files. But if there are none
>I get an error message that there are no .JOU files. If you see the
>text "error..." on the screen you look at it even it isn't a "real"
>error. Is there a way to suppress the error message

try
        $SET MESSAGE/NOTEXT/NOIDENT/NOFACILITY/NOSEVERITY
before the delete command. and reset it to /TEXT/IDENT/FAC/SEV afterwards.

>I would like to get the physical terminal name  within a DCL
>command procedure. But if you have disconnectable terminals the
>lexical functions return only the virtual terminal name. Is there
>a way to find the relationship between the virtual terminal and
>the real (physical) one ?

pterm=f$getdvi(f$getjpi("","TERMINAL"),"TT_PHYDEVNAM")

then pterm will contain the physical terminal name

>We are about to run a TeX driver for a Laser printer on one of our VAXen.
>
>Until today we are printing on the laser printer with the unmodified VMS
>printer symbiont, as a spooled device over a printer queue.
>
>Since the output of the TeX driver to the laser printer (bit map) is too
>large to keep it in a queue, for TeX-printing we have to
> - stop the 'normal' printer queue and
> - 'unspool' the printer device
>
>After the TeX output is finished ,
> - the printer has to be set as a spooled device and
> - the normal spooled printer queue will be started again
>
>Our problem is, that we do not want to give any privileges to those
>students who are printing their TeX output - in addition I like to
>have a 'fully automated mechanism' to handle this problem.

I don't understand why the output of TeX driver will be TOO LARGE to keep
in a queue? if you want smaller jobs to print before larger ones, you can
initialize the queue /schedule=SIZE or set block limit by using the
/block_limie qualifier in INIT/QUEUE.

-------------------- VAXstation 2000 information -------------------
Someone asked for information on uVAX 2000, well, I have some info on
VAXstation 2000.

configuration, kernel (four options)

$10125  VS450-DA/D3     4mb, 1 plane, monochrome, VMS,VWS,LAVC,DECnet endnode
$10125  VS450-FA/F3     4mb, 1 plane, monochrome, Ultrix license
$12125  VS450-EA/E3     6mb, 1 plane, monochrome, VMS,VWS,LAVC,DECnet endnode
$12125  VS450-GA/G3     6mb, 1 plane, monochrome, Ultrix license

order separately - power cord, keyboard ($200), pointing device($175 for
mouse or $995 for tablet), mass storage for ULTRIX (optional for VMS)

optional items - in system box
$650 for RX33 1.2Mb half-height floppy and
$2000 for  RD32 42Mb half-height Winchester.

Or RD53 71Mb full-height Winchester for $4050. ($5050 when in expansion box)
Expansion adapter is $1200. TK50 also available in expansion box for $4495.
all prices are MLP.

To run VAXstation 2000 as standalone requires uVMS 4.5b (available April),
To run it in a Local Area VAXcluster (LAVC) requires VMS 4.5c be loaded on
the cluster's boot node (available Q4/FY87). To run Ultrix requires Ultrix 2.0
(available Q4/FY87)which includes the NFS from Sun , C, Fortran,Ultrix-32w V1.0
workstation software (which includes X-windw). This version of Ultrix supports
installing OS over the network.

4-plane version is "program announced", also quoted from the Sales Update
"When the color VAXstation 2000 is available, it will be a replacement
product for 4-plane VAXstation II/GPX customers that do not require
Q-bus expansion or more than 6MB of memory"

-- Portia Shao              UUCP -- {allegra|ihnp4}!scgvaxd!engvax!portia
   Hughes Aircraft Co.      ARPA -- portia%engvax.uucp@usc-oberon.usc.edu
   (213) 616-2635