On Thu, 8 Apr 2010 09:41:09 -0700, Guy Gardoit <[email protected]> wrote:
>Haven't experienced any problems with our 3 so far. Next maintenance cycle >will be in July, but it will be quarterly RSU1003+HIPERs+PRP. I've found >using a policy of staying at currentquarterlyRSU-1 works pretty well for us >anyway. > Exactly what we do (see past posts of mine). Except when rolling out a new OS level - depending on how soon after GA and how long it "sits" before any roll outs, we may go more current. Also, the level of user and system testing is much greater so we feel more comfortable with being more current than current quarter-1. Since my 1.11 came at RSU1001, that is what I am going with (+ PE fixes and some HIPERs) even though RSU1003 just came out. In my past posts about this I've said the reason why. Even though RSU and CST is much better testing than we had in the past, a large portion of the community does quarterly RSU maintenance. So rolling out the current quarter right after it comes out has some of the same exposure staying current with PUT did. You are testing the maintenance for everyone else. But doing it this way means keeping a close tab on ASAP notifications to make sure we don't miss something we really should get on right away. Overall since we started doing this instead of RSU*, we have had a much more stable environment. Realize that by the time a PTF is out, tested, hits PUT, then RSU and then waiting as we do, there is a long period of time that has elapsed. As usual, YMMV. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
