t you are at Step 0, and the loaded scenario has 26 steps. G. Press the button All located under Redo: (or press 26 times the redo Simulator button): when you see end of scenario execution and 26/26, it means that the scenario loaded from the file retry1.s has been replayed entirely³9. If the scenario does not replay until the end, check that your feeds are loaded: see Section 4.3.1.4. Interactive Simulation 85 Now: 0 Figure 4.48 The current and maximum step numbers after loading the scenario H. The bottom of the MSC generated by the Simulator looks like Figure 4.49(a): the signal dlcstopped has been transmitted, but it is in the queue of process dispatch. dicstopped(9) dicstopped(0) Figure 4.49 MSC trace: signal dlcstopped in the process queue (a) and consumed (b) I. To watch the input FIFO queues of the model, press the Watch button; in the Watch creation window, press Queues: as depicted in Figure 4.50, a watch window appears, dis- playing the contents of the queues. As expected, you can see the signal dlcstopped in the queue of process dispatch. Watch Watch creation dicaldispatch ! queue first signal in the queue Queues sender = dicaldic(1) States name = dicstopped signal name Active timers dicstopped = signal parameter value State coverage dicbidispatch ! queue = () Transition coverage process dicaldic not created or stopped New window process dicbidic not created or stopped atob(1) ! queue = () Close btoa(1) queue = () empty queue Figure 4.50 Watching the input queues J. In the Simulator, double-click the transition trans dlca!dispatch : from_waitua_input_dlcstopped the signal dlcstopped disappears from the watch and the MSC shows a filled arrowhead as in40 Figure 4.49(b). We have returned to the initial model state, from where we can simulate other scenarios. 40 The arrow is inclined, because the actual input of dlcstopped (the arrowhead) occurred after the process stop (the X symbol). A horizontal arrow would mean output dlcstopped, followed by input dlcstopped and then by process stop, which is not the a