to get a good overview of the expected behaviors. Remark: to be used in the Validator, all the MSCs used in an HMSC must contain the same entities; for example, it is not allowed to have block DLCa in one MSC and < <block DLCa>> process DLC in another MSC. 122 Validation of Communications Systems with SDL Navigator Up 1: Transition START Pld : <<Block DLCa>> dispatch:1 State : ready Input : DLCstopped Sender Stopped Pld Parameter(s) : 0 second operator No down node branch 1 followed MSC test1 inline verified MSC sequence: test1inline_alt_2_1 test1inline_loop_1 test1inline_alt_3_1 Figure 5.12 The MSC testlinline is verified 5.2.4.1 Create the HMSC With the MSC Editor, you will rework a copy of the basic MSC testl.msc generated by the Simulator in Chapter 4, to obtain the hierarchical HMSC testlops.msc shown in Figure 5.13. This HMSC testlops represents the following behavior expected from the V.76 SDL model 4: 1. one connection phase (cnx1h), 2. followed or not by the repetition of data transfers from A to B (data_a2b) or from B to A (data_b2a), 3. followed by the disconnection phase initiated by A (disc_0_by_a) or initiated by (disc_0_by_b). A. In the Organizer, select Edit> Add New, check MSC, choose HMSC, enter the document name testlops, as shown in Figure 5.14, and press OK. B. The HMSC Editor appears. Draw the HMSC represented in Figure 5.13, and save it into the file testlops.mrm. Now create the five MSCs referenced in the HMSC: C. In Windows (or Unix), make copies of the file testlinline.msc into the files: cnx1h.msc, data_a2b.msc, data_b2a.msc, disc_0_by_a.msc and disc_0_by_b.msc. D. In the Organizer, select Edit > Add Existing and choose cnx1h.msc. The MSC is loaded into the MSC Editor. 4 To simplify the example, this HMSC is incomplete: connection initiated by B is missing, DLC number 1 is not tested and SO on. Automatic Observation of Simulations 123 MSC test1ops cnx1h alternative data_a2b data_b2a bypass (no data) disc_0_by_a disc_0_by_b Figure 5.13 The HMSC testlops.msc Add New New document type Obje