[mod.computers.vax] I haven't seen this on yet - apologies if you already have

SYSRUTH@UTORPHYS.BITNET.UUCP (02/07/87)

From:   ATLAS::SYSRUTH       5-FEB-1987 12:48
To:     Orig_To! info-vax@sri-kl.arpa, SYSRUTH
Subj:   tcp info file, MAIL COMPRESS, and DLVJ1's
 
Several things this time:
 
1. I could not reach the following people who requested a copy of my collection
   of TCP responses: R. Haslam, I. Ahn, D. Morgan, and S. Cavrak. Please send
   me a FULL address (some of it gets truncated or left out in the messages you
   send me) if you still want a copy. Preferably something not too far
   removed from BITNET if possible.
 
2. A note about the MAIL COMPRESS command - it does NOT lock the MAIL.MAI file,
   or at least it didn't in 4.3. I got a message once during a COMPRESS and
   had to use the SET FILE command to get at it - it was in MAIL.OLD. Maybe
   they have fixed this in 4.4 (did they FIX anything in 4.4?). I would be
   interested to know what sort of message it gives someone trying to send
   a COMPRESSor mail. "File locked by another user" would not be very helpful.
 
3. A plea for HELP! We have just received a DLVJ1-M 4-line asynch. terminal
   line Q-bus interface. It is covered in jumpers. According to the technical
   manual that came with it, some of the features (speed etc.) are software
   settable. It is my understanding that this device uses the DLDRIVER. Is
   this the case? Is it truly software settable or do we have to pick a
   speed, wire it, and stick to it? What device names do things show up as?
   Would the SET TERM commands work the way they do with DZQ lines, or would
   we be stuck with SET DEVICE?
 
   I would try some of these things out for myself, but it is a production
   machine being used exclusively by one group in our department, and I
   can't take it away from them for long to play with it. CSR's and vector's
   (ignore the last apostrophe) should not be a problem as the CSR is uniqie
   uniqUe (having problems today - got bitten by a squirrel this morning)
   and we have nothing else at vector 300. Which brings me to another
   question - since the driver comes with uVMS, will the device autoconfigure?
 
   Thanks for any help you folks can give on this one. I have no exposure to
   the original UNIBUS device this is based on, either, so you'll need to
   get down to reasonably basic points (this is what I get for being non-
   technical - but that's changing!).
 
Ruth Milner
System Manager
University of Toronto Physics
 
SYSRUTH@UTORPHYS (BITNET)