On Tuesday, 02/26/2008 at 06:12 EST, "Schuh, Richard" <[EMAIL PROTECTED]> wrote:
> 16:12:32 HCPSWU2843E A stall was detected for TCP/IP Controller DTCVSW1. > HCPSWU2843E It was managing device 0F00 for VSWITCH SYSTEM VM3SW1. > 16:12:32 HCPSWU2830I VSWITCH SYSTEM VM3SW1 status is in error recovery. > HCPSWU2830I DTCVSW2 is new VSWITCH controller. > 16:12:33 HCPSWU2831E CP Controller error 5 for DTCVSW1. > 16:12:33 HCPSWU2830I VSWITCH SYSTEM VM3SW1 status is ready. > HCPSWU2830I DTCVSW2 is VSWITCH controller. > > There was a daylong stream of DTCOSD246I and DTCOSD247I messages. The > only other messages from the controller were: > > OSA 0F00 DETACHED DTCVSW1 0F00 BY DTCVSW1 > OSA 0F01 DETACHED DTCVSW1 0F01 BY DTCVSW1 > OSA 0F02 DETACHED DTCVSW1 0F02 BY DTCVSW1 For whatever reason, CP was unhappy with the controller. Perhaps your system is loaded down and the controller is being starved of resources or something is driving it crazy with NETSTATs or it is sitting in MORE/HOLDING or CP READ? The book says to ignore "error 5" (so why display it?). Alan Altmark z/VM Development IBM Endicott
