| Title: | Siemens Connectivity |
| Notice: | FTSIE Contact is Michael Eisenhut @MUC 865-1487 |
| Moderator: | UFHIS::MEISENHU |
| Created: | Tue Aug 30 1988 |
| Last Modified: | Mon Feb 19 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 195 |
| Total number of notes: | 512 |
We are trying to exchange mails between a BS2000 system that makes use of an office application called CONNECT and A1 on the vax. The producer of CONNECT says they can produce x400 mail output. So, since siemens has a x400 product and we have a x400 product, could there be any problem to exchange mails between them ?? Is there a site where this x400 connection is already made ? We have the intention to use vots and psi/ethernet as the physical layer. idea's ? thanks danny
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 27.1 | It has been done | ECCGY4::STROHMAIER | Mon Jul 03 1989 16:39 | 7 | |
Try Alfred Weigel in N�rnberg @NBO - he has worked with X.400 and
Siemens already.
Regards
Elisabeth
| |||||
| 27.2 | TSAP-id's could be a problem | MUNICH::KLOEPPER | Vera Kloepper/Net&Comms-Support | Mon Jul 10 1989 10:34 | 21 |
The BS2000 X.400 software we tested with - was for Siemens internal use
only. Name AKOM !
So - for the connection you are trying I can give you only one tip:
The Siemens OSI transport supports only ebcdi-code TSAP's and they
havn't any help to put in a TSAP in binary.
On the VAX-MRX side there isn't any help for an binary TSAP as well,
because X.400 defines the TSAP as IA5 digits.
MRX supports all IA5 characters so you can choose the following TSAP
id's for BS2000 and VMS/MRX:
BS2000 8x # (hex: 7B ebcdic)
VAX 8x { (hex: 7B ascii)
8x, because every TSAP at the Siemens side has to 8 Byte long.
regards Vera
| |||||