f instances or process DLC, which is equal to the size of the array DLCs, declared in Figure 3.14. 44 The DLC number (of type DLCident) of the new connection is 1, and the corresponding instance number of process DLC (given by the Simulator) is 2. 92 Validation of Communications Systems with SDL dataLink BLOCK/ BLOCK/ BLOCK/ v76test v76test/ v76test /dlca datalink /dlcb _estabreq(0 v76frame( sabme : (.0.) v76frame( sabme : (.0.) _estabind( 0 /* Establishment of DLC number 0: */ I_estabresp v76frame( ua (.0.) ) v76frame( ua (.0.) I_estabconf( 0) I_estabreq(1) v76frame( sabme : (.1.) v76frame( sabme : (.1.) I_estabind( 1 ) Establishment of DLC number 1: */ lestabresp v76frame( (.1.) v76frame( ua : (.1.) _estabconf( 1) /* Transfer of data 39 through DLC number 1:*/ I_datareq(1,39) v76frame(i:(.1,39,15.) v76frame( 1,39,15 ) I_dataind( 1,39) Figure 4.58 Two connections 0 and 1 in parallel A. If you exited the tools since Section 4.3.5.1, launch the Simulator and replay the scenario cnx2.scn: two instances of process DLC exist on each side of the system, the maximum is reached. B. Execute the transition dlca!dispatch: rom_ready_input_l_estabred with l_estabreq(0) from env_dlcasu. You see in the MSC trace that the system answers with an L_RelelaseInd(0): it means that no more connection can be established. But if you look at the SDL trace (or enter print state), you discover that process dispatch is stuck in state waitUA: this is a modeling bug. Also, transitions are missing in the list of firable transitions. You will correct process dispatch to go to state ready instead of state waitUA after trans- mitting L RelelaseInd. C. Exit from the Simulator (answering No to the question) to enable the modification features of the Editor. Do not exit from the Editor. D. In Windows (or Unix), make a copy of the file v76.pr into v76_v2.pr. E. In process dispatch, partition part2, select the output of L_RelelaseInd under the ELSE branch of the decision and click on the nextstate palette symbol; enter - in the newly created symbol, 