| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
| MQ for VB |
« View previous topic :: View next topic » |
| Author |
Message
|
| rbanik |
 Posted: Thu Jan 08, 2004 3:15 pm Post subject: MQ for VB |
 |
|
Newbie
Joined: 08 Jan 2004
Posts: 1
|
Hi,
I downloaded your code samples for Visual Basic and tried running them.
I have MQ Client installed on my machine and trying to access a remotr Queue.
I am getting error "File not found: MQM.dll".
I read some where that VB cannot make direct calls to MQM.dll and that we should use MQAXSTD.DLL instead.
If so, what does this dll come with?
If not how can I get it working.
I require it very urgently.
Thanks |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Thu Jan 08, 2004 10:17 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
The VB / MQ code that you download is the sample VB code that IBM ships with MQ (I current only have v5.1 & v5.2 posted).
Therefore, if your installed MQ Client is v5.3, you should be using the included VB samples (i.e. mq_install_dir\Tools\VB\samplVB6 ).
I have never heard of the MQAXSTD.DLL file.
I am not a VB expert but I believe you have 3 choices for coding VB apps: native MQ / VB MQI calls, COM and .NET.
For VB client code, you need to set 2 environment variables:
This variable tells MQ to use the client libraries (versus binding mode)
| Code: |
| GMQ_MQ_LIB=MQIC32.DLL |
This variable tells MQ where the queue manager is located:
| Code: |
| MQSERVER=CHANNEL1/TCP/server-address(port) |
where CHANNEL1 is the name of the SVRCONN channel
and server-address(port) is the IP/hostname and port # where your queue manager's listener is running.
Hope that helps.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Jan 09, 2004 2:14 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Make sure you dont use the ancient support pack ma04, and ensure you are picking up the correct cmq*.bas when the project is compiling. If you meant MQMSTD then thats definitely from the old support pack, I dont recognize the MQAXSTD (unless that is a similar wrapper to the mqax200 code from the old support pack?).
If you are using VB on a machine which has both client and server installed
You need to set MqType:
1. Select the menu option "Project - xx Properties" (where
xx is the name of the project).
2. On the tab labelled "Make", edit the field "Conditional
Compilation".
In the "Conditional Compiliation" field, enter (without the
quotes):
"MqType = 1" for the WebSphere MQ server
"MqType = 2" for the WebSphere MQ client
If you are using the activeX interface on a machine which has both client and server installed
The ActiveX class use a method known as 'late binding' when deciding which MQSeries API module (either MQM.dll or MQIC32.dll) to use. This mathod takes the approach that, if MQM.dll is present in the path, the application must be running as a server side application and as such uses MQM.dll otherwise it assumes that the application was meant to run as a client side application and uses MQIC32.dll. This can be overridden using the undocumented environment variable, GMQ_MQ_LIB which should be set to the full path of the dll to use (either MQIC32.dll or MQM.dll). |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
