Re: terminal servers, X-terminals in upgrade to Integrity

tadamsmar wrote:
We have some Xyplex Maxserver 1600s. Xyplex was apparently bought by
MRV.

And, we have some old Tektronics X-terminals that are no longer
supported by Tektronics.

These upload from and communicate with Alphas running OpenVMS.

I wonder if these will work if I upgrade to Integrity Servers?

I can find any of the products or vendors listed in the HP application
status report:

http://h71000.www7.hp.com/solutions/matrix/partner_s.html

which seems to indicate that I would not be able to install on
Integrity Servers. But the files for upload are the only thing
installed, I think. Alpha already had support for the communication
protocols, I think.

But if I have all the files from the Alpha in place on Integrity, and
if Integrity supports the devices, then in theory they should work.

Right, wrong, or depends?

As you have been told, it depends.

Many of the third party terminal servers and most of the third party X-Terminals were also designed to be used with UNIX in shops that had no VMS at all.

While the early DECServers required a MOP download on boot to function, most of the 3rd party terminal servers did not.

They only needed entries in the LANCP/DECNET Phase IV data base to allow management tools to talk to them, and also could use MOP to upgrade their firmware. Most of the third party terminal servers could use alternate programs to update their firmware.

I seem to remember having a Xyplex at one time, and I do not remember if it really needed a MOP download.

The third party decservers supported TCP/IP long before DECServers did.

So there is a chance that the only thing that you need to do to use your Xyplex on an Integrity VMS system is to make sure that the LAT protocol is started.

As far as managing it, you may need to use a console terminal port on it, or manually use LANCP commands to connect to it. It may also allow TCP/IP to be used to manage it, once a TCPIP address is assigned.

I would recommend searching for a online manual for it, or checking to see if you can find out how UNIX users manage the device via TCP/IP.

As far as X-terminals go, they were usually designed for UNIX, and usally will work in a TCP/IP only environment. Current TCP/IP and DECW-Motif both support TCP/IP including font servers.

Older VMS versions did not provide that complete support using TCP/IP and third party X-11 servers that wanted the VMS market would put their own helper servers on the VMS systems to compensate.

So it is likely that if you configure your X-terminals to treat VMS as a UNIX host and just use TCP/IP, they should just work, unless they need fonts served. In that case all you may need to do is turn on the font server on VMS in the DECW$PRIVATE_SERVER_STARTUP.COM (check my spelling), as it is off by default, and set up the X-terminal to use it via TCP/IP just as if it were UNIX.

And you do not have to wait to get a I64 system to verify all of this, because the ALPHA works the same way.

-John
wb8tyw@xxxxxxxxxxx
Personal Opinion Only


.

Relevant Pages

  • Re: terminal servers, X-terminals in upgrade to Integrity
    ... Many of the third party terminal servers and most of the third party ... VMS at all. ... The third party decservers supported TCP/IP long before DECServers did. ... DECW-Motif both support TCP/IP including font servers. ...
    (comp.os.vms)
  • Re: Xah Lees Unixism
    ... > I thought VMS did get TCP/IP into it. ... > NFS. ... software and decent hardware support." ...
    (comp.lang.perl.misc)
  • Re: Xah Lees Unixism
    ... > I thought VMS did get TCP/IP into it. ... > NFS. ... software and decent hardware support." ...
    (comp.lang.python)
  • Re: Xah Lees Unixism
    ... > I thought VMS did get TCP/IP into it. ... > NFS. ... software and decent hardware support." ...
    (comp.lang.lisp)
  • Re: Xah Lees Unixism
    ... > I thought VMS did get TCP/IP into it. ... > NFS. ... software and decent hardware support." ...
    (comp.unix.programmer)