Xref: utzoo comp.unix.xenix:7042 comp.unix.questions:15582 Path: utzoo!censor!geac!jtsv16!uunet!ncrlnk!ncr-sd!sceard!mrm From: mrm@sceard.COM (M.R.Murphy) Newsgroups: comp.unix.xenix,comp.unix.questions Subject: Re: HPUX->SCO Xenix UUCP PROBLEM (long) Keywords: HPUX SCO XENIX UUCP Message-ID: <902@sceard.COM> Date: 9 Aug 89 21:02:04 GMT References: <449@ntcsd1.UUCP> Reply-To: mrm@sceard.COM (0040-M.R.Murphy) Distribution: usa Organization: Sceard Systems, Inc. San Marcos, CA 92069 Lines: 29 In article <449@ntcsd1.UUCP> kdl@ntcsd1.UUCP (Dean Lane) writes: > >############## >Sorry for such a long article but I wanted to try and provide all pertinent >information. [Long part deleted...] Hopefully accurate summary 386 box SCO 2.3.1 HDB talks to HP 9000/840 HP-UX 3.1 HDB errors of the form >kdl ntcsd1 ntcsd1N0414 (7/27-XX:XX:XX,XXX,1) BAD READ (expected 'S' got FAIL) occur. I've had these same symptoms occur with HP 9000/350 HP-UX 6 HDB talking to HP 9000/8?? HP-UX HDB. Also same types of errors with 286 box SV/AT HDB talking to HP 9000/8?? HP-UX HDB. TB+ PEP on HP 9000/8?? side at 19.2k with no flow control and our side at 9600 with no flow control. The symptom is bad read followed by subsequent permission denied since the file was actually transferred ok. It seems to be associated with master/slave turnarounds. Short files were mostly ok, longish files showed the problems. I might suspect the SV/AT or SCO HDB, but we have no problems communicating with systems other than the HP 9000. Also, same symptoms in an HP-HP environment tend to direct suspicions in other directions. Unfortunately, I didn't check the 9000/350 -- SV/AT configuration when I had the chance. Next time I'll use a line monitor :-( Sorry for the lack of detail in this posting, I wish I had more solid information. -- Mike Murphy Sceard Systems, Inc. 544 South Pacific St. San Marcos, CA 92069 mrm@Sceard.COM {hp-sdd,nosc,ucsd,uunet}!sceard!mrm +1 619 471 0655