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 is announcing an update to the RDi product. For IBM i users there is (very) little new functionality but two new features that caught my eye are:
Both are extremely useful features; I'm speculating IBM is integrating ACS's 5250 emulator plug-in, but the interesting one is the 80-column RPG support. I haven't read or heard about IBM relaxing the 80-column restriction, if they do, that'll be a great day so long as the compiled code runs on v7r1 as well as v7r2.
[UPDATE: IBM confirms that the RDi announcement "pre-announces an upcoming RPG IV feature" but won't add anything further. My speculation is that RPG IV may FINALLY free itself from its 80-column Punch Card Legacy!]
What I do not see is support for non-Windows environments, specifically Mac OS X.
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.
Hi Buck, I'm still looking for the Mac version.
If Java is "so portable" what's keeping it?
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.