As many know, and is openly published on IBM's web site, V6R1 will cause
concerns with some vendor (and probably many in house) packages. The
general rule is that if you compiled to a target release prior to V5R1,
and did not have observability, you WILL have issues.
I am getting the impression that many vendors out there are not running
ANZOBJCVN prior to them receiving V6R1.
That they are waiting to recompile until they get V6R1 in.
Now, I don't know if that is so that you can get a target release of V6R1
and avoid the conversion upon first touch delays; or;
if it is to avoid running ANZOBJCVN, and fixing the issue, until the last
possible second that they have to.
My question is: Which would you rather have: A vendor release targeted
for V5R3 or V5R4 but passes ANZOBJCVN. Or, a release that is compiled to
a target release of V6R1?
Personally, I'd rather have the V5R4 release passing ANZOBJCVN. This
would allow me to upgrade vendor packages prior to upgrading the OS and
not have quite so many tasks to do all at once.
COMMON Webcast - Free to COMMON Members
Getting Ready for V6R1
Speaker: Paul Godtland, IBM
Wednesday, November 14, 2007 – 11:00am to 12:00pm Central Time (12:00pm to
1:00pm Eastern Time)
For i5/OS V6R1, all programs created for previous releases that use the
i5/OS Machine Interface (MI) must be converted. IBM will explain the
benefits of program conversion, and how you can use a free tool on V5R4 or
V5R3 to estimate conversion times and check whether you have any programs
that cannot simply be converted.
Learn more and register online at
http://www.common.org/webcasts
Rob Berendt
midrange.com
