On Wednesday, 10/23/2002 at 04:25 ZE2, Robert Matthews <[EMAIL PROTECTED]> wrote: > 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.
The parser is dumping what it knows about BsdRoutingParms. You aren't using BsdRoutingParms, so the information is meaningless anyway. (The default BSDRoutingParms MTU size is 0.) Alan Altmark Sr. Software Engineer IBM z/VM Development
