×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Larry,
I agree that they've blown the opportunity to announce EOS for 7.1 in
2017. It's just too late to put anything in the budget.
What's really odd is that IBM traditionally has EOS for a version roughly
one year after x+2 comes out. (Ignoring that crazy stupid EOS for V5R4
due to ANZOBJCVN concerns with 6.1.) EOS for 7.1 should have been
announced shortly before 7.3 was made available with the EOS date one year
after GA of 7.3.
http://www-947.ibm.com/systems/support/i/planning/upgrade/suptschedule.html
At the rate 7.1 is going they could, in theory, announce EOS for both 7.1
and 7.2 together at the next COMMON and have rNext at the COMMON after.
With this delay I expect a push back of at least a year.
This is all conjecture based on the above web site ONLY! And I mean that.
There is no 'wink-wink'.
While I agree that with the 'wild wild west' approach you end up with
people voting for stuff they'll never use (like I'll never use 7.1 again
so why do I want enhanced ciphers for that), I did have some bad
experiences with COMMON misinterpreting some of my requirements to
something someone on the board wanted.
Some of my 'wild wild west' requirements were quickly PTF'd. Those data
service people love grinding out new services for SQL.
Rob Berendt
midrange.com
