|
Yikes! I would map all of your V4R1 licensed programs to the equivalent of V5R3. I would do GO SAVE 23 on the V4R1 side. On the V5R3 system, I would do: RSTUSRPRF RSTLIB *ALLUSR OMITLIB(QGPL QUSRSYS) RSTDLO RST, Then remount the tapes, and do RSTLIB QGPL RSTLIB(QGPL_O) Then use PDM or your poison of choice to meld the objects from QGPL_O to QGPL RSTAUT. I would not attempt to restore QUSRSYS, because that would execute the MAKEAMESS COMMAND. System values, network attributes, edit descriptions, service providers would all have to be fat fingered. 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 Sarvapriya_Tripat hi@xxxxxxxxx Sent by: To midrange-l-bounce midrange-l@xxxxxxxxxxxx s@xxxxxxxxxxxx cc Subject 06/09/2005 12:50 Suggestions on Upgrading from V4R1 PM to V5R3 Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Good Noon All, My company has (finally) decided to upgrade from V4R1 to i5 V5R3. Does anyone have any suggestions on how to handle/manage such an upgrade. We will be getting the new H/W in about a month and I want to be as much prepared for this as possible. Regds Sarvapriya ****************************************************************************** The information contained in this electronic communication and any accompanying document is confidential, may be attorney-client privileged, and is intended only for the use of the addressee. It is the property of Ryder System, Inc. Unauthorized use, disclosure or copying of this communication, or any part of it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately by return email, and destroy this communication and all copies of it, including all attachments. Electronic communication may be susceptible to data corruption, interception and unauthorized tampering and Ryder disclaims all liability of any kind for such actions or any consequences that may arise directly or indirectly therefrom. ****************************************************************************** -- 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-2025 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.