ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » MA0Z on SLES 10 and MQ 7.0.1.3

Post new topic  Reply to topic
 MA0Z on SLES 10 and MQ 7.0.1.3 « View previous topic :: View next topic » 
Author Message
WarrenDuckworth
PostPosted: Thu Dec 16, 2010 12:38 pm    Post subject: MA0Z on SLES 10 and MQ 7.0.1.3 Reply with quote

Newbie

Joined: 07 Apr 2010
Posts: 4

I am having an issue setting up the MA0Z support pack and the wmqcml channel exit.

OS Level
SUSE Linux Enterprise Server 10 (i586)
VERSION = 10
PATCHLEVEL = 2
Linux 2.6.16.60-0.42.10-default i686

dspmqver
Name: WebSphere MQ
Version: 7.0.1.3
CMVC level: p701-103-100813
BuildType: IKAP - (Production)

Here is my channel definition
CHANNEL(TESTCONN)
CHLTYPE(SVRCONN)
COMPHDR(NONE)
COMPMSG(NONE)
DESCR( )
HBINT(300)
KAINT(AUTO)
MAXINST(999999999)
MAXINSTC(999999999)
MAXMSGL(4194304)
MCAUSER( )
MONCHL(QMGR)
RCVDATA(LF=/tmp/mlivt.txt;LO=0,6;LC=1)
RCVEXIT(wmqcml.so(wmqcml))
SCYDATA( )
SCYEXIT( )
SENDDATA(LF=/tmp/mlivt.txt;LO=0,6;LC=1)
SENDEXIT(wmqcml.so(wmqcml))
SHARECNV(10)
SSLCAUTH(REQUIRED)
SSLCIPH( )
SSLPEER( )
TRPTYPE(TCP)

When attempting to connect here is what I get in the AMQERR log
-------------------------------------------------------------------------------
12/16/2010 01:42:32 PM - Process(8838.46) User(mqm) Program(amqrmppa)
Host(svmqhub01)
AMQ6261: An exception occurred trying to dynamically load shared library
'/var/mqm/exits/wmqcml.so'. The queue manager will continue without this module.

EXPLANATION:
This message applies to UNIX systems. Exception number '8' name 'SIGFPE', occurred trying to dynamically load shared library '/var/mqm/exits/wmqcml.so'.
ACTION:
Check the shared library has not been corrupted. If the shared library contains any initializer functions, ensure these are not causing the problem and that they conform to the expected function prototype.
----- amqxufnx.c : 1170 -------------------------------------------------------
12/16/2010 01:42:32 PM - Process(8838.46) User(mqm) Program(amqrmppa)
Host(svmqhub01)
AMQ9535: User exit not valid.

EXPLANATION:
Channel program 'TESTCONN' ended because user exit 'wmqcml.so(wmqcml)' is not valid.
ACTION:
Ensure that the user exit is specified correctly in the channel definition, and that the user exit program is correct and available.

Here is my /var/mqm/exists directory
#/var/mqm/exits> ls -l
total 112
-rwxr-xr-x 1 mqm mqm 1295 2010-02-28 21:44 mlconfig.ivt
-rwxr-xr-x 1 mqm mqm 1658 2010-02-28 21:44 mlconfig.sample
-rwxr-xr-x 1 mqm mqm 8920 2010-02-28 21:44 mlutil
-rwxr-xr-x 1 mqm mqm 93397 2010-02-28 21:44 wmqcml.so

Does anyone have any idea what I am doing wrong in this setup?
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu Dec 16, 2010 1:52 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Best bet with any SupportPac is to contact the owner/maintainer by the mechanism they have included in the documentation or on the website for the Spac.

That said, unless the documentation specifically said to set the exit as wmqcml.so(wmqcml), I would think it would be something different.

If it *did* specifically say that it had to be that value, make sure you have enclosed it in single-quotes when you issues the MQSC to change it. From the error message, it doesn't *appear* that it's being upper-cased, but it could be.
Back to top
View user's profile Send private message
WarrenDuckworth
PostPosted: Thu Dec 16, 2010 2:03 pm    Post subject: Reply with quote

Newbie

Joined: 07 Apr 2010
Posts: 4

In the IBM SupportPac MA0Z - WebSphere MQ Channel Message Logger - User Guide Version 1.0.1 of 8 Mar 2010

Page 29
Linux 32 bit x86 Unix: SENDEXIT('wmqcml.so(wmqcml)')

I ran
alter channel(TESTCONN) CHLTYPE(SVRCONN) RCVEXIT('wmqcml.so(wmqcml)')
2 : alter channel(TESTCONN) CHLTYPE(SVRCONN) RCVEXIT('wmqcml.so(wmqcml)')
AMQ8016: WebSphere MQ channel changed.

display channel(WFSRVCONNE) RCVEXIT
AMQ8414: Display Channel details.
CHANNEL(TESTCONN) CHLTYPE(SVRCONN) RCVEXIT(wmqcml.so(wmqcml))

So it appears the single quotes are ignored in this case.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu Dec 16, 2010 2:17 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

No, the single-quotes aren't ignored.

They're used to protect the contents of the field from being upper-cased, which they have done. They just aren't necessarily stored in the channel definition or necessarily reported back by runmqsc.

I expect that someone with more experience will be along soon, as it is already past 9 am Australia time.
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Thu Dec 16, 2010 11:30 pm    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

please have a try with the full path name, e.g.

RCVEXIT('/var/mqm/exists/wmqcml.so(wmqcml)')

make sure wmqcml is the correct name
_________________
Regards, Butcher
Back to top
View user's profile Send private message
mvic
PostPosted: Fri Dec 17, 2010 1:46 am    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

Better not to supply a full path name because you want MQ to automatically go to /var/mqm/exits64 for 64-bit processes.
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Fri Dec 17, 2010 2:39 am    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

well yes you are right, i also missed that MQ already tries to pick up the exit from the proper location.
_________________
Regards, Butcher
Back to top
View user's profile Send private message
WarrenDuckworth
PostPosted: Mon Dec 20, 2010 5:51 am    Post subject: Reply with quote

Newbie

Joined: 07 Apr 2010
Posts: 4

I contacted Glenn Baddeley the developer of this support pack. He provided me with a version compiled for SLES that is working fine.
He asked that I do not distribute it, but if anyone else is having an issue Glenn provided a quick turn around to my inquiry.
Thank you all for your feedback.
Back to top
View user's profile Send private message
mvic
PostPosted: Mon Dec 20, 2010 6:09 am    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

WarrenDuckworth wrote:
He provided me with a version compiled for SLES that is working fine.

What is it about that distribution of Linux that requires a separate build?
Back to top
View user's profile Send private message
WarrenDuckworth
PostPosted: Mon Dec 20, 2010 6:17 am    Post subject: Reply with quote

Newbie

Joined: 07 Apr 2010
Posts: 4

Here is what Glenn sent to in response to my original inquiry

"There is a known issue that the exit module for Linux in the SupportPac v1.0.1 does not always work on SLES. It was compiled on RHEL, and works OK on RedHat.
I have attached an interim version of the exit module that was compiled on SLES x86.... Please do not distribute it to anyone else."

So, you will need to contact Glenn to get anything further.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » MA0Z on SLES 10 and MQ 7.0.1.3
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.