× 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 did a cisc-risc very basic upgrade back a couple of months
ago.

I concluded that since we were going from V3R2 to V5R3
on a 520, there were some risks.

(1) I saved the libraries(*allusr) on the V3R2 machine.
(2) Restored only their production and data libraries.
(3) Ran a strobjcvn on each library.
(4) Plugged in the twinax cables.
(5) Rekeyed all the user profiles manually.(8)
(6) Ran the daily production procedures.(all ran fast and fine)
(7) Went home. (total time 7 hrs)

The "only" issues that have come up are security issues due to
the fact that the V3R2 was running at seclvl=10 and they went to 40.

That caused two minor security issues that were fixed in 30 seconds.

They are very happy and I have not heard a peep out of them in over
a month.

I forgot... I also added two additional drives and started mirroring
on the new drives.


Al Barsa wrote:

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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.