SA generated MRT needs to be consistent with auto-generated trap behaviour

Under OTHERMSG SA should use the EXIT statement by default so trap behaviour is the same as a default UPON MSGID(...).
Example of an UPON MSGID...
UPON( MSGID = 'IEFC166D' )
REVISE('Y' AUTOMATE)
When there is a hit on this message, there is no additional search performed in the MRT.

When messages are defined to SA to ignore leading characters, they are placed in a SELECT/WHEN/END group under 'UPON (OTHERMSG)'.

Example showing 2 traps:

SELECT
* No outstanding alerts
WHEN (WORD 1 RIGHT 8 = 'HASP9121')
REVISE('Y' AUTOMATE)
* Main task wait detected
WHEN (WORD 1 RIGHT 8 = 'HASP9201')
REVISE('Y' AUTOMATE)
OTHERWISE
END

If this was the ONLY SELECT/WHEN/END group under OTHERMSG, the search would stop at finding one of these messages.

HOWEVER....
If one adds customized MRT entries for messages where you ignore the leading prefix, it requires another SELECT/WHEN/END, or if one uses the option to add more SELECT/WHEN/END groups to the end of the MRT, then the search continues through every SELECT/WHEN/END under OTHERMSG until another match is found or the end of the table is reached. While occasionally this may be desirable and can be customized by the experienced user, the DEFAULT built by the SA dialogs should include the EXIT statement to stop unnecessary searches