Activate

---

General Action Statement

The Activate statement starts an independent subroutine. The calling logic then continues without waiting for the called subroutine to finish. Therefore, independent subroutines can run in parallel with the logic that called them. Independent subroutines are not Entity-dependent or Location-dependent and run without regard to what happens inside the logic that called them.

Use Activate to process logic containing Wait or Wait...Until statements when you do not want to use an Entity to process these statements. For example, an Activate statement in the initialization logic could call a subroutine that adjusts the arrival frequency for an Entity type depending on the time of day.

Syntax

Activate <subroutine>({parameter1>,<parameter2>...})

Example

Activate Sub1()

Parameters

<subroutine>

The subroutine name to run. This name must appear exactly as when the subroutine is being called normally. Any return value for this function is ignored.

<parameter>

The parameters that the subroutine normally takes.

Remarks

Independent subroutines called with Activate cannot use Entity-specific or Location-specific system functions. If the subroutine has a return value, that value is ignored. External subroutines cannot be called with Activate, although they may be called from within an activated subroutine.