| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error 2018 |
« View previous topic :: View next topic » |
| Author |
Message
|
| ammjacks |
 Posted: Thu Jan 10, 2002 1:59 pm Post subject: |
 |
|
Newbie
Joined: 09 Jan 2002
Posts: 2
|
I'm running a PowerBuilder application and use VB DLLs to open, close, etc queues. For one PC only, a 2018 error occurs when opening and closing the queue. I can successfully open and close the queue via DOS. I have identical applications and DLLs on other PCs that work fine. It uses Windows 95.
Can you tell me what's going wrong? |
|
| Back to top |
|
 |
| StefanSievert |
| Posted: Thu Jan 10, 2002 2:47 pm Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
Hi,
I am guessing (from reading Windows 95) here, but I am assuming that you use the MQS Client to connect to a queue manager on a different machine!?
I'm also guessing when I say that your application probably doesn't check the returncode from the MQCONN call, because a 2018 usually occurs on the second MQ call (typically an MQOPEN call). As you say that amqsputc in a DOS box works, there are two reasons for the failing connect I can think of:
1) the setting of your environment variables (MQSERVER or MQCHLLIB/MQCHLTAB) are not picked up by your VB application. Did you already try to re-boot the machine?
2) Assuming that you can specify the queue manager and queue name your application uses in a configuration file (not hardcoded), have you double checked the spelling and case of these names?
If these ideas do not apply, can you please provide more details on how you get from the client to the server. i.e. which technique you use (channel file, MQSERVER, MQCONNX).
Hope that helps,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| ammjacks |
| Posted: Fri Jan 11, 2002 3:07 pm Post subject: |
|
|
Newbie
Joined: 09 Jan 2002
Posts: 2
|
I did reboot the PC. The user says it worked one day and didn't another.
We are setting MQSERVER in the autoexec.bat in C:/Windows/System. I checked that MQSERVER was set correctly. We define the queue in an ini file, which is in the working directory of the PB application. The queue is defined correctly.
From PB, we are calling functions in VB DLLs. The call that is erroring out is MQOPEN. At the time we call MQOPEN we have a connection handle. Can we go farther and see what is causing MQOPEN to fail?
We wrote out the connection handle to a text file to see what is being passed into MQOPEN, and a 5 was displayed as the connection handle. Is there any way to find out exactly what the connection handle looks like?
Thanks. |
|
| 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
|
|
|
|
