Specifying the destination threads when resending messages

The uniform destinations for all resent messages can be specified on the Network Monitor and SMAT resend dialog boxes. For the reply type, multiple destinations are not supported.

For other editable metadata, they can be the same as the destinations. Destinations in the metadata file are overridden by dest from the command line.

Note: When specifying the destination thread for the resend, inter-site threads are not supported.

On the command line, resend takes dest_for_ib as the option between location and type:

resend ib_pre_tps | ib_post_tps | ob_pre_tps | ob_post_tps [dest_for_ib] 
data|reply priority filename len10|nl|eof 
[metafilename] 

Examples

Examples include:

  • hcicmd> conn_6 resend ib_pre_tps {conn_1 conn_3} data 5120 d:\\-A.txt nl

    This places two messages from file d:\-A.txt into the ib_pre_tps data queue.

  • hcicmd> conn_6 resend ib_pre_tps {conn_1 conn_3} datc 5120 d:\\-A.txt nl

    Response: Type must be data or reply

    resend ib_pre_tps|ib_post_tps|ob_pre_tps|ob_post_tps [dest_for_ib] data|reply pri
    filename len10|nl|eof [metafilename]
  • hcicmd> conn_6 resend ib_pre_tps {conn_1 conn_3} datc 5120 d:\\-A.txt nlx

    Response: Incorrect options: Style len10|nl|eof or Type data|reply

    resend ib_pre_tps|ib_post_tps|ob_pre_tps|ob_post_tps [dest_for_ib] data|reply pri
    filename len10|nl|eof [metafilename]