Timothy, First I agree strongly with Chris, having been there done that, porting an application generally requires recoding (a ton of #ifdef statements inserted into the code), and also, it doesn't answer the original question about how does someone with an idea for a z/OS product (not a linux product) get to develop it, without coming up with a ton of money, or finding a company to let them write it. No offense, but if I am going to write a linux product, I can spend less than a thousand dollars US and get a dual core intel box and put Fedora linux on it, and I can start writing it. Why would I give a hoot about running it on a z box, especially if I had to pay as much per month for access as the whole machine (that I own, can carry with me (assuming a laptop), and don't need internet access)? As for you comments about IBM buying software companies and putting out software (much of which is OEM'd, not written by IBM internally btw), I think that IBM is attempting to become a monolith on z/OS development, and killing the Flex and suing any others is part of that strategy! Wayne Driscoll Product Developer JME Software LLC NOTE: All opinions are strictly my own.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Sipples Sent: Wednesday, June 13, 2007 11:47 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Patents, Copyrights, Profits, Flex and Hercules Steve Comstock writes: >And your Linux products port to z/OS how? If they're written in C or C++, you recompile them and run them on z/OS, probably with USS. IBM has considerably smoothed this path in recent times (64-bit compiler, dbx, Debug Tool V7, WebSphere Developer for System z V7, ....), and z/OS 1.9 introduces USS improvements that reduce the effort even more. A shout out also to Dignus and their compilers. If they're written in Java you just run them. No changes required. (Write Java and you're already a z/OS developer.) If they're written in Perl you (probably) just run them. If they're written in PHP (for Apache) you (probably) just run them. I've just described the vast majority of Linux development scenarios. Now, to add spit and polish to your z/OS product you might want to package for SMP/E, cut appropriate SMF records, add ISPF configuration panels, include some sample JCLs, add explicit support for EBCDIC, etc. It depends on your product and your market. >It seems to me that IBM has pretty clearly shown their only long term >interest in z is to run Linux there. If you think that's what's going on, why the orgy -- can I say that? -- why the orgy of new z/OS products from IBM? And why is IBM buying all these software companies (including Consul, Candle, Isogon, and Ascential among others)? Why is IBM pouring gob$$ of money into these companies' z/OS products? Why is IBM acquiring other software companies without z/OS products then bringing their products to z/OS, e.g. Webify (now WebSphere Business Services Fabric for z/OS)? Why did IBM Rational just introduce the Rational Unified Process (RUP) for System z? Why, why, why? :-) Anybody got something they want on z/OS that's still missing? Go ahead and ask your IBM rep. At this torrid pace, you'll probably get it. - - - - - Timothy Sipples IBM Consulting Enterprise Software Architect Specializing in Software Architectures Related to System z Based in Tokyo, Serving IBM Japan and IBM Asia-Pacific E-Mail: [EMAIL PROTECTED] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
