Linked by Thom Holwerda on Wed 14th Apr 2010 23:51 UTC
IBM This article describes a real-word software port, with examples of how various porting challenges are resolved. If you are a software developer porting software to UNIX, you will find these techniques invaluable in avoiding common pitfalls, resolving bugs, and improving your productivity.
Thread beginning with comment 419185
To read all comments associated with this story, please click here.
Why port things to IBM's mainframes?
by twitterfire on Thu 15th Apr 2010 18:02 UTC
Member since:

This is very simple. Because those mainframes are junk compared to x86/nvidia/powerpc/cell powered supercomputers. They are even crap compared to powerful x86 servers.

But they have one quality. That is: they cost a very large amount of cash and IBM is making big bucks from selling them.

Reply Score: 2

daedalus8 Member since:


I can tell that you have not ever worked on a zSeries machine, they are VERY powerful machines. Virtualization is a new thing? zOS has been using LPARs to do this for a LONG LONG time. I believe that the mainframe will remain at the core of a lot of businesses for quite sometime.

Regarding running native code on zOS, I believe this is a great idea although I don't know how many people will be doing this as OMVS really provides enough functionality, but you are clsoed to whatever is provided with it, I'm not sure what the compiling capabilities are within OMVS besides an assembler linker.

The other problem that exists is that most of the applications written for zOS were written in Cobol and the work to port that into a more mainstream language (c, c++, java) would be a HUGE task that would require A LOT of dollars. Don't fix it, if it ain't broke!

So with all this being said, I think it is a great idea but it will take a long time to adopt.

Reply Parent Score: 1