New Execution - Sequence Call Advanced Settings Window
- Updated2025-07-21
- 4 minute(s) read
New Execution - Sequence Call Advanced Settings Window
New Execution
The Sequence Call Advanced Settings window contains the following options when you select Use New Execution in the Execution Options control on the Module tab:
- Initially Suspended —When you enable this option, TestStand creates the new execution in a suspended state. Call the Execution.Resume method in the TestStand API to start the execution.
-
Initially Hidden and Disable Tracing
—When you enable this option, the window for the new execution is initially hidden and tracing is initially disabled.
Note If you enable the Initially Hidden and Disable Tracing option, TestStand ignores the Break on Entry option in this window when calling new executions.
- Restartable —When you enable this option, the execution can be restarted after it completes.
- Close Window when Done —When you enable this option, TestStand closes the window for the execution when the execution completes.
-
Use Single-Threaded Apartment
—Specifies whether the concurrency model of the thread is initialized as single-threaded apartment (STA) or multi-threaded apartment (MTA). By default, TestStand initializes new executions and threads to use the multi-threaded apartment model. A thread must use the single-threaded apartment model if the thread creates or launches a dialog box that contains ActiveX controls.
If you use this option to launch a sequence that contains a step that displays an ActiveX control, you might need to set the Load option in the Run Options panel of the Step Settings pane to Load Dynamically to ensure that TestStand loads the module the step in the thread initialized as STA calls.
-
Wait for Execution to Complete
—Specifies whether to wait for the execution to complete. The following options are available in the ring control:
- Before executing next step —Calling sequence waits for the execution to complete before executing another step. TestStand propagates status and error information from the asynchronous execution call to the waiting sequence, and adds results for the asynchronous execution call to the results of the step.
- Do not wait —Calling sequence does not wait for the execution to complete. Use this option and insert a Wait step in the sequence when you want to obtain the results and control whether TestStand copies status and error information from an asynchronous execution call to the Wait step.
- At end of current sequence —Calling sequence waits for the execution to complete before the calling sequence returns. TestStand propagates status and error information from the asynchronous execution call to the waiting sequence. However, TestStand does not add results for the asynchronous execution call to the results of the waiting sequence. Use the Do not wait option and use a Wait step if you want to obtain the results and control whether TestStand copies status and error information from the asynchronous execution call to the Wait step.
-
Process Model Option
—Specifies which process model the new execution uses. The following options are available in the ring control:
- Do not use a process model —The new execution does not run under a process model.
- Use process model of the specified client file —The execution runs under the process model the sequence file you call specifies as the model of the sequence file. If the file you call does not specify a model, the execution runs under the default station model. When you select this option, you can use the Sequence Call Module tab to designate which entry point to call in the process model. Typically, the Process Model entry point calls MainSequence in the client sequence file you specify.
- Use a specific process model —When you select this option, you can use the controls on the Sequence Call Module tab to specify the process model under which the new execution runs. When you select this option, you can use the Sequence Call Module tab to designate which entry point to call in the process model. Typically, the Process Model entry point calls MainSequence in the client sequence file you specify.
- Additional Execution Type Mask Settings (optional) —Passes a numeric value that specifies the execution mask settings for the new execution. Refer to ExecutionTypeMask for a list of available type mask settings. The settings you specify in this control are combined with any execution mask settings other options in the dialog box specify.
- Store an Object Reference to the New Execution in (optional) —Stores a reference to the new Execution object in the ActiveX reference variable you specify. You can use this reference in subsequent calls to the TestStand API. You can also use this reference in a Wait step to wait for the execution to complete.
-
Break on Entry
—When you enable this option, TestStand suspends the execution before executing the first step.
Note If you enable the Initially Hidden and Disable Tracing option in this window, TestStand ignores the Break on Entry option when calling new executions.
-
CPU Affinity for Initial Thread of Execution
—The CPUs on which the initial thread of the execution executes. The following options are available in the ring control:
- Use Station Option for CPU Affinity —TestStand uses the Default CPU Affinity For Threads station option on the Preferences tab of the Station Options dialog box as the CPU affinity of the initial thread.
- Use CPU Affinity of Caller —TestStand uses the CPU affinity of the calling sequence as the CPU affinity of the initial thread.
- Use All CPUs —TestStand uses all CPUs available to the process as the CPU affinity of the initial thread.
- Use Custom CPU affinity —TestStand determines the CPU affinity of the initial thread using an expression that evaluates to a numeric value, where each bit represents a CPU. The lowest order bit represents the first CPU. For example, a value of 12 ( 1100 ) represents CPUs 3 and 4 on a quad-core computer. A value of -1 represents all CPUs available to the process.