Scalability (under VM) was another basic reason for our choices. Kevin
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, November 01, 2006 11:39 AM To: [email protected] Subject: Re: zLinux experience - Solaris? > I'm curious - why a z/Linux front end to handle XML, MQ, and TCP/IP > inbound messages when CICS has the facilities for all of them (and SOAP/ > Web Services, HTTP, etc.)? Don't know if this is the specific reason, but one simple reason others have used: XML and MQ processing tends to be processor-intensive (lots of encoding and decoding of elements). zLinux can run on IFLs which are always full speed and cost 1/3 the price of a standard engine, the software costing model is directly proportional to the # of physical engines deployed(regardless of the # of instances), and you don't risk increasing your OS and system management software charges if traffic increases require you to turn on more std engine capacity. Doing similar processing within CICS requires standard engine capacity, gets you involved in all kinds of complex licensing computations, and if you burst up to a larger machine via CoD for long enough, you get to pay more for OS and management software, often more than the price of the hardware. It's a pretty compelling argument. -- db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
