The USS/OMVS environment offers only a subset of z/os features. More, things like security, ordinary file activities, and product upkeep is very different. Being so different complicates everything. And makes for a poor business case.
Native z/os applications typically command higher prices. But, of course, the standards are somewhat higher. Not even in the same ball park when it comes to security. In my limited experience, I have found that native 'nix applications are hard to fit into production environments. Many cannot conceive of not having a human to chat with and 'press any key'. 'nix server applications sometimes cannot tolerate the required security constraints. So, when we go looking for solutions, 'nix based products don't make the first cut. HTH, and good luck. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Julian Levens Sent: Monday, October 17, 2005 8:50 AM To: [email protected] Subject: Port to z/OS or OMVS? All I need to port our latest piece of software to the mainframe. The software runs as a server using TCP/IP on Linux/Unix/Windows already. Therefore, porting to USS should be fairly painless. What pros and cons would there be porting this server to native z/OS? + Better performance? + Would customers prefer a native version? If so, by how much? + Do some clients resist/abhor using Unix on the mainframe? + SMP/E installation of OMVS software supported (and straightforward) or not? + Other I assume that Hipersockets are available to both USS & z/OS to improve throughput. If so, is this a scarce/costly resource for customers? Thanks Julian ---------------------------------------------------------------------- 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
