RE: AW: End of the road for 7.1?

Rob,

That's quite a list.
Did your experience some of these.
I wish there was more.

Thanks
Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Friday, April 08, 2016 9:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: AW: End of the road for 7.1?

<snip>
But, I've always stated our software works on the latest OS level.
</snip>

There's a difference between 'stated' and tested.

There are lots of cases where things have broke because of a release upgrade.
- API phobics who do CPYSPLF of printed outputs instead only to find out IBM changed the format of the printed (included in the release of every Memo To Users!).
- People who code APIs wrong and hardcode offsets instead of using the values in the header of the API.
- Vendors who hard code a prerequisite check for 5761JV1 would no longer work on 7.2 (IBM did this with earlier versions of Domino).
- Vendors who insist on a certain level of Java, but allow you to specify a different Java yet still require the one version of Java still be there.
(Seen this).
- SQL behavior differences (does "select * into :MyExtDs" after you've added a column to the table but not recompiled the program work this release or not, for example).
- SQL new reserved words. (Why does select RID, ... from FRT now require me to use select "RID", ... from FRT?
- New limit changes. Number of spool files per jobs requires more digits.

Now, if your RPG code is limited to something simple like (in pseudo
code!)

loop tag
x add 1 x
dsply x
x iflt 10
goto loop
endif
*inlr *on

And you do no APIs, CPYSPLF, chaining to files which now have columns with new data types, IOW, if your code is stagnant and featureless, it is quite possible you can just keep upgrading OS with oblivion.




Rob Berendt