Differences

This shows you the differences between two versions of the page.

--- transsecs_message_matching [2020/05/12 15:45]
wikiadmin
+++ transsecs_message_matching [2020/05/12 17:06] (current)
wikiadmin
@@ Line 1: / Line 1: @@
-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.
+If no match is found, if a message of the given stream exists in TransSECS then an S9F5 message will be generated.  If the stream is unknown, an S9F3 message will be generated.
 Whenever TransSECS receives a message is will first check to see if any of the messages match a known GEM standard message. This matching is described in the links below for tools and hosts.
 [[GEM Host messages]]
 [[GEM Tool messages]]
@@ Line 54: / Line 59: @@
 If selected, TransSECS will not match the list unless the incoming list exactly matches the list defined in the TransSECS message.
+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**
+For a tool interface, there is the option for special handling of S2F41 and S2F49 - remote or host command messages.
+{{:pasted:20200512-163941.png}}
+To enable this special handling, check the "Remote Command" checkbox. The "Command" field should be marked as a key in almost all cases.
+When enabled, the message will be matched regardless of the order of the parameters.  In the example, if the PPID CPName is first and the LOTID second, the message will match.  The published data will match the CPName and not the location in the message.  All the CPNames must exist for the message to be matched.  There must not be unknown CPNames.
+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**