 trace that the system answers with an L_RelelaseInd(0): it means that no more connections can be established. But if you look at the Command Window, you discover that process dispatch in block DLCa is stuck in state waitUA: this is a modeling bug. E. Exit from the Simulator. You will correct process dispatch to remain in state ready instead of going to state waitUA after transmitting L RelelaseInd: F. In Windows (or Unix), make a copy of the file dispatch.spr into dispatch_v2.spr G. In process dispatch, page part2, select the output of L_RelelaseInd under the ELSE branch of the decision and double-click on the state palette symbol; enter - in the newly created symbol, as shown in Figure 4.24. PROCESS dispatch(1, 1) part2(2) L EstabReq (DLCnum) (DLCnum) DLCnum not used, we create an instance of L Releaselnd (DLCnum, True) process DLC (DLCnum) DLCs(DLCnum) We store into the OFFSPRING table the PID of the new instance waitUA Figure 4.24 After the bug correction with the SDL Editor H. Save the process. I. Simulate again to check that the bug has disappeared: launch the Simulator, replay the command script cnx2.com as before, send an L_EstabReq to the model and execute its input: you see that process dispatch now stays in state ready. 4.2.6 Write a script for automatic validation In an actual project, to test a more complex SDL model, you would produce, for example, 40 simulation scripts. After a change in the SDL model, you must check that it still works correctly (nonregression) : the Simulator command language17 enables you to write a script to 17 A few commands such as add-macro are interpreted by the SimUI (Simulator User Interface), not by the Simulator itself. Interactive Simulation 63 automatically replay the 40 scripts (stored in . com files) and write the test results into a log file, and write the MSC trace. After the execution of the script, looking into the log file and into the MSC trace tells you if the 40 scripts have been replayed correctly or not. Here is a Simulator script to replay our two scripts