|
What is the "by the book" approach? We'll soon be migrating from a 620 v4r5 to an 810 v5r2. Dan Thomas Director of Information Technology MDI 4500 Progress Blvd Louisville, KY 40218 (502) 318-1208 This message is a privileged and confidential communication protected by the Electronic Communications Act and is intended for the designated recipients only. Duplication or distribution of this email beyond the intended recipients without prior written consent of the sender is strictly prohibited. -----Original Message----- From: Doug Hart [mailto:doughart@xxxxxxxxxxxx] Sent: Monday, June 30, 2003 9:29 AM To: Midrange Systems Technical Discussion Subject: 730 to 825 migration I am planning to migrate from a 730 at v4r5 to a new 825 partition at v5r2. My client does not want his 730 to be upgraded to v5r2 as he is concerned with having problems in v5r2. He is requesting that I NOT do a "by the book" migration where the source system is upgraded then the target partition loaded from scratch from the save of the source system. I have done two of these "user data" migrations before but both were very small systems (600, 170). I know the issues with QGPL, QUSRSYS, QDLS, IFS, etc. Two requests. I would like to hear from all of you if going from v4r5 to v5r2 has given anyone problem. Are the clients fears founded? Please comment on the non-conventional migration. Is this a reasonable request? --- Doug Hart _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.