 L Releaselnd (0) (UA:(.0.)) L_Releaselnd (0) Figure 5.19 The MSC disc_0_by_b.msc Organizer - v76.sdt File Edit View Generate Tools Help test1ops nw test1ops.mrm cnx1h nw cnx1h.msc data_a2b nw data_a2b.msc data_b2a nw data_b2a.msc disc_0_by_a nw disc_0_by_a.msc disc_0_by_b nw disc_0_by_b.msc Figure 5.20 The HMSC testlops and the five referenced MSCs in the Organizer 126 Validation of Communications Systems with SDL 5.2.4.2 Use the HMSC to check the SDL model A. Start the Validator as indicated in Section 5.2.1.2, and enter the command5: load-msc testlops.mr B. Select Commands > Toggle MSC Trace. C. Press the Navigator button in the Explore group. D. Using the Navigator, execute an SDL scenario matching the loaded HMSC (when there are two possibilities, select the left one): for example, establish DLC number 0, then transmit data 86, and then release DLC number 0. E. After around 37 transitions, the Navigator window displays: No down node - MSC testlinline verified, as shown in Figure 5.21. It means that one of the signal sequences present in the loaded HMSC has been simulated. The Navigator also indicates which MSCs have been followed in the HMSC. These MSCs have been manually shown in bold in the figure. Navigator MSC test1ops Up 1: Transition START cnx1h Pld : <<Block DLCa>> dispatch:1 State : ready Input : DLCstopped Sender Stopped Pld Parameter(s) 0 data_a2b data_b2a No down node MSC :1ops verified the simulated path MSC sequence: cnx1h data_a2b disc_0_by_a disc 0 by disc 0 by b Figure 5.21 The MSC testlops is verified You could press the buttons Top or Up in the Explore group to go back to the initial or to the previous SDL model states, and try to verify other paths, for example, no data transfer, or a data transfer from B to A and SO on. 5 If the load-msc command reports errors, check that inline expression separators (horizontal dashed lines) do not remain in the faulty MSC. Automatic Observation of Simulations 127 5.2.5 More details on MSCs 5.2.5.1 How the Validator monitors the MSC events When verifying