[Info-vax] Anyone using IBM MQ (client) on OpenVMS ?

[Alex Rubens]

On Tuesday, January 29, 2013 4:57:54 AM UTC-5, Jan-Erik Soderholm wrote:
> Hi.
> 
> 
> 
> Is there anyone out there who runs IBM MQ (client)
> 
> on their OpenVMS *Alpha* systems ?
> 
> 
> 
> $ tcpip sh ver
> 
> 
> 
>    HP TCP/IP Services for OpenVMS Alpha Version V5.7 - ECO 3
> 
>    on an AlphaServer DS25 running OpenVMS V8.4
> 
> 
> 
> I'm currently trying to get one of the demo apps in the
> 
> "Websphere MQ for HP OpenVMS Alpha, Version 6.0".
> 
> 
> 
> Installed from :
> 
> MQC4_AXPVMS-WMQ600_CLIENT.ZIP
> 
> IBM-AXPVMS-WMQCLIENT-V0600--1.PCSI
> 
> 
> 
> The demo app is :
> 
> 
> 
> $ d mqs_examples:AMQ0PUT0.COB
> 
> 
> 
> Directory SYS$COMMON:[SYSHLP.EXAMPLES.MQSERIES]
> 
> 
> 
> AMQ0PUT0.COB;1    23  17-JAN-2010 17:26:00.00
> 
> 
> 
> Total of 1 file, 23 blocks.
> 
> $
> 
> 
> 
> Built with :
> 
> 
> 
> $ cob AMQ0PUT0 /ansi
> 
> $ link AMQ0PUT0, sys$input/opt
> 
> sys$share:mqicb_64.exe/shareable
> 
>   Exit
> 
> $
> 
> $
> 
> 
> 
> But when run crasches with a stack overflow:
> 
> 
> 
> $ r AMQ0PUT0
> 
> AMQ0PUT0 start
> 
> Please enter the name of the target queue
> 
> asdgfasdg
> 
> %SYSTEM-F-STKOVF, stack overflow, PC=00000000002EF7A8, PS=0000001B
> 
> 
> 
>    Improperly handled condition, image exit forced by last chance handler.
> 
> 
> 
> The MQ startup has been run so sys$share:mqicb_64.exe is
> 
> istalled as it should.
> 
> 
> 
> Adding some extra debug "displays" shows that this happens
> 
> within MQ (in the first MQCONN connect call). I do not have
> 
> any server to run against, but it should give a proper
> 
> MQ error back, not a stack overflow...
> 
> 
> 
> Now, I have now found out from :
> 
> http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27013058#2
> 
> that MQ V6.0 might not be supported on Alpha V8.4, IA64 is.
> 
> 
> 
> And, to further turn the knife around, prabably de-supported :
> 
> http://www-01.ibm.com/support/docview.wss?uid=swg21584325#EOS2
> 
> (Where OpenVMS isn't mentioned at all.) But de-support should not
> 
> make it crasch...
> 
> 
> 
> Up to Alpha V8.3 there is a patch (like VMS83A_MQ-V0100) that
> 
> is mandatory for MQ on OpenVMS.
> 
> 
> 
> The patch-readme says :
> 
> 
> 
> 5.2.1.4  Release Version of OpenVMS that will contain this change:
> 
>                 Next release of OpenVMS Alpha after V8.3
> 
> 
> 
> So I guess a similar patch would not be neeed on V8.4.
> 
> *If* MQ runs *at all* on V8.4!
> 
> 
> 
> Anyway, all input on this matter is genuinely appreciated.
> 
> 
> 
> Jan-Erik.

You mention you have MQ Client 6.  No mention whether you're using a channel table, which would have to be created in the context of a  queue manager, or the old 2.2 logical name references to the queue manager.  If the queue manager is on another platform, the channel table, if shared with you, needs to be converted.

If the logicals, or channel table, are set up properly, all should connect OK, the only errors you should see are MQ related such as listener not up, or srvrconn parameters not allowing you in etc.