Reporting monitoring settings

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

About this task

The following examples show how to report monitoring options for an integration node that is called INODE1, integration server default, and a message flow PurchaseOrderFlow that is part of an application called PurchaseOrderApp.

Reporting configured events for a message flow

Procedure

Run the following command on Linux®, UNIX, or Windows:

mqsireportflowmonitoring INODE1 -e default -f PurchaseOrderFlow -k PurchaseOrderApp -n

Issue the following command on z/OS®: z/OS platform

F MI10BRK,rm INODE1,e='default',f='PurchaseOrderFlow',k='PurchaseOrderApp',n='yes''

Note: If the message flow is part of a library that is referenced by the application, you must also include the library name by using the y argument.

Reporting all possible events for a message flow

Procedure

Run the following command on Linux, UNIX, or Windows:

mqsireportflowmonitoring INODE1 -e default -f PurchaseOrderFlow -k PurchaseOrderApp -a

Issue the following command on z/OS: z/OS platform

F MI10BRK,rm e='default',f='PurchaseOrderFlow',k='PurchaseOrderApp',a='yes'

Note: If the message flow is part of a library that is referenced by the application, you must also include the library name by using the y argument.

Reporting specified events for a message flow

Procedure

Run the following command on Linux, UNIX, or Windows:

mqsireportflowmonitoring INODE1 -e default -f PurchaseOrderFlow -k PurchaseOrderApp 
     -s "MQInput1.transaction.Start,MQOutput1.terminal.catch"

Issue the following command onz/OS: z/OS platform

F MI10BRK,rm e='default',f='PurchaseOrderFlow',k='PurchaseOrderApp',
     s="MQInput1.transaction.Start,MQOutput1.terminal.catch"

Note: If the message flow is part of a library that is referenced by the application, you must also include the library name by using the y argument.

Tip: When you specify values for the -s parameter, use the Event source address property of the event, not the Event name property.

Exporting a message flow monitoring profile

About this task

Use the following command to export a profile to file myMonProf.xml.

Procedure

Run the following command on Linux, UNIX, or Windows:

mqsireportflowmonitoring INODE1 -e default -f PurchaseOrderFlow -k PurchaseOrderApp -x -p myMonProf.xml

Issue the following command onz/OS: z/OS platform

F MI10BRK,rm e='default',f='PurchaseOrderFlow',k='PurchaseOrderApp',x='yes',p='myMonProf.xml'

Note: If the message flow is part of a library that is referenced by the application, you must also include the library name by using the y argument.

If message flow monitoring is configured by using monitoring properties, rather than a monitoring profile configurable service, the command creates and returns the equivalent monitoring profile XML file.

Tip: This method is an alternative to using an XML editor to create a monitoring profile XML file.