WebSphere Message Brokers
File: an28110_
Writer: Bill Oppenheimer

Reference topic

This build: July 31, 2007 21:34:09

mqsichangetrace command - z/OS

Syntax

z/OS console command

User trace

Service trace

Parameters

-u
(Required for user trace only if the component is a broker) .

Specifies that user trace options are to be modified. This option is only valid if you have issued this command against a broker, that is, not a Configuration Manager or User Name Server.

-e EgName
(Required for user trace; optional for service trace)

Identifies the execution group for which trace options are to be modified (for example, started or stopped). This option is valid only for a broker.

This name is case sensitive and you must include the names in single quotes if they contain mixed case characters.

-f MessageFlow

(Optional) Identifies the message flow for which trace options are to be modified. This option is only valid if you have specified an execution group (flag -e).

This name is case sensitive and you must include the names in single quotes if they contain mixed case characters.

-r

(Optional) This option requests that the trace log is reset: that is, all current records are discarded. Use this option when you start a new trace to ensure that all records in the log are unique to the new trace.

This option is only valid if you have specified an execution group (flag -e).

-l Level
(Optional) Set the level of the trace. This must be one of:
  • normal. This provides a basic level of trace information.
  • none. This switches tracing off.
  • debug. This provides a more comprehensive trace.

This is valid for all components and each component is created with a default value of none. If you do not specify this parameter, the current value is unchanged. Once you successfully change this value, it is persistent.

-m Mode
(Optional) Indicate the way trace information is to be buffered:
  • safe. This mode causes trace entries to be written to file when they are generated.
  • fast. This mode causes trace entries to be buffered, and only written to file in batches.
Each component starts with a default value of safe. If you do not specify this parameter, the current value is unchanged.
This parameter is valid only if the component you have specified is:
  • A broker. If you change this value, it affects tracing for the execution group (if you have specified one), or for the agent component (if you have not specified an execution group).
  • The User Name Server. If you change this value, it affects tracing for the entire component. This second option is valid only for service trace and, once you have successfully changed this value, it is persistent.
-c Size
(Optional) The size of the trace file in KB (kilobytes). If you do not specify this parameter, the current value is left unchanged. Each component starts with a default value of 4096 KB. Specify this option to reset the value. The maximum value you can specify depends on how you subsequently intend to read the log, using the mqsireadlog command:
  • If you use this command with the -f option set, the log file is read directly from the file system. In this case, the maximum value that you can specify is 2097151, which allows a trace file up to 2 GB (gigabyte) to be created.
  • If you use this command without setting the -f option, a WebSphere MQ message is sent to the broker to retrieve the log. In this case, do not allow the trace file to exceed 70 MB (megabytes). The maximum value that you can set is 70000.

However you intend to retrieve the trace file, you might want to keep its size small, either by using a low value for this parameter or by using the reset (-r) option on this command to clear the trace log. The benefit of adopting this approach is that the formatting process (mqsiformatlog) is much faster and requires less resource to carry out its task.

This parameter is valid only if the component you have specified is:
  • A broker. If you change this value, it affects tracing for the execution group (if you have specified one), or for the agent component (if you have not specified an execution group).
  • The User Name Server. If you change this value, it affects tracing for the entire component. This second option is valid only for service trace.

Additional parameters exclusive to service trace

Use these options only when directed to do so by your IBM Support Center or by a BIPxxxx message.

-t

(Required) Specifies that service trace options are to be modified.

-b

(Required) Specifies that service trace options for the agent subcomponent of the component specified are to be modified (for example, started or stopped). You can specify this flag only if -t is also specified.

Examples

To collect and process a user trace for the default execution group use the command:
F MQP1BRK,ct U=YES ,E='DEFAULT' ,L=NORMAL ,C=5000
and in the PDSE member BIPRELG, set the option for mqsireadlog to
U= E=DEFAULT
To collect and process a service trace for flow f1 in the default execution group use the command:
F MQP1BRK,ct U=YES ,E='DEFAULT' ,F='F1' ,M=FAST
and in the PDSE member BIPRELG, set the option for mqsireadlog to
T= ,E=DEFAULT ,F=F1
To collect and process a service trace for an agent use the command:
F MQP1BRK,ct T=YES ,B=YES ,M=FAST ,L=DEBUG
and in the PDSE member BIPRELG, set the option for mqsireadlog to
T= ,B=AGENT
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:34:09

an28110_ This topic's URL is: