RE: Woes on ANZOBJCVN...

Joe,

Please clarify. As I'm reading this, you say no observability since
4.5...but from what I'm hearing from IBM, even though observability was
removed in the 5.1-4 range, it was still "there" for upgrade purposes...but
observability 4.5 and before was actual removal...ergo, if the observability
factor was removed 5.1-5.4...there's no issue. Pre-5.1, there's a issue
potential... Is this what you intended to say?

Don in DC



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Saturday, March 01, 2008 7:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: Woes on ANZOBJCVN...

Pete Massiello wrote:

Joe,

Your missing the point. I am finding programs compiled under V4R1,
V5R3, any release and they have observability and will be fine. I am also
finding programs that were compiled under V4R5, V4R3, V4R2, V3R2 that have
had their observability removed. Therefore, those programs cannot be
re-encapsulated at V6R1, hence the problem.

No, I'm not missing the point at all, Pete. I'm trying to break it down
by segment. Most people are not affected by this; at worst they have to
recompile their programs. At the end of the day, what it comes down to
is that if you've been running on software with no source and no
observability since V4R5 (or even S/38 code, as you say), then you can't
upgrade to V6R1. You now have a tough decision - stay on an older
release, or replace the software with no source.

Joe