How the trace-route message is handled

Use this page 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:

-d Deliver

Specifies whether the trace-route message is to be delivered to the target queue on arrival. Possible values for Deliver are:

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 we do not specify this parameter, the trace-route message is not put to the target queue.

-f Forward

Specifies the type of queue manager that the trace-route message can be forwarded to. For details of the algorithm that queue managers use to determine whether to forward a message to a remote queue manager, refer to The TraceRoute PCF group. The possible values for Forward are:

all

The trace-route message is forwarded to any queue manager. Warning: If forwarded to an IBM MQ queue manager earlier than Version 6.0, the trace-route message will not be recognized and can be delivered to a local queue despite the value of the -d Deliver parameter.

supported

The trace-route message is only forwarded to a queue manager that will honor the Deliver parameter from the TraceRoute PCF group

If we 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:

-s Activities

Specifies the maximum number of recorded activities that can be performed on behalf of the trace-route message before it is discarded. This prevents the trace-route message from being forwarded indefinitely if caught in an infinite loop. The value of Activities is either greater than or equal to 1, or MQROUTE_UNLIMITED_ACTIVITIES. MQROUTE_UNLIMITED_ACTIVITIES specifies that an unlimited number of activities can be performed on behalf of the trace-route message.

If we do not specify this parameter, an unlimited number of activities can be performed on behalf of the trace-route message.

-xs Expiry

Specifies the expiry time for the trace-route message, in seconds.

If we do not specify this parameter, the expiry time is specified as 60 seconds.

-xp PassExpiry

Specifies whether the expiry time from the trace-route message is passed on to a trace-route reply message. Possible values for PassExpiry are:

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.

If we do not specify this parameter, MQRO_PASS_DISCARD_AND_EXPIRY is not specified.

-ro discard

Specifies the MQRO_DISCARD_MSG report option. This can prevent the trace-route message remaining in the queue manager network indefinitely.

Parent topic: Parameters for trace-route messages