Xref: utzoo comp.sys.dec:5782 comp.os.vms:38850 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!news.nd.edu!mentor.cc.purdue.edu!WESTERM@aclcb.purdue.edu From: westerm@aclcb.purdue.edu (Rick Westerman) Newsgroups: comp.sys.dec,comp.os.vms Subject: Re: Putting a modem on a LAT server Message-ID: <00948BEE.E7AC8EA0@aclcb.purdue.edu> Date: 17 May 91 20:44:35 GMT References: <42405@cup.portal.com> Sender: news@mentor.cc.purdue.edu Reply-To: westerm@aclcb.purdue.edu (Rick Westerman) Followup-To: comp.sys.dec Distribution: na Organization: Purdue AIDS center Lines: 29 Having answered (I hope) Billy D'Augustine's question about connecting an outgoing modem to the VAX via an terminal server, I have a related question for the *true* experts out there. I wish to make my outgoing Hayes compatible modems be 'dial-back' modems. E.g., my users would like to dial in to an incoming-to-the-VAX modem, login, and then run a script which would then call them back via an outgoing-to- the-VAX modem. The point behind this is to have the VAX absorb any long distance telephone charges instead of the user doing so. However, I can't get this scheme to work. I can use 'set host/lat' to connect to the outgoing modem and dial out manually, but the 'set host' program doesn't seem to take any commands from a DCL script. Am I missing something obvious here? Also, I have a DCL script (DIALOUT.COM) from Kevin Oberman (LLNL) which is suppose do a call back scheme using direct connect modems (which I don't have -- is it a sign of the times that I don't have any serial lines on my computers any more?) and I can't get the terminal-server-modems to work with it either. Any help/advice/hints would be appreciated. Thanks, -- Rick Rick Westerman System Manager of the AIDS Center Laboratory westerm@aclcb.purdue.edu for Computational Biochemistry (ACLCB), BCHM (317) 494-0505 bldg., Purdue University, W. Lafayette, IN 47907 If you can't fight or flee, then flow.