× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




I am doing a P7 to P9 migration right now.

The P7 had crap all over the place with stuff in system libraries and a
real mess in my mind.

We chose the path to NOT do the full restore but to migrate and clean up
the environment as we went.

I documented every step of the way, every command and added notes were
necessary for any objects that we relocated to more correct locations.

This Sunday we do the final Go Live migration and I have used that document
to create a script (CL Program) that will replicate everything we did and
omit steps not required to be duplicated.

The initial migration to get a working system for user acceptance was
tedious. User acceptance identified a few issues with missing objects that
I found in system libraries but overall no major problems.

We will now have a cleaner system with all user/application objects in user
libraries and all modified commands, sub-system descriptions, etcetera in a
user system library and the changes documented and scripted so an OS
upgrade can just call the program to re do the changes.

My 2 cents

Don Brown




"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 14/11/2018 12:05:04
AM:

From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date: 14/11/2018 12:05 AM
Subject: P7 to P9 migration plan
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

I'm rethinking my P7 to P9 migration plan.

Normally, I do a test migration, followed by days or weeks of testing.
Then, on the day of the live migration, I clear the system ASP, and
then do the final migration, either BRMS recovery or restore 21.

My new plan is to NOT clear the system ASP for the final migration,
only delete/clear libraries that changed, then only restore those
changed libraries.
Same for IFS.

Has anyone from the group ever done a similar migration, pros/cons.

Pros:
System already confirm as working.
Less down time
License keys already installed, do not have to re-install

Cons:
Missing a changed library or IFS folder

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.