Manual Chapter : Out of Order Message Solutions

Applies To:

Show Versions Show Versions


  • 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.3, 13.1.1, 13.1.0
Manual Chapter

Out of Order Message Solutions

  • Store the request-sequence-number as an attribute in the request message that will be returned by the server as part of the response message.
  • Maintain a table mapping an attribute in the request/response to the request-sequence-number.
  • Implement an independent response routing system.
If the pending request table is not usable for the use case, the script author will need to disable automatic response routing by setting the 'no-response' attribute of the message via the "GENERICMESSAGE::message no-response true" command. To disable the table for all messages the no-response attribute in the protocol profile should be set to 'yes'.
Response messages may be routed by setting the nexthop or route attribute of the message.