Dave Jones <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
12/23/2003 02:41 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Os/390 (no MQ) to Linux LPAR (MQ) anyone?
Funny you should ask about this, Ranga; we just faced such a situation at
a
client of ours. They had to accept data transfers from other organizations
via MQ, but didn't want the expense of having the MQ Series server
installed
on their z/OS system. Another consideration was that the z/OS system was
inside their firewall and they didn't want it opened up to the Internet.
Our
solution was as follows:
1) install Linux as a guest operating system under z/VM (this client
already
had z/VM installed in an LPAR). Of course, you could also install Linux
natively in an LPAR.
2) Install MQ Series for Linux on zSeries Version 5.3. (This is the
version
that also supports SSL security.)
3) Install and configure the Linux NFS server.
4) configure the NFS client on USS for z/OS and mount a Linux directory
from
the USS nFS client so that it can be read
5) when data arrives from an external site via MQ, it's placed in the
directory that is accessible by the z/OS (USS) NFS client.
6) when a new file arrives, the z/OS NFS client can transfer it, via in
this
case hypersockets, to the z/OS side for further processing.
Since Linux can do hipersockets what add-on value is provided by the
OS/390 NFS client, unless it also has access to native OS/390 file system.
Can we perhaps define a pipe from OS/390 to Linux LPAR?
No need for MQ on the z/OS side at all, and the NFS file transfer can be
automated by a number of means.
Hope this helps.
Dave Jones
Sine Nomine Associates
Houston
----- Original Message -----
From: "David Boyes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 23, 2003 12:35 PM
Subject: Re: Os/390 (no MQ) to Linux LPAR (MQ) anyone?
> 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!) :-(
>
>
