Mosquitto is a VAX Image

[praetor]

The official Mosquitto packages on VSI's service platform won't run. I try and run the startup scripts and it says:

$ run SYS$STARTUP:MOSQUITTO$STARTUP.COM.
%DCL-W-ACTIMAGE, error activating image SYS$STARTUP:MOSQUITTO$STARTUP.COM.
-CLI-E-IMGNAME, image file SVR1$DKB0:[SYS0.SYSCOMMON.][SYS$STARTUP]mosquitto$sta
rtup.com;1
-IMGACT-F-NOT_X86_IS_VAX, image is an OpenVMS VAX image, X86 image required


Both Mosquitto versions are like this. Can we get some x86 versions? Also on a side-note, when is the RabbitMQ broker going to be available for OpenVMS?

[arne_v]

Also on a side-note, when is the RabbitMQ broker going to be available for OpenVMS?

RabbitMQ broker? That depends on Erlang!

Has there been any indication that VSI would make Erlang and RabbitMQ broker available?

The C client is available on VMS Alpha and Itanium and it seems quite likely that they will port to x86-64 as well.

If you need a broker then ActiveMQ is available on Itanium and VSI may very well port to x86-64. And even if they don't then somebody else could. It is pure Java.

And ActiveMQ can speak AMQP.

[sms]

Code: Select all

> The official Mosquitto packages on VSI's service platform won't run.
> [...]

   Which of "The official Mosquitto packages on VSI's service platform"
are you running, and on what, exactly?

> $ run SYS$STARTUP:MOSQUITTO$STARTUP.COM.

   That's not how I'd attempt to use "<anything>.COM".  For example:

R86 $ run login.com
%DCL-W-ACTIMAGE, error activating image login.com
-CLI-E-IMGNAME, image file R86$DKA100:[SYS0.][SYSMGR]login.com;2
-IMGACT-F-NOT_X86_IS_VAX, image is an OpenVMS VAX image, X86 image required

   That "login.com" is actually a DCL script, not "an OpenVMS VAX
image", but the x86_64 image activator is rather less discriminating
than it might be, making that message less helpful than _it_ might be.

   On the bright side, the Release Notes in the kit do say how to "run"
(poor choice of words?) that DCL script:

        $ file := SYS$STARTUP:MOSQUITTO$STARTUP.COM
        $ if f$search("''file'") .nes. "" then @'file'

In other words (without the blade-guard):

      @ SYS$STARTUP:MOSQUITTO$STARTUP.COM

not:

      run SYS$STARTUP:MOSQUITTO$STARTUP.COM

   Welcome to VMS.

[praetor]

And that worked! Thanks I'm still learning, but loving OpenVMS. I'm a telephone nerd and using it for the backend of my phone stuff.

Code: Select all

> The official Mosquitto packages on VSI's service platform won't run.
> [...]

   Which of "The official Mosquitto packages on VSI's service platform"
are you running, and on what, exactly?

> $ run SYS$STARTUP:MOSQUITTO$STARTUP.COM.

   That's not how I'd attempt to use "<anything>.COM".  For example:

R86 $ run login.com
%DCL-W-ACTIMAGE, error activating image login.com
-CLI-E-IMGNAME, image file R86$DKA100:[SYS0.][SYSMGR]login.com;2
-IMGACT-F-NOT_X86_IS_VAX, image is an OpenVMS VAX image, X86 image required

   That "login.com" is actually a DCL script, not "an OpenVMS VAX
image", but the x86_64 image activator is rather less discriminating
than it might be, making that message less helpful than _it_ might be.

   On the bright side, the Release Notes in the kit do say how to "run"
(poor choice of words?) that DCL script:

        $ file := SYS$STARTUP:MOSQUITTO$STARTUP.COM
        $ if f$search("''file'") .nes. "" then @'file'

In other words (without the blade-guard):

      @ SYS$STARTUP:MOSQUITTO$STARTUP.COM

not:

      run SYS$STARTUP:MOSQUITTO$STARTUP.COM

   Welcome to VMS.

Added in 1 minute 22 seconds:
I've searched and searched and there seems to be several indications porting Erlang to OpenVMS is in the works. Having a telco-grade MQTT broker (as well as Erlang) on OpenVMS would be STELLAR. Mosiquitto can't cluster, and RabbitMQ would be a nice fit for VMS's clustering.

Also on a side-note, when is the RabbitMQ broker going to be available for OpenVMS?

RabbitMQ broker? That depends on Erlang!

Has there been any indication that VSI would make Erlang and RabbitMQ broker available?

The C client is available on VMS Alpha and Itanium and it seems quite likely that they will port to x86-64 as well.

If you need a broker then ActiveMQ is available on Itanium and VSI may very well port to x86-64. And even if they don't then somebody else could. It is pure Java.

And ActiveMQ can speak AMQP.

[arne_v]

I've searched and searched and there seems to be several indications porting Erlang to OpenVMS is in the works. Having a telco-grade MQTT broker (as well as Erlang) on OpenVMS would be STELLAR. Mosiquitto can't cluster, and RabbitMQ would be a nice fit for VMS's clustering.

http://erlangonopenvms.blogspot.com/

https://www.erlang-factory.com/upload/p ... pcloud.pdf

VSI certainly has the expertise to do it.

The question is whether they have a business case to do it.

[hb]

That's not how I'd attempt to use "<anything>.COM". For example:

Code: Select all

R86 $ run login.com
%DCL-W-ACTIMAGE, error activating image login.com
-CLI-E-IMGNAME, image file R86$DKA100:[SYS0.][SYSMGR]login.com;2
-IMGACT-F-NOT_X86_IS_VAX, image is an OpenVMS VAX image, X86 image required

That "login.com" is actually a DCL script, not "an OpenVMS VAX
image", but the x86_64 image activator is rather less discriminating
than it might be, making that message less helpful than _it_ might be.

The message is not very helpful and it will very likely be improved/fixed. You probably noticed that -IMGACT is a secondary message, not a %IMGACT-message. On x86, the image activator behaves the same way as on IA64, but on IA64 you do not get such a message.