On 25/01/2014 3:52 AM, Ed Jaffe wrote:
Most mainframe modernization efforts are rooted in Java.
That's because there are no viable alternatives. It probably wouldn't be
the case if there was a zIIP enabled Ruby on Rails, Python Django or
node.js framework available.
One of the most impressive mainframe modernization products I've seen
recently is an ISV integration solution that uses a server side
JavaScript engine (zIIP enabled) that runs in CICS. I wish IBM would do
stuff like that. Dynamic languages are just so productive. Java is about
as agile as an oil tanker.
I can speak from personal experience that our emerging Java-based
mainframe offerings have been well received by our customer base.
http://phoenixsoftware.com/ejes/ejes_future.htm
Nice to see a product use a browser UI and not a dreaded Eclipse
plug-in. Have you published your REST API so your customers can use it?
From a strategic standpoint, IBM has given z/OS Java highly
preferential treatment in both System z hardware/software design and
customer terms and conditions. This trend is expected to continue,
making z/OS Java a solid language/platform choice with good investment
protection for the foreseeable future.
I still remember when at times it seemed that DB2 was the ONLY driver
of new innovations on the platform. Of course, DB2 is still an
important contributor. But, in my view, it has taken somewhat of a
back seat to more numerous performance enhancements aimed squarely at
Websphere/Java.
I heard that a resource intensive Java program was run on both a z/OS
zIIP and zLinux IFL. zLinux was x10 faster. The conclusion was that the
z/OS software stack was the bottle neck.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
