[Info-vax] MQ on Alpha ?

[Jan-Erik Söderholm]

seasoned_geek wrote:

> When it was just MQ Series V2.X then V5.X, you didn't
> need Java or anything.

It's my understanding that the licensing routine in the
install procedure needs Java, but that a JVM is part of the
install kit and used for that. Besides of that, you need
Java *if* you're going to use the Java based API against MQ.
We are not. Remote mangement might also need Java, we'll see
if I can convince everyone that we can manage MQ localy on
the VMS systems. And finely, the survailance tools (Tivoli)
also seems to need Java. Maybe we could run without those
tools, anyway, we are not running Tivoli or anything like that
for the rest of the VMS server anyway...

Or, we might have to install Java...

> There was at one time, I don't know if it still exists today
> because I don't do systems management work, the option to
> install "client only" on OpenVMS.

You can still do that. Actualy, we do "use" a 2.x client of MQ to
connect to another MQ box (yes, a Windows box in this case).
Curently this is only to send to one single queue. Now,
some projects includes the need for new interfaces that
are going to use MQ both in and out of the VMS systems and
the client isn't installing client kits anymore. Hence my
interest in MQ at the moment.

> Put the queue manager on a bullet proof platform and MQ Series
> is a bullet proof product.

Yes, I do not think that the basic MQ itself is any problem.
If it runs as well as DMQ did (does ?) there is no problem... :-)

Jan-Erik.