Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hao!woods
From: woods@hao.UCAR.EDU (Greg Woods)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: NSC HyperchannelB - Ethernet TCP/IP gateway
Message-ID: <732@hao.UCAR.EDU>
Date: Wed, 17-Jun-87 14:11:19 EDT
Article-I.D.: hao.732
Posted: Wed Jun 17 14:11:19 1987
Date-Received: Sun, 21-Jun-87 10:02:58 EDT
References: <153@geocub.UUCP> <250@idacrd.UUCP>
Reply-To: woods@hao.UUCP (Greg Woods)
Organization: High Altitude Obs./NCAR, Boulder CO
Lines: 38

In article <250@idacrd.UUCP> mac@idacrd.UUCP (Bob McGwier) writes:
>in article <153@geocub.UUCP>, ief@geocub.UUCP (Didier Demigny ) says:
>> 
>> In our lab, we have a TCP/IP Ethernet network and a Network System Corp.
>> HyperchannelB network. Thus we are naturally leaded to imagine a gateway
>> between them : this gateway seems a rather difficult problem.

  We have the same situation. I wrote a hyperchannel server that runs on
the gateway VAX 750 (attached to both Ethernet and hyperchannel) for non-
hyperchannel Ethernet machines to submit jobs to the CRAYs (on hyperchannel
only, of course). I created a local "ntwk" port (in /etc/services) and
the hyperchannel gateway server just listens on this port for a connection
in the same manner as any other TCP server and handles submitting the job to
the appropriate CRAY when it comes in. Such a server is not hard to write,
I'd be glad to send you mine if you think it would help (but it might be
easier to write your own; it was not written to be portable and does have
some site-dependent code in it). It turns out that the problem of what to
do with outputs coming back from the CRAY is a LOT harder. I had to modify
our local hyperchannel software to check each returned output file to see
if it belonged to a job that was submitted from an Ethernet host, and if
so, connect to yet another server running on the submitting host (also fairly
easy to write) and send the output across the Ethernet. The hyperchannel
changes were by far the hardest part of this and are COMPLETELY implementation
dependent and therefore useless to anyone else. However, a similar design
could probably be used for those wishing a similar capability.

>This is meant as encouragement ONLY this software
>will never leave the building.

  I'd be happy to mail you any of my software, it is public domain. However,
because it is implementation-dependent, it probably would be useful only
as a guide in designing your own.

--Greg
-- 
UUCP: {hplabs, seismo, nbires, noao}!hao!woods
CSNET: woods@ncar.csnet  ARPA: woods%ncar@CSNET-RELAY.ARPA
INTERNET: woods@hao.ucar.edu