| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ C++ program client connection MRQC 2058 |
« View previous topic :: View next topic » |
| Author |
Message
|
| David.Partridge |
 Posted: Fri Oct 10, 2008 12:38 am Post subject: MQ C++ program client connection MRQC 2058 |
 |
|
Master
Joined: 28 Jun 2001
Posts: 249
|
A third party C++ application was working just fine when connecting to the QMGR using the MQSERVER environment variable.
When we changed the user's profile to specify the connection using MQCHLLIB, MQCHLTAB, and MQSSLKEYR, it gets MQRC 2058.
I realise that the C++ code will use MQCONNX under some circumstances, but does it always do so, or only if the application uses ImqQueueManager.setChannelReference()?
Put another way, is it possible to make a simple change to the C++ application code to enable the use of MQCHLLIB, MQCHLTAB, and MQSSLKEYR, or does the third party vendor need to change their code to specify all the parameters of the SSL client connection in the IMQChannel object?
Thanks
Dave Partridge |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Oct 10, 2008 1:36 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If the channel table was built leaving the QM name blank , and the app specifies the QM name on the MQCONN call, even the correct one!, it will give you a 2058.
I think the reverse is true too. Not 100% sure.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| David.Partridge |
| Posted: Sun Oct 12, 2008 11:31 pm Post subject: |
|
|
Master
Joined: 28 Jun 2001
Posts: 249
|
Hi Peter,
The QM name is specified in the channel table file. I'm not certain at this point whether the application specifies the QM name on the ctor (or uses ImqObject.setName() to do the equivalent) or not. I believe that it does.
My guess is that the application is creating an ImqChannel object, partially populating it and setting into the channel reference of the queue manager obect prior to issuing the ImqQueueManager.connect() method. I suspect that if the MQSERVER environment variable is set, then it (the application) uses the information to complete the population of the ImqChannel object prior to issuing the connect request, and this enables it to work when MQSERVER is set, but fail when using the MQCHLLIB/MQCHLLTAB/MQSSLKEYR definition of the connection.
_________________
Cheers,
David C. Partridge |
|
| 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
|
|
|
|
