Re: Trigger Monitors (run under an ID other than mqm)
Hi Peter, well done on getting this working, but you may want to consider copying the runmqtrm binary and renaming it, rather than changing the installed binary by altering the permissions. Some installation packaging features don't like it when the software you are upgrading doesn't exactly match what is expected, and I never feel comfortable changing the installed software config like that. I would look at "cp /opt/mqm/bin/runmqtrm /var/mqm/exits/mymqtrm; chmod 755 /var/mqm/exits/mymqtrm" and then use mymqtrm instead of runmqtrm. Regards, Neil Casey National Australia Bank Southern Star Technology WebSphere MQ Support 1/122 Lewis Rd Wantirna South office. +61 3 9886 2375 (x82375) mobile. +61 414 615 334 "Potkay, Peter M (ISD, IT)" <[EMAIL PROTECTED] To HARTFORD.COM> [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject n.AC.AT> Re: Trigger Monitors (run under an ID other than mqm) 23/07/2004 10:35 Please respond to MQSeries List <[EMAIL PROTECTED] n.AC.AT> Well, I got the default runmqtrm to run under another ID, and it kicks off processes under that ID as well. Those triggered processes truly are running under the new ID (not mqm), as they follow the rules I set with setmqaut, and doing a Q status shows the User ID connected is in fact the ID I want, not mqm. If I try and send the triggered app to a queue I did not give it authority to, it gets the 2035. All I did to get runmqtrm to run as mqappsaa, and any triggered process to run as mqappsaa, was the following. The triggered app should only be able to GET/PUT from SYSTEM.DEFAULT.LOCAL.QUEUE, no other queue: 1. Create a group called mqappsaa 2. Create a user called mqappsaa, and put him into the group mqappsaa 3. setmqaut -m SOLARIS1 -t qmgr -g mqappsaa +allmqi 4. setmqaut -m SOLARIS1 -t q -n SYSTEM.DEFAULT.INITATION.QUEUE -g mqappsaa +allmqi 5. setmqaut -m SOLARIS1 -t q -n SYSTEM.DEAD.LETTER.QUEUE -g mqappsaa +allmqi 6. setmqaut -m SOLARIS1 -t q -n SYSTEM.DEFAULT.LOCAL.QUEUE -g mqappsaa +allmqi 7. chmod 777 runmqtrm, so that anyone can start it. Probably can be tighter on this step, but you get the point. 8. log on as mqm, just to prove it will work even if I su to mqappsaa # masun1 > su mqappsaa Password: $ whoami mqappsaa $ runmqtrm -m SOLARIS1 5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED. WebSphere MQ trigger monitor started. __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER End of application trigger. __ Waiting for a trigger message # 9. Open up another session, and check what ID runmqtrm is running under: masun1 > ps -ef|grep runmqtrm mqm 4160 3977 0 20:09:49 pts/30:00 grep runmqtrm mqappsaa 4145 4143 0 20:02:12 pts/20:00 runmqtrm -m SOLARIS1 10. Drop a test message into the triggered queue, and quickly do the following command to see what ID amqsget is running under. I triggered amqsget to run in the background. masun1 > ps -ef|grep amqsget mqm 4165 3977 0 20:20:09 pts/30:00 grep amqsget mqappsaa 4163 1 0 20:20:03 pts/20:00 /opt/mqm/samp/bin/amqsget SYSTEM1 A Queue Status on the INIT queue and the DLQ shows runmqtrm running as mqappsaa. A Queue Status on SYSTEM.DEFAULT.LOCAL.QUEUE shows amqsget running as mqappsaa, and it consumes the message. Switching the process def to run amqsget against SYSTEM.DEFAULT.LOCAL.QUEUEXX causes the app to get a 2035, proving security can be set on a triggered process started by the default runmqtrm. -Original Message- From: marty [mailto:[EMAIL PROTECTED] Sent: Saturday, July 10, 2004 8:33 AM To: [EMAIL PROTECTED] Subject: Re: Trigger Monitors Peter, >Can't you start the TM under another ID in the first place, like this? > >/usr/bin/su - mqappid -c "/opt/mqm/bin/runmqtrm -m MYQMname -q >APP.INIT.QUEUE" & > >Wouldn't this cause the TM to run as mqappid, and then any process it >started would also run as mqappid? > > World has no permissions by default so only root and user mqm or group mqm members can start it (mqappid would need to be a member of group mqm). Regardless of who starts runmqtrm, since it is setuid (and setgid) mqm it will run with effective id mqm and effective group mqm, as will any triggered program. Plus, mqappid being a member of group mqm is probably not a good thing. If you unset setuid (and setgid), as Greg suggested in (b) (possibly leaving group mq
Re: Trigger Monitors (run under an ID other than mqm)
Well, I got the default runmqtrm to run under another ID, and it kicks off processes under that ID as well. Those triggered processes truly are running under the new ID (not mqm), as they follow the rules I set with setmqaut, and doing a Q status shows the User ID connected is in fact the ID I want, not mqm. If I try and send the triggered app to a queue I did not give it authority to, it gets the 2035. All I did to get runmqtrm to run as mqappsaa, and any triggered process to run as mqappsaa, was the following. The triggered app should only be able to GET/PUT from SYSTEM.DEFAULT.LOCAL.QUEUE, no other queue: 1. Create a group called mqappsaa 2. Create a user called mqappsaa, and put him into the group mqappsaa 3. setmqaut -m SOLARIS1 -t qmgr -g mqappsaa +allmqi 4. setmqaut -m SOLARIS1 -t q -n SYSTEM.DEFAULT.INITATION.QUEUE -g mqappsaa +allmqi 5. setmqaut -m SOLARIS1 -t q -n SYSTEM.DEAD.LETTER.QUEUE -g mqappsaa +allmqi 6. setmqaut -m SOLARIS1 -t q -n SYSTEM.DEFAULT.LOCAL.QUEUE -g mqappsaa +allmqi 7. chmod 777 runmqtrm, so that anyone can start it. Probably can be tighter on this step, but you get the point. 8. log on as mqm, just to prove it will work even if I su to mqappsaa # masun1 > su mqappsaa Password: $ whoami mqappsaa $ runmqtrm -m SOLARIS1 5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED. WebSphere MQ trigger monitor started. __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER End of application trigger. __ Waiting for a trigger message # 9. Open up another session, and check what ID runmqtrm is running under: masun1 > ps -ef|grep runmqtrm mqm 4160 3977 0 20:09:49 pts/30:00 grep runmqtrm mqappsaa 4145 4143 0 20:02:12 pts/20:00 runmqtrm -m SOLARIS1 10. Drop a test message into the triggered queue, and quickly do the following command to see what ID amqsget is running under. I triggered amqsget to run in the background. masun1 > ps -ef|grep amqsget mqm 4165 3977 0 20:20:09 pts/30:00 grep amqsget mqappsaa 4163 1 0 20:20:03 pts/20:00 /opt/mqm/samp/bin/amqsget SYSTEM1 A Queue Status on the INIT queue and the DLQ shows runmqtrm running as mqappsaa. A Queue Status on SYSTEM.DEFAULT.LOCAL.QUEUE shows amqsget running as mqappsaa, and it consumes the message. Switching the process def to run amqsget against SYSTEM.DEFAULT.LOCAL.QUEUEXX causes the app to get a 2035, proving security can be set on a triggered process started by the default runmqtrm. -Original Message- From: marty [mailto:[EMAIL PROTECTED] Sent: Saturday, July 10, 2004 8:33 AM To: [EMAIL PROTECTED] Subject: Re: Trigger Monitors Peter, >Can't you start the TM under another ID in the first place, like this? > >/usr/bin/su - mqappid -c "/opt/mqm/bin/runmqtrm -m MYQMname -q >APP.INIT.QUEUE" & > >Wouldn't this cause the TM to run as mqappid, and then any process it >started would also run as mqappid? > > World has no permissions by default so only root and user mqm or group mqm members can start it (mqappid would need to be a member of group mqm). Regardless of who starts runmqtrm, since it is setuid (and setgid) mqm it will run with effective id mqm and effective group mqm, as will any triggered program. Plus, mqappid being a member of group mqm is probably not a good thing. If you unset setuid (and setgid), as Greg suggested in (b) (possibly leaving group mqm as owner and giving world r-x) then it will run as whomever starts it, as will any triggered programs. That allows any user to run the trigger monitor but the object authorities will determine if it can actually work. The MQ permissions need to be set so that the user's group(s) has permissions necessary to run the trigger monitor successfully. I forget exactly what the required settings are but something like get+inquire on the inititiation queue and display on the process. I think a benefit of settings "-r-xr-xr-x mqm mqm", as opposed to "-r-xr-x--- mqm mqapps" (see Greg's solution b), would be more control of which groups could listen to which initq(s) and start which process(es) instead of lumping them all into one group with common permissions. Depends on requirements - I guess that'd be more flexible but entail a bit more administrivia. Having all triggered programs run as user/group mqm can be problematic though not nearly as bad as running them as root :-) One issue is you probably don't want to give away mqm rights so readily. Another is mqm often doesn't have rights to either start the triggered app or do something the app is supposed to do. Yet another arises when you use the client trigger monitor and hopefully enforce clients attach as a user other than mqm. I believe a problem with Dennis' suggestion is you cannot su in a s
Re: How to trigger amqsput into the background
Nope, /dev/null never fills up although people *have* tried. It's actually and interface to a stargate so, perhaps one day, all those bits may show up again and boy will they be mad! -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (ISD, IT) Sent: Thursday, July 22, 2004 8:05 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background /opt/mqm/samp/bin/amqsget SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 1>/dev/null 2>/dev/null & This worked. This is my trigger monitor window when I dropped ONE message onto the triggered queue. Kinda weird I got the double output. $ runmqtrm -m SOLARIS1 5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED. WebSphere MQ trigger monitor started. __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER End of application trigger. __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER End of application trigger. __ Waiting for a trigger message And ps -ef|grep amqsget showed the amqsget process for the next 15 seconds. Thanks T.Rob (and Justin). Can dev/null ever fill up? I am guessing no? Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How to trigger amqsput into the background
Peter, You are both right. Amqsput waits for either an EOF or a blank line. When run in the background, STDIN is not open so the first read returns an EOF and the program immediately ends. Have you ever tried to redirect a file into amqsput? Notice you don't need a blank line at the end of the file to make it work. Note also that whether in the foreground or background, it waits forever for that EOF or blank line. You can prove that by tailing a log file and piping it to amqsput like so... (tail -f /var/mqm/qmgrs/SOLARIS1/errors/AMQERR01.LOG | cat -n | amqsput SYSTEM.DEFAULT.LOCAL.QUEUE) >/dev/null 2>&1 & The tail -f will read the AMQERR01.LOG file and print out new entries as they are written. The cat -n insures there are no blank lines. This command line now runs in the background indefinitely waiting for an EOF. Do a ps and you will see all three processes (tail, cat and amqsput) running. Now start and stop a few channels. Still running. Ok, now kill -9 the tail process. As soon as that happens, amqsput will dump all the log entries to the queue. So to make amqsput run in the background, you need to give it some input to process (either intermittent input such as with tail -f or a really big file that will take 30 seconds to process) while you are trying to catch it with a ps -ef. Or else run amqsget which will wait around long enough to be seen. -- T.Rob -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (ISD, IT) Sent: Thursday, July 22, 2004 7:38 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background Dennis, I haven't a clue on how to code C. I could probably figure it out, but for some reason trying to find a C compiler in this company is impossible! I didn't want to have to alter write code. By the way, amqsput does not end when there is no more input. It sits forever (at least 20 minutes anyway) waiting for text or a double press of the enter key. There has gotta be someway to get it to run in the background. Where the heck do I stick that & to make it run in the background? -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 7:11 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background Can't you mod amqsput to just run indefinately instead of ending when there's no more input? -Original Message- From: Potkay, Peter M (ISD, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 1:08 PM To: [EMAIL PROTECTED] Subject: How to trigger amqsput into the background Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TM
Re: How to trigger amqsput into the background
/opt/mqm/samp/bin/amqsget SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 1>/dev/null 2>/dev/null & This worked. This is my trigger monitor window when I dropped ONE message onto the triggered queue. Kinda weird I got the double output. $ runmqtrm -m SOLARIS1 5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED. WebSphere MQ trigger monitor started. __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER End of application trigger. __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER End of application trigger. __ Waiting for a trigger message And ps -ef|grep amqsget showed the amqsget process for the next 15 seconds. Thanks T.Rob (and Justin). Can dev/null ever fill up? I am guessing no? -Original Message- From: Wyatt, T.rob [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 7:46 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background Peter, Are you sure it's in the foreground? Amqsget will inherit the I/O handles of peterscript.sh which inherits from runmqtrm which means that it's output will always go to your screen - even if it's in the background - as long as: a) runmqtrm is in the foreground and b) you don't redirect the output. So you are on the right track. 1) Use amqsget instead of amqsput because it doesn't need STDIN and will remain active waiting for a 2033. 2) Redirect STDOUT and STDERR if you don't want to see them in runmqtrm's output. Send them to /dev/null or a file. 3) Do your ps -ef | grep and you should see the process. -- T.Rob -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (ISD, IT) Sent: Thursday, July 22, 2004 4:44 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background Well, this time amqsget ALWAYS starts up in the foreground and the output looks the same, whether I have the & in the script file and the end of the command, in the Env Data of the process def, or no & anywhere at all. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How many Listeners can a QM on a windows box have?
I have found that if you load more than 600 clients on a listener, the box pretty well dies, hence the 8 listeners to spread the load. Sid -Original Message- From: Potkay, Peter M (ISD, IT) [mailto:[EMAIL PROTECTED] Sent: Friday, 23 July 2004 9:25 AM To: [EMAIL PROTECTED] Subject: Re: How many Listeners can a QM on a windows box have? Someone I know created 22 of them on a Windows box, but they weren't being heavily used. IBM said that there is no official limit. Its more a function of system resources. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 7:03 PM To: [EMAIL PROTECTED] Subject: Re: How many Listeners can a QM on a windows box have? I have 8... Seams to work OK. -Original Message- From: Potkay, Peter M (ISD, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, 22 July 2004 2:49 AM To: [EMAIL PROTECTED] Subject: How many Listeners can a QM on a windows box have? Windows 2000 MQ 5.3 CSD05 How many Listeners can a QM on a windows box have? I am setting up an Edge Queue Manager, and want to have one dedicated listener per outside company, to lessen the risk of CompanyA overwhelming a listener shared by CompanyB. I also asked this of IBM, but would like to hear about real life examples. And [EMAIL PROTECTED], I don't care if you read this! ;-) Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How to trigger amqsput into the background
>>First Don't you run the script that is triggered in the background??? Tried that by sticking the & in various places in the Process Definition. No luck. >>Not the command that is inside the script you are starting??? Tried that to by sticking a blank space and the & after the QM name inside the script. No luck. >>I am assuming you are testing something weird!!! ;-> I will post it as soon as I get this one last test (triggering an MQ app in the background) completed. >>How about a loop. Its not the length of time that is the issue, I only need it to run 15 seconds or so. Its getting the damn thing to run in the background versus the Trigger Monitor window! -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 6:30 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background First Don't you run the script that is triggered in the background??? Not the command that is inside the script you are starting??? And it you want something to run for a while that you want to kill (I am assuming you are testing something wierd!!! How about a loop. (Hopfully this will not kill your machine!!!) Get something like this to work. Read from the queue and write to the same queue. Not sure this will work. BUT you get the idea /opt/mqm/samp/bin/amqsget SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 | /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 >From: Rick Tsujimoto <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: How to trigger amqsput into the background >Date: Thu, 22 Jul 2004 16:35:17 -0400 > >Peter, > >Doesn't amqsput require two null inputs to terminate the application? If >you run in background, how are you providing the double nulls? > > > > > "Potkay, Peter M > (ISD, IT)" > <[EMAIL PROTECTED] To > HARTFORD.COM> [EMAIL PROTECTED] > Sent by: MQSeries cc > List > <[EMAIL PROTECTED] Subject > n.AC.AT> How to trigger amqsput into the >background > > 07/22/2004 04:08 > PM > > > Please respond to >MQSeries List > <[EMAIL PROTECTED] > n.AC.AT> > > > > > > >Solaris 2.8 >MQ 5.3 CSD4 > >I have runmqtrm running in the foreground. > >I have the following in my ApplID field of the process definition: >/var/mqm/peterscript.sh > >I have the following in /var/mqm/peterscript.sh: >/opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 > >This works great, as I see the following in the Trigger Monitor Window: >__ >Waiting for a trigger message > >/var/mqm/peterscript.sh 'TMC2PETER >Sample AMQSPUT0 start >target queue is SYSTEM.DEFAULT.LOCAL.QUEUE >my test message to be put > >Sample AMQSPUT0 end >End of application trigger. > >__ >Waiting for a trigger message > > >So now I want the trigger monitor to kick off amqsput in the background. I >don't care that I won't be able to put to it, I will use ps -ef|grep >amqsput >to verify it is up, and then kill -9 it. > >I tried putting this inside the script: >/opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & > >and got this in the trigger monitor window: >__ >/var/mqm/peterscript.sh 'TMC2PETER >Sample AMQSPUT0 start >target queue is SYSTEM.DEFAULT.LOCAL.QUEUE >Sample AMQSPUT0 end >End of application trigger. > >__ >Waiting for a trigger message > > >It just ends amqsput right away. It is not running in the background. And >notice the Waiting for Trigger message line does not come up either. But if >I then try retriggering it in the foreground again, I get this: > >/var/mqm/peterscript.sh 'TMC2PETER >Sample AMQSPUT0 start >target queue is SYSTEM.DEFAULT.LOCAL.QUEUE >Sample AMQSPUT0 end >End of application trigger. > >__ >Waiting for a trigger message > >I didn't get the chance to add my message; amqsput ends right away again, >but now the Waiting for Trigger Message comes up, and now I can retrigger >correctly in the foreground as I did in the beginning. > > >I also tried putting the & in the Environment Data of the Process Def, I >got >this: >__ >Waiting for a trigger message >Sample AMQSPUT0 start >target queue is SYSTEM.DEFAULT.LOCAL.QUEUE >Sample AMQSPUT0 end > >again no Waiting for Trigger message error. Altering the Process def to >remove the & and trying to trigger again gave me this: > >/var/mqm/peterscript.sh 'TMC2PETER >Sample AMQSPUT0 start >target
Re: How to trigger amqsput into the background
Peter, Are you sure it's in the foreground? Amqsget will inherit the I/O handles of peterscript.sh which inherits from runmqtrm which means that it's output will always go to your screen - even if it's in the background - as long as: a) runmqtrm is in the foreground and b) you don't redirect the output. So you are on the right track. 1) Use amqsget instead of amqsput because it doesn't need STDIN and will remain active waiting for a 2033. 2) Redirect STDOUT and STDERR if you don't want to see them in runmqtrm's output. Send them to /dev/null or a file. 3) Do your ps -ef | grep and you should see the process. -- T.Rob -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (ISD, IT) Sent: Thursday, July 22, 2004 4:44 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background Well, this time amqsget ALWAYS starts up in the foreground and the output looks the same, whether I have the & in the script file and the end of the command, in the Env Data of the process def, or no & anywhere at all. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How to trigger amqsput into the background
Dennis, I haven't a clue on how to code C. I could probably figure it out, but for some reason trying to find a C compiler in this company is impossible! I didn't want to have to alter write code. By the way, amqsput does not end when there is no more input. It sits forever (at least 20 minutes anyway) waiting for text or a double press of the enter key. There has gotta be someway to get it to run in the background. Where the heck do I stick that & to make it run in the background? -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 7:11 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background Can't you mod amqsput to just run indefinately instead of ending when there's no more input? -Original Message- From: Potkay, Peter M (ISD, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 1:08 PM To: [EMAIL PROTECTED] Subject: How to trigger amqsput into the background Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE test message to put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message This time it didn't need that double triggering to get amqsput to show up properly. Any ideas of how to get it to start up in the background properly? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: QMgr leaving Cluster
"somehow is removed from the cluster" What makes you think that? -Original Message-From: Lynn Nelson [mailto:[EMAIL PROTECTED]Sent: Thursday, July 22, 2004 5:13 PMTo: [EMAIL PROTECTED]Subject: QMgr leaving Cluster Hello, Has anyone ever seen this? We have a cluster that had been working fine until we recently added a new fourth QMgr. Everything is processing properly and suddenly this new QMgr decides it wants no part of the Cluster and somehow is removed from the cluster. Thanks, Lynn This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies.
Re: MQ on Windows with shared disks
Regarding security: If you have specific UserIDs that need setmqaut commands run against them, you must use Domain Ids so that the Windows SID will be the same for the ID, regardless of which server it is running on. Define a UserID called PETER on Server1 and define a UserID called PETER on Server2 will give you to IDs that to the human eye look alike, but your setmqaut commands that you run for QM1 will all not be recognized when QM1 fails over to Server2. You need an ID like DOMAIN_NAME/PETER, and then add that ID to both servers. -Original Message- From: Crupi, Margherita [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 6:49 PM To: [EMAIL PROTECTED] Subject: Re: MQ on Windows with shared disks Paul, We run MSCS clusters using EMC-SRDF for the MQ data files for live/failover purposes on W2K without any issues - which would be similar enough for your query. We do not have to replicate the registries between the 2 clusters and have had no issues with security using domains either. Hope this helps. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Meekin, Paul Sent: Friday, 23 July 2004 1:44 AM To: [EMAIL PROTECTED] Subject: MQ on Windows with shared disks Hi all, We are looking at the feasability of running MQ on a pair of Windows 2000 servers in a live/fail-over configuration. The idea is to put all of the MQ data files onto a shared disk using EMC-SRDF which will be available to whichever machine is currently running in production. Note that we cannot use MSCS for this - only a shared disk. Has anyone done this? Potential problems that we can see include the need to replicate the registry entries as well as the fact that the local mqm group on each machine will have a different sid (if that's the right terminology for groups) which might cause problems with regard to the MQ file permissions. Any experiences would be very helpful. Cheers, Paul Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How many Listeners can a QM on a windows box have?
Someone I know created 22 of them on a Windows box, but they weren't being heavily used. IBM said that there is no official limit. Its more a function of system resources. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 7:03 PM To: [EMAIL PROTECTED] Subject: Re: How many Listeners can a QM on a windows box have? I have 8... Seams to work OK. -Original Message- From: Potkay, Peter M (ISD, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, 22 July 2004 2:49 AM To: [EMAIL PROTECTED] Subject: How many Listeners can a QM on a windows box have? Windows 2000 MQ 5.3 CSD05 How many Listeners can a QM on a windows box have? I am setting up an Edge Queue Manager, and want to have one dedicated listener per outside company, to lessen the risk of CompanyA overwhelming a listener shared by CompanyB. I also asked this of IBM, but would like to hear about real life examples. And [EMAIL PROTECTED], I don't care if you read this! ;-) Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Moving the list server ?
Not a bad suggestion but personally NO. The current service works quite well with the occasional problem and its much more likely to remain free of charge. Regards Tim A -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, 23 July 2004 9:01 AM To: [EMAIL PROTECTED] Subject: Moving the list server ? In light of all the problems with users sending read replies and not being able to get the owners/moderators to do anything, perhaps it is time to move the list to Yahoo groups... I know they send advertising but a group of us could be moderators and hence control things a bit better ? Any thoughts anyone... Sid Young QML Pathology Brisbane Australia Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How to trigger amqsput into the background
Can't you mod amqsput to just run indefinately instead of ending when there's no more input? -Original Message- From: Potkay, Peter M (ISD, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 1:08 PM To: [EMAIL PROTECTED] Subject: How to trigger amqsput into the background Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE test message to put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message This time it didn't need that double triggering to get amqsput to show up properly. Any ideas of how to get it to start up in the background properly? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How many Listeners can a QM on a windows box have?
I have 8... Seams to work OK. -Original Message- From: Potkay, Peter M (ISD, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, 22 July 2004 2:49 AM To: [EMAIL PROTECTED] Subject: How many Listeners can a QM on a windows box have? Windows 2000 MQ 5.3 CSD05 How many Listeners can a QM on a windows box have? I am setting up an Edge Queue Manager, and want to have one dedicated listener per outside company, to lessen the risk of CompanyA overwhelming a listener shared by CompanyB. I also asked this of IBM, but would like to hear about real life examples. And [EMAIL PROTECTED], I don't care if you read this! ;-) Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Moving the list server ?
In light of all the problems with users sending read replies and not being able to get the owners/moderators to do anything, perhaps it is time to move the list to Yahoo groups... I know they send advertising but a group of us could be moderators and hence control things a bit better ? Any thoughts anyone... Sid Young QML Pathology Brisbane Australia Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: MQ on Windows with shared disks
Paul, We run MSCS clusters using EMC-SRDF for the MQ data files for live/failover purposes on W2K without any issues - which would be similar enough for your query. We do not have to replicate the registries between the 2 clusters and have had no issues with security using domains either. Hope this helps. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Meekin, Paul Sent: Friday, 23 July 2004 1:44 AM To: [EMAIL PROTECTED] Subject: MQ on Windows with shared disks Hi all, We are looking at the feasability of running MQ on a pair of Windows 2000 servers in a live/fail-over configuration. The idea is to put all of the MQ data files onto a shared disk using EMC-SRDF which will be available to whichever machine is currently running in production. Note that we cannot use MSCS for this - only a shared disk. Has anyone done this? Potential problems that we can see include the need to replicate the registry entries as well as the fact that the local mqm group on each machine will have a different sid (if that's the right terminology for groups) which might cause problems with regard to the MQ file permissions. Any experiences would be very helpful. Cheers, Paul Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How to trigger amqsput into the background
First Don't you run the script that is triggered in the background??? Not the command that is inside the script you are starting??? And it you want something to run for a while that you want to kill (I am assuming you are testing something wierd!!! How about a loop. (Hopfully this will not kill your machine!!!) Get something like this to work. Read from the queue and write to the same queue. Not sure this will work. BUT you get the idea /opt/mqm/samp/bin/amqsget SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 | /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 From: Rick Tsujimoto <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background Date: Thu, 22 Jul 2004 16:35:17 -0400 Peter, Doesn't amqsput require two null inputs to terminate the application? If you run in background, how are you providing the double nulls? "Potkay, Peter M (ISD, IT)" <[EMAIL PROTECTED] To HARTFORD.COM> [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject n.AC.AT> How to trigger amqsput into the background 07/22/2004 04:08 PM Please respond to MQSeries List <[EMAIL PROTECTED] n.AC.AT> Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE test message to put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message This time it didn't need that double triggering to get amqsput to show up properly. Any ideas of how to get it to start up in the background properly? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wie
QMgr leaving Cluster
Hello, Has anyone ever seen this? We have a cluster that had been working fine until we recently added a new fourth QMgr. Everything is processing properly and suddenly this new QMgr decides it wants no part of the Cluster and somehow is removed from the cluster. Thanks, Lynn
Bug found in MS0B - Java / PCF
All,
Well, it must be my lucky week because I have found a very weird bug in
SupportPac MS0B. It has to do with non mqm accounts doing a PCF command to get
queue attribute information via client mode connection. I believe the problem
is with the SupportPac rather than WMQ.
If anyone would like to test this out (IBM Hursley!?!), here's what you need to
do. First get the latest release of MS0B SupportPac and have WMQ V5.3 (any CSD
level) installed.
I did the test with the queue manager on Solaris but any platform should give
the same results. Now create a group and user account.
i.e.
groupadd mygrp
useradd -d /export/home/fredf -m -g mygrp -s /bin/sh -c "Fred Flinstone" fredf
If you want to, create a new create queue manager or use an existing queue
manager (same box that you created the goup & user accounts on) and then do the
following commands (I'll use TESTQM as the queue manager):
setmqaut -m TESTQM -t qmgr -g mygrp +dsp +allmqi
setmqaut -m TESTQM -t q -n SYSTEM.** -g mygrp +dsp +allmqi
Now do the following 2 MQSC via runmqsc for TESTQM queue manager:
define channel(TESTQM_SVR.CH01) chltype(SVRCONN) trptype(TCP) MCAUSER('fredf')
and then issue the REFRESH SECURITY command.
Yes, I put the 'fredf' UserID in the MCAUSER on purpose.
Now from your PC or any box, but in client mode, run some of the MS0B examples.
i.e
PCFMessageListQueueNames works as expected:
java PCFMessageListQueueNames 1.2.3.4 1414 TESTQM_SVR.CH01
PCFMessageListQueueDepth throws an exception at the 'agent.send()' method but it
IS supposed to work basic on the setmqaut commands:
java PCFMessageListQueueDepth 1.2.3.4 1414 TESTQM_SVR.CH01
After a LOT of testing I finally discovered something VERY interesting. Run the
attached PCFMessageListQueueDepth2.
java PCFMessageListQueueDepth2 1.2.3.4 1414 TESTQM_SVR.CH01
Either I found a security hole or I found a work-around for the bug (I believe
it is the latter). I created a 'dummy' PCFAgent and connected it to queue
manager BEFORE the real PCFAgent call. Now the code works fine. The only
other thing I added is a CompCode check in the loop to make sure it is 0.
Now here is why I think it is a bug in MS0B rather than anything else (i.e.
security hole).
It appears that IBM decided that absolutely nobody can have any access to the
'SYSTEM.AUTH.DATA.QUEUE' queue except for mqm. This is where the problem lies
with MS0B.
For PCFMessageListQueueDepth, the exception is thrown on the 'agent.send()' with
CompCode of 2 & ReasonCode of 2035. The agend.send() method is supposed to
return a group of MQCFH structures. Each with its own CompCode & ReasonCode.
But MS0B throws an exception for the entire group (CompCode of 2 & ReasonCode
of 2035 plus lots of other items.).
For PCFMessageListQueueDepth2, I don't know 'what' is getting correctly set in
MS0B with the 'dummy agent' but it is returning a correct set of MQCFH
structures where all but one have a CompCode of 0 & ReasonCode of 0. The MQCFH
structure for 'SYSTEM.AUTH.DATA.QUEUE' does have CompCode of 2 & ReasonCode of
2035.
Can someone from IBM Hursley have a look at this problem and comment? (Primary
tests were conducted from Windows 2000 to a Solaris 8 box).
Regards,
Roger Lacroix
Capitalware Inc.
http://www.capitalware.biz
PCFMessageListQueueDepth2.java
Description: Binary data
Re: How to trigger amqsput into the background
Well, this time amqsget ALWAYS starts up in the foreground and the output looks the same, whether I have the & in the script file and the end of the command, in the Env Data of the process def, or no & anywhere at all. -Original Message- From: Awerbuch, David (CALYON) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 4:34 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background Peter, When you have an application that expects keyboard input (like amqsput) and run it in the background, the program gets an immediate EOF on the first read. In this case, amqsput is getting the EOF and is terminating without having processed a message. I am guessing that this is a simple test you are trying, to prove that the trigger actually works and that the target application starts up properly. I would suggest for this test that you run amqsget; amqsget will wait for (I believe) 15 seconds, and then terminate on NO_MSGS_AVAIALBLE. Good luck, let us know what happenned. Dave A. -Original Message- From: Potkay, Peter M (ISD, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 4:08 PM To: [EMAIL PROTECTED] Subject: How to trigger amqsput into the background Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE test message to put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message This time it didn't need that double triggering to get amqsput to show up properly. Any ideas of how to get it to start up in the background properly? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive *** Calyon This message and/or any attachments (the "message") is intended for the sole use of its addressee. If you are not the addressee, please immediately notify the sender and then destroy the message. The unauthorized
Re: How to trigger amqsput into the background
Rick, I can't get it to run in the background, thats what I am trying to figure out. Once it is in the background, I'll just kill -9 it. The point of this is I need a app that I can trigger that will run (in the background) long enough for me to do a ps -ef|grep appname on it in another session. -Original Message- From: Rick Tsujimoto [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 4:35 PM To: [EMAIL PROTECTED] Subject: Re: How to trigger amqsput into the background Peter, Doesn't amqsput require two null inputs to terminate the application? If you run in background, how are you providing the double nulls? "Potkay, Peter M (ISD, IT)" <[EMAIL PROTECTED] To HARTFORD.COM> [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject n.AC.AT> How to trigger amqsput into the background 07/22/2004 04:08 PM Please respond to MQSeries List <[EMAIL PROTECTED] n.AC.AT> Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE test message to put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message This time it didn't need that double triggering to get amqsput to show up properly. Any ideas of how to get it to start up in the background properly? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for man
Re: How to trigger amqsput into the background
Hi Peter, Try redirecting the stdio streams as follows (particularly stdin): /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 0&1 & Best regards, Justin T. Fries WebSphere MQ Support Raleigh, North Carolina "Potkay, Peter M (ISD, IT)" <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 07/22/2004 04:08 PM Please respond to MQSeries List To [EMAIL PROTECTED] cc Subject How to trigger amqsput into the background Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC 2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC 2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background.
NetIQ App Manager for MQ
Hi all, Anyone have any experiences with this tool that they would like to share? Monitoring gurus are considering migrating from PATROL to this suite... TIA! Gary Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How to trigger amqsput into the background
Peter, Doesn't amqsput require two null inputs to terminate the application? If you run in background, how are you providing the double nulls? "Potkay, Peter M (ISD, IT)" <[EMAIL PROTECTED] To HARTFORD.COM> [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject n.AC.AT> How to trigger amqsput into the background 07/22/2004 04:08 PM Please respond to MQSeries List <[EMAIL PROTECTED] n.AC.AT> Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE test message to put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message This time it didn't need that double triggering to get amqsput to show up properly. Any ideas of how to get it to start up in the background properly? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: How to trigger amqsput into the background
Peter, When you have an application that expects keyboard input (like amqsput) and run it in the background, the program gets an immediate EOF on the first read. In this case, amqsput is getting the EOF and is terminating without having processed a message. I am guessing that this is a simple test you are trying, to prove that the trigger actually works and that the target application starts up properly. I would suggest for this test that you run amqsget; amqsget will wait for (I believe) 15 seconds, and then terminate on NO_MSGS_AVAIALBLE. Good luck, let us know what happenned. Dave A. -Original Message- From: Potkay, Peter M (ISD, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 4:08 PM To: [EMAIL PROTECTED] Subject: How to trigger amqsput into the background Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE test message to put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message This time it didn't need that double triggering to get amqsput to show up properly. Any ideas of how to get it to start up in the background properly? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive *** Calyon This message and/or any attachments (the "message") is intended for the sole use of its addressee. If you are not the addressee, please immediately notify the sender and then destroy the message. The unauthorized disclosure, use, dissemination or copying (either whole or partial) of this e-mail, or any information it contains, is prohibited. E-mails are susceptible to alteration and their integrity cannot be guaranteed. As this message and/or any attachments may have been altered without our knowledge, its content is not legally binding on CALYON Corporate and Investment Bank. All rights reserved. Instructions for manag
Re: How to trigger amqsput into the background
Peter, have you also tried: nohup commmand_to_execute_in_background & -Oorspronkelijk bericht- Van: MQSeries List [mailto:[EMAIL PROTECTED] Potkay, Peter M (ISD, IT) Verzonden: Thursday, July 22, 2004 10:08 PM Aan: [EMAIL PROTECTED] Onderwerp: How to trigger amqsput into the background Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE test message to put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message This time it didn't need that double triggering to get amqsput to show up properly. Any ideas of how to get it to start up in the background properly? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
How to trigger amqsput into the background
Solaris 2.8 MQ 5.3 CSD4 I have runmqtrm running in the foreground. I have the following in my ApplID field of the process definition: /var/mqm/peterscript.sh I have the following in /var/mqm/peterscript.sh: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 This works great, as I see the following in the Trigger Monitor Window: __ Waiting for a trigger message /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE my test message to be put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message So now I want the trigger monitor to kick off amqsput in the background. I don't care that I won't be able to put to it, I will use ps -ef|grep amqsput to verify it is up, and then kill -9 it. I tried putting this inside the script: /opt/mqm/samp/bin/amqsput SYSTEM.DEFAULT.LOCAL.QUEUE SOLARIS1 & and got this in the trigger monitor window: __ /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message It just ends amqsput right away. It is not running in the background. And notice the Waiting for Trigger message line does not come up either. But if I then try retriggering it in the foreground again, I get this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message I didn't get the chance to add my message; amqsput ends right away again, but now the Waiting for Trigger Message comes up, and now I can retrigger correctly in the foreground as I did in the beginning. I also tried putting the & in the Environment Data of the Process Def, I got this: __ Waiting for a trigger message Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE Sample AMQSPUT0 end again no Waiting for Trigger message error. Altering the Process def to remove the & and trying to trigger again gave me this: /var/mqm/peterscript.sh 'TMC2PETER Sample AMQSPUT0 start target queue is SYSTEM.DEFAULT.LOCAL.QUEUE test message to put Sample AMQSPUT0 end End of application trigger. __ Waiting for a trigger message This time it didn't need that double triggering to get amqsput to show up properly. Any ideas of how to get it to start up in the background properly? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Moving Queue Manager to New Server
Bill is correct in that the existing qmgr should be removed from the cluster before you join the new one. I have already done this before. Here are the steps: 1- Save all objects on the exisiting qmgr (QM1), and save it to file (file1) 2- Create the new QM1 on the other server 3- Remove QM1 from the cluster 4- Make sure QM1 is "really" removed from the cluster: DISPLAY CLUSQMGR(*) on the full-reps will verify that for you... If it is still there, you would have to force-remove it from the cluster... 5- Issue REFRESH CLUSTER on all cluster qmgrs 6- Issue RUNMQSC QM1 7- DISPLAY CLUSQMGR(*) to see your new QM1 in the cluster. Best regards, Ruzi Bill Anderson <[EMAIL PROTECTED]> wrote: I guess in my mind that is duplicating a queue manager. It has the samename, objects, etc. But that is just semantics.I understand the fundamentals of clustering, but have little personalexperience with implementing it, so take this with a grain of salt.It seems to me if, after building the new queue manager, you could thenremove the existing queue manager from the cluster, and then bring up thenew queue manager on a different box, the new queue manager would advertiseits self to the cluster main repositories like any new queue manager thatjoins an existing cluster. That should not require any sort of resetting ofsequence numbers.I would check the manual to determine what steps may be necessary to ensureall members of the cluster are aware of the existing queue managersremoval.Cheers"AkBar E. Dar"<[EMAIL PROTECTED] [EMAIL PROTECTED]COM> cc:Sent by: MQSeries Subject: Re: Moving Queue Manager to New ServerList<[EMAIL PROTECTED]N.AC.AT>07/22/2004 11:01AMPlease respond toMQSeries ListI am not duplicating the Queue Manger, rather we moving to a new machine.Once New machine is imaged, I will turn off the other machine and configurethe same Queue Manager on the New machine with the information like ServerName(CONNAME) and reset the Channel Sequence Number. Then run the securityfile(was created using "amqoamd") back in with the updated securityinformation. This should get the Queue Manager running in a Cluster underthe new location.Bill; I did find the Channel information, once I ran the "saveqmgr" butcluster definition is not there. I don't think there is anything else.Let me know if I am missing anything.Thanks,(Embedded image moved to file: pic02306.gif)-This e-mail, and any attached file(s), is intended solely for the use ofthe individual or entity to whom this e-mail is addressed and may containinformation that is privileged, confidential or exempt from disclosure. Ifyou are not one of the named recipient(s) or otherwise have reason tobelieve that you have received this message in error, please notify the UIInformation Security Manager at 203-499-3689 and delete this messageimmediately from any computer. Any other use, retention, dissemination,retransmission, printing or copying of this e-mail is strictly prohibited.(See attached file: pic02306.gif)> ATTACHMENT part 2 image/gif name=pic02306.gif
Re: MQ on Windows with shared disks
Sounds like Veratas for UNIX. From: "Meekin, Paul" <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: MQ on Windows with shared disks Date: Thu, 22 Jul 2004 16:43:54 +0100 Hi all, We are looking at the feasability of running MQ on a pair of Windows 2000 servers in a live/fail-over configuration. The idea is to put all of the MQ data files onto a shared disk using EMC-SRDF which will be available to whichever machine is currently running in production. Note that we cannot use MSCS for this - only a shared disk. Has anyone done this? Potential problems that we can see include the need to replicate the registry entries as well as the fact that the local mqm group on each machine will have a different sid (if that's the right terminology for groups) which might cause problems with regard to the MQ file permissions. Any experiences would be very helpful. Cheers, Paul Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Collecting Events on two Queues
I didn't get the orig message so I am going on faith of context here. Do you have a DR site. Point one tool to the primary and one to the DR site. This would be good until you have a failover. From: "Williams, Arlen" <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Collecting Events on two Queues Date: Thu, 22 Jul 2004 10:57:37 -0500 Send the events to one queue and then use the q program (SupportPac MA01 - http://www-1.ibm.com/support/docview.wss?rs=203&uid=swg24000647&loc=en_US&cs =utf-8&lang=en) to duplicate the messages onto 2 separate queues for the 3rd party tools to use. -Original Message- From: Agarwal, Krishan [IT] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 9:56 AM To: [EMAIL PROTECTED] Subject: Collecting Events on two Queues Hi, I have a sitiutaion where I want to collect Events for two third party tools on two different queues. I have deleted the system event queues and defined them as alias queues pointing to Q1. But I want same events to be collected on Q2 also. Is there anyway to do this? Regards, Krishan Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: MQ HFS information
Title: Message Mike Good question. I had asked a question about maintenance and installation standards a short while back but no one answered. So my question went onto IBM support and eventually Hursley. We are running WMQ V5.3.1 on OS/390. I don't think we will be installing anything new for WMQ when we go to z/OS. This is what we have looked at so far as a guideline for handling HFS installs: APAR II12059 INFO APAR for CICS TS 1.3 HFS related issues BDC24686 HFS question about how to manage change BDC21224 HFS Sysplex Sharing questions Manuals to read: z/OS UNIX System Services User's Guidez/OS UNIX System Services Planning z/OS Parallel Sysplex Test Report Version 1 Release 5 Hierarchical File System Usage Guide Redbook e-business Cookbook for z/OS Volume II: Infrastructure Redbook WebSphere MQ in a z/OS Parallel Sysplex Environment Redbook The Program Directory for MQ V5.3.1 We are just beginning to plow through a portion of this material. If you have some UNIX background, it will go easier for you. If you come up with anything better please let me know. If you want to exchange any ideas, we could go off list. Thanks Frank -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Mike DavidsonSent: Thursday, July 22, 2004 11:05 AMTo: [EMAIL PROTECTED]Subject: MQ HFS information (We're running MQ v5.3 on z/OS 1.4) I don't expect alot of responses on this one b/c nobody seems to know anything about this stuff, but here it goes: I'm looking for any information/documentation I can find on the data, directories, and files contained within the MQ HFS structure under USS. Thanks in advance.Mike DavidsonTSYS MQ Tech SupportIBM Certified System Administrator - WebSphere MQ V5.3IBM Certified Solution Designer - WebSphere MQ V5.3[EMAIL PROTECTED] The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you This e-mail message and any attachments contain confidential information from Medco. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.
Re: MQ on Windows with shared disks
Paul, What is the block on using MSCS - that looks to be the exact tool you need! Dave Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Collecting Events on two Queues
Krishan, Since the event messages are only generate donce, the best suggestion I can make is to use the multiplexor program MMX that you can download from Lacroix's website (http://www.capitalware.biz/dl/code/c/mmx.zip). MMX would read the event queue, and copy the events to two separate queues, one for each product you wish to see the events. I use this program for capturing production data to replay on a test system, so I can assure you it works just fine. I source is included as well so you can migrate the code to any system that supports a C compiler. Good luck, let us know what you do and how it turns out. Dave A. David Awerbuch MQSeries Specialist APC Consulting Services Inc. mailto:[EMAIL PROTECTED] -Original Message- From: Agarwal, Krishan [IT] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 11:38 AM To: [EMAIL PROTECTED] Subject: Re: Collecting Events on two Queues Paul, I can't make a code change as these are third party tools. The only thing that I am allowed to do is on infrastructure level. Regards, Krishan -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul Clarke Sent: Thursday, July 22, 2004 11:28 AM To: [EMAIL PROTECTED] Subject: Re: Collecting Events on two Queues You could daisy chain the event handlers. ie. have that part of the processing of the event message is to put a copy of it to another queue. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley "Agarwal, Krishan [IT]" [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject N.AC.AT> Collecting Events on two Queues 22/07/2004 15:55 Please respond to MQSeries List Hi, I have a sitiutaion where I want to collect Events for two third party tools on two different queues. I have deleted the system event queues and defined them as alias queues pointing to Q1. But I want same events to be collected on Q2 also. Is there anyway to do this? Regards, Krishan Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive *** Calyon This message and/or any attachments (the "message") is intended for the sole use of its addressee. If you are not the addressee, please immediately notify the sender and then destroy the message. The unauthorized disclosure, use, dissemination or copying (either whole or partial) of this e-mail, or any information it contains, is prohibited. E-mails are susceptible to alteration and their integrity cannot be guaranteed. As this message and/or any attachments may have been altered without our knowledge, its content is not legally binding on CALYON Corporate and Investment Bank. All rights reserved. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Moving Queue Manager to New Server
I guess in my mind that is duplicating a queue manager. It has the same name, objects, etc. But that is just semantics. I understand the fundamentals of clustering, but have little personal experience with implementing it, so take this with a grain of salt. It seems to me if, after building the new queue manager, you could then remove the existing queue manager from the cluster, and then bring up the new queue manager on a different box, the new queue manager would advertise its self to the cluster main repositories like any new queue manager that joins an existing cluster. That should not require any sort of resetting of sequence numbers. I would check the manual to determine what steps may be necessary to ensure all members of the cluster are aware of the existing queue managers removal. Cheers "AkBar E. Dar" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] COM> cc: Sent by: MQSeriesSubject: Re: Moving Queue Manager to New Server List <[EMAIL PROTECTED] N.AC.AT> 07/22/2004 11:01 AM Please respond to MQSeries List I am not duplicating the Queue Manger, rather we moving to a new machine. Once New machine is imaged, I will turn off the other machine and configure the same Queue Manager on the New machine with the information like Server Name(CONNAME) and reset the Channel Sequence Number. Then run the security file(was created using "amqoamd") back in with the updated security information. This should get the Queue Manager running in a Cluster under the new location. Bill; I did find the Channel information, once I ran the "saveqmgr" but cluster definition is not there. I don't think there is anything else. Let me know if I am missing anything. Thanks, (Embedded image moved to file: pic02306.gif) - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. (See attached file: pic02306.gif) <>
Re: Collecting Events on two Queues
Krishan, if your using Candle or BMC, I have configured the agents in the past to just Browse vs destructive GET. Check with the vendors and see if this is possible, then just put the one that can first. Glen Larson Zurich North America "Agarwal, Krishan [IT]" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 07/22/2004 10:37:45 AM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: Collecting Events on two Queues Paul, I can't make a code change as these are third party tools. The only thing that I am allowed to do is on infrastructure level. Regards, Krishan -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul Clarke Sent: Thursday, July 22, 2004 11:28 AM To: [EMAIL PROTECTED] Subject: Re: Collecting Events on two Queues You could daisy chain the event handlers. ie. have that part of the processing of the event message is to put a copy of it to another queue. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley "Agarwal, Krishan [IT]" [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject N.AC.AT> Collecting Events on two Queues 22/07/2004 15:55 Please respond to MQSeries List Hi, I have a sitiutaion where I want to collect Events for two third party tools on two different queues. I have deleted the system event queues and defined them as alias queues pointing to Q1. But I want same events to be collected on Q2 also. Is there anyway to do this? Regards, Krishan Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive *** PLEASE NOTE *** This E-Mail/telefax message and any documents accompanying this transmission may contain privileged and/or confidential information and is intended solely for the addressee(s) named above. If you are not the intended addressee/recipient, you are hereby notified that any use of, disclosure, copying, distribution, or reliance on the contents of this E-Mail/telefax information is strictly prohibited and may result in legal action against you. Please reply to the sender advising of the error in transmission and immediately delete/destroy the message and any accompanying documents. Thank you. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Collecting Events on two Queues
Send the events to one queue and then use the q program (SupportPac MA01 - http://www-1.ibm.com/support/docview.wss?rs=203&uid=swg24000647&loc=en_US&cs =utf-8&lang=en) to duplicate the messages onto 2 separate queues for the 3rd party tools to use. -Original Message- From: Agarwal, Krishan [IT] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 9:56 AM To: [EMAIL PROTECTED] Subject: Collecting Events on two Queues Hi, I have a sitiutaion where I want to collect Events for two third party tools on two different queues. I have deleted the system event queues and defined them as alias queues pointing to Q1. But I want same events to be collected on Q2 also. Is there anyway to do this? Regards, Krishan Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Collecting Events on two Queues
Krishnan, You will need to write something to make this work. For example, you could point the alias to a new queue, QA, and then write your own triggered program to move copies of the messages to Q1 and Q2. There is a Perl program on MQSeries.net that moves messages using passall authority to preserve the context info. You could easily modify that to put the messages to two queues. Look for AdminMove.pl here: http://www.mqseries.net/pafiledb203/pafiledb.php?action=viewcat&id=1 -- T.Rob -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Agarwal, Krishan [IT] Sent: Thursday, July 22, 2004 11:38 AM To: [EMAIL PROTECTED] Subject: Re: Collecting Events on two Queues Paul, I can't make a code change as these are third party tools. The only thing that I am allowed to do is on infrastructure level. Regards, Krishan -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul Clarke Sent: Thursday, July 22, 2004 11:28 AM To: [EMAIL PROTECTED] Subject: Re: Collecting Events on two Queues You could daisy chain the event handlers. ie. have that part of the processing of the event message is to put a copy of it to another queue. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley "Agarwal, Krishan [IT]" [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject N.AC.AT> Collecting Events on two Queues 22/07/2004 15:55 Please respond to MQSeries List Hi, I have a sitiutaion where I want to collect Events for two third party tools on two different queues. I have deleted the system event queues and defined them as alias queues pointing to Q1. But I want same events to be collected on Q2 also. Is there anyway to do this? Regards, Krishan Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
MQ on Windows with shared disks
Hi all, We are looking at the feasability of running MQ on a pair of Windows 2000 servers in a live/fail-over configuration. The idea is to put all of the MQ data files onto a shared disk using EMC-SRDF which will be available to whichever machine is currently running in production. Note that we cannot use MSCS for this - only a shared disk. Has anyone done this? Potential problems that we can see include the need to replicate the registry entries as well as the fact that the local mqm group on each machine will have a different sid (if that's the right terminology for groups) which might cause problems with regard to the MQ file permissions. Any experiences would be very helpful. Cheers, Paul Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Collecting Events on two Queues
Paul, I can't make a code change as these are third party tools. The only thing that I am allowed to do is on infrastructure level. Regards, Krishan -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul Clarke Sent: Thursday, July 22, 2004 11:28 AM To: [EMAIL PROTECTED] Subject: Re: Collecting Events on two Queues You could daisy chain the event handlers. ie. have that part of the processing of the event message is to put a copy of it to another queue. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley "Agarwal, Krishan [IT]" [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject N.AC.AT> Collecting Events on two Queues 22/07/2004 15:55 Please respond to MQSeries List Hi, I have a sitiutaion where I want to collect Events for two third party tools on two different queues. I have deleted the system event queues and defined them as alias queues pointing to Q1. But I want same events to be collected on Q2 also. Is there anyway to do this? Regards, Krishan Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Collecting Events on two Queues
You could daisy chain the event handlers. ie. have that part of the processing of the event message is to put a copy of it to another queue. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley "Agarwal, Krishan [IT]" [EMAIL PROTECTED] Sent by: MQSeries cc List <[EMAIL PROTECTED] Subject N.AC.AT> Collecting Events on two Queues 22/07/2004 15:55 Please respond to MQSeries List Hi, I have a sitiutaion where I want to collect Events for two third party tools on two different queues. I have deleted the system event queues and defined them as alias queues pointing to Q1. But I want same events to be collected on Q2 also. Is there anyway to do this? Regards, Krishan Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: MQ HFS information
Title: Message Mike, the program directory gives you about as much as there is I think - what information are you actually after ? thanks, Pete -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Mike DavidsonSent: 22 July 2004 16:05To: [EMAIL PROTECTED]Subject: MQ HFS information(We're running MQ v5.3 on z/OS 1.4) I don't expect alot of responses on this one b/c nobody seems to know anything about this stuff, but here it goes: I'm looking for any information/documentation I can find on the data, directories, and files contained within the MQ HFS structure under USS. Thanks in advance.Mike DavidsonTSYS MQ Tech SupportIBM Certified System Administrator - WebSphere MQ V5.3IBM Certified Solution Designer - WebSphere MQ V5.3[EMAIL PROTECTED] The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you Notice to recipient:The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.If this email originates from the U.K. please note that Bank of America, N.A., London Branch, Banc of America Securities Limited and Banc of America Futures Incorporated are regulated by the Financial Services Authority.
Collecting Events on two Queues
Hi, I have a sitiutaion where I want to collect Events for two third party tools on two different queues. I have deleted the system event queues and defined them as alias queues pointing to Q1. But I want same events to be collected on Q2 also. Is there anyway to do this? Regards, Krishan Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Brian E Wilson/Albany/IBM is out of the office.
I will be out of the office starting 07/22/2004 and will not return until 07/26/2004. I will be out of the office visiting a customer site on 7/22 and will be in a full day training session on 7/23. I will not have access to e-mail during this period. I will respond when I return. If the matter is urgent, call and leave a message at 518-487-6221. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
MQ HFS information
(We're running MQ v5.3 on z/OS 1.4) I don't expect alot of responses on this one b/c nobody seems to know anything about this stuff, but here it goes: I'm looking for any information/documentation I can find on the data, directories, and files contained within the MQ HFS structure under USS. Thanks in advance. Mike Davidson TSYS MQ Tech Support IBM Certified System Administrator - WebSphere MQ V5.3 IBM Certified Solution Designer - WebSphere MQ V5.3 [EMAIL PROTECTED] The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you
Re: Moving Queue Manager to New Server
I am not duplicating the Queue Manger, rather we moving to a new machine. Once New machine is imaged, I will turn off the other machine and configure the same Queue Manager on the New machine with the information like Server Name(CONNAME) and reset the Channel Sequence Number. Then run the security file(was created using "amqoamd") back in with the updated security information. This should get the Queue Manager running in a Cluster under the new location. Bill; I did find the Channel information, once I ran the "saveqmgr" but cluster definition is not there. I don't think there is anything else. Let me know if I am missing anything. Thanks, (Embedded image moved to file: pic02306.gif) - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. <>
Re: Moving Queue Manager to New Server
I never considered he was duplicating the queue manager on the same network as the existing one. I am in the middle of a similar project, but in a distributed queuing environment, not a clustered one. It's about upgrading AIX to 5.2 and to a small degree the servers are a bit faster. So I don't have to worry about queue managers with the same name on the same system. When I have finished, we migrate our customers and its done. Knowing more about the project would shed some light on the issue. Bill "Wyatt, T.rob" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] MERICA.COM> cc: Sent by: MQSeries Subject: Re: Moving Queue Manager to New Server List <[EMAIL PROTECTED] C.AT> 07/21/2004 01:35 PM Please respond to MQSeries List Bill, When he does this and creates two QMgrs with the same name in the cluster, he will have to issue a RESET QMGR command to clear the temporary one (or at least the old one) from the cluster. Does the command force you to use a QMID when it finds two QMgrs with the same name, or does it just delete them both? -- T.Rob -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Bill Anderson Sent: Wednesday, July 21, 2004 11:00 AM To: [EMAIL PROTECTED] Subject: Re: Moving Queue Manager to New Server I have never run saveqmgr on a cluster qmgr, but the DEFINE CHANNEL statements will be in the script for sure (and I assume the cluster definitions to). And the resulting flat file saveqmgr produces is editable for sure. I would suggest doing a dry run. Run the saveqmgr utility on the existing qmgr, and give editing a try. If you create a queue manager that is "broke" you can always delete it. "AkBar E. Dar" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] COM> cc: Sent by: MQSeriesSubject: Moving Queue Manager to New Server List <[EMAIL PROTECTED] N.AC.AT> 07/21/2004 10:24 AM Please respond to MQSeries List Hi: We are moving One of our Queue Manager in the Cluster to a New Machine. I have downloaded MS03 SupportPac(saveqmgr) to copy the Queue definitions and "amqoamd" to copy over the Security information. I am wondering that Is there way of creating the Channel and Cluster information to a Script file, editing that script file with the New server information then implementing it to the New Queue Manger? This would make the process less manual. Thanks, (Embedded image moved to file: pic19264.gif) - This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the UI Information Security Manager at 203-499-3689 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail is strictly prohibited. (See attached file: pic19264.gif) Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: downloading MO71 support pac....
Dan, Is it possible you're using the old webpage. The SupportPacs have been re-arranged recently. I've just tried it from http://www-1.ibm.com/support/docview.wss?rs=203&uid=swg24000142&loc=en_US&cs=utf-8&lang=en and it seems to work fine for me. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley "Capodicci, Dan (GE Commercial Finance)" To <[EMAIL PROTECTED] [EMAIL PROTECTED] .COM> cc Sent by: MQSeries List Subject <[EMAIL PROTECTED] downloading MO71 support pac N.AC.AT> 20/07/2004 15:00 Please respond to MQSeries List Hi After having read so many positive things recently about the MO71 support pac, I decided to download it and take a look. But of course, it is never that easy :) As I am trying to download it by clicking on the link, I get the license acceptance window which I respond to "accept", then I get a "Not Authorized" page ?!?!?!?!?!??!?!? I have only done this about a million times over the years (although it has been a while since the last) and never had this happen. Has something changed that I missed?!? Any clues about what I can do to download this support pac?!?!? Thanks Dan Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: emque5
Yup, same guy. And the bounce message I got for him said his address at IBM was no longer valid so I'm under the impression he left too! Don't see any emque5 messages so far today...hmmm...maybe Christian heard our pleas. -- T.Rob -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Robert Broderick Sent: Wednesday, July 21, 2004 6:21 PM To: [EMAIL PROTECTED] Subject: Re: emque5 Didn't Jeff Hooper coordinate the Support Pacs updtes and notify of when it happened. I was also under the impression he had left. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
