Author |
Message
|
nik_iway |
Posted: Tue Mar 28, 2006 11:24 pm Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi All
I am using VB API to connect to MQServer on 2000. the following MQIC32.DLL is added to the path directory. I set the
Variable Name : MQSERVER
Value : CHAN1/TCP/11.102.31.36(1414)
Is there any other configuration that needs to be done...
I am getting error 2195
C:\>mqrc 2195
2195 0x00000893 MQRC_UNEXPECTED_ERROR
Help needed
Regards
Nik |
|
Back to top |
|
 |
mvic |
Posted: Tue Mar 28, 2006 11:25 pm Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
|
Back to top |
|
 |
mvic |
Posted: Tue Mar 28, 2006 11:27 pm Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
nik_iway wrote: |
2195 0x00000893 MQRC_UNEXPECTED_ERROR |
Often there is an FDC file in the errors directory when a 2195 appears. Is there one on your system (check "c:\program files\ibm\websphere mq\errors" for example) |
|
Back to top |
|
 |
Vitor |
Posted: Tue Mar 28, 2006 11:30 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Quote: |
Hi,
I am using the sample supplied by the IBM, the program used is
amqsputb.vbp. I am changing the MQCONN to MQCONNX.
|
From this I deduced he'd found the samples & the comment regarding MqType. I still respectfully assert that it's better / cleaner / faster to bang on the client rather than pick & choose DLLs. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
nik_iway |
Posted: Tue Mar 28, 2006 11:56 pm Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi mvic,
I installed MQ Client and used MQAX200.DLL to connect to the MQSERVER on another machine. It was working Fine. But MQ Supports nomal API calls to connect to the Queue Manager. I was Connecting to the MQServer using normal JAVA API programs using the follwing .jar files
import com.ibm.mq.MQC;
import com.ibm.mq.MQEnvironment;
import com.ibm.mq.MQException;
import com.ibm.mq.MQMessage;
import com.ibm.mq.MQPutMessageOptions;
import com.ibm.mq.MQQueue;
import com.ibm.mq.MQQueueManager;
Correct me if i am wrong, by using the normal VB API program from one machine cant we connect to MQServer on another machine
I am using the MQIC32.DLL which is added into the path directory
I set up the
Variable Name : MQSERVER
Value : CHAN1/TCP/11.102.31.36(1414)
Is installation of MQClient needed to connect to MQServer
Regards
Nik |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 29, 2006 12:11 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
nik_iway wrote: |
Hi mvic,
Correct me if i am wrong, by using the normal VB API program from one machine cant we connect to MQServer on another machine |
Using the VB API and an MQ Client installation you can connect to a queue manager on a remote machine. I have achieved this. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mvic |
Posted: Wed Mar 29, 2006 12:22 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
nik_iway wrote: |
I installed MQ Client and used MQAX200.DLL to connect to the MQSERVER on another machine. It was working Fine. |
Now I'm confused; you said here that you were having problems. I assume you overcame the problems with using MQAX200.DLL.
Quote: |
I am using the MQIC32.DLL which is added into the path directory |
If you installed the MQ client, then please don't copy the DLLs around. Just add the MQ bin directory to your PATH before running the app.
Quote: |
Correct me if i am wrong, by using the normal VB API program from one machine cant we connect to MQServer on another machine |
Yes. Did you look into the errors directory to see if there are any FDC files as I suggested? 2195 is not a common failure when connecting client to server.
Also, take a look through this troubleshooting section in the MQ Clients manual : http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzaf.doc/amq251c.htm#amq251c and see if it helps. |
|
Back to top |
|
 |
nik_iway |
Posted: Wed Mar 29, 2006 1:21 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi All,
Correct me if I am wrong. if there is no MQClient installed in a machine. With the help of the .DLL files copied from the MQServer. Can a normal VB API connect to Remote Queue Manager on another Machine by TCP/IP
Regards
Nik |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 29, 2006 1:31 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Again with the no. You need the client installed. I do not believe you can achieve connection by copying a few dll files.
You need to install the client, which is not that much more than a few dll files. Why are you resisting installing the client? Why is it preferable in your position to attempt to use a small group of dll files? What issue are you trying to overcome? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
nik_iway |
Posted: Wed Mar 29, 2006 1:50 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi Vitor,
Thanks for the reply,
I have a requirement where 200 clients applications will put a
message on a remote queuemanager residing on Windows2000 Server.
if thats the case i need to install MQClients on all 200 Machines so
as to enable them to put a message in MQServer, then would it not
Costlier, so infuture in a client apllication wants to put a message he
needs to install MQClient Software...........
Waiting for reply
Nik |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 29, 2006 2:14 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
So what you really need is not a method of connecting to a queue manager with a few DLLs, but a method of remotly installing MQ client on 200 machines? I would refer you to the MQ Clients manual (to be found at http://www-306.ibm.com/software/integration/wmq/library/ amongst other places) or the online infomation centre at http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp. There's a section on unattended installation which covers the subject more completely than I ever could.
Also remember that the MQ Client is license free so your 200 clients do not increase the cost of your MQ installation. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
nik_iway |
Posted: Wed Mar 29, 2006 2:28 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi Vitor,
i need a method of connecting to a queue manager with a few
DLLs with out installing MQCLient - can we acheive that???
Thanks for the information that MQClient is a free Software
Regards
Nik |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 29, 2006 2:39 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
[quote="Vitor"]Again with the no. You need the client installed. I do not believe you can achieve connection by copying a few dll files.
quote]
I still stand by this statement.
I fail to understand your problem. You say you have 200 client applications, all using a remote queue manager. I get that, it's quite a standard configuration. I get that this means you need to install 200 MQ clients. You also need to install the 200 client applications! Why can you not perform these 2 tasks simultaniously? What is the issue?
Please assist by repairing my understanding. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
nik_iway |
Posted: Wed Mar 29, 2006 3:15 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi Vitor,
Thanks for the reply. I had developed a standalone java API
to connect to the remote queue manager just by copying the
jar files and i am able to connect and put a message. i thought
that it can be acheived in VB
Nik |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 29, 2006 3:21 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
I stand by my previous assertion that it cannot. The VB API uses the same technology as the C/C++ interface not the Java one. There's not a direct correlation between the mqic32.dll et al & the jar files. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|