Activating monitoring

Use the mqsichangeflowmonitoring command to activate monitoring after you configure monitoring event sources.

Before you begin

Configure monitoring event sources by using either monitoring properties or a monitoring profile:

About this task

The use of a monitoring profile configurable service overrides the monitoring properties of a message flow.

If monitoring is activated for a message flow, and monitoring properties or a monitoring profile configurable service are not configured for the flow, transaction events are emitted from each input node of the message flow. The events contain the bit stream of the input message.

To activate and deactivate monitoring, use the examples in the following sections:

Activating monitoring

About this task

To activate monitoring, use the -c active parameter. You can activate monitoring for all message flows in all integration servers, or specify the integration servers and message flows for which monitoring is to be activated.

Procedure

  • To activate monitoring for all message flows in all integration servers on Linux®, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring myBroker -c active -g -j
    To activate monitoring for all message flows in all integration servers on z/OS®: z/OS platform
    F MI10BRK,cm c=active,g=yes,j=yes
  • To activate monitoring for all message flows in the default integration server on Linux, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring myBroker -c active -e default -j
    To activate monitoring for all message flows in the default integration server on z/OS: z/OS platform
    F MI10BRK,cm c=active,g=default,j=yes
  • To activate monitoring for the myFlow message flow in the default integration server on Linux, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring myBroker -c active -e default -f myFlow
    To activate monitoring for the myFlow message flow in the default integration server on z/OS: z/OS platform
    F MI10BRK,cm c=active,g=default,f=myFlow
  • To activate monitoring for all message flows in application application1 in integration server default on Linux, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring IBNODE -c active -e default -k application1 -j 
    To activate monitoring for all message flows in application application1 in integration server default on z/OS:z/OS platform
    F IBNODE,cm c=active,e=default,k=application1,j=yes 
  • To activate monitoring for message flow myflow1 in library library1, referenced by application application1, in integration server default, on Linux, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring IBNODE -c active -e default -y library1 -k application1 -f myflow1
    Activate monitoring for message flow myflow1 in library library1, referenced by application application1, in integration server default, on z/OS:z/OS platform
    F IBNODE,cm c=active,e=default,y=library1,k=application1,f=myflow1

Deactivating monitoring

About this task

To deactivate monitoring, use the -c inactive parameter. You can deactivate monitoring for all message flows in all integration servers, or specify the integration servers and message flows for which monitoring is to be activated.

Procedure

  • To deactivate monitoring for all message flows in all integration servers on Linux, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring myBroker -c inactive -g -j
    To deactivate monitoring for all message flows in all integration servers on z/OS: z/OS platform
    F MI10BRK,cm c=inactive,g=yes,j=yes
  • To deactivate monitoring for all message flows in the default integration server on Linux, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring myBroker -c inactive -e default -j
    To deactivate monitoring for all message flows in the default integration server on z/OS: z/OS platform
    F MI10BRK,cm c=inactive,g=default,j=yes
  • To deactivate monitoring for the myFlow message flow in the default integration server on Linux, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring myBroker -c inactive -e default -f myFlow
    To deactivate monitoring for the myFlow message flow in the default integration server on z/OS: z/OS platform
    F MI10BRK,cm c=inactive,g=default,f=myFlow
  • To deactivate monitoring for all message flows in application application1 in integration server default on Linux, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring IBNODE -c inactive -e default -k application1 -j 
    To activate monitoring for all message flows in application application1 in integration server default on z/OS:z/OS platform
    F IBNODE,cm c=inactive,e=default,k=application1,j=yes 
  • To deactivate monitoring for message flow myflow1 in library library1, referenced by application application1, in integration server default, on Linux, UNIX, and Windows:
    Linux platformWindows platformUNIX platform
    mqsichangeflowmonitoring IBNODE -c inactive -e default -y library1 -k application1 -f myflow1
    Activate monitoring for message flow myflow1 in library library1, referenced by application application1, in integration server default, on z/OS:z/OS platform
    F IBNODE,cm c=inactive,e=default,y=library1,k=application1,f=myflow1