| Author |
Message
|
| skrv |
 Posted: Wed Mar 19, 2014 9:41 am Post subject: Help Needed with using Q tool |
 |
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
Hi,
Using the below command I was able to send out email successfully (Broker flow sends out email).
q -o WMQ.EMAIL.REQUEST -m VL1CN4002 -CA -Aitest -r abc@xyz.com -F test.txt
But if I specify multiple email IDs like below, it is not working.
q -o WMQ.EMAIL.REQUEST -m VL1CN4002 -CA -Aitest -r abc@xyz.com,xxx@xyz.com -F test.txt
I tried enclosing both email IDs in double quotes, even then it is not working.
Any suggestions? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Mar 19, 2014 8:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Did you try separating them with a semi-colon instead of a comma. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| skrv |
| Posted: Thu Mar 20, 2014 6:04 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
| yes I did. it's not working either. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 20, 2014 8:27 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
The Q tool -r option sets the MQMD reply queue name AFAIK.
Not too surprised it doesn't like characters which are invalid in a queue name.
Why don't you change your broker flow to use some other field?
Perhaps the Applid, Origin data, or Account Token as Q tool can also set these.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| skrv |
| Posted: Thu Mar 20, 2014 9:01 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
| it worked in the first instance which has -r = abc@xyz.com |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 20, 2014 10:58 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Yes, and the reason for your post is that it doesn't work now!
So I am giving you another option.
Of course the broker flow would have to changed to support other fields.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Fri Mar 21, 2014 1:32 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
It seems likely to me that the problem is more with the shell rather than Q.
You don't say what platform you are on or what exactly happens.
| Quote: |
q -o WMQ.EMAIL.REQUEST -m VL1CN4002 -CA -Aitest -r abc@xyz.com,xxx@xyz.com -F test.txt
|
Have you tried something like....
q -o WMQ.EMAIL.REQUEST -m VL1CN4002 -CA -Aitest -r 'abc@xyz.com,xxx@xyz.com' -F test.txt
I can well imagine that shells will get upset about commas in parameters.
Having said that I suspect that Q will treat the comma as a separator as well and will make the first email address the Reply Queue and the second the Reply Queue Manager which is probably not what you wanted. You need to do a command like
q -o WMQ.EMAIL.REQUEST -m VL1CN4002 -CA -Aitest -$# -r 'abc@xyz.com,xxx@xyz.com' -F test.txt
The $ parameter sets the character used for separation.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Mar 21, 2014 3:58 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I am impressed once again that the Q program has an option for everything (well almost everything...).
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Mar 21, 2014 5:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| PaulClarke wrote: |
| It seems likely to me that the problem is more with the shell rather than Q. |
 |
|
| Back to top |
|
|
|
|
