I am in the process of transferring a series of MQ applications from one box to another (running Solaris)
I have installed MQSeries server software on the new box and created the new qmgr. connections to the other qmgrs in the network are working OK (new channel names etc.) and applications using MQ Client are working fine.
The applications running directly on the server are failing with 2059 error code. We are passing the new qmgrname to the applciaitons.
I can duplciate the problem using two sample utilities - BUT... one works and the other doesn't :-
amqstrg - sample trigger monitor gets hit 2059 every time BUT...
amqsbcg (sample browse program) works perfectly!
both from same userid etc. - I have looked at the source code for both - and both are doing the same work - on the MQCONN call - one dies and the other doesn't.
Of course, none of the application programs work either
Any suggestions? - it probably doesn't help I'm not a unix guru....
replies by posting here - and/or email to Len@kiwiInternet.com
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
When you say:
"Of course, none of the application programs work either"
Do you mean that you have tried running the same application outside of the trigger monitor (from the command line) and you get the same errors? I ask because I'm trying to discern whether you have a trigger problem, or something is wrong with your application code...
_________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
It isn't just "trigger monitor programs" that fail to connect - there are other application programs which run (to feed messages onto the queues for example) which also fail to connect to the QMgr - what I can't understand is why one program (IBM supplied sample Browse program) works fine when the IBM supplied sample trigger monitor program fails - same source code for the MQCONN call...
The applications are working perfectly on the old box...
Kiwi,
I am not sure whether you have sorted this problem. I faced a similar problem when promoting our application to Production. Application worked fine in UAT but in production we received error 2059 while connecting. Ours is a NT application. I copied the application to MQ Seriesbin area and found that application worked fine. Later I found that one extra dll (amqxcs2.dll) was found in c:winnt apart from MQ Seriesbin. On removing that dll or adding MQ Seriesbin before c:winnt in PATH solved the problem.
I found that your application is running in UNIX. Reply if this message helped you in any way.
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