| Both sides previous revision
Previous revision
|
|
transsecs_message_matching [2020/05/12 16:48]
wikiadmin |
transsecs_message_matching [2020/05/12 17:06] (current)
wikiadmin |
| TransSECS Message Matching | **TransSECS Message Matching** |
| |
| TransSECS will attempt to match all incoming messages against known messages. As soon as a match is found, not further matching is performed and the data is published and any notifications associated with the message are executed. | TransSECS will attempt to match all incoming messages against known messages. As soon as a match is found, not further matching is performed and the data is published and any notifications associated with the message are executed. |
| Somewhat common is to rely on the order of the message matching in TransSECS to match a "default" message after all more-precise messages have been matched. Messages are ordered either by stream/function/alphabetical or alphabetically. In this case, create a message that starts with a Z_ and it will be moved to the last element of the matched list and so matched last. | Somewhat common is to rely on the order of the message matching in TransSECS to match a "default" message after all more-precise messages have been matched. Messages are ordered either by stream/function/alphabetical or alphabetically. In this case, create a message that starts with a Z_ and it will be moved to the last element of the matched list and so matched last. |
| |
| Remote Command Messages | **Remote Command Messages** |
| |
| For a tool interface, there is the option for special handling of S2F41 and S2F49 - remote or host command messages. | For a tool interface, there is the option for special handling of S2F41 and S2F49 - remote or host command messages. |
| If the "Send Err Msg" box is checked, if the "Key" field matches, or there is no "Key" field but the rest of the match fails, TransSECS will automatically return an S2F42 with an error description. If there is only one message with a given "Key" the "Send Err Msg" button should be checked on that message. If there are multiple messages with the same Key, the last message in the tree should have the "Send Err Msg" checked. It's also possible to add "Default" S2F41 messages that do not have a key to force particular errors. Make sure that they are the last S2F41 message and that the "Send Err Msg" box is checked. | If the "Send Err Msg" box is checked, if the "Key" field matches, or there is no "Key" field but the rest of the match fails, TransSECS will automatically return an S2F42 with an error description. If there is only one message with a given "Key" the "Send Err Msg" button should be checked on that message. If there are multiple messages with the same Key, the last message in the tree should have the "Send Err Msg" checked. It's also possible to add "Default" S2F41 messages that do not have a key to force particular errors. Make sure that they are the last S2F41 message and that the "Send Err Msg" box is checked. |
| |
| | **Advanced Message Matching** |