Correct, however we'll say it again: Are you doing your saves with previous
release? If not it won't restore, so change the backup program to previous
release (specifically V7R1) and do it again.
The only way to downgrade the LIC is to install it, and that requires the
DASD to be initialized, so it's option 2 on the install menu.
On the save, BEFORE you scratch the system, check to be sure no objects were
not saved due to OS save version. I would also add *PRINT to the saves to
you can find sequence numbers etc.
If you are using BRMS consider doing a bare save without BRMS. In the end
it will be easier since BRMS will have a hard time going back to V7R1. File
changes in the BRMS database make that almost impossible.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Monday, February 26, 2018 10:53 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: V7R3 to V7R1 rollback plan
I opened a new PMR to confirm the rollback plan.
Here's what IBM is stating.
"A scratch install is the Install of LIC and Initialize System. The disks
will be initialized.
This is covered in App C Recovering your system in the Recovery manual....
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rzarm/rzarmsteps.ht
m
Step 7 is the "scratch" - Install LIC and Initialize."
I was not expecting to have to "initialize the disks" , this will add
several hours.
Also, on the restore, I was hoping to only restore IBM V7R1 files.
I was planning to restore V7R3 user data from tonight's current save.
No need to restore user data twice, correct.
Hopefully not needed, but will this be the plan.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Monday, February 26, 2018 10:46 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V7R3 to V7R1 rollback plan
Remember to set the previous release to V7R1.
I know there will be several object types that will not save to previous
release. Security data is one of the big ones.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: Monday, February 26, 2018 9:30 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: V7R3 to V7R1 rollback plan
That's what I was thinking. Restore your 7.1 full save and then load your
data from the latest 7.3 save.
-----Original Message-----
From: DrFranken [mailto:midrange@xxxxxxxxxxxx]
Sent: Monday, February 26, 2018 8:08 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: V7R3 to V7R1 rollback plan
I agree with Jim. While I am not aware of any Specific updates to objects in
this upgrade there are almost always some. Common examples of objects that
get internal changes are user profiles and database objects. In some cases
you can restore them back to i 7.1 if saved that way but I wouldn't bet that
restoring IBM i 7.1 on top of 7.3, if it even allows you to do that' is a
workable option.
Use the backups!
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
--
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:
http://amzn.to/2dEadiD
--
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:
http://amzn.to/2dEadiD
--
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:
http://amzn.to/2dEadiD
midrange.com
