| Author |
Message
|
| Studv01 |
 Posted: Tue Feb 24, 2015 2:54 pm Post subject: Qload tool not working with WebSphere MQ for Linux (x86-64 ) |
 |
|
Apprentice
Joined: 23 Jan 2015
Posts: 27
|
can some one help me with qload
when I am running qload tool this is what I get
QLOAD Program by Paul Clarke [ V1.9 Build:Jun 26 2012 ]
Error loading MQAPI DLL RC(11)
here is my MQ version
Name: WebSphere MQ
Version: 7.5.0.2
Level: p750-002-130704
BuildType: IKAP - (Production)
Platform: WebSphere MQ for Linux (x86-64 platform)
Mode: 64-bit
O/S: Linux 2.6.32-431.29.2.el6.x86_64
InstName: Installation2
InstDesc:
Primary: Yes
InstPath: /opt/apps/mqm/7502
DataPath: /var/mqm
MaxCmdLevel: 750 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Feb 24, 2015 3:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
run or source crtmqenv before running QLoad ?? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Tue Feb 24, 2015 3:33 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
This is identical to the MA01 thread currently being discussed next door. My answer was along these lines....
The error message "Error Loading MQ library RC(11)" is merely QLOAD saying it can't find your MQ libarary.
You should be able to get it working by setting environment variables MQIC_DLL_PATH or MQM_DLL_PATH to the location of your MQ libraries.
You can tell QLOAD to print out what it's searching for by setting environment variable MQACCESS_DEBUG to anything at all.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Feb 25, 2015 1:10 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
On Linux there is also the 'ldd' command.
That can be useful for finding missing libraries.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| tczielke |
| Posted: Wed Feb 25, 2015 6:20 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
Setting environment variables like the following:
export LD_DEBUG=all
exoprt LD_DEBUG_OUTPUT=/tmp/ldoutput.out
can be helpful for debugging linking issues on Linux, too.
In the qload case, it looks like the MQ shared object files are being loaded at runtime with a dlopen call, so I don't believe ldd would be of much help here. The LD_DEBUG information should show you what specific shared object files the dlopen call is trying to load. Of course, this qload program seems to be full of debugging information, so none of this linking debugging information is needed for this use case, anyway. But still good to be aware of for future reference.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| Studv01 |
| Posted: Wed Feb 25, 2015 7:39 am Post subject: Thanks Every one |
|
|
Apprentice
Joined: 23 Jan 2015
Posts: 27
|
| I got it resolved by exporting MQM_DLL_PATH variable to mq libs location |
|
| Back to top |
|
|
|
|
