That's true, but then there are a lot of old systems that didn't understand things anyway. :)
In my experience, the biggest drawbacks to conversion have always been the sites home-grown code. There is still a lot of code that probably should have been updated years ago, but never was, and when you make a big jump, you will surely find them, but so long as you are careful, those issues shouldn't be too difficult to overcome. There will be exits that need to be re-written, but even if you had stayed within the N+/-2 scheme, you still would have run into the issue a some point. Sites that are fairly vanilla (home grown and exit-wise), don't really have much to fear from making the big jumps. There are a lot of people who got bitten just from the JES2 changes from z/OS 1.6 to 1.7. So, while there will be issues that need to be addressed, they are the same ones that would have to be addressed if the original thread creator was to jump in multiple steps, (OS/390 to z/OS 1.4, then 1.6 then 1.8), they just would have had a great deal of extra conversion work that might have masked the basic changes that they needed to make to their own "home grown" code. I'm not into making people jump through hoops to get from point A to Z, (get it?), if I can get them there directly, why force them to go through B, C D, etc. when all they will really get from it is extra work? 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
