| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
Hi,
One of my customers has some programs written over the Ethernet drivers
in VAX/OpenVMS.
Now he wants to install some Alphas with OpenVMS and FDDI instead of
Ethernet.
The question comes with the differences of programming on Ethernet
versus doing it on FDDI.
Can anyone advise on this? The same programs written for Ethernet can
be used for FDDI without change?
Thanks in advance,
Jose
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1538.1 | STAR::STOCKDALE | Wed Dec 28 1994 05:39 | 16 | ||
>> The question comes with the differences of programming on Ethernet >> versus doing it on FDDI. Not much is different except for maximum packet size. You could also specify that you want to send and receive the frame control header byte which is not particularly useful. If you use VCI instead of QIO you have some options with respect to how the header is constructed and what fields point to (ie. you can go out of your way to make things different). If you use QIO and promiscuous mode, the header returned is different. Its all described in the LAN chapter of the I/O Users Guide in the VMS doc set. But in general, the same programs written for Ethernet can be used for FDDI without change. - Dick | |||||