Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!miavx1!pemurray From: pemurray@miavx1.acs.muohio.edu (Peter Murray) Newsgroups: comp.mail.uucp Subject: Re: FSUUCP to VMS DECUS uucp initalization problem Message-ID: <2617.271a225f@miavx1.acs.muohio.edu> Date: 16 Oct 90 01:55:59 GMT References: <2590.271890d8@miavx1.acs.muohio.edu> <2718d438.1ed8@petunia.CalPoly.EDU> Lines: 57 In article <2718d438.1ed8@petunia.CalPoly.EDU>, cambler@polyslo.CalPoly.EDU (Fubar's Carbonated Hormones) writes: > pemurray@miavx1.acs.muohio.edu (Peter Murray) recently informed us: >>I tried the "-h" option of CALLOUT ("ignore host name") but, that only >>got the process one step farther before it stopped. > > Which step, specifically, and what are the conditions of it stopping? About as specific as I can get is what the screen says on the FSUUCP program and the debug log under DECUS uucp. First, the command to initiate the connection was: CALLOUT -X9 -H muun The FSUUCP screen looks something like... FSUUCP Version 1.1 Release 5 System: muun Action: Start communication [... blank fields ...] --Messages--- STARTUP: Host ASSUMED as muun FSUUCP: calling [muun], debug [9] --Debug-- STARTUP: sending [Sbigblu] 1st msg = [Shere] The debug log on the DECUS uucp system looks like... p:uucp h:- [10/15-20:36:20-22a00244] STARTUP (Version simpact- 1.31) u:BIGBLU p:uucp -< h:- [10/15-20:36:20-22a00244] Incoming (_LTA49: 2400 bps ) u:BIGBLU Sending: 0x10 S h e r e 0x00 Reading null-term str (getstring), rcvd: 0x00 p:uucp -< h:- [10/15-20:36:21-22a00244] * No Shostname rcvd () u:BIGBLU p:uucp -< h:- [10/15-20:36:21-22a00244] * Inc failed (see prev msg) u: BIGBLU p:uucp -< h:- [10/15-20:36:21-22a00244] Dropping DTR () u:BIGBLU p:uucp -< h:- [10/15-20:36:27-22a00244] Exiting (Version simpact- 1.31) u:- (Sorry about the wrapped lines. It's in the log file.) Any help would be greatly appreciated. Peter