Author |
Message
|
leetc |
Posted: Wed Mar 19, 2003 8:02 pm Post subject: Stop message flow from command line |
|
|
Newbie
Joined: 14 May 2002 Posts: 8
|
Hi,
Is there a way to stop a message flow from a command line without using the Control Center ?
Understand that the message communication between Control Centre and Configuration Manager for the above purpose (stop message flow) is via XML message.
Do you have the exact XML message format for stopping a message format, so that we can PUT directly this message to the ConfigMgr queue ? Please give details of the message tree, understand it uses different MQMD.Format field as well.
Thanks.
-Thiam Cheng |
|
Back to top |
|
 |
kirani |
Posted: Wed Mar 19, 2003 9:28 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
|
Back to top |
|
 |
leetc |
Posted: Thu Mar 20, 2003 12:14 am Post subject: |
|
|
Newbie
Joined: 14 May 2002 Posts: 8
|
Kiran, i tried with the following data input
----------------------------------------------------------------
<Broker uuid="b49bf0a8-f000-0000-0080-ab9e1f61a030" label="WMQIBRK" version="1">
<ExecutionGroup uuid="ece1f0a8-f000-0000-0080-ab9e1f61a030">
<Start>
<MessageFlow uuid="3df0a85c-f100-0000-0080-ab9e1f61a030"/>
</Start>
</ExecutionGroup>
</Broker>
---------------------------------------------------------------------
and i rceived the following failure message.
----------------------------------------------------------------
Received response: correlId=414d5120574d5149
Data: <Broker uuid="b49bf0a8-f000-0000-0080-ab9e1f61a030" label="WMQIBRK" versio
n="1"><OverallCompletionCode result="failure"><LogEntry catalog="WMQIv210" numbe
r="2051"><Insert type="string" text="WMQIBRK"/><Insert type="string" text="b49bf
0a8-f000-0000-0080-ab9e1f61a030"/></LogEntry><LogEntry catalog="WMQIv210" number
="2087"><Insert type="string" text="WMQIBRK"/><Insert type="string" text="b49bf0
a8-f000-0000-0080-ab9e1f61a030"/></LogEntry></OverallCompletionCode></Broker>
-----------------------------------------------------------------
Do you know what went wrong ?
MQMD.Format=MQSTRING
-Thiam Cheng |
|
Back to top |
|
 |
mverh |
Posted: Thu Mar 20, 2003 4:49 am Post subject: |
|
|
Voyager
Joined: 06 Mar 2002 Posts: 97
|
You can also disable a message flow by altering the flow input queue "get(disabled)"...messages will be written to the log indicating the flow can't get messages...to restart the flow alter the input queue back to "get(enabled)"...it's simple, always works and does not rely on unpublished messages that may change across WMQI releases... |
|
Back to top |
|
 |
leetc |
Posted: Fri Mar 21, 2003 1:41 am Post subject: |
|
|
Newbie
Joined: 14 May 2002 Posts: 8
|
Understand that disable the queue from getting will stop the message flow. But, it will occupied the System Log with the GET inhibit error message.
So, which leaves only the Control message options as stated by Kiran.
-Thiam Cheng |
|
Back to top |
|
 |
leongor |
Posted: Fri Mar 21, 2003 4:01 am Post subject: |
|
|
 Master
Joined: 13 May 2002 Posts: 264 Location: Israel
|
Thiam,
It only gives you one inhibite message in event log.
The other way I wouldn't recommend to use, because it's not
documented option and can be changed in the next versions. _________________ Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
Back to top |
|
 |
vmcgloin |
Posted: Fri Mar 21, 2003 4:56 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002 Posts: 560 Location: Scotland
|
Thiam,
Going back to your failure response... I have a note next to BIP2051 in an old copy of the Messages manual that says 'if you get BIP2051 without insert &3 it could be that there are extra spaces in the deploy message causing problems'.
If you which to retry the method suggested by Kiran remove any extra whitespace including carriage returns from the input message you use.
Cheers,
Vicky |
|
Back to top |
|
 |
|