|
Pat, I've done this before. For the user profiles, output them to a file, write a CL to ADDUSRPRF back in to the new system. You can do a similar thing with the ADDDIRE and authorization lists. As far as communications, I'd just reset it back up, from a printout of the configurations. The resource names changed, so you've got to touch them all anyway. A client recently went through a merger, they had a cisc, the "mergee" had a risc...we had to do the "manual" method, since both machines were running side-by-side, with production data, communications, software, and all..... The "reload" method would have killed the existing risc system...... At the same time another smaller client was upgrading, I "followed the roadmap".....wanna guess where I had the most problems????? In other words, you can do this, but you better spend time on the plan. And plan on some clean up time. Make sure your supportline bill is paid up. -- William A.(Tony) Corbett corbett@asresources.com http://www.asresources.com http://www.cbt400.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.