-----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Monday, December 19, 2005 2:50 PM Tom,
I think we ran into that problem with our POWER a few years back. If I recall, the "quick and dirty" answer we used was to stop some of the PNET lines, which freed up enough getvis until we could fix it permanently by making F1 a bigger partition. We spent a day stopping and starting the PNET lines as needed until we got to a window where we could IPL the VSE guest. Ron To: [email protected] Subject: Re: forcing a user Yep, that was it. VM crashed (I played around too much) so the problem is solved. This machine is the center of a PNET star of the other 8 VSE machines. Manually ftping the jobs around got old, quick. I had a count of 5. When looking at the console logs, I see that Power ran out of 24 bit space. No big deal except that I had PNET transfers from 3 other VSE machines active at that time. I'm guessing that the PNET transfers were the active I/O load when the machine was forced off. The Operator didn't correct the situation, didn't try to shutdown the machine normally, just forced it off. Just taking any partition down, would have freed up the 24 bit area and allowed things to continue. At least that is my guess. Tom Duerbusch THD Consulting
