MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2012

Re: V5r4 Upgrade



fixed

Following things you need to take care of before upgrading the system from
V5R4 to V7R1,

1. Review memo to the users . Both V6R1 and V7R1. There are many changes in
V6R1 eg. Telnet changes.
2. i5/OS program conversions ( ANZOBJCVN). For this tool, you should have
MRI and code ptf.
3. HTTP ptf Group level 21 or higher should be applied.
4. From V5R4 to V7R1, there are issues with SQL query joins. Your
application team needs to take care of this.
5. Check Cross reference ptf.

I would suggest you to first upgrade your development or test box and let
the application team and users test before upgrading the production.

The upgrade may take 7-8 hours. Time excludes the pre upgrade tasks and
conversion part.

Also, IPL after the OS installation may take very long time. it remains at
SRC code C9002A95 for about an hour or more. So don't get nervous when IPL
remains at this SRC for a long period of time. This is normal.

Else, everything is pretty simple. Have fun while upgrading.



Thanks,
Ankush Agrawal
On Wed, Oct 31, 2012 at 5:07 PM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:

Plan, Plan and More Planning as the others have basically said. Verify with
your Vendors that their apps are 7.1 compliant and run the Anzobjcnv
process until it is clean or you completely understand what will or won't
convert to 7.1 and if it won't, can you abandon that program/app or do you
need to replace / upgrade it either before or just after the upgrade.

Upgrading the Old system to 7.1 has its risks, but they are manageable.
Leaving the 5.4 box alone and moving everything to the 7.1 also needs very
careful plan and care so you don't down level OS objects in places like
QGPL, QUSRSYS etec as well as the IFS. 2 advantages I see of 'moving
things' to the new box and not up grading. #1 Great time to Clean House and
leave crap behind you don't need any more. #2 You be able to get to the
point of refreshing your data files to go live, This should be much shorter
downtime in theory than Upgrade to 7.1 and then later Save/Restore 21 to
move the the new box.

On Wed, Oct 31, 2012 at 8:53 AM, Billy Waters <bwaters@xxxxxxxxxxxxxxxxxx
wrote:

We are in the planning stage of migrating from V5r4 to V7.x loaded to a
new server. Is anyone willing to share their time line related to
testing
this process? My boss is under the impression we can do this "cutover"
over
the weekend without any prior testing on the new server / OS. Thanks in
advance for your assistance.
Billy Waters

--
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.




--
Kirk
--
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.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact