RE: Woes on ANZOBJCVN...

I checked our production program libraries with apx. 550 programs and none showed up as a problem. We even have some programs with system level V1R2.
The only problem I see is a program that uses a file that build by another program. We know which ones they are and steps can be taken.
We would do the upgrade over a weekend and that would give us time for the re-compiles.
As with any release upgrade PLANING is the most important part. We start months in advance working with IBM and our vendors. We make sure that we have the updated version of our vendors program. This has always served us good in the passed.
William

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Joe Pluta
Sent: Thursday, February 28, 2008 9:24 AM
To: Midrange Systems Technical Discussion
Subject: Re: Woes on ANZOBJCVN...


Al Barsa wrote:

Joe,

With all due respect. IBM kept this as a @#$%ing state secret until last
summer. When we did CISC-to-RISC, they were all over the airwaves for two
years talking about the observability issue. I talk to vendors every day
that don't believe that they have to recompile their code. Unless IBM
pulls off a full court press, this could make V3R1 look like a field day!

What am I missing here? Exactly how long does it take to recompile your
programs? At SSA, this would have required exactly one overnight.
Hell, we recompiled everything all the time anyway, every time the
darned product folks changed a field in the item master!

Seriously, I fail to recognize the issue here. How many programs are
non-compliant once you recompile them?

Joe