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 IBM MQ Support » MSGEXIT parameter (two exits to a sender channel)

Post new topic  Reply to topic
 MSGEXIT parameter (two exits to a sender channel) « View previous topic :: View next topic » 
Author Message
Carla Viragh
PostPosted: Tue Dec 09, 2003 10:53 am    Post subject: MSGEXIT parameter (two exits to a sender channel) Reply with quote

Voyager

Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil

Does anybody know how to define two exits in the MSGEXIT parameter?
I tried this:

ALTER CHANNEL(MY_CHANNEL) CHLTYPE(SDR) MSGEXIT('msgmon(MsgExit)' 'msg_exit(MSG_Exit)')

MQ did not execute the exits, it works if I define only one exit.

I tried a lot of things, like comma, space, etc etc... I don´t know how to define this field to work with 2 exits...

OS: Windows 2000

Thanks.
_________________
Carla Viragh
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Tue Dec 09, 2003 11:02 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Intercommunications Guide wrote:
On AIX, Compaq Tru64 UNIX, Compaq OpenVMS Alpha, HP-UX, Linux, OS/400, OS/2 Warp, Solaris, Windows systems, and z/OS, you can specify a list of receive, send, or message exit program names. The names should be separated by a comma, a space, or both. For example:
RCVEXIT(exit1 exit2)
MSGEXIT(exit1,exit2)
SENDEXIT(exit1, exit2)

In WebSphere MQ for AIX, iSeries, HP-UX, Linux, Solaris, Windows systems, and z/OS, and MQSeries V5.1 for Compaq Tru64 UNIX, Compaq NonStop Kernel, Compaq OpenVMS Alpha, and OS/2 Warp, the total length of the string of exit names and strings of user data for a particular type of exit is limited to 500 characters. In WebSphere MQ for iSeries you can list up to 10 exit names. In WebSphere MQ for z/OS you can list up to eight exit names.
I think you may have the wrong quotes. Try using double-quotes instead of single.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Carla Viragh
PostPosted: Tue Dec 09, 2003 11:16 am    Post subject: Reply with quote

Voyager

Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil

Yes Jeff, this was the first thing I tried, just a space, just comma but no success. Quotes ( " and ' ) was the last ...

These were the commands that failed:

1 - MSGEXIT(msgmon(MsgExit),msg_exit(MSG_Exit))
2 - MSGEXIT("msgmon(MsgExit),msg_exit(MSG_Exit)")
3 - MSGEXIT("msgmon(MsgExit)","msg_exit(MSG_Exit)")
4 - MSGEXIT("'msgmon(MsgExit)','msg_exit(MSG_Exit)'")
5 - MSGEXIT(msgmon(MsgExit) msg_exit(MSG_Exit))
6 - MSGEXIT('msgmon(MsgExit)','msg_exit(MSG_Exit)')
7 - MSGEXIT('msgmon(MsgExit)' 'msg_exit(MSG_Exit)')

God....


_________________
Carla Viragh
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Tue Dec 09, 2003 11:34 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Okay, I'm wrong about the quotes. I should have double-checked the Script Command Reference first. Single-quotes are the correct thing.

I was able to get the following command to work just fine for me on windows
Code:
 alter channel(test) chltype(sdr) msgexit('a(b)','b(c)')

So, the syntax of the MQSC command is correct. You may have an issue with one of your exits. Which means you have to debug them. Which I haven't done.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Carla Viragh
PostPosted: Tue Dec 09, 2003 12:07 pm    Post subject: Reply with quote

Voyager

Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil

I was afraid to see you write that the problem is my exits.

First of all, I saw the command reference and it says: Single quote and comma is the same as one space... But I tried quote, double quote, comma, space

Well, but if you tested and the manual is right... I will debug my exits (ohhh )

Thanks very very much... I don´t have no more exits here to test.


_________________
Carla Viragh
Back to top
View user's profile Send private message Send e-mail
Carla Viragh
PostPosted: Tue Dec 09, 2003 12:12 pm    Post subject: Reply with quote

Voyager

Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil

Oh... But... I´ve tested both of exits and they are working separately!

Did you test with real exits?
_________________
Carla Viragh
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Tue Dec 09, 2003 12:42 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Carla Viragh wrote:
Oh... But... I´ve tested both of exits and they are working separately!

Did you test with real exits?

No, I don't have any I could test with.

Having them work separately doesn't guarantee that they will work together, either. At least, as I understand it. I'm basing this off what I remember from a session at the T&M conference last year. As a simple example, suppose you have a compression exit and an encryption exit. They both work correctly as individual exits. But if the sender channel calls them in the order "encrypt and then compress", and the receiver channel calls them in the order "uncompress and then decrypt", you're obviously going to have a problem.

From what I remember, they are called in the order they appear in the list.

From the foggier parts of my memory, there is a possibility that you could also run into problems like the first exit returning "skip all the rest of the exits, and forward the message".

You said that "MQ did not execute the exits" in your original post. Can you be more explicit about how you know this? Do your exits write something to a log every time they are invoked? Are you snooping the channel in some way (ip snooping, mq tracing)?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Carla Viragh
PostPosted: Wed Dec 10, 2003 4:05 am    Post subject: Reply with quote

Voyager

Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil

Sure! When I say MQ did not execute the exits, I suppose this because the first exit only logs the message in a text file, the second one encrypt the message. Both together makes the first one fail, the text file doesn´t grow and the message goes to a queue that handles messages that was not encrypted by the second exit. That´s why I suppose none of them are running. But you are right, maybe the first exit is in trouble. But I think at least the text file (log) should grow...
_________________
Carla Viragh
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » MSGEXIT parameter (two exits to a sender channel)
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.