f to see only the script traces. C. Enter source scriptl.wri in the Simulator. If the model (and the script!) is correct, you see > source script1.wri Execution of script1.wri: scenario in initial state Replay test1.scn OK scenario in initial state Replay cnx2.scn OK scenario in initial state Replay retry1 scn OK TEST PASSED The file test_resl.wri contains the same results, informing you of which scenario(s) failed. By just reading the last line, you are sure that all the scenarios passed. If you want to generate the MSC trace and store it into the file test5.msc after replaying a scenario, you can add the following command into the script: msc test5 You will learn in Chapter 5 how to check that your SDL model behavior complies with an MSC. This will be even more powerful to test automatically an SDL model: for example, we will be able to check the value of a parameter in a signal transmitted, which is not performed here. 4.3.7 Other Simulator features: watch, trace, filter etc. This section describes features of the Simulator not absolutely essential to validate an SDL model, but which can be very helpful and save a lot of time on an actual system validation. 45 The file extension .wri ensures opening the file with WordPad just by double-click, if you are running Microsoft Windows™ 96 Validation of Communications Systems with SDL 4.3.7.1 Aliases To shorten textual commands, you can create aliases, a kind of macros. Alias definitions are generally stored in the file geodesm.startup (see Section 4.3.7.2) to be executed automatically. Here are some examples of aliases you could write: alias h 'history' alias p 'print' - - Basic blocks (paths) never executed: alias bb0 cover bblocks all 0:0' Then, you have only to enter h instead of history, bb0 instead of cover bblocks all 0:0, and SO on. Also, aliases can have parameters; for example, to print the state of instance $2 of process DLC in block DLC$1: > alias p_dlc 'print dlc$1!dlc($2) !state' > p_dlc a 1 dlca!dlc (1) ! state = waitua 4.3.7.2 Automatic scripts execut