🚀 go-pugleaf

IN reply to two different messages.  


X-News: aurora.alaska.edu bit.listserv.hp3000-l:756

>From: Matti Yrjola <yrjola@HKKK.FI>
>Subject:Re: 3000 Networking sucks. RE: Networking on MPE
>Date: Thu, 14 Oct 1993 12:29:37 +0200
>Message-ID:<9310141029.AA23651@hkkk.fi>

>
>
>What do you mean by "HP emulating software"? HP-terminal emulation?
>If the online catalog software requires some special HP-terminal emulation then
>it is a problem with the library software not with the machine.
 
One of the problems we have is that any type of box can connect to us.  NeXT, 
Mac, PC, mainframe.  Most of them use VT100 emulation.  Wish the 3000 would 
have a termcap so I could change the DEL key to BS.  Next the university 
network which they connect through is has moved dialup, terminals, and any 
other tty to terminal servers that now telnet to connect.  Our one dtc that
has the Telnet card will soon be swamped with trafic.  We want a more cost
efective way to expand telnet traffic.

   
>Don't use the VT3k it will put load both on the UNIX box and the HP3000.
Dang..!  Glad you told me this.   I would like to offload as much CPU stuff
as I can.   


>If you just need to use telnet to connect to the HP3000 (and your HP3000 is
>a PA-RISC machine series 9xx-something) then you should use the Telnet
>Access Card on the DTC (ie. buy it). For the users it will look like they
>are connecting straight to the HP3000, we haven't had any problems with this.
>You don't need to change your users hardware and software.

Have one.  but it still does not get around the fact that the users do not want
to deal with a machine just chugs them downto a : prompt and demands that
they type hello to do anything.  


******
Just thought of another thing.   There is no way to keep accurate stats when 
telnet does not fake a nail down for specific users.  Circulation, Reserve 
room, ect.

We are using a 3rd party package.  VTLS.  It has many problems when it comes
to interfacing to our users.  UGLY!!!   


Thanks Again.  Robert

-----------

   I want to try again to clear up some of the comments to my recent post.

1)  The people at HP would do a lot of good for themselfs if they
would inform their own people what is happening.  My boss talked with
them and the reps we talked to told us that VT3K is being phased out.
It would be nice to hear that they were going to rewrite it instead...

2)  My 3rd party application software for which we have unrestricted access
to is NOT block mode.  Thank goodness.  We cannot use HP Specific software
to connect via Network since it may be any type of computer that is
connecting to us.   

3)  The University is switching everything, dialup, terminals, ect. to use the 
network to connect through TELNET.   At this time we are looking for a better
way to do this than the telnet card in the DTC we have.

4)  We need a better interface for the University world than I want to try to 
put on the MPE box.  I don't want to overload it until it is as slow as slugs.
     If we use a UNIX box we need a way to TCP/IP directly to the 3000.
This way we can uses the UNIX box as a frontend gateway to the 3000 and 
other resorces without killing our 3000.  I like my 3000 and want to keep 
it but its connectivity is still lame.

5)  I do not get on and skim the NEWS very often so I tend to miss what
other people have posted.  

6)  We want a LOGON process.  Something that will ask the user question that 
they are use to.  At present the 3000 is the only machine on campus that
just sits there and displays a : prompt.  Most student falculty types at that 
point think it is broken...  To agravate this it makes the user type in HELLO..
   With the University enviroment we lose half our user at that point.
They do not want to be using a dinosaur.  We have numerous VAX's, IBM (sucks) 
mainframe, THE Worlds biggest CRAY (UNIX), silicongraphics workstations, and 
may other machines.   In my opinion it is unrealistic to try to make people 
change for one oddball machine.  

If I was HP I would want a package for the 3000 that alows any box to easly 
connect to the 3000 directly.  Something that is cost effective (CHEAP) and 
would alough the HP to change to support other terminal types.  We want 
people to use the 3000.  

                   FNRJH@Aurora.Alaska.edu