The WebSphere MQ display route application, dspmqrte, provides many parameters that determine characteristics of the trace-route message itself, and how the trace-route message should be treated as it is routed through a queue manager network. This section gives an overview of the parameters available with the WebSphere MQ display route application that are related to the generation, configuration, and use of trace-route messages.
The queue manager that the WebSphere MQ display route application connects to is specified using the following parameters:
If you do not specify this parameter, the WebSphere MQ display route application does not connect as a client application.
If you do not specify this parameter, the default queue manager is used.
The target destination of a trace-route message is specified using the following parameters:
If you do not specify this parameter, the queue manager to which the WebSphere MQ display route application is connected is used as the target queue manager.
If you do not specify this parameter, the target queue is bound to a specific destination.
One use of trace-route messaging is to help determine the last known location of a message that did not reach its intended destination. The WebSphere MQ display route application provides parameters that can help configure a trace-route message to mimic the original message. For information on the importance of mimicking the original message, see Mimicking a message. When mimicking a message, you can use the following parameters:
yes | The generated trace-route message is persistent. (MQPER_PERSISTENT). | |
no | The generated trace-route message is not persistent. (MQPER_NOT_PERSISTENT). | |
q | The generated trace-route message inherits its persistence value from the queue specified by -q TargetQName. (MQPER_PERSISTENCE_AS_Q_DEF). |
If Persistence is specified as yes, you must specify the parameter -rq ReplyToQ. The reply-to queue must not resolve to a temporary dynamic queue.
If you do not specify this parameter, the generated trace-route message is not persistent.
If you do not specify this parameter, the priority value is taken from the queue specified by -q TargetQName.
If you do not specify this parameter, the expiry time is specified as 60 seconds.
none | Specifies no report options are set. | |
ReportOption | Specifies report options for the
trace-route message. Multiple report options can be specified using a comma
as a separator. Possible values for ReportOption are:
|
If neither -ro ReportOption nor -ro none are specified, then the MQRO_ACTIVITY and MQRO_DISCARD_MSG report options are specified.
The WebSphere MQ display route application does not allow you to add user data to the trace-route message. If you require user data to be added to the trace-route message then manually generate a trace-route message, see Configuring and generating a trace-route message.
The route a trace-route message has taken is determined using recorded activity information. Recorded activity information can be returned using the following:
For more information, see How recorded activity information is acquired.
When using dspmqrte, the method used to return recorded activity information is determined using the following parameters:
If you do not specify this parameter, activity information is not accumulated within the trace-route message.
If you do not specify this parameter, activity information is not accumulated within the trace-route message.
If you do not specify this parameter, the trace-route message is not put to the target queue.
The trace-route message can then be retrieved from the target queue, and the recorded activity information acquired.
You can combine these methods as required.
Additionally, the detail level of the recorded activity information can be specified using the following parameter:
low | Activities performed by user-defined application are recorded only. | |
medium | Activities specified in low are recorded. Additionally, activities performed by MCAs are recorded. | |
high | Activities specified in low, and medium are recorded. MCAs do not expose any further activity information at this level of detail. This option is available to user-defined applications that are to expose further activity information only. For example, if a user-defined application determines the route a message takes by considering certain message characteristics, the routing logic could be included with this level of detail. |
If you do not specify this parameter, medium level activities are recorded.
By default the WebSphere MQ display route application uses a temporary dynamic queue to store the returned messages. When the WebSphere MQ display route application ends, the temporary dynamic queue is closed, and any messages are purged. If the returned messages are required beyond the current execution of the WebSphere MQ display route application ends, then a permanent queue must be specified using the following parameters:
If you do not specify this parameter then a dynamic reply-to queue is created using the system default model queue, SYSTEM.DEFAULT.MODEL.QUEUE.
If you do not specify this parameter, the queue manager to which the WebSphere MQ display route application is connected is used as the reply-to queue manager.
There are various parameters that are used to control how a trace-route message is handled as it is routed through a queue manager network. The following parameters can restrict where the trace-route message can be routed in the queue manager network:
yes | On arrival, the trace-route message is put to the target queue, even if the queue manager does not support trace-route messaging. | |
no | On arrival, the trace-route message is not put to the target queue. |
If you do not specify this parameter, the trace-route message is not put to the target queue.
If you do not specify this parameter, the trace-route message will only be forwarded to a queue manager that will honor the Deliver parameter.
The following parameters can prevent a trace-route message from remaining in a queue manager network indefinitely:
If you do not specify this parameter, an unlimited number of activities can be performed on behalf of the trace-route message.
If you do not specify this parameter, the expiry time is specified as 60 seconds.
yes | The report option MQRO_PASS_DISCARD_AND_EXPIRY
is specified in the message descriptor of the trace-route message.
If a trace-route reply message, or activity reports, are generated for the trace-route message, the MQRO_DISCARD report option (if specified), and the remaining expiry time are passed on. This is the default value. |
|
no | The report option MQRO_PASS_DISCARD_AND_EXPIRY
is not specified.
If a trace-route reply message is generated for the trace-route message, the discard option and expiry time from the trace-route message are not passed on. |
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqzax0588 |