| Hi Elisabeth,
1. As far as the business potential concerning RISC <-> BS2000 is concerned
please contact the sales unit "�ffentliche Verwaltung". The unit manager is
Karl-Heinz Klein @MFR and the sales rep I'm currently dealing with is
Hans-Peter Klein @MFR. This group has many dealings with German ministries.
I also feel certain that the GS-IGK can give you valuable input.
2. Nevertheless, in the meantime we're interested in hooking the DS3100 to a
PC-MX 4 via TCP/IP. There's a similar scenario at the planned new Munich
Airport, but this is currently at the tender (bid) stage. The sales person
responsible is Robert Heuss @MFR based in the unit "Handel und Dienst-
leistung".
Regards
Mitch
|
| >In the meantime, we need an interim solution for communicating between
>DECstations and BS2000.
Yes but only over LAN with TCP/IP(see reasons below) with the restrictions
listed in the other notes in this notes conference pertaining to the Internet
applications. This also requires the BS2000 to have a 9632(?) channel adaptor -
a costly piece of hardware (DM 40,000.-)
>Is it possible to connect the DS directly to the PC via TCP/IP?
Only on a LAN basis. Siemens has no WAN TCP-IP boards at the present time.
>
>+----------+ +----------+ +----------+
>| | TCP/IP ? | | PDN | |
>| DS3100 +------------+ PC-MX 4 +------------+ BS2000 |
>| | ^ | | | |
>+----------+ | +----------+ +----------+
> |
> +------- Siemens refers to this as an "AFP-interface"
>
>
Siemens uses a PC-MX4 to provide the WAN connectivity using their Siemens
specific NEA protocols.
What kind of communication requirements exist for these DS's - Terminal
Emulation, File Transfer, etc ...?
What kind of communication access is required - DS <=> BS2000 and DS=> ???.
If you can restrict the above you may avoid having to:
1. implement NEA protocols
2. wait for Phase V and Siemens to announce and implement the equivalent
In the short term it seems you cannot offer a total solution.
Hope this helps a bit.
John
|
|
Maybe this is a way to communicate between
DS3100 <-> PC-MX4 <-> BS2000
On ULTRIX V4.0 there's a file called /etc/sliphosts which gives hints how run
INTERNET protocol (and the upper guys as TCP..) over async line which
is built into each DS/VS.
I didnt tried out how it performs. It is said that it's not very speedy, but
better slow than nothing.
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
The criteria is whether SINIX provides a similar capability for the MX's.
Who has some channel to SINIX comm guru/knowledge to find out? If they offer
async Internet, it would be worth to test connectivity DS<->MX over this.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If it would work, there would be the possibility to run the MX as a Internet
routing Gateway if thers also a Internet link between MX and BS2000.
(TCP should be available as 3rd party implementation on BS2000).
If thers no Internet on BS2000 side, file transfer has to be done in a two
stage process: DS<->MX and MX<->BS2000. (Maybe with some remote shell script)
The DS<->MX could also be realized over uucp link which resembles FT over
async lines. I think nearly every U*X OS supports it; but dont know
exactly status of SINIX implementation.
Andreas
Appended is the file /etc/sliphosts for easy reference :
# @(#)sliphosts 2.2 (ULTRIX) 4/12/89
#
# /etc/sliphosts contains information about Serial Line Internet Protocol
# hosts. Hosts come in numerous types but all are considered masters
# or slaves depending on what is present in this file. Masters
# initiate the connection as:
#
# /usr/new/slattach host
#
# where host is the name to search for in /etc/hosts (the destination
# found is eventually passed to an /etc/ifconfig).
# Slaves use /usr/new/slattach as their login shell (shell field of /etc/passwd)
# and the login name is matched against the host field below.
#
# Slip requires a special line discipline in the kernel. To build
# slip into a binary system, add the line "pseudo-device sl" to your
# configuration file, remove your machine directory, and rebuild
# the kernel (config MACHINE; make depend; make vmunix).
#
# The fields describing each connection are:
#
# host destination gateway netmask speed tty modemtype phonenum logininfo
#
# Host is used to match the entry in this file.
#
# Destination is used an argument to ifconfig
#
# Gateway is usually the hostname of the system although it may be
# changed for specific routing cases.
#
# Netmask depends on your network and is passed to
# /etc/ifconfig. Speed is the speed at which the connection is to be
# run (this may be "any" for slaves and the speed of the line will
# not be modified).
#
# The device is the line to use for this connection
# (for masters this is the outgoing line to use and for slave /dev/tty
# is usually specified).
#
# Modemtype is specified as the type of modem
# to use (name must match an entry in /etc/acucap or "hw" for hardwired
# connections - Master only).
#
# Phonenum is present if modemtype is not "hw"
# and is the phone number to use (Master only).
#
# Logininfo is UUCP like info
# needed to negotiate the SLIP login at the remote host (Master only).
#
# Thus a sample Master might be:
#
# decvax decvax.dec.com test.fun netmask 19200 /dev/ttyd0 hayes-V 5-5555 ogin: Stest ssword: guess
#
# (Notice "decvax.dec.com", "test.fun", "netmask" must be found in /etc/hosts,
# /etc/networks or resolved by a name server as these are passed
# to /etc/ifconfig).
#
#
# Master dec7 calling (on a hardwired line) slave cyclops:
#
cyclops cyclops dec7.dec.com 255.255.255.0 19200 /dev/tty01 hw "" \r\c ogin: dec7 ssword: dec7
#
# What slave cyclops would have in its /etc/sliphosts file to allow the
# connection. In addition, the dec7 would need to be present in the
# password file with the shell set to "/usr/new/slattach"
#
dec7 dec7.dec.com cyclops 255.255.255.0 any /dev/tty
#
# What Master dec7 calling (on a hayes 9600 baud modem) slave cyclops:
#
cyclops cyclops dec7.dec.com 255.255.255.0 19200 /dev/ttyd0 hayes-V 10329 "" \r\c ogin: dec7 ssword: dec7
|