RE: Skipping lots of releases - Was: Looking at Power 7

Wow, reading that stream sure took me a while when I got back from customer
visits all day today. I think I needed WATSON to help me out as well. Lots
of great points by Chuck, and he is certainly right, you aren't going to
upgrade from V4R3 to 7.1, but remember, the last point of my original reply
was "get that model 600 up to the latest release it can support" (which
would have been V5R2) before you try this. Then you could have done a V5R2
to V6R1, and while this isn't supported, I didn't have any problems when I
did one 3 or 4 months ago.

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn: http://www.linkedin.com/groups?gid=2206093

iTech Solutions because IBM i (AS/400s) didn't come with System
Administrators


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, January 24, 2011 5:27 PM
To: Midrange Systems Technical Discussion
Subject: Re: Skipping lots of releases - Was: Looking at Power 7

Good example, Granted, it might be able to be shot down by just running a
RCLSTG and have most of the database cross reference files rebuilt. But:
1 - I get your example
2 - Then again, SYSPROCS are different because unlike (for example) doing
a DSPFFD or something to recreate it I have a devil of a time with where
does sql store a CREATE PROCEDURE... So, maybe that is harder to recreate.

I get your point about where IBM is not going to create an APAR to
document that chopping yourself in the foot with an axe hurts. Just
didn't know if it was created tangentially. Like, "user was getting
MCH.... when trying to run ... It was determined that this was caused by
performing an undocumented N-Many upgrade...". Then again, that might be
a bear to search for.

Rob Berendt