| Author |
Message
|
| 5555harsha |
 Posted: Wed Jun 18, 2014 5:35 am Post subject: Issue while connecting to Queue Managers via QTP |
 |
|
Newbie
Joined: 05 Jun 2014
Posts: 2
|
Hi,
We are exploring the possibility of putting messages to MQ queues via COM/API instead of using tools like SOATEST.
We have loaded the MQ DLL in the path "C:\Program Files (x86)\ibm\WebSphere MQ\bin\MQAX200.dll"
When we try to execute the below piece of code.
Set MQSess = CreateObject("MQAX200.MQSession")
Set QMgr = CreateObject("MQAX200.MQQueueManager")
Set qm= MQSess.AccessQueueManager(QUEUE_NAME)
We are getting the error :
MQAX200.MQSession::AccessQueueManager CompletionCode = 2, ReasonCode = 2393, ReasonName = Not found in retcode translation table (959) (2393)
Can anyone please throw some light on this?
Please let us know if this can be due to SSL Authentication issue? If yes, any idea how we can handle this?
Thanks
NOTE :
*) We have set MQSERVER as an environment variable.
*) We are using the jks keystore (Same keystore is being used in Parasoft SOATEST and it is working fine) |
|
| Back to top |
|
 |
| 5555harsha |
| Posted: Wed Jun 18, 2014 5:36 am Post subject: |
|
|
Newbie
Joined: 05 Jun 2014
Posts: 2
|
| Please note we are using QTP while running the piece of code |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 18, 2014 5:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What's QTP?
Why are you using the deprecated and ugly COM API rather than the .NET API? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 18, 2014 5:41 am Post subject: Re: Issue while connecting to Queue Managers via QTP |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| 5555harsha wrote: |
| We have loaded the MQ DLL in the path "C:\Program Files (x86)\ibm\WebSphere MQ\bin\MQAX200.dll" |
Isn't that the old ActiveX dll that's been depreciated for ever? What version of WMQ are you using and what programming language? VB6??? 
| 5555harsha wrote: |
| Please let us know if this can be due to SSL Authentication issue? |
Given that if you look up a 2393 reason code it comes back "SSL Initialization Error" I'd say it's a good bet.
| 5555harsha wrote: |
| If yes, any idea how we can handle this? |
Use SSL for your connection.
| 5555harsha wrote: |
| *) We have set MQSERVER as an environment variable. |
This does not support for use of SSL in a client connection. Because this doesn't specify but implies the client side of the connection, it doesn't set up the SSL parameters the connection needs on the client side.
| 5555harsha wrote: |
| *) We are using the jks keystore (Same keystore is being used in Parasoft SOATEST and it is working fine) |
I'm sure it brings you lots of joy. How exactly are you "using" this keystore within your application? Referenced by it? Stored on the same server as your application? In the same building as your application?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 18, 2014 6:38 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
Since when does a com api / .net api use a java (jks ) keystore? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 18, 2014 7:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Since when does a com api / .net api use a java (jks ) keystore? |
Hence my question......
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
