the trace that the number of reports is no longer null, press on Break: Break at user input Bit state exploration statistics ** No of reports: 2. Generated states: 1888000. Truncated paths: 0. Unique system states: 1165580. Size of hash table: 8000000 (1000000 bytes) No of bits set in hash table: 2062758 Collision risk: 25 % Max depth: 3639 Current depth: 3623 Min state size: 212 Max state size: 628 Symbol coverage : 98.22 I. In the Report Viewer, double-click on the ImplSigCons box to unfold it, as shown in Figure 7.31. J. The first box from the left shows that signal L_DataReq has been discarded by process DLC in block DLCa. K. Double-click on this box: the MSC Editor displays the trace of the scenario leading to the error; this trace is shown in Figure 7.32. We see that the target instance of process DLC in block DLCa (named DLC_25) is in state waitUA. If we look at the SDL model, under this state no input or save of signal L_DataReq are specified. Thus, this signal has been discarded. 7.3.5.2 Correct the error We decide to save signal L_DataReq in state waitUA, because once the connection is set up, the signal can be processed. A. Exit from the Validator (answering No to the question). B. In Windows (or Unix), make a copy of the file dlc.spr into dlc_v7.spr. 210 Validation of Communications Systems with SDL Report Viewer 2 reports 2 ImplSigCons Warning: Implicit Warning: Implicit signal consumption signal consumption of signal L_DataReq of signal Sender: <<Block L_ReleaseReq DLCa>> dispatch:1 Sender: <<Block Receiver: <<Block DLCa>> dispatch:1 DLCa>> DLC:1 Receiver: <<Block Depth: 786 DLCa>> DLC:1 Depth: 781 Figure 7.31 The Report Viewer (2 reports) MSC bug_exh5 process process process <<Block DLCa> Block DLCa>> <<Block DLCb>> dispatch dispatch env_0 dispatch_3 DLC_25 AtoB_1 BtoA_2 dispatch_4 Removed beginning (784 messages) waitUA L_DataReq ( 0, 86) L_DataReq ( 0, 86) Figure 7.32 The end of the error MSC trace C. In process DLC, page part1, add below state waitUA a save symbol containing signal L_DataReq, as