The code for this was written as a circumvention and is still under review. As initial performance testing has been very positive, it may wind up becoming the official fix, however it is still to early for us to make that decision. No matter what, the fix test can be obtained by opening a PMR (this allows us to track anyone with the fixtest, keeping everyone with the most current information regarding its status). Thanks and Best Regards,
Kurt Acker
| Peter Rothman <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 03/27/2006 10:40 AM
|
|
We are also planning to upgrade to z/VM 520 within the next few weeks - any
idea when the fix will close so it can be ordered.
Martha McConaghy
<[EMAIL PROTECTED]
DU> To
Sent by: The IBM IBMVM@LISTSERV.UARK.EDU
z/VM Operating cc
System
<[EMAIL PROTECTED] Subject
ARK.EDU> Update on z/VM 5.2.0 problem
03/27/2006 10:25
AM
Please respond to
The IBM z/VM
Operating System
<[EMAIL PROTECTED]
ARK.EDU>
Those of you who attended our z/VM 5.2.0 Early Experiences presentation
at SHARE know that Marist had some serious problems that forced us to back
out our upgrade. An APAR has been opened on the problem, VM63968. Not
long after SHARE, another customer also had a similar problem, so it is
not isolated to Marist.
This past weekend, we tested a fix for the problem and I'm glad to say that
it appears to work. We were able to run for 6 hours without the problem
reoccuring. (The problem involves a serious deadlock situation that can
bring all of CP to its knees.) We are planning to bring 5.2.0 up for a
longer
period of time during Easter break.
Martha
