Add a sub-event to a BTS composite event.
Description
ADD SUBEVENT adds a sub-event to a
BTS composite event. The sub-event:
- Must be an atomic (not a composite) event
- Cannot be a system event
- Must not currently be part of a composite event
- Cannot, if the predicate of the composite event uses the AND Boolean operator, be an input event.
Adding a sub-event causes the composite's predicate to be re-evaluated.
Options
- EVENT(data-value)
- specifies the name (1–16 characters) of the composite event. This must previously have been defined to the current activity, using the DEFINE COMPOSITE EVENT command.
- SUBEVENT(data-value)
- specifies
the name (1–16 characters) of the atomic event to be added to the composite
event as a sub-event. The sub-event must previously have been defined to the
current activity, using one of the following commands:
- DEFINE ACTIVITY
- DEFINE INPUT EVENT
- DEFINE TIMER
It:- Must not currently be part of a composite event
- Cannot, if the predicate of the composite event uses the AND Boolean operator, be an input event.
Conditions
- 111 EVENTERR
- RESP2
values:
- 4
- The event specified on the EVENT option is not recognized by BTS.
- 5
- The sub-event specified on the SUBEVENT option is not recognized by . BTS.
- 16 INVREQ
- RESP2
values:
- 1
- The command was issued outside the scope of an activity.
- 2
- The event specified on the EVENT option is invalid—it is not a composite event.
- 3
- The sub-event specified on the SUBEVENT option is invalid. Specifying
any of the following as a sub-event produces this error:
- A composite event
- A system event
- A sub-event of another composite event
- A sub-event of this composite event—that is, an atomic event that has already been added to this composite event
- An input event, if the composite uses the AND Boolean operator.
