IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Reporting monitoring settings

Use the mqsireportflowmonitoring command to report monitoring settings for a flow.

The following examples show how to report monitoring options for a broker called BROKER1, integration server default, and message flow PurchaseOrder.

Report configured events for a message flow

Issue the following command on Linux, Unix, or Windows:

Linux platformUNIX platformWindows platform
mqsireportflowmonitoring BROKER1 –e default –f PurchaseOrder –n

Issue the following command on z/OS®: z/OS platform
F MI10BRK,rm BROKER1,e='default',f='PurchaseOrder,n='yes''

Report all possible events for a message flow

Issue the following command on Linux, Unix, or Windows:

Linux platformUNIX platformWindows platform
mqsireportflowmonitoring BROKER1 –e default –f PurchaseOrder –a

Issue the following command on z/OS: z/OS platform
F MI10BRK,rm e='default',f='PurchaseOrder,a='yes'

Report specified events for a message flow

Issue the following command on Linux, Unix, or Windows:

Linux platformUNIX platformWindows platform
mqsireportflowmonitoring BROKER1 –e default –f PurchaseOrder 
     -s "MQInput1.transaction.Start,MQOutput1.terminal.catch"

Issue the following command on z/OS: z/OS platform
F MI10BRK,rm e='default',f='PurchaseOrder',
     s="MQInput1.transaction.Start,MQOutput1.terminal.catch"
Tip: When specifying values for the -s parameter, use the Event source address property of the event, not the Event name property.

Export a message flow's monitoring profile

Use the following command to export a profile to file myMonProf.xml
Issue the following command on Linux, Unix, or Windows:

Linux platformUNIX platformWindows platform
mqsireportflowmonitoring BROKER1 -e default -f PurchaseOrder -x -p myMonProf.xml

Issue the following command on z/OS: z/OS platform
F MI10BRK,rm e='default',f='PurchaseOrder',x='yes',p='myMonProf.xml'
If monitoring for a message flow is configured using monitoring properties, rather than a monitoring profile configurable service, the command creates and returns the equivalent monitoring profile XML file.
Tip: This is an alternative to using an XML editor to create a monitoring profile XML file.
Related tasks:
Business-level monitoring
Configuring monitoring event sources using monitoring properties
Configuring monitoring event sources using a monitoring profile
Related reference:
mqsichangeflowmonitoring command
mqsichangeproperties command
mqsireportflowmonitoring command
ac60384_.htm | Last updated Friday, 21 July 2017