<snip> Management has decided that it is time for the mainframe to go. They've got a project manager looking at a mainframe decommissioning project (feel my pain?). We are current now on z/os 1.7 and had ordered the 1.9 ServerPac and are in the beginning stages of that. Suddenly this project manager has decided that the majority of our applications will be moved off of the mainframe by the end of the year. Along with that, they have my supervisor asking for a risk assessment of NOT doing (completing) the 1.9 upgrade. </snip>
LOL I agree w/Gil. The timeframe is ridiculously short for a project of this magnitude, even if you are a batch only shop! I would start asking the project manager questions: What if something "goes wrong?" (and it will, just ask Murphy) What are your contingency plans? What is you contingency plan if the schedule slips? What is you applications inventory? Have you mapped all of the relationships between applications (file transfers, data shares,.....)? What is the destination platform? Is it homogenous (all *nix, Windoze)? How will all of the applications communicate during and after the transition? What is your security plan? (the answer to this one should be a hoot!) Etc.... The risk of going unsupported should be minor in this case, but if the *whole* project fails, you are far behind the curve. The have been plenty of failures in the past (http://www.actscorp.com/reboothill.htm) ---------------------------------------------------------------------- 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
