Re: Re: NUMCPU >1 = IEE331A EXCESSIVE DISABLED SPIN LOOP DETECTED

On 5/23/2010 4:04 AM, Mike Stramba wrote:
> How do you do that from the config file?

I could have sworn I saw a parameter in the conf description, 
but I just reread the user guide, and couldn't anything. But the 
CPU specification option for a controller is also available as 
part of an MVS sysgen? (it's been a long time)

I got a reminder about the CPU vs I/O processor on our 4381. We 
had four channels on each CPU, running SP 1.3, and I made the 
mistake of letting one of my employees handle a move, device 
configuration, and sysgen. He know that load balancing was 
important, so he defined our NCR/Comten 3695 on channel 0, but 
on CPU 2. So whenever a task requested an I/O, it was routed to 
CPU 0 for processing. CPU 0 shipped the request for the Comten 
to CPU 2, which issued the I/O. The response came back on CPU 2, 
which had to ship it to 0, ad nauseam. The problem came to my 
attention because on the first day of production, user's remote 
JES lines kept dropping on time-out errors. I switched cables to 
CPU 0, ran a quick I/O gen, and the problem disappeared.

And I was wrong about running with 2 CPUs. I set the number in 
the conf file, changed it in HercGUI, and IPLed (twice so far) 
then wrote a little program to format the LCCA and PCCA, only to 
find out I only have one CPU active - so I'll go back into my 
corner and work on Wylbur...


Gerhard Postpischil
Bradford, VT