V6R1 in A HA environment

I have a development LPAR, production LPAR, & HA Backup LPAR, all at
V5R4.

I plan on resolving all issues on each machine prior to going to V6R1.

Once all programs have been resolved, I will upgrade development, then
the HA Backup, then the production LPAR.

I do not plan on going to V6R1 prior to the 4th quarter this year (in
development), but as long as you resolve all V6R1 program conversions on
all machines before upgrading any of them, then I would expect normal
migrations using HA processes would be fine.

Just my thoughts.

Thanks.
James Salter
Systems Programmer
American Cast Iron Pipe Co

message: 2
date: Tue, 6 May 2008 13:28:57 -0400
from: rob@xxxxxxxxx
subject: V6R1 in a HA (High Availability) environment.

When migrating to a new version of the operating system in an HA
environment the generally accepted practice is to upgrade your "target"
machine first and then your "source" machine. Your source system should

not be higher than the target machine. The theory being that it may be
hard to send changes to a program if it couldn't do a TGTRLS(*CURRENT)
and
get it to the target machine. Of course, the onus is now on you, once
you've upgraded your target machine, to upgrade your source machine
before
your next scheduled switch or you're back into that trap.

My question is this:
If I upgrade my target machine to V6R1 and run STROBJCVN and then start
up
my HA solution will the audits fail because of some change date or other

errata that STROBJCVN may perform to a program object? My HA vendor is
saying that I should be fine. I am wondering what your experiences have

been. (I sure miss Al Barsa.)


Rob Berendt