What am I doing wrong? It finds the flow name in the first command, but I cannot use the flow name in the second command...
C:\IBM\MQSI\184.108.40.206\bin>mqsireportflowstats MB8BROKER -e default -j -a
BIP8187I: Statistics Archive collection for flow Simple_Monitoring/Simple_Monitoring_MF in execution group default is...
BIP8071I: Successful command completion.
C:\IBM\MQSI\220.127.116.11\bin>mqsireportflowstats MB8BROKER -e default -f Simple_Monitoring/Simple_Monitoring_MF -a
BIP8045E: The message flow is not available.
The message flow could not be found; it may have been deleted by the Message Broker Toolkit or a CMP application.
Use the Message Broker Toolkit or a CMP application to see if the message flow exists.
SystemAdmin 110000D4XK4179 Posts
Re: slashes in flow name?2012-10-15T04:55:19ZThis is the accepted answer. This is the accepted answer.I figured out that the slashes in the flow name has something to do with message flows being defined in an application as opposed to being defined as an independent resource. It might be something new in V8. Not sure.
There seem to be some big differences in capability between these two ways of building flows. It seems like I can do stuff in one that I can't do in the other and vice versa.
I can't deploy a flow that's part of application separate from that application. But deploying them together is what's putting the slash in the flow name. And I can't enable monitoring events if there's a slash in the flow name. But if I make the flow into an independent resource I lose other capabilities.
fjb_saper 110000H916125 Posts
Re: slashes in flow name?2012-10-15T10:01:42ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
Have you tried encasing the flow name in quotes when issuing the command?