RE: V7R3 TR6 release date / Next CUM release date

Why yes we did put on a cume. The one that came with the order. Been sitting in this box here for 3 years.

SMH

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of DrFranken
Sent: Wednesday, May 1, 2019 11:09 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: V7R3 TR6 release date / Next CUM release date

This is true and they did fix it by doing so. However had the correct tapes been used from the start the entire issue would not have happened.
This is why we plan such things rather than just grabbing the closest image that might be available. :-)

Point is 'Just having a valid re-save for this hardware' doesn't cut it.


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 4/30/2019 7:10 AM, Rob Berendt wrote:

That's a little different than a resave issue. That could have been solved by applying a current cume and current groups before doing the restore. Granted, failure to do that was a boneheaded move, but still different.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
DrFranken
Sent: Monday, April 29, 2019 5:44 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: V7R3 TR6 release date / Next CUM release date

And other things go haywire as well. Helped a customer who used a 'different business partner' to install their new hardware. It happens.
Partner used an older resave "New enough for Power8!" and then restored customer O/S etc on top of that. Customer's was newer. Restoring many libraries failed. Hundreds of objects wouldn't restore.

Turns out needed MF PTFs were not in evidence. Oops.


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 4/29/2019 3:25 PM, Rob Berendt wrote:

IBM, as usual, will be issuing a resave of IBM i 7.3 to match the new TR.
https://www-01.ibm.com/support/docview.wss?uid=nas8N1022067
When doing an upgrade, or especially a new install on new hardware, I recommend using the latest resave.

Once you've tried to do a new install with an older I_BASE_01 and couldn't get it to boot from the new device you tend to remember this.
This is why using an older I_BASE_01 with the latest cume may not always be acceptable.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steinmetz, Paul via MIDRANGE-L
Sent: Monday, April 29, 2019 2:42 PM
To: 'Midrange Systems Technical Discussion'
<midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: V7R3 TR6 release date / Next CUM release date

V7R3 TR6 is scheduled for 5/10/19.
V7R3 Next cumulative package is scheduled for 5/24/19.

I thought the TR's had dependencies that were normally included in a related CUM.
Thus, CUM would be out before the TR.
Or,
Are the TR's and CUM totally independent?

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<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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