nagy%warner.hepnet@LBL.ARPA.UUCP (09/12/87)
>We wish to confirm some technical information about DECServer 200s, >also known as DSRVB-AB, namely: >1. On a single DECServer 200, can two terminals communicate with each >other, e.g. in practice can a PC use a printer? Two terminals can "communicate" with the BROADCAST command. This allows one user to send a short message to another user. See 2nd answer for more. >2. On two DECServer 200s connected to the same ethernet, using LAT-11, can >a terminal on one of the DECS200s communicate with a terminal on the other? >If this is the case, how would the "source" terminal (say a PC) address the >"destination" terminal (say a printer) on the other DECS200, that is, what >command would be used?. No, a terminal cannot communicate in any way to a terminal on another DS200 except for... Besides ports on DS200's being able to "originate" connections, ports can be declared to be services which can "receive" incoming connections. This can be used for: - "Reverse LAT" to connect to a host computer which does not support the LAT protocols on Ethernet but which has async terminal lines which can be connected to a DS200. - Outgoing modem connections. - Printers. We have experience with the later: we have 2 Printronix-300 printers connected to two different DS200s. We drive the printers with print queues on several VAXes; we have not tried to drive them with PCs. In all of the above cases, these items are declared as "services" by the DS200 which hosts the ports. These services then appear as such to any other DSxxx or VAX on the network which can access LAT services. If I do a SHOW SERVICES from "Local>" on my LAT line, I see not only our VAX host services but also WH12W_PRINTRONIX service for the printer on our floor. As far as PCs talking to these services, I know that DECnet/DOS supports LAT connections with its SETHOST program but I don't know if DECnet/DOS or anyone else supports PC connections to LAT-served printers. = Frank J. Nagy "VAX Guru" = Fermilab Research Division EED/Controls = HEPNET: WARNER::NAGY (43198::NAGY) or FNAL::NAGY (43009::NAGY) = BitNet: NAGY@FNAL = USnail: Fermilab POB 500 MS/220 Batavia, IL 60510
da@bvax.UUCP (Dave Sellers) (09/16/87)
In article <870912093131.026@Lbl.Arpa>, nagy%warner.hepnet@LBL.ARPA writes: > Besides ports on DS200's being able to "originate" connections, ports can > be declared to be services which can "receive" incoming connections. This > can be used for: > > - "Reverse LAT" to connect to a host computer which does not support > the LAT protocols on Ethernet but which has async terminal lines > which can be connected to a DS200. > > - Outgoing modem connections. > > - Printers. > > In all of the above cases, these items are declared as "services" by > the DS200 which hosts the ports. > This talk has raised a couple of questions (I'm not a DECnet user): 1) If you wanted to use a port on the 200 for a point to point async port (non-DEC to non-DEC host) could you, a) tell the 200's to make a connection from one port to the other from a remote location or must you be connected to the 200 via a terminal to initiate the connection? b) will the connection stay up forever? c) if a communications link failed between LAN's would the connection be rerouted via another link (if one existed) automatically? 2) It was stated that a "service" must be created so that a port can be accessed. a) Is there a limit to the number of services (ie. could it handle 3000+ services) (does this relate to 1 above) b) Are all the services known to all users (if * permissions assumed)? c) Does the connection to these services put a load on a VAX (somewhere)? In summary, is there a problem with using DECnet as a replacement for point-to-point async communication lines (non-DEC)? Dave Sellers Manager - Peripheral Systems Bell Canada 416-599-2085