That's the point Rick. Here, with this particular migration there isn't any "required" toleration to perform for them. That doesn't mean that there isn't any available to download, but none of it is "required" for their conversion to be successful. For them (and a great number of sites) it's a simple system, no real special complexities involved. There are (almost) no "required" toleration updates for most basic upgrades such as theirs, it's only when local complexities are involved that you can run into any type of issues. The toleration issues are normally localized to a specific release. The WLM issue is a good case where a change in a single release is the problem, not every release. That said, there are a number of sites that are so complex that even just applying maintenance at the same release is a huge undertaking. But again, for this site as for (most) others, that doesn't apply.
There are a lot of other things to worry about that make more sense, but have nothing to do with toleration or "supported" fall back. For instance, (and no amount of toleration PTF's will help) when they changed the JES2 exit point capabilities, it was a single version that the change affected, if you were changing from the previous JES to that new version, you now had to contend with the new exit points, where you used to have only one point to handle everything, you now had to think about two. If you were upgrading from 5 releases back to that same release, you still had that same problem, there was no difference in the conversion itself than a single release jump. If you were 5 releases back and you were converting to two releases beyond those new JES changes, you still had to contend with the changes of that release you were skipping whether or not you decided to stop there on your way to the newest release or not, so there is very little sense in causing a multi-stop migration (for these people 1.4 to 1.7 to 1.9). There is no benefit in it for them, nor would there be for most sites. You've been around a while so you understand that most of the migration issues that people run in to have very little to do with the release itself that you were coming from, just that you have to be VERY aware of what has changed in the releases between your starting point and your proposed endpoint. I'm sure that what IBM might or might not think about your migration has very little to do with anything for you and probably doesn't keep you up at night. :) Brian ---------------------------------------------------------------------- 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
