31 The Analyzer

Error and Warning Messages

This section contains a list of the Analyzer error and warning messages. Each message has a short explanation and, where applicable, a reference to the appropriate section of the recommendation Z.100, or to the formal definition. Z.100 is appended by the Formal Definition of SDL (Annex F.1-F.3) where a formal mathematical definition of the language is given.

Some messages contain a "#" followed by a number, which is used to indicate where information, specific to the error situation, will be included.

Some messages include a reference to the object that is the source of the diagnostic. These messages adhere to the format adopted in SDT. See chapter 41, References in SDT-3 for a reference to this format and for examples.

ERROR 1 Internal error

This message indicates an error in the implementation of the Analyzer. Please send a software performance report to Telelogic Customer Support, especially if the error can be reproduced as the only error message of an analysis. The telephone, telefax and E-Mail numbers to Telelogic Customer Support can be found at the beginning of this manual.

ERROR 2 Cannot open file: #1

This error message indicates that an error occurred when the Analyzer attempted to open a file. Modify, if necessary, the file protection and try to run the Analyzer again. If the error persists, contact Telelogic customer support.

ERROR 3 Cannot close file: #1

This error message indicates that an error occurred when the Analyzer attempted to close a file. Modify, if necessary, the file protection and try to run the Analyzer again. If the error persists, contact Telelogic customer support.

ERROR 4 Cannot delete file: #1

This error message indicates that an error occurred when the Analyzer attempted to delete a file. Modify, if necessary, the file protection and try to run the Analyzer again. If the error persists, contact Telelogic customer support.

ERROR 5 Cannot rename file: #1 to #2

This error message indicates that an error occurred when the Analyzer attempted to rename a file. Modify, if necessary, the file protection and try to run the Analyzer again. If the error persists, contact Telelogic customer support.

ERROR 6 Recursive definition of signal list #1

A signal list must not be based on itself, directly or indirectly.
(Z100: 2.5.5)

ERROR 7 More than one #1 is visible in Packages

Several definitions with same name were found in a package. A qualifier might resolve the problem.
(Z100: 2.4.1.2)

ERROR 8 Ending identifier (#2) must be equal to defining 
identifier (#1) in a referenced definition

When writing a definition, the name must be the same on the last row as on the first row.
(Z100: 2.2.2)

ERROR 9 Referenced definitions are not unique (#1)

There are more than one definition which matches the reference.
(Z100: 2.4.1.3)

ERROR 10 Number of instances must be lexically equal in 
referenced process definition and process reference

(Z100: 2.4.4)

ERROR 11 Different virtuality attributes in reference 
and referenced heading

(Z100: 6.3.2)

ERROR 12 A referenced definition may not reference itself

It is not allowed to have a reference to itself in the reference definition.
(Z.100: 2.4.1.3)

ERROR 13 No referenced definition matches reference

A reference is found but not the corresponding definition.
(Z100: 2.4.1.3)

ERROR 14 Virtual start not allowed in operator definition

It is not allowed to have the start as virtual in an operator definition.
(Z.100: 5.3.2)

ERROR 15 Referenced definition matching type reference 
is not a type definition

(Z100: 2.4.1.3)

ERROR 16 Input #1 and output #2 should be different, 
aborting!

An Analyzer pass requires the input and output files to be different. Specify other input and/or output files.

ERROR 17 Definition name may not be qualified when not a 
referenced definition

A qualifier is only allowed on a definition if it is a referenced definition.
(Z100: 2.4.1.3)

ERROR 18 Referenced definition (#1) is not referenced in 
the Package definition

A reference to the definition (#1) is missing in the package definition.
(Z.100: 2.4.1.3)

ERROR 19 Referenced definition (#1) is not referenced in 
the system definition

A reference to the definition (#1) is missing in the system definition.
(Z100: 2.4.1.3)

ERROR 20 Invalid separate analysis unit

It is not allowed to make a separate analysis of the unit selected. Start the analysis on the whole specification instead.

ERROR 21 Referenced substructure definition without name

It is not allowed to have a substructure without a name when referencing it or converting it to SDL-GR.
(Z100: 3.2.2, 3.2.3)

ERROR 22 System definition may not occur as referenced 
definition to a system

Only system types may be referenced, not systems.
(Z.100: 2.4.1.3)

ERROR 23 Illegally placed process context parameter

A process context parameter is used where it is not allowed. Examples of bad use is in a system type or in a block type.
(Z.100: 6.2, 6.1.1.1, 6.1.1.2)

ERROR 24 Illegally placed procedure context parameter

A procedure context parameter is used where it is not allowed.
(Z.100: 6.2)

ERROR 25 Illegally placed signal context parameter

A signal context parameter is used where it is not allowed.
(Z.100: 6.2)

ERROR 26 Illegally placed timer context parameter

A timer context parameter is used where it is not allowed. For example in a system type, block type or service type.
(Z.100: 6.2, 6.1.1.1, 6.1.1.2, 6.1.1.4)

ERROR 27 Illegally placed variable context parameter

A variable context parameter is used where it is not allowed. For example in a system type or block type.
(Z.100: 6.2, 6.1.1.1, 6.1.1.2)

ERROR 28 Illegally placed synonym context parameter

A synonym context parameter is used where it is not allowed. For example in a signal.
(Z.100: 6.2, 2.5.4)

ERROR 29 Illegally placed remote procedure context 
parameter

A remote procedure context parameter is used where it is not allowed.
(Z.100: 6.2)

ERROR 30 Illegally placed remote variable context 
parameter

A remote variable context parameter is used where it is not allowed.
(Z.100: 6.2)

ERROR 31 Illegally placed sort context parameter

A sort context parameter is used where it is not allowed.
(Z.100: 6.2)

ERROR 32 Illegal redeclaration of name

All definitions in the same scope unit belonging to the same entity class must have different names, with some exceptions.
(Z100: 2.2.2)

ERROR 33 Illegally placed gate definition

A gate is defined where it is not allowed.
(Z.100: 6.1.4)

WARNING 34 String #1 truncated

A name or a character string exceeds the implementation limits (currently 500 characters)

ERROR 35 Invalid regular interval

The character strings in a nameclass must be of length one and the first one smaller than the second.
(Z100: 5.3.1.14)

ERROR 36 Integer literal expected

The name in the priority clause of a continuous signal must be an integer literal. This is also true for the name following a regular element in a name class literal.
(Z100: 4.11, 5.3.1.14)

ERROR 37 Invalid generator parameter #1

The actual generator parameter must match the type of the formal one.
(Z100: 5.3.1.12.2)

ERROR 38 Illegal number of arguments

The number of actual parameters must be equal to the number of formal parameters when calling a procedure or creating a process. Similar rules apply for output, input and save of signals and timers.

ERROR 39 More than one default assignment; last from 
generator #1

A sort must not contain more than one default assignment. When instantiating many generators in a sort, only one of them may contain a default assignment.
(Z100: 5.4.3.3)

ERROR 40 Recursive instantiation of generator #1

A generator definition must not instantiate itself, directly or indirectly.
(Z.100: 5.3.1.12.1)

ERROR 41 Undefined generator

Attempt to instantiate an undefined generator.
(Z100: 5.3.1.12.2)

ERROR 42 No virtual definition #1 in super of enclosing 
definition

It is only allowed to redefine or finalize a definition if it is defined as virtual in the inherited type.
(Z100: 6.3.2)

ERROR 43 Ordering must not be defined more than once

All operator signatures in a sort must be different (ordering is shorthand for the relational operators).
(Z100: 5.3.1.8)

ERROR 44 Name of formal parameter of class type must not 
equal name of generator #1

A generator must not have a formal parameter of class type with the same name as the generator definition.
(Z100: 5.3.1.12.1)

ERROR 45 Formal generator parameters of classes literal 
and constant mixed

Literal and constant parameters must not have the same name.
(Z100: 5.3.1.12.1)

ERROR 46 Only task, decision and transition option 
allowed in operator definition

(Z.100: 5.3.2)

ERROR 47 Only Join and Return allowed in operator 
definition

(Z.100: 5.3.2)

WARNING 48 Ending name (#1) in an asterisk state may lead 
to an error

The optional state name ending a state may be defined only if the state list is a single state name, in which case the ending state name should be that state name. The state list for an asterisk state is probably more than a single state name.
(Z100: 2.6.3)

ERROR 49 A state with more than one state name in the 
state list cannot contain an ending name (#1)

The optional state name ending a state may be defined only if the state list is a single state name, in which case the ending state name should be that state name.
(Z100: 2.6.3)

ERROR 50 Ending name (#2) must be equal to defining name 
(#1)

When defining a sort, the name must be the same on the last row as on the first row.
(Z100: 2.2.2, 2.6.3)

ERROR 51 Illegally placed virtuality

Virtual is used in a place where it is not allowed.

ERROR 52 Illegally placed context parameter

The context parameter is placed where it is not allowed.
(Z.100: 6.2)

ERROR 53 Illegally placed virtuality constraint

The virtuality constraint is placed where it is not allowed.

ERROR 54 Illegally placed specialization

The specialization is placed where it is not allowed.

ERROR 55 Illegally placed instantiation

The instantiation is placed where it is not allowed.

ERROR 56 Packages can only contain type definitions

Systems, blocks, processes and services are not allowed, but their corresponding type are.
(Z.100: 2.4.1.2)

ERROR 57 Undefined package #1 in use clause

An used package is not defined. This error may also occur if you have two mutually dependent packages, which is not allowed.

ERROR 58 Illegally placed exported attribute

The exported attribute is placed where it is not allowed.

ERROR 59 Omitted actual context parameter

(Z.100: 6.2)

ERROR 60 Parameterized type #1 cannot be used as actual 
context parameter

A type with context parameters is not allowed to be used as an actual context parameter.
(Z.100: 6.2)

ERROR 61 Undefined actual context parameter

The actual context parameter is undefined or is not visible.
(Z.100: 6.2)

ERROR 62 Illegal number of actual context parameters (>)

(Z.100: 6.2)

ERROR 63 Illegal number of actual context parameters (<)

(Z.100: 6.2)

ERROR 64 Illegal number of actual context parameters (0)

(Z.100: 6.2)

ERROR 65 Formal context parameter #1 cannot be used as 
super type

It is not allowed to specialize a formal context parameter.
(Z.100: 6.2)

ERROR 66 Invalid operator application

The actual types of arguments and/or results do not match the context. For instance, if one of the in-parameters to an operator is of the wrong type.
(Z100: 2.2.2)

ERROR 67 Boolean expression expected

An expression must be of the predefined Boolean sort.

ERROR 68 Invalid conditional expression

The sort of the consequence and the alternative expressions, of a conditional expression, does not match.
(Z100: 5.3.3.7, 5.4.2.3)

WARNING 69 Implicit remote variable, consider making it 
explicit `);

Please read about this in the volume SDT 3.02 Release and Documentation, chapter 2, Compatibility Notes, section "Import" on page 42.

ERROR 70 Invalid import expression

The import identifier in an import expression is erroneous.
(Z100: 4.13)

ERROR 71 PId Expression expected

An expression must be of the predefined PId sort.

ERROR 72 Invalid variable or attribute of variable

Reference to a nonexisting variable or a variable with illegal type or attribute from a view definition, a view expression or an export action.

ERROR 73 Illegal use of parameterized signal

This message is output when context parameters are used in an SDL structure. Context parameters are not supported in SDT 3.02.

ERROR 74 Illegal use of parameterized sor

This message is output when context parameters are used in an SDL structure. Context parameters are not supported in SDT 3.02.

ERROR 75 Undefined timer

Use of an undefined timer in set, reset or active.
(Z100: 2.8)

ERROR 76 No range condition equals true in transition 
option

Exactly one of the branches out from a transition option must be true.
(Z.100: 4.3.4)

ERROR 77 Undefined sort

A sort which is not defined is referenced.
(Z100: 2.2.2)

ERROR 78 Error not allowed in constant expression

(Z100: 5.3.9.1, 5.4.2.1)

ERROR 79 Variable expected

A variable was expected at this place.
(Z100: 2.4.6)

ERROR 80 In parameter expected

An in parameter was expected according to the definition.

ERROR 81 Unexpected parameter

The parameter should not be there according to the definition.

ERROR 82 Start transition required in instantiated type 
#1

An instantiated type must contain a start transition.

ERROR 83 Start transition required in called procedure

(Z100: 2.4.6)

ERROR 84 Procedure call not allowed in constant 
expression

(Z100: 5.3.1.9.1)

ERROR 85 Parameterized procedure cannot be called

(Z100: 6.1.2)

ERROR 86 PId Expression or Process Identifier expected

An pid expression or a process identifier was expected at this place.

ERROR 87 Pid expression in procedure call only allowed 
for remote procedures

It is only allowed to have pid expressions in a procedure call if the procedure is a remote procedure.
(Z.100: 2.7.3, 4.14)

ERROR 88 Undefined procedure

Attempt to call an undefined procedure.
(Z100: 2.2.2, 2.7.3)

ERROR 89 Invalid primary in expression

The primary of an expression does not match the actual context.
(Z100: 2.2.2)

ERROR 90 Two range conditions equals true in transition 
option

The branches out from a transition option must be mutually exclusive.
(Z.100: 4.3.4)

ERROR 91 Sorts should be identical #1 #2

Please read about this in the volume SDT 3.02 Release and Documentation, chapter 2, Compatibility Notes, section "Import" on page 42.

ERROR 92 Undefined remote variable

Attempt to use an undefined remote variable.
(Z.100: 4.13)

ERROR 93 Label expected on first item in free action

(Z100: 2.6.7)

ERROR 94 Formal parameters required in operator 
definition

The operator definition must have formal parameters.
(Z.100: 5.3.2)

ERROR 95 Recursive definition of parent sort #1 in 
syntype

A syntype must not be based on itself, directly or indirectly.
(Z100: 5.3.1.9)

ERROR 96 Expression(s) not resolvable by context

More than one sort is possible in the actual context.
(Z100: 2.2.2)

ERROR 97 Invalid literal renaming in inheritance

Literals to be renamed when inheriting from a sort must be defined in that sort.
(Z100: 5.3.1.11)

ERROR 98 New literal #1 must only occur once in literal 
renaming

All literals renamed in an inheritance must be given unique names.
(Z100: 5.3.1.11)

ERROR 99 Old literal #1 must only occur once in literal 
renaming

A literal must only be renamed once when inheriting.
(Z100: 5.3.1.11)

ERROR 100 Illegal redeclaration of operator signature

It is not allowed to have several operators with the same signature. This error may also occur if you use the same name twice in a sort with implicit operators, for example "structure".

ERROR 101 Sort has no values

This message only concerns SDL-88.

ERROR 102 Invalid expression(s) in number of instances

Type mismatch in the number of instance expression(s) in a process definition.
(Z100: 2.4.4)

ERROR 103 More than one sub signal is visible

(Z100: 3.3)

ERROR 104 Undefined signal, signallist name or timer

A signal, signallist or timer which is undeclared or not visible in this scope has been used.

ERROR 105 Remote procedure definition missing

A definition of the remote procedure is missing.

ERROR 106 No signallist identifier allowed in a remote 
procedure input

It is not allowed to use signal lists in a remote procedure input.
(Z.100: 4.14)

ERROR 107 Empty Transition (result from transition option)

(Z100:4.3.4)

-------------------------------------------------------------------
Note:                                                                
When the error "Empty transition" is issued, a task with the in      
formational text:                                                    
Syntax Error: inserted in transition option expansion                
is inserted by the Analyzer in order to make the SDL specification   
syntactically correct and to be able to continue the semantic analy  
sis.                                                                 
-------------------------------------------------------------------

ERROR 108 Qualifier not allowed

It is not allowed to use a qualifier at this place.

ERROR 109 Formal parameters may not be specified in a 
process type with inheritance

This error should never be issued.

ERROR 110 Procedure formal parameters may not be 
specified in a procedure with inheritance

This error should never be issued.

ERROR 111 Unexpected return value

The procedure has to be value returning to use return values.

ERROR 112 Return value expected

A value returning procedure must specify a return value.

ERROR 113 Undefined state #1

A nextstate contains a name of a state which is not defined.
(Z100: 2.6.7.2.1)

ERROR 114 Undefined label #1

Attempt to join an undefined label (connector).
(Z100: 2.6.8.2.2)

ERROR 115 Open range does not match

A range condition does not match the actual context.
(Z100: 5.3.1.9)

ERROR 116 Inherited operator #1 is not visible

Operators containing an exclamation cannot be inherited (and renamed).
(Z100: 5.3.1.11)

ERROR 117 Old operator name #1 must only occur once in 
operator renaming

An operator must only be renamed once when inheriting.
(Z100: 5.3.1.11)

ERROR 118 New operator name #1 must only occur once in 
operator renaming

All operators renamed in an inheritance must be given unique names.
(Z100: 5.3.1.11)

ERROR 119 Inheritance for #1 is circular

(Z100: 6.3.1)

ERROR 120 Atleast constraint for #1 is circular

(Z100: 6.3.2)

ERROR 121 Recursive sort inheritance

A sort must not inherit from itself, directly or indirectly.
(Z100: 5.3.1.11)

ERROR 122 Unexpected connect statement

A connect statement was not supposed to be found at this place.

ERROR 123 Undefined variable or formal parameter

Variable used in assign statement or input is not declared or does not match the actual context.
(Z100: 2.6.4, 5.4.3)

ERROR 124 Signal expected in output

An output must contain at least one signal.
(Z.100: 2.7.4)

ERROR 125 Undefined channel or signal route in output via

Identifiers used in a via clause of an output must be visible channels or signal routes.
(Z100: 2.7.4)

ERROR 126 Set with no time expression is only allowed for 
timers with default duration

It is only allowed to omit the time expression in set if there is a default duration specified for the timer.
(Z.100: 2.8)

ERROR 127 Set must contain a time expression and a timer 
id

When using set you must specify when the timer should expire and which timer to set.
(Z.100: 2.8)

ERROR 128 Undefined process

Attempt to create an undefined process.
(Z100: 2.2.2, 2.7.2)

ERROR 129 The processtype in create request must be 
defined in the same block

It is only allowed to create a dynamic instance of a process type if the process type definition is in the same block.
(Z100: 2.7.2, FD)

ERROR 130 Remote procedure input cannot contain 
parameters

It is not allowed to have parameters in a remote procedure input.
(Z.100: 4.14)

WARNING 131 #1 : Signal not used in input or output

The defined signal has neither been used in an input nor in an output.

ERROR 132 Invalid procedure call

Expressions in Enabling condition and continuous signal must not contain procedure calls.

ERROR 133 State name #1 in asterisk state list must be 
contained in other state lists

The state names used within the parenthesis (the exceptions) of an asterisk state must be defined somewhere in the enclosing body or the body of a supertype.
(Z100: 4.4)

ERROR 134 No state left to expand the asterisk with

The asterisk state list in the asterisk state includes all states in the enclosing process/procedure/service body.
(Z100: 4.4)

ERROR 135 At least one state list must be different from 
asterisk

A process/procedure/service body cannot only contain asterisk states.
(Z100: 4.4)

ERROR 136 Only one continuous signal may be specified 
when priority is omitted in supertype

Since there is no priority on the virtual continuous transition in the inherited type, it is only allowed to specify one continuous signal.
(Z.100: 6.3.3)

ERROR 137 Priority must be specified on continuous signal 
when priority is specified in supertype

Since there is priority on the virtual continuous transition specification in the inherited type, priority must also be defined on the redefined continuous signal.
(Z.100: 6.3.3)

ERROR 138 Continuous signal priority is not consistent 
with the continuous signal in the supertype

The priority of the redefined continuous signal is not consistent with the virtual continuous signal.
(Z.100: 6.3.3)

ERROR 139 Continuous signal is not consistent with the 
virtuality of the continuous signal in the supertype

A redefined or finalized continuous signal must be virtual in the super type of this type.
(Z100: 6.3.3)

ERROR 140 Only one continuous signal may be specified 
when priority is omitted

A state contains both continuous signals with and without priority.
(Z100: 4.11)

ERROR 141 Two continuous signals of a state cannot have 
the same priority

The values of the priorities in continuous signals of a state must be distinct.
(Z100: 4.11)

ERROR 142 Continuous signal may only be redefined or 
finalized in subtypes

It is only allowed to use redefined or finalized on a continuous signal if the continuous signal transition is defined as virtual in the inherited type.
(Z.100: 6.3.2, 6.3.3)

ERROR 143 Start is already defined in super type

It is not allowed to have more than one start transition and a start transition is already defined in the inherited type.
(Z.100: 2.6.2, 6.3)

ERROR 144 Start is defined as finalized in super type

It is not allowed to define the start transition as redefined, since it is defined as finalized in the inherited type.
(Z.100: 2.6.2, 6.3.3)

ERROR 145 Start is not defined as virtual in super

It is not allowed to define the start transition as redefined, since it is not defined as virtual in the inherited type.
(Z.100: 2.6.2, 6.3.3)

ERROR 146 Multiple exits from state #2 with signal, timer 
or remote procedure #1

The signal, timer or remote procedure is contained in two inputs or one input and one save.
(Z100: 2.6.3, 2.6.5)

ERROR 147 Virtual input #1 is already defined as input 
in state #2 in supertype

It is not allowed to define the input #1 as virtual, since it is already defined without virtual in the inherited type.
(Z.100: 6.3.3)

ERROR 148 Redefined input #1 is not defined as virtual 
input in state #2 in supertype

It is not allowed to define the input #1 as redefined, since it is not defined with virtual in the inherited type.
(Z.100: 6.3.3)

ERROR 149 Redefined input #1 is defined as finalized 
input in state #2 in supertype

It is not allowed to define the input #1 as redefined, since it is defined as finalized in the inherited type.
(Z.100: 6.3.3)

ERROR 150 Redefined input #1 is defined as input in state 
#2 in supertype

It is not allowed to define the input #1 as redefined, since it is defined without virtual in the inherited type.
(Z.100: 6.3.3)

ERROR 151 Finalized input #1 is not defined as virtual 
input in state #2 in supertype

It is only allowed to define an input as finalized if it is a virtual defined input in a inherited type.

ERROR 152 Finalized input #1 is defined as finalized 
input in state #2 in supertype

It is not allowed to define the input #1 as finalized, since it is already defined as finalized in the inherited type.
(Z.100: 6.3.3)

ERROR 153 Signal #1 is already defined as input in state 
#2 in supertype

It is not allowed to have the same signal in more than one input to the same state. In this case there is already a input of the signal #1 in the type you inherit from.

ERROR 154 A state (#1) cannot contain both asterisk input 
and asterisk save

It is not allowed to both have a asterisk input and a asterisk save to a state.
(Z100: 4.6, 4.7)

ERROR 155 A state (#1) may only contain one asterisk 
input

It is only allowed to have one asterisk input to a state.
(Z100: 4.6)

ERROR 156 A state (#1) may only contain one asterisk save

It is only allowed to have one asterisk save to a state.
(Z100: 4.7)

ERROR 157 Valid input signal set must be specified (in 
process/service #1) when no signal routes are specified 
in the enclosing block/process (#2)

If there are no signal routes specified to the process/service. "Signalset" must be used inside the process/service extended heading to specify the valid input signal set.
(Z100: 2.5.2)

ERROR 158 Value returning procedure expected

A value returning procedure was expected at this place.

ERROR 159 Sort of parameter does not match #1

The sort of the #1 does not match the expected parameter sort.

ERROR 160 In/out parameter expected

An in/out parameter was expected according to the definition.

ERROR 161 Missing parameter

A parameter is missing according to the definition.

ERROR 162 Virtual definitions only allowed in types

It is only allowed to use virtual in a type definition.

ERROR 163 Virtual definition #1 does not conform to its 
virtuality constraint

(Z100: 6.3.2)

ERROR 164 Redefinition of #1 does not conform to the 
virtuality constraint

(Z100: 6.3.2)

ERROR 165 A gate with addition of signals can only occur 
in subtypes

Adding in gate definition can only be used if the type is inherited from another type.
(Z.100: 6.1.4)

ERROR 166 Definition of #1 exists already in super type

An already defined gate can not be defined again. If you want to add signals to an already existing gate, the word adding must be used.

ERROR 167 A gate with addition of signals must already 
be defined in a super type

Adding in gate definition can not be used when defining a new gate.
(Z.100: 6.1.4)

ERROR 168 Two gate constraints may not use the same 
direction in gate #1

It is not allowed to have the same direction (in or out) in two gate constraints.
(Z.100: 6.1.4)

ERROR 169 Undefined type #1 in gate endpoint constraint

The endpoint constraint in the gate contains a undefined or not visible type.
(Z.100: 6.1.4)

ERROR 170 The two endpoint constraints of gate #1 is not 
consistent

The endpoint constraints, to and from, in the gate are not consistent.
(Z.100: 6.1.4)

ERROR 171 Undefined block, channel or signal route in 
connection

Identifiers used in a connection must be visible in the scope and of the above mentioned types.
(Z100: 2.5.3, 3.2.3)

ERROR 172 Undefined block, process or service in path

The identifiers following the text "from" and "to" in channel and signal route definitions must be visible blocks, processes or services.
(Z100: 2.5.1, 2.5.2)

ERROR 173 Illegal expression in initial number of block 
instances

The expression giving the number of block instances is not allowed.
(Z.100: 6.1.3.2)

ERROR 174 Undefined type #1 in instance specification

The type must be defined and visible in the scope to be instantiated.

ERROR 175 Undefined component #1/#2 in use clause

(Z100: 2.4.1.2)

ERROR 176 Parameterized type #1 cannot be used as 
constraint type

It is not allowed to use a type with context parameters as a constraint type.
(Z.100: 6.3.2)

ERROR 177 Undefined type #1 in constraint specification

The type #1 used in the constraint specification is undefined or not visible.

ERROR 178 Substructure name in subtype and supertype must 
be the same

(Z100: 6.3.1)

ERROR 179 Undefined type #1 in inheritance specification

A type which is inherited is not defined or not visible.

ERROR 180 Undefined type #1 in virtuality constraint

The type #1 used in the virtuality constraint is undefined or not visible.

ERROR 181 Environment must only appear in one connection

When a channel is partitioned and has the environment as one of its endpoints, the channel substructure must contain one and only one connection with environment.
(Z100: 3.2.3)

ERROR 182 The path #1 must only appear in one connection

It is not allowed to have the same channel or signalroute name mentioned in more than one connection.
(Z100: 2.5.3, 3.2.2)

ERROR 183 All subsignals to the channel #1 must be 
included in the signal lists of the subchannels

In the connection between a channel and subchannels, each signal conveyed by the channel must either be conveyed by the subchannels or all of its subsignals must be conveyed by the subchannels.
(Z100: 2.5.3, 3.3)

ERROR 184 Signal #1 must be included in the signal list 
of the inner paths

In a connection point, all signals in the outer paths must be conveyed by at least one of the inner paths.
(Z100: 2.5.3, 3.3)

ERROR 185 Signal #1 must be included in the signal list 
of the outer paths #2

In a connection point, all signals in the inner paths must be conveyed by at least one of the outer paths.
(Z100: 2.5.3, 3.3)

ERROR 186 In the implicit connection with #2 is signal 
#1 not included in any of the outgoing implicit signal 
routes

Each signal in the channels, directed out from the block, must be mentioned in at least one output in a process. See also ERROR 187.
(Z100: 2.5.2, 2.5.3)

ERROR 187 In the implicit connection with #2 is signal 
#1 not included in any of the incoming implicit signal 
routes

When a block contains no signal routes, the signal route definitions and the connections are derived from the valid input signal sets and the outputs (of the processes in the block) and the channels connected to the block. (The same is valid for a service decomposition with no service signal routes.) Each signal in the channels, directed into the block, must be included in at least one valid input signal set.
(Z100: 2.5.2, 2.5.3)

ERROR 188 Actual context parameter #1 does not conform 
to the fpar constraint

The actual context parameter is not correct according to the fpar constraint given for the formal context parameter.
(Z.100: 6.2)

ERROR 189 Actual context parameter #1 does not conform 
to the sort signature constraint

The actual context parameter is not correct according to the sort signature constraint given for the formal context parameter.
(Z.100: 6.2)

ERROR 190 Actual context parameter #1 does not conform 
to the atleast constraint

The actual context parameter is not correct according to the at least constraint given for the formal context parameter.
(Z.100: 6.2)

ERROR 191 Actual context parameter #1 does not conform 
to the process type constraint

The actual context parameter is not correct according to the process type constraint given for the formal context parameter.
(Z.100: 6.2)

ERROR 192 Actual context parameter #1 does not conform 
to the sort list constraint

The actual context parameter is not correct according to the sort list constraint given for the formal context parameter.
(Z.100: 6.2)

ERROR 193 Actual context parameter #1 does not conform 
to the signal set constraint

The actual context parameter is not correct according to the signal set constraint given for the formal context parameter.
(Z.100: 6.2)

ERROR 194 Block definition must contain process 
definition(s) or a substructure definition

A block definition must at least contain one process or a substructure.
(Z100: 2.4.3)

ERROR 195 Block definition must contain process 
definition(s) when containing signal route definition(s)

A block definition cannot contain signal routes when no processes are defined.
(Z100: 2.4.3)

ERROR 196 Block definition must contain process 
definition(s) when containing connection(s)

A block definition cannot contain connections when no processes are defined.
(Z100: 2.4.3)

WARNING 197 Expansion of select definition is not yet 
implemented

The SDL concept select definition is not supported by the SDT Analyzer.

------------------------------------------------------------------------
Caution!                                                                  
A consequence of this is that the parts of your SDL system which          
are contained in the select definition will not be analyzed or be input   
to the C Code Generator.                                                  
------------------------------------------------------------------------

ERROR 198 Substructure definition must contain at least 
one block definition

At least one block must be defined inside a substructure.
(Z100: 3.2.2)

ERROR 199 Gate only allowed in paths with instance of a 
type or env in a type

Gates are only allowed when connecting channels or signal routes to types.
(Z100: 6.1.4)

ERROR 200 Undefined gate

Use of an undefined gate in a channel or signal route definition.

ERROR 201 Connected to gate (#1) in wrong scope

(Z100: 6.1.4)

ERROR 202 Connected instance #1 does not conform to the 
endpoint constraint of gate #2

The type of the instance #1 connected to gate #2 must be equal to or be a subtype of the endpoint constraint of gate #2.

ERROR 203 ENV does not conform to the endpoint constraint 
of gate #1

A gate with an endpoint constraint cannot be connected to the environment.

ERROR 204 Signal #1 in path is not an incoming signal of 
#3 gate #2

The gate #2 of instance #3 must be defined to convey the incoming signal #1. Add the signal to the gate definition.

ERROR 205 Signal #1 in path is not an outgoing signal of 
#3 gate #2

The gate #2 of instance #3 must be defined to convey the outgoing signal #1. Add the signal to the gate definition.

ERROR 206 Via gate expected in env path with block type 
or process type

A channel or a signal route must be defined using "via <gate>" when connected to the environment in a block type or system type.

ERROR 207 Via gate expected in path with typebased 
instance

Defining a channel or a signal route using "via <gate>" is only possible when the connected instance is type based and thus contain gates.

ERROR 208 Endpoints of the path #1 must be different

A channel/signal route cannot connect a block/process/service with itself.
(Z100: 2.5.1, 2.5.2)

ERROR 209 Endpoint #1 of channel #2 must be a block

A channel must be connected to at least one block!
(Z100: 2.5.1)

ERROR 210 Endpoint #1 of the path #2 must be locally 
defined

The endpoints of a channel/signal route must be defined in the same scope as the channel/signal route is defined.
(Z100: 2.5.1, 2.5.2)

ERROR 211 The second path must denote reverse direction 
of the first path in #1

In a bidirectional channel or signal route, the second path must be in the reverse direction of the first path.
(Z100: 2.5.1, 2.5.2)

ERROR 212 Endpoint #1 of signal route #2 must be a 
process or a service

A signal route must connect at least one process or service.
(Z100: 2.5.2)

ERROR 213 Process and service cannot contain return

(Z100: 2.6.8.2.4)

ERROR 214 Process definition must contain either 
processbody or service decomposition

Syntax requirement.
(Z100: 2.4.4)

ERROR 215 Process cannot contain timer definition when 
decomposed into services

(Z100: 2.4.5)

ERROR 216 Revealed and exported variables only allowed 
in process.

(Z100: 2.4.6)

ERROR 217 Complete semantic analysis requires a system

(Z100: 2.4.6)

ERROR 218 Procedure cannot contain stop

Syntax requirement.
(Z100: 2.6.8.2.3)

ERROR 219 Procedure cannot contain states when the 
enclosing process is decomposed into services
ERROR 220 Priority signal (#1) may not occur in input or 
save

This error message is only issued when running the Analyzer in SDL-88 mode. It is never issued in normal circumstances.

ERROR 221 Priority signal (#1) may not occur in an 
incoming (explicit or implicit) signal route

This error message is only issued when running the Analyzer in SDL-88 mode. It is never issued in normal circumstances.

ERROR 222 Priority signal (#1) may not occur in an 
outgoing (explicit or implicit) signal route

This error message is only issued when running the Analyzer in SDL-88 mode. It is never issued in normal circumstances.

ERROR 223 Signal #1 in priority output must be a priority 
signal

The signal must occur in a priority input in the enclosing service decomposition

ERROR 224 No receiver found

Attempt to view a variable that is not a viewed variable.

ERROR 225 Two services cannot have the same signal (#1) 
in their valid input signal set

The complete valid input signal sets of the service definitions within a process definition must be disjointed.
(Z100: 2.4.5)

ERROR 226 Recursive package #1 in use clause

A package must not use itself.

ERROR 227

Reserved for future purpose.

ERROR 228

Reserved for future purpose.

ERROR 229 Service signal routes cannot be specified when 
no signal routes are specified in the enclosing block

(Z100: 2.4.5)

ERROR 230 Service decomposition must contain at least one 
service definition

(Z100: 2.4.4)

ERROR 231

Reserved for future purpose.

ERROR 232

Reserved for future purpose.

ERROR 233

Reserved for future purpose.

ERROR 234

Reserved for future purpose.

ERROR 235 Valid input signal set cannot contain a signal 
(#1) twice

In the signal list every signal identifier must be distinct (all signal list identifiers are replaced by the signals they denote).
(Z100: 2.5.5)

ERROR 236 Valid input signal set cannot contain a timer 
(#1)

(Z100: 2.4.4, 2.4.5)

ERROR 237 Two signals (#1 and #2) in the complete valid 
input signal set are on different refinement levels of 
the same signal

(Z100: 3.3)

ERROR 238 Two signals (#1 and #2) among the output-
signals of the process are on different refinement levels 
of the same signal

(Z100: 3.3)

ERROR 239 Signal #1 in save cannot be received

The signal is not included in the complete valid input signal set of the process/service.
(FD)

ERROR 240 Signal #1 in input cannot be received

The signal is not included in the complete valid input signal set of the process/service.
(FD)

ERROR 241

Reserved for future purpose.

ERROR 242 Signal #1 in priority input cannot be received

The signal is not included in the complete valid input signal set of the service.
(FD)

ERROR 243

Reserved for future purpose.

ERROR 244

Reserved for future purpose.

ERROR 245 Signal #1 in priority output cannot be sent

The signal is not included in any of the outgoing signal routes (explicit or implicit) or in the valid input signal set (= output to own service).
(Z100: 2.7.4)

ERROR 246 Signal #1 in output cannot be sent

The signal is not included in any of the outgoing signal routes (explicit or implicit) or in the valid input signal set (= output to own process type/service).
(Z100: 2.7.4)

ERROR 247 Path #1 in via must originate from the process 
enclosing the sending service

When an output contains via, all channel/signal routes specified in the via, must originate from the process (or the block if the signal routes are implicit) enclosing the service that contains the output.
(Z100: 4.10.2)

ERROR 248 No service signal route exist between sending 
service and the via-path #1

(Z100: 4.10.2)

ERROR 249 No service signal route with the signal #1 
exist between sending service and the via-path #2

(Z100: 4.10.2)

ERROR 250 Signal #1 must appear in the via-path #2

Each signal route/channel in a via-output must be able to convey the output-signals.
(Z100: 2.7.4)

ERROR 251 Path #1 in via must originate from the sending 
process

When an output contains via, all channel/signal routes specified in the via must originate from the process (or the enclosing block if the signal routes are implicit) that contains the output.
(Z100: 2.7.4)

ERROR 252 Gate #1 in via must be an outgoing gate of the 
sending process

The gate #1 used in the "from #2 via #1" must be an outgoing gate of instance #2.

ERROR 253 Connection with #1 is missing

Either a path is connected to a block/process but is not contained in a connection or a block is connected to a channel but is not contained in a connection in the channel substructure.
(Z100: 2.5.3, 3.2.2, 3.2.3)

ERROR 254 Connection with environment is missing

When a channel is partitioned and has the environment as one of its endpoints, the channel substructure must contain a connection with the environment.
(Z100: 3.2.3)

ERROR 255 Transition must end with a terminator

If the terminator of a transition is omitted, then the last action in the transition must contain a terminating decision.
(Z100: 2.6.4, 2.6.8.1)

ERROR 256

Reserved for future purpose.

WARNING 257 Statement not reached

SDL-92 allows dead code in transition. The warning is issued to notify the user of the dead code.

ERROR 258 Initial transition ends (directly or 
indirectly) with dash nextstate

A nextstate in the initial transition (of a process/ procedure/ service) must be specified with a state name.
(Z100: 4.9)

ERROR 259 Ending name (#1) cannot be qualified (except 
for remote definitions)

(Z100: 2.2.2)

ERROR 260 The outer channeldef must have the first 
connectionpoint (environment) as one of the endpoints

A channel substructure can only contain a connection with the environment if the partitioned channel is connected to the environment.
(Z100: 3.2.3)

ERROR 261 The first connectionpoint #1 must be defined 
in scope unit #2

The first path of a connection must be defined in the scope enclosing the scope of the connection.
(Z100: 2.5.3, 3.2.2)

ERROR 262 The outer channeldef must have the first 
connectionpoint (block) #1 as one of the endpoints

The block identifier in a connection in a channel substructure must identify one of the endpoints of the partitioned channel.
(Z100: 3.2.3)

ERROR 263 One of the endpoints of path #1 must be the 
scope unit #2

A path that occurs as the first connection point in a connection, must be connected to the block/process that contains the connection.
(Z100: 2.5.3, 3.2.2)

ERROR 264 The second connectionpoint #1 must be defined 
in the scope unit #2

A path occurring in the second part (i.e. the list of subpaths) in a connection must be locally defined.
(Z100: 2.5.3, 3.2.2)

ERROR 265 One of the endpoints of path #1 must be the 
environment

A path that occurs in the second part (i.e. the list of subpaths) of a connection must have the environment as one of its endpoints.
(Z100: 2.5.3, 3.2.2)

ERROR 266 System definition must contain at least one 
block definition

An SDL system must contain at least one block.
(Z100: 2.4.2)

ERROR 267 System instance selection does not denote a 
block with processes and a substructure

(Z.100: 3.2.2)

ERROR 268 System instance selection is not a block

(Z.100: 3.2.2)

ERROR 269 Invalid qualifier in system instance selection

(Z.100: 3.2.2)

ERROR 270 System instance selection disabled by other 
selection

(Z.100: 3.2.2)

WARNING 271 Separate analysis/generation cannot be 
performed on an unit when implicit signal routes

This message will be issued when running the Analyzer stand-alone and specifying an input that is not a complete block.

WARNING 272 No analysis is performed when the infile is 
empty

The SDL-PR input file cannot be empty.

WARNING 273 No semantic analysis is performed when the 
input is not a system or a package

Semantic analysis can only be performed on a system or a package.

ERROR 274 Compile and link exited with error code

The code generated by the SDT Code Generator caused compile or link errors.

ERROR 275 Lost license

The connection to the license server is lost. You must wait until the Analyzer has regained access to the license server before resuming your work. If required, contact your system manager to get the problem solved.

ERROR 276 Cannot get license

No license was available when starting up Analyzer. You must wait until a license becomes available (which will occur when another user terminates his Analyzer).

ERROR 277 Cannot return license

The Analyzer could not return its license to the license pool. To return the license, you may need to stop and restart the license server.

WARNING 278 Analyzer command could not be fully performed

The Analyzer did not perform all the passes that were ordered. The results from the Analyzer may not be what you expect. This message is output as a result from a syntactic or semantic error that in turn causes the remaining passes not to be executed.

ERROR 279 The number of block instances must be one or 
greater

The number of block instances in a multiple block instantiation must be greater than 0.

ERROR 280 Unreachable path #1 in VIA

The path #1 must be connected to the process instance.

ERROR 281 Unreachable process instance set #1 in TO expr

There must be a path leading to the process instance set #1 from this process instance.

WARNING 282 Several possible paths in VIA list 
(interpretation in SDL-92 not equal to SDL-88)

There are several paths that can convey the signal, one of them will be non deterministically chosen.

WARNING 283 Several possible paths (interpretation in 
SDL-92 not equal to SDL-88)

There are several paths that can convey the signal, one of the paths will be non deterministically chosen during execution.

ERROR 284 Only process gate allowed

This error message should never be issued.

ERROR 285 Only process gate is allowed in VIA list in 
output in process type

"Output via" can only be performed via a gate in a process type.

ERROR 286 Process instance set in TO expr not allowed in 
process type

"Output to <process name>" is not allowed in a process type.

ERROR 287 Via list in output in global procedure not 
possible

"Output via" is not allowed in a global procedure.

ERROR 288 Process instance set in TO expr not possible 
in global procedure

"Output to <process name>" is not allowed in a global procedure.

ERROR 289 Invalid expression in transition option

One of the expressions in a transition option is erroneous.
(Z100:4.3.4)

ERROR 290 External synonym not allowed

External synonyms are only allowed in a number of instances in process reference symbols and in heading symbols in process diagrams.

ERROR 291 Range check failed

(Z100:5.3.1.9.1)

ERROR 292 Maximal number of instances equals zero

A process should have at least one instance.
(Z100:2.4.4)

ERROR 293 Maximum number of instances is less than 
initial number

In the process instances definitions, the maximum number of instances must be greater or equal to the initial number.
(Z100:2.4.4)

ERROR 294 Terminator in nonterminating transition 
(result from transition option)

(Z100: 4.3.4)

ERROR 295 Two terminating transitions (result from 
transition option)

In a transition option, all options have been terminated with terminator symbols, but according to the PR source, they are succeeded by symbols.
(Z100:4.3.4)

ERROR 296 Only label left in transition (result from 
transition option)

(Z100:4.3.4)

-------------------------------------------------------------------
Note:                                                                
When the error "Only label left in transition (result                
from transition option)" is issued, a task with the information      
al text:                                                             
Syntax Error: inserted in transition option expansion                
is inserted by the Analyzer in order to make the SDL specification   
syntactically correct and to be able to continue the semantic analy  
sis.                                                                 
-------------------------------------------------------------------

ERROR 297 Error limit reached, terminating

The number of diagnostics that the Analyzer has reported exceeds the value of the

WARNING 298 Accumulated expression depth: #1 parts: #2 
matches: #3

Semantic analysis of complex expression may cause long execution time. The execution time will increase in a fashion that is exponential rather than linear. If possible, try to reduce the complexity of expressions by breaking them down into multiple expressions.

WARNING 299 Expression depth: #1 parts: #2

See WARNING 298 Accumulated expression depth: #1 parts: #2 matches: #3 above.

ERROR 300 Command not found

The command that was input to the Analyzer's command interpreter was not recognized.

ERROR 301 Unexpected end of command: #1

The command that was input to the Analyzer does not contain all necessary parameters.

ERROR 302 Ambiguous command

The command that was input to the Analyzer's command interpreter was ambiguous. More characters need to be supplied to identify the command.

ERROR 303 Parameter expected

The command that was input to the Analyzer's command interpreter
requires one or more parameters.

ERROR 304 Macro must not be part of a qualifier

A macro is not allowed to be part of a qualifier.

ERROR 305 Non existing diagram

The diagram set as input to the Analyzer using the set-input command does not exist.

ERROR 306 No input specified

There is no input set to the Analyzer using the set-input command.

WARNING 307 #1: unknown, line ignored!

The command line is ignored.

WARNING 308 #1: too long, line ignored!

The command line is too long.

ERROR 309 #1: wrong magic number, aborting!

The input Organizer file is corrupt. Check the file contents. See "Contents of the System File" on page 1142 in chapter 22, The SDT Organizer.

WARNING 310 #1: is not bound, ignored!

The Organizer has ordered to analyze a diagram that is not connected to a file.

WARNING 311 No command found in Organizer file

An Organizer file that was input to the Analyzer did not contain any commands to the Analyzer. Check the file contents/syntax. "Contents of the System File" on page 1142 in chapter 22, The SDT Organizer.

ERROR 312 Syntax error in rule #1, symbol #2 found but 
one of the following expected:

Syntax error!

ERROR 313 Syntax error, symbol #1 found but one of the 
following expected:

Syntax error!

ERROR 314 Lexical error in rule #1, symbol #2 found but 
one of the following expected:

Syntax error!

ERROR 315 Lexical error, symbol #1 found but one of the 
following expected:

Syntax error!

ERROR 316 File #1 not found in environment variable #2 
#3, check installation!

Check the installation. If the error persists, contact TeleLogic customer support.

ERROR 317 Path of file #1 found in environment variable 
#2 exceeds implementation limit

The directory path is too long!

WARNING 318 #1 : signal not used

The signal #1 should be used.

WARNING 319 #1 : timer not used in input

The timer #1 should occur in an input.

WARNING 320 #1 : timer not used in set

The timer #1 should be set in the process.

WARNING 321 #1 : signallist not used

The signallist #1 should be used.

WARNING 322 #1 : variable not used

The variable #1 should be used.

WARNING 323 #1 : formal parameter not used

The formal parameter #1 should be used.

WARNING 324 #1 : synonym not used

The synonym #1 should be used.

WARNING 325 #1 : viewed variable not used

The viewed variable #1 should be used.

WARNING 326 #1 : imported variable not used

The imported variable #1 should be used.

WARNING 327 #1 : sort not used

The sort #1 should be used.

WARNING 328 #1 : generator not used

The generator #1 should be used.

WARNING 329 #1 : label might not be used

The GR to PR converter may cause false messages.

WARNING 330 #1 : system type not used

The system type #1 should be used.

WARNING 331 #1 : block type not used

The block type #1 should be used.

WARNING 332 #1 : process type not used

The process type #1 should be used.

WARNING 333 #1 : procedure not used

The procedure #1 should be used.

WARNING 334 #1 : package not used

The package #1 should be used.

ERROR 335 Input must be one complete unit, cannot contain 
references

The input to the Analyzer must be one complete unit which cannot contain references.

ERROR 336 Feature of SDL not implemented: #1

The SDL feature #1 is not implemented. Consider using an alternative approach.

ERROR 337 Generated line exceeded MaxLineLength

The generated line is too long!

ERROR 338 Input must be a separate generated unit

The Code Generator failed to generate code for the unit specified as input (for instance a process or procedure).

ERROR 339 Internal error. Node = nil in #1