That's what I'm suggesting: use MQ to speak to the outside world for people that require it, and use something else between Linux and the OS/390 system.
In any case, since you're probably building your own apps on z/OS to access all that Adabas data, you can choose to make the external interface (between the Linux system and the z/OS system) for the z/OS portion whatever you please. Let the Linux system do MQ via a small "adapter" app that listens on a MQ queue, receives the MQ query, does the web services call and returns the output via MQ to the people that require it, and build your z/OS apps to be web services. Seems to accomplish the best of both worlds to me -- you build your core apps for the future, and put the MQ-specific stuff in a compartmentalized front end for backward compatibility. Otherwise, I think you're stuck with forking over the bushel of shekels for the z/OS MQ server. -- db David Boyes Sine Nomine Associates > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Ranga Nathan > Sent: Tuesday, December 23, 2003 12:38 PM > To: [EMAIL PROTECTED] > Subject: Re: Os/390 (no MQ) to Linux LPAR (MQ) anyone? > > > MQ is not my choice. I would have preferred an open source. I > would have > installed Stem from Stem Systems > (http://www.stemsystems.com/) which is > an excellent MOM written in Perl which supports many > protocols and can be > easily extended. > > But MQ is imposed on us by an external entity (US Govt!) :-(
