|
Agreed. See my prior note. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Lukas Beeler" <l.beeler@datalin e.ch> To Sent by: "Midrange Systems Technical midrange-l-bounce Discussion" s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 10/31/2006 02:12 Subject PM RE: CISC to RISC Circa 2006 (was RE: V5R4 upgrade from V5R3) Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> A new i5 520 can't run V5R3 (The Power 5+ Models). This makes the procedure a lot more complicated. You can go through the V5R3M5 LIC (this one runs on the the Power 5+ machines). I don't know if the 170 can run V5R3M5, but it can't run V5R4 for sure. And for V5R3M5, you will need a 17GB load source, which the 170 probably doesn't have. If your customer has a clear documentation of their setup, a restore of just the library and then reapplying the settings might be a lot easier. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Tuesday, October 31, 2006 8:05 PM To: Midrange Systems Technical Discussion Subject: Re: CISC to RISC Circa 2006 (was RE: V5R4 upgrade from V5R3) I agree. And I agree with the multiple steps. Maybe I worded something wrong. I guess I was concerned how you were going to get from V5R2 on the 170 to V5R4 on the 520. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/31/2006 02:00 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: CISC to RISC Circa 2006 (was RE: V5R4 upgrade from V5R3) Because the contents of QUSRSYS will be screwed up. Also, the CISC to RISC Upgrade process preserves system values, network attributes, edit descriptions, service providers, and a few other things that I can no longer remember. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 10/31/2006 01:41 cc PM Subject Re: CISC to RISC Circa 2006 (was Please respond to RE: V5R4 upgrade from V5R3) Midrange Systems Technical Discussion <midrange-l@midra nge.com> If you're going to skip some release upgrades, why do some of them anyway? Versus treating it like your fathers AS/400 and just restore a few user libraries and be done with it? You're going CISC-to-RISC to a 170 at V4R5. Then you plan on upgrading the 170 to V5R2. Actually, the 170 supports V5R3 so I'd get to that also. Then go to the 520 and V5R4. I don't think V5R2 ran on a 520. I think the only thing I was missing was V5R3. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/31/2006 01:29 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject CISC to RISC Circa 2006 (was RE: V5R4 upgrade from V5R3) The customer in the S36E (and very happy with it) has initiated the upgrade because they had no connectivity to their Windoze server. We think we have all the PTFs. We will migrate them to a decommissioned 170 at V4R5, and then upgrade that to V5R2. Then we will upgrade that onto a 520 at V5R4. Not a lot of knowledge running around about this process any more. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Chuck Lewis" <chuck.lewis@lees upply.net> To Sent by: "'Midrange Systems Technical midrange-l-bounce Discussion'" s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 10/31/2006 01:24 Subject PM RE: V5R4 upgrade from V5R3 Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> You are KIDDING Al - of course you aren't :-) Wow - CISC to RISC, that was a LONG time ago and another employer when I did that but man was it slick (take that MS, et al) :-) Chuck -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Al Barsa Sent: Tuesday, October 31, 2006 1:17 PM To: Midrange Systems Technical Discussion Subject: Re: V5R4 upgrade from V5R3 Technically no, but if you've had any major disruption (like an abnormal termination) RCLSTG is generally good for what ails you. I'm currently doing a CISC to RISC, and a RCLSTG is mandatory there. Al -- 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. -- 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. -- 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. -- 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. -- 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. -- 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.
midrange.com
