| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Getting NNSY User Exit from other than default /opt/nnsy/bin |
« View previous topic :: View next topic » |
| Author |
Message
|
| Paul D |
 Posted: Tue Jan 07, 2003 4:50 am Post subject: Getting NNSY User Exit from other than default /opt/nnsy/bin |
 |
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
This is one for all the Neon users, and those who have User Exits. Since we converted over to the MQSI 2.* world, I've never been able to get MQSI to point to anywhere other than the default location for the User Exit Shared Library /opt/nnsy/bin. Altering the Shared Libary path does nothing (method stated in NNSY manuals to replace the stub). Has anyone else been able to do this on a UNIX based platform? This is annoying for several reasons, as you can imagine.
I've got a case open with IBM on this one, I'll post the feedback from them whenever I get it. Things move slow between IBM and NNSY so it might take a while. |
|
| Back to top |
|
 |
| sjclark1 |
| Posted: Tue Jan 07, 2003 6:46 am Post subject: |
|
|
Apprentice
Joined: 06 Jan 2003
Posts: 35
Location: Scotland
|
Paul - yes I have been able to do exactly what you describe on a UNIX system using WMQI V2.1. All I did was place the location of the libnnuserexit.so file at the start of the LD_LIBRARY_PATH environment variable, then started the broker. Can't think of anything else I did that might be of help.
I suppose you could always make a copy of the orignal user exit library, then place your library in /opt/nnsy/bin, until the issue is resolved.
You are correct about raising NEON-specific problems with IBM - things move very, very slowly. |
|
| Back to top |
|
|
| Paul D |
| Posted: Wed Jan 08, 2003 5:24 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
Got word back from IBM Tech Support. For HP-UX the DataFlowEngine is built with SHLIB_PATH searching disabled so that it will always look for its shared libraries in the default locations. You can see these settings by running:
chatr /opt/mqsi/bin/DataFlowEngine
What you must do is use chatr and modify the binary to enable SHLIB_PATH library searching like this:
chatr +s enable /opt/mqsi/bin/DataFlowEngine
Stop the broker first and get/set appropriate permissions so the binary can be modified. Also, this will set the SHLIB_PATH to be used second after the embedded path. Due to this, you need to remove the stub in /opt/nnsy/bin. This is because that directory in part of the embedded path. Use the SHLIB_PATH every time to find the real exit or the stub in all instances. I'll try and get word back from IBM on if this will be fixed in future releases to be consistent with other platforms and the documentation. |
|
| Back to top |
|
|
| Paul D |
| Posted: Thu Jan 09, 2003 6:05 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
| Since HPUX is such a different animal in the OS area, they plan on continuing to ship the DataFlowEngine for HPUX in the same manner. Thus, you would need to do the chatr after every patch/version. |
|
| Back to top |
|
|
| Paul D |
| Posted: Mon Feb 17, 2003 10:20 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
I had a update to this I thought I should add in. If the broker doesn't find a valid libnnuserexit.sl in the path, you will get the error...
Feb 4 08:53:02 poof WMQIv210[1042]: (POOFD1.cdm)[1]BIP2308E: File
'/opt/mqsi/lil/imbdfsql.lil' could not be loaded; operating system
return code ' 12 from shl_load '. :
POOFD1.d0a054d8-ef00-0000-0080-fa380858c4a8:
/build/S210_P/src/DataFlowEngine/DataFlowDLL/Unix/ImbLibrary.cpp: 99:
ImbLibrary::ImbLibrary: :
And will also see messages like this from stdout from the broker
/usr/lib/dld.sl: Not enough space
/usr/lib/dld.sl: Call to mmap() failed - TEXT /opt/wmqi/lib/libImbRdl.sl
For all the shared libraries that the DataFlowEngine is trying to load. I'm pretty sure it's all of them, but I'd have to check the log for sure. When I got this corrected and it was able to load a valid one, then things are fine. This was just very misleading since only the libnnuserexit.sl was not found. |
|
| 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
|
|
|
|
