Re: Woes on ANZOBJCVN...

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!

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

"i" comes before "p", "x" and "z"
e gads

Our system's had more names than Elizabeth Taylor!

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com
http://www.systemiconnection.com/




Joe Pluta
<joepluta@plutabr
others.com> To
Sent by: Midrange Systems Technical
midrange-l-bounce Discussion
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc

02/27/2008 04:15 Subject
PM Re: Woes on ANZOBJCVN...


Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>






Walden H. Leverich wrote:

How come, when MS changes something that makes old code break everyone
yells at MS and points out how we never have this problem on System i,
but when IBM changes stuff that makes old code break it's the vendor's
fault? Hmmmm????

Other people will probably chime in, Walden, but I think it's because
IBM gives everybody a long lead time, plenty of notice, and a specific
way to address the problem, and it's usually pretty simple. In this
case, it's as easy as recompiling your programs. There have been
numerous occasions when Microsoft has completely broken backwards
compatibility at both the source and object level (VB.NET being one of
the classic examples).

But that's just my personal opinion. YMMV :)

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