Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!RITA.ACS.WASHINGTON.EDU!SUE
From: SUE@RITA.ACS.WASHINGTON.EDU
Newsgroups: comp.os.vms
Subject: Problems setting term when setting host to VAX from PDP 11/44 via
 DECNET
Message-ID: <8807071016.AA18742@ucbvax.Berkeley.EDU>
Date: 4 Jul 88 23:25:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 29



  Hello.  Pardon me if I may sound a bit naive in posing this question but
I am not a systems person.  Our department had recently bought a VAX 8250
which we linked to 2 pdp11/44's via DECNET. We had noticed this problem:
when we use SET HOST to the VAX from the PDP's, we are unable to spawn
subprocess or set many terminal characteristics we could odinarily do when
we connect directly to a VAX port. The terminal comes up set as "hardcopy".

    When we try to spawn a subprocess, as from within mail, for example,
we get something like:

  - mail-e-editproc. error creating or executing edit subprocess
  - rms-f-dev, error in devname or inappropriate device type


    When we try to do set term/xxx, about the only thing it will let us set
is /dev=, the other qualifiers gives us:

  -set-w-notset, error modifiying RTA1:
  -system-f-badparam, bad parameter value

   The in-house programmer responsible for setting this up is not really
familiar with the vax and is learning as he goes from the supplied manuals.
He has some vague notions of what may be wrong, but no real idea if it is
possible to fix.

   Could anybody shed some light into this problem and how or if it is possbile
to fix up?? Could it be simply an incorrect setup problem?