## Storage Device Driver Reference

[prev][next][parent][TOC]

### @THREAD

       @Thread log_filename

This function starts the new thread of execution. Any resulting DDTT file logs will be written to log_filename. The DDTT shares access to log_ filename, and the same log_filename may be used for multiple @THREAD commands within the same test case. The DDTT also creates a separate OS/2 Presentation Manager window for every @THREAD token. Any operator messages and prompts generated in the @THREAD section are displayed in the corresponding window.

Each occurrence of the @THREAD token marks the start of a section in the test case script file which is to be executed sequentially under the control of a single OS/2 thread created by DDTT. DDTT parses the entire test case file looking for @THREAD tokens. When the entire test case file (including any @IMPORT commands) has been parsed, DDTT creates and starts an OS/2 thread for each @THREAD token located. All threads are initially created within the DDTT process with the following characteristics:

       Stack size:   4KB

Note:

Thread windows are created on top of each other. To access multiple windows simultaneously, drag the thread windows to separate places on the screen

All OS/2 threads are started at approximately the same time.

The DDTT must encounter an @THREAD command as the first command after resolving all @IMPORT commands in the test case file.

The DDTT test scripts can start no more than 50 threads.