Midrange News for the IBM i Community

Posted by: Bob Cozzi
Rogue Programmer
Cozzi Productions, Inc.
IBM RDi v9.5 Coming
has no ratings.
Published: 02 Sep 2015
Revised: 03 Sep 2015 - 1196 days ago
Last viewed on: 12 Dec 2018 (3424 views) 

Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.

IBM RDi v9.5 Coming Published by: Bob Cozzi on 02 Sep 2015 view comments(3)

Return to midrangenews.com home page.
Sort Ascend | Descend


(Sign in to Post a Comment)
Posted by: starbuck5250
Premium member *
Comment on: IBM RDi v9.5 Coming
Posted: 3 years 3 months 11 days 4 hours 48 minutes ago

I'm not overly fond of the way IBM scatters information across multiple web sites these days.  The official announcement, ENUS215-380 has a section for Software Prerequisites, and that points to the IBM RDi home page.  Click the System Requirements tab, and there, click the Requirements by Component > Clients button and you finally reach the RDi requirements page which says that RDi works with several versions of Red Hat, SUSE, and Ubuntu as well as several versions of Windows.

With respect to the 80-column limitation, it looks like the IDE is being changed slightly in advance of the compiler.  Soon, we'll finally be able to write RPG code free of the ancient 80 column limit.

Posted by: bobcozzi
Site Admin ****
Comment on: IBM RDi v9.5 Coming
Posted: 3 years 3 months 10 days 17 hours 46 minutes ago

Hi Buck, I'm still looking for the Mac version.

If Java is "so portable" what's keeping it?

Posted by: starbuck5250
Premium member *
Comment on: IBM RDi v9.5 Coming
Posted: 3 years 3 months 9 days 23 hours 35 minutes ago

I've been an RDi user for many years, more than a decade.  I really, REALLY liked Code/400 which was OS/2.  Everyone was running Windows, so IBM spent time and money to port it to Windows.  And then the next Windows, and the next, etc.  At some point IBM decided to move to Eclipse.  Native Eclipse is Java-only, but there was a transition period where some of the parsers were implemented with Windows DLLs, so while the base Eclipse would run anywhere, the LPEX plugin was Windows-only.  

Tim Rowe, in 2013, said that the issue is the verifiers would need to be ported.  I guess that means that the verifiers (essentially offline compilers) are still DLLs or Windows or .so files for Linux.  I never use Verify, so I wouldn't care if they were there or not, and that was suggested - ship the Mac version sans verifiers.  Apparently Corporate didn't care for that idea.