Author |
Message
|
prince_mq |
Posted: Thu Nov 23, 2006 5:49 am Post subject: cluster sender/receiver + exit |
|
|
Voyager
Joined: 10 Aug 2006 Posts: 76
|
Hi There,
I have a cluster setup with Solaris and ISERIES machines.
Cluster Receiver is on ISERIES.
Cluster Sender is on Solaris.
I want to invoke an exit on Solaris. As the cluster sender attributes get copied from the cluster receiver, i am trying to define exit on the Cluster receiver channel
ALTER CHL(CHLNAME) CHLTYPE(CLUSRCVR) MSGEXIT(LIB/PRGNAME)
and getting confused as to how do i define this bcoz the sourcephysical location on solaris is /var/mqm/exits64. So ideally on cluster receiver I should give it as MSGEXIT(/var/mqm/exits64) which is not possible on ISERIES.
my question is how do i define the MSGEXIT attribute in the CLUSRCVR channel so that the MSGEXIT value gets copied to CLUSSDR and invokes exit on /var/mqm/exits64.
Kindly help!
Thanks in Advance! |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Nov 23, 2006 6:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I think you should only give the name of the exit, and not the path. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
prince_mq |
Posted: Thu Nov 23, 2006 6:39 am Post subject: |
|
|
Voyager
Joined: 10 Aug 2006 Posts: 76
|
Thanks for the reply Jeff,
But I should give LIBRARY name like QGPL or QMQM in MSGEXIT.
FOR E.g., MSGEXIT(QGPL/PRGNAME)
I hope the library name doesnt get copied onto CLUSSDR channel. |
|
Back to top |
|
 |
wschutz |
Posted: Thu Nov 23, 2006 7:21 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
If the exits are in the "default" location, then you don't need to specify the path. _________________ -wayne |
|
Back to top |
|
 |
prince_mq |
Posted: Fri Nov 24, 2006 8:13 am Post subject: |
|
|
Voyager
Joined: 10 Aug 2006 Posts: 76
|
Hi Wayne,
Thanks for your reply.
I am running into another problem now.
MSGEXIT attribute defined on CLUSRCVR of ISERIES takes length of 10 characters.
But on the CLUSSDR which is defined on SOLARIS, The message exit can be called as
EXITNAME(MsgExit)
which occupies minimum length of 10 characters assuming EXITNAME to be a single character.
for e.g., A(MsgExit) or B(MsgExit) etc..
The naming for this exit is not good enough as it is a single character. This is all because of the Iseries restriction on length of MSGEXIT which takes 10 characters for message exit name and 10 characters for library name.
Any Ideas abt this?
Pls throw some light!
Gracious! |
|
Back to top |
|
 |
prince_mq |
Posted: Sun Nov 26, 2006 11:37 pm Post subject: |
|
|
Voyager
Joined: 10 Aug 2006 Posts: 76
|
Hi,
On the Cluster Receiver, I thought i Can give a single character for Message exit name followed by a function name like A(MsgExit) for MSGEXIT attribute. Even its not allowing me to use Brackets in the MSGEXIT name.
The Clussdr defined on Solaris is expecting message exit of the form
Messag_Exit_Name(MsgExit).
Kindly let me know as to how to solve this. |
|
Back to top |
|
 |
Nigelg |
Posted: Mon Nov 27, 2006 1:17 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
The solution is quite complicated.
The CLUSRCVR definition from Solars is copied into the CLUSSDR definition on iSeries when the channel is created and every time the channel starts (or something like that).
You need to write a Channel Definition exit to work on iSeries; this is invoked whenever the CLUSSDR channel is copied from the CLUSRCVR.
The CHADEF exit should change the SDR/RCVR exit definition from the syntax used on Solaris to the iSeries syntax.
This (rather advanced) topic is discussed in the Intercomms manual. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
prince_mq |
Posted: Mon Nov 27, 2006 4:47 am Post subject: |
|
|
Voyager
Joined: 10 Aug 2006 Posts: 76
|
Thanks so much Nigelg,
Its a good Idea. We will go ahead and try this one along with two other possible solutions we are thinking of.
Regards,
Prince |
|
Back to top |
|
 |
|