Specifications

Last Statement
choice
{
event "StartA" Process Start { ExecutableName="SQRW" }
event "StartB" Process Start { ExecutableName="PSCRRUN }
}
choice
{
event "StopA" Process Stop { ExecutableName="SQRW" }
event "StopB" Process Stop { ExecutableName="PSCRRUN }
}
}
Last Statement
In some cases, you may have difficulty identifying the end of a transaction,
particularly if the transaction does not end with any windowing activity, but
instead with a flurry of network activity. Use the last statement to instruct
Application Response to identify the end of a transaction by looking for the last
in a series of similar events.
The last statement allows you to specify an iterative series of events (of
indeterminate number) for a transaction. A last statement starts with the last
keyword and is followed by any number of event specifications. You can only
use event specifications within a last statement. You cannot use nested choice,
sequence, or last statements within a last construct. Application Response
considers the last statement to be satisfied if it observes an uninterrupted
series of events (each of which matches an event specification in the list).
More specifically, the final matching event is considered to satisfy the last
construct.
Syntax
A last statement uses the following syntax:
last
{
event-specification
event-specification
.
.
.
}
168 BTStudio Administration Guide