 Figure 5.55 Building the MSC P. Double-click the scenario data_b2a_0, create the four new signals 14 (message button), copy the text from the old signals to the new signals, delete the four old signals, and finally replace 86 and 15 by 97 and 23 to obtain the scenario shown in Figure 5.56. data_b2a_0 inst_dlca inst_datalink inst_dlcb BLOCK/ BLOCK/ BLOCK/ v76test v76test/ v76test /dlca datalink /dlcb /* Transfer of data 97 through DLC number 0: */ I _datareq( 0,97) y76frame( i : (. 0,97,23 .) ) I_dataind( 0,97) v76frame( : (. 0,97,23 .) ) Figure 5.56 The scenario data_b2a_0 Q. Double-click the scenario disc_0_by_a, create the seven new signals, copy the text from the old signals to the new signals, and delete the seven old signals to obtain the scenario shown in Figure 5.57, taking care to have exactly the same ordering between signal outputs and inputs. R. In the Framework window, select the file testlops.msc and do File > Save. The hierarchical MSC testlops is now ready for tracking. 5.3.3.2 Compile the SDL model plus the two MSCs A. In the SDL Editor, check that the V.76 SDL model plus the two MSCs contained in testlops.msc and xid1.msc are loaded. 14 Do not move the existing signals because the Editor stores some VIA <channel name> in the .msc file, which may provoke compilation errors (for example, when moving a signal from DLCa to DLCb). 148 Validation of Communications Systems with SDL disc_0_by_a inst_dlca inst_datalink inst_dlcb BLOCK/ BLOCK/ BLOCK/ v76test v76test/ v76test /dlca datalink /dlcb |_releasereq( 0) /* Release of DLC number 0 initiated by A: */ v76frame( disc (.0.) ) v76frame( disc : (.0.) ) v76frame( ua: (.0.) ) v76frame( (.0.) I_releaseind( 0) I_releaseind( 0) Figure 5.57 The scenario disc_0_by_a B. Unload any other files from the SDL Editor, and close all the diagrams opened in the right area. C. Quit (do NOT minimize) the ObjectGeode Launcher if running. D. In the SDL Editor, select Tools > SDL & MSC Simulator. The ObjectGeode Launcher appears: check that its left area only contains v76.p