Alan, yes it was after an obeyfile which contained a STOP for a device which was not started (not during initialization as I originally said). This produced the messages
DTCPRS007E Error encountered in reading OBEYFILE TCPIP Z: DTCPAR123I Line 6: Device not started That explains why I didn't see such messages before moving to the new subnet. But why does it report the MaxMtu as zero? It's 1492 in the PROFILE TCPIP and, as far as I can tell, communication is working fine in both directions. Bob Matthews. ----- Original Message ----- From: "Alan Altmark" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 23, 2002 3:54 PM Subject: Re: DTC messages not found > On Wednesday, 10/23/2002 at 03:18 ZE2, Robert Matthews > <[EMAIL PROTECTED]> wrote: > > I've just been required to change the IP addresses of all my Linux > virtual > > machines > > and their VM TCP/IP stack in order to transfer everything to a new > subnet. After > > starting the stack I find a PROFILE TCPERROR file on the TCPIP 191 disk > > containing > > > > DTCPAR113I BSD info for links: > > > > then for each link > > > > DTCPAR114I LNXxxx: BrdAddr . . . , DstAddr . . . , MaxMtu 0, Metric 0, > > SubnetMask . . . > > > > The information in the messages is correct but I'm worried by the fact > that I > > never > > had these messages before moving everything to the new subnet and the > fact that > > the "MaxMtu" is reported as 0. Unfortunately the messages are not > documented. > > Can anyone explain what's going on? TCP/IP is level 310 and I'm using > static > > routing with proxyarp. > > > > Bob Matthews, > > University of Geneva. > > Bob, look at the console log. Somewhere prior to this point is an error > message. When the parser (DTCPAR) hits an error, it issues an error > message and then begins to disgorge everything it knows. PROFILE TCPERROR > would be present only if you performed an OBEYFILE with errors in it, but > you would have also received a copy in your RDR. > > Alan Altmark > Sr. Software Engineer > IBM z/VM Development
