ereq (?) feed dlcasu l_datareq(?,?) Then you can copy the feed skeletons and paste them into a file executed at startup. The character ? in the feed skeletons means the default value. For example, for Integer, the default value is 0. 108 Validation of Communications Systems with SDL 4.4 ERRORS DETECTABLE BY INTERACTIVE SIMULATION In addition to the static errors detected when compiling the SDL model to generate the C code used for simulation (e.g. the ObjectGeode SDL Checker geodecheck, called before simulation, detects 541 kinds of errors and warnings), many kinds of dynamic errors are detected by simulation. It enables you to find bugs before writing a line of code. 4.4.1 Dynamic errors detected by Tau SDL suite Simulator Tau SDL Suite Validator detects the same errors as the Simulator, plus errors detected by state graph analysis, described in Chapter 7 on exhaustive simulation. 4.4.1.1 SDL model errors Nonconformance to expected behavior: by examining the simulation textual or MSC trace, you discover that the SDL model does not behave as expected. An example of such error was discovered in Section 4.2.5.2. Deadlock: the SDL simulation should continue but no transition is ready. Infinite loops: within a transition, detected because the maximum number of symbols Define- Max-Transition-Length is reached. Discarding an unexpected signal: an example of such error was discovered in Section 4.2.3.1. For example, if signal sigl is sent to a process whose current state does not specify any input of sigl, the Simulator displays the message: Signal sigl caused an immediate null-transition. 4.4.1.2 SDL dynamic errors Decision answer missing: the value of the expression in a decision did not match any of the answers. Create process instance: attempt to create more process instances than the maximum num- ber specified. Warning in SDL output to <Pid : Pid is Null, or no path exists between the sender and the receiver that can convey the signal. The signal is discarded. Warning in SDL output: no possible receiver found, or s