![]() |
![]() |
![]() |
![]() |
![]() |
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 the SDL Suite. See SDT References for a reference to this format and for examples.
INFO 0 Internal error: message %1 not found
This message indicates an error in the implementation of the Analyzer. Please send a report to IBM Rational Customer Support, especially if the error can be reproduced as the only error message of an analysis. Contact information for IBM Rational Customer Support can be found in How to Contact Customer Support.
ERROR 1 Internal error
This message indicates an error in the implementation of the Analyzer. Please send a report to IBM Rational Customer Support, especially if the error can be reproduced as the only error message of an analysis. Contact information for IBM Rational Customer Support can be found in How to Contact Customer Support.
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 IBM Rational Customer Support. Contact information for IBM Rational Customer Support can be found in How to Contact 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 IBM Rational Customer Support. Contact information for IBM Rational Customer Support can be found in How to Contact 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 IBM Rational Customer Support. Contact information for IBM Rational Customer Support can be found in How to Contact 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 IBM Rational Customer Support. Contact information for IBM Rational Customer Support can be found in How to Contact Customer Support.
ERROR 6 Recursive definition of signal list %1
A signal list must not be based on itself, directly or indirectly.
(Z.100: 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.
(Z.100: 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.
(Z.100: 2.2.2)ERROR 9 Referenced definitions are not unique (%1)
There are more than one definition which matches the reference.
ERROR 10 Number of instances must be lexically equal in referenced process definition and process reference
ERROR 11 Different virtuality attributes in reference and referenced heading
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.
- You define a diagram as REFERENCED, but do not give a non-referenced definition of the diagram later.
ERROR 14 Virtual start not allowed in operator definition
It is not allowed to have the start as virtual in an operator definition.
INFO 15 Required item %1 is not connected to a file
The Organizer has ordered to analyze something depending on a diagram that is not connected to a file.
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.
- Remove the qualifier.
- Use the keyword REFERENCED and move the definition of the child diagram out of the parent diagram.
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.
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.
(Z.100: 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.
- Change one of the names in all appropriate places.
- Remove one of the declarations if the intention was to use the same variable.
ERROR 33 Illegally placed gate definition
A gate is defined where it is not allowed.
(Z.100: 6.1.4)ERROR 34 %1 is not a time stamp file, will not save time stamps
On successful analysis the Analyzer saves info about this. Examine the file and rename or delete it to allow the Analyzer to save time stamps and possibly avoid unnecessary reanalysis in the future.
ERROR 35 Invalid regular interval
The character strings in a nameclass must be of length one and the first one smaller than the second.
(Z.100: 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.
ERROR 37 Invalid generator parameter %1
The actual generator parameter must match the type of the formal one.
(Z.100: 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.
(Z.100: 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.
(Z.100: 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.
- Make sure you are trying to redefine the correct entity.
- Make sure that there is a virtual entity to redefine in the super type.
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).
(Z.100: 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.
(Z.100: 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.
(Z.100: 5.3.1.12.1)ERROR 46 Only task, decision and transition option allowed in operator definition
ERROR 47 Only Join and Return allowed in operator definition
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.
(Z.100: 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.
(Z.100: 2.6.3)ERROR 50 Ending name (%2) must be equal to defining name (%1)
- Change the name either at the beginning or at the end of the definition to get the same name in both places.
- Remove the optional name at the end.
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.
- You use the ATLEAST keyword for a type-based diagram that is not placed inside a type-based diagram.
- Remove the ATLEAST construct.
- Move the type-based diagram with the ATLEAST construct to a type-based diagram.
- Make the diagram containing the type-based diagram with the ATLEAST construct a type-based diagram too.
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. If you use ASN.1 modules or C headers, it may also occur if there are no dependency links between these and the SDL system.
ERROR 58 Illegally placed exported attribute
The exported attribute is placed where it is not allowed.
ERROR 59 Omitted actual context parameter
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 (>)
ERROR 63 Illegal number of actual context parameters (<)
ERROR 64 Illegal number of actual context parameters (0)
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 Several matches
Resolution by context found several possible interpretations, use qualifiers to reduce the number of possibilities.
(Z.100: 2.2.2)ERROR 67 No matching synonym or literal
- You are using a synonym or literal of the wrong type. For instance, a constant expression of type integer may be required, but you supply a value of type real.
- Replace the synonym or literal with a constant expression of the correct type.
- Define a synonym or literal of the correct type.
WARNING 68 Optional parameter of sort %1 omitted
A missing parameter may lead to uninitialized values, make sure it is not left out by mistake.
To remove the warning, either:
- Supply a constant value or a variable to the parameter in the procedure call.
- Remove the parameter from the procedure and from all calls to the procedure.
WARNING 69 Implicit remote variable, consider making it explicit
ERROR 70 Invalid import expression
The import identifier in an import expression is erroneous.
ERROR 71 Signal %1 is shadowed in connection
- You have multiple declarations of a signal (same name) and two channels or signal routes that are connected uses different versions of a carried signal.
- remove the inner declaration of the signal
- Rename one of the signals and determine which one the channels or signal routes in the connection should use.
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.
- You EXPORT a variable that is not visible from the current scope.
- You EXPORT a variable that is not defined as EXPORTED.
- Find the correct name of the variable you want to export.
- Make sure that the variable you want to export is defined as EXPORTED.
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.
ERROR 74 Illegal use of parameterized sort
This message is output when context parameters are used in an SDL structure. Context parameters are not supported.
ERROR 75 Undefined timer
Use of an undefined timer in set, reset or active.
ERROR 76 No range condition equals true in transition option
Exactly one of the branches out from a transition option must be true.
- Change the condition for taking one of the alternatives to make sure that one alternative is always taken.
- Add a new alternative with a condition that evaluates to true.
ERROR 77 Undefined sort
A sort which is not defined is referenced.
ERROR 78 Error not allowed where constant required
ERROR 79 Variable expected
A variable was expected at this place.
- You use a constant value or an operator on the left side of the assignment.
- You give a constant value or the value of an operator instead of a variable as an actual parameter in a procedure call, when the corresponding formal parameter is an IN/OUT parameter.
To remove the error in the above cases, either:
- Use a variable on the left side of the assignment instead.
- Use a variable as an actual parameter in the procedure call instead.
You also get this error either if:
- You call a procedure using a constant as an actual in/out parameter.
- You call a procedure without specifying a parameter that is an in/out parameter.
To remove the error in the above cases, either:
- Change the constant or the not specified parameter to a variable of the correct type instead.
- Change the procedure to accept an in parameter instead of an in/out parameter.
ERROR 80 In parameter expected
An in parameter was expected according to the definition.
- You are using an IN/OUT parameter in an imported procedure signature that should match an IN parameter in a remote procedure signature.
- Change the imported procedure signature to use an IN parameter instead.
- Change the remote procedure signature to use an IN/OUT parameter instead.
ERROR 81 Unexpected parameter
The parameter should not be there according to the definition.
- You supply a parameter when you create a process that is not defined in an FPAR statement in the process definition.
- You add an extra parameter or return value to an imported procedure signature that should match a remote procedure signature.
- Remove the extra parameter or return value.
- Add the extra parameter or return value to the definition of the called or created entity.
ERROR 82 Start transition required in instantiated type %1
An instantiated type must contain a start transition.
- Instantiate a process type or a service type that has a start transition instead.
- Add a start transition to the process type or the service type.
ERROR 83 Start transition required in called procedure
ERROR 84 Procedure call not allowed where constant required
- You call a procedure in a place where a constant is required, such as in a variable or synonym definition.
- Assign the variable a constant value in the variable definition.
- Assign the variable the return value of a procedure call in the start transition instead.
ERROR 85 Parameterized procedure cannot be called
ERROR 86 PId Expression or Process Identifier expected
An PId expression or a process identifier was expected at this place.
- Change the second parameter to a pid expression or a process identifier.
- Remove the second parameter if it is not needed.
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.
- Remove the TO construct from the procedure call, if it is a normal procedure residing in this process.
- Make the procedure a REMOTE procedure in the other process, and declare the procedure as IMPORTED in this process.
ERROR 88 Undefined procedure
Attempt to call an undefined procedure.
- Make an existing procedure with the correct name visible from the current scope.
- Create an appropriate procedure if it does not exist.
WARNING 89 Trailing parameter of sort %1 omitted
A missing parameter may lead to uninitialized values, make sure it is not left out by mistake.
ERROR 90 Two range conditions equals true in transition option
The branches out from a transition option must be mutually exclusive.
- Change the condition for taking one of the alternatives to make sure that only one alternative is taken.
- Remove one of the alternatives that evaluated to true.
INFO 91 Location of the global definition previously mentioned
ERROR 92 Undefined remote variable
Attempt to use an undefined remote variable.
ERROR 93 Label expected on first item in free action
ERROR 94 Formal parameters required in operator definition
The operator definition must have formal parameters.
ERROR 95 Recursive definition of parent sort %1 in syntype
A syntype must not be based on itself, directly or indirectly.
- Make sure that syntypes not equals each other in a circular chain, and that one syntype equals a non-syn-type.
INFO 96 Setlocale failed
The Analyzer failed to set the character handling part of the locale. It will remain in the default C locale.
ERROR 97 Undefined signallist
ERROR 98 New literal %1 must only occur once in literal renaming
All literals renamed in an inheritance must be given unique names.
- You are declaring a newtype that inherits from another type, and renames two or more old literals to the same new name.
ERROR 99 Old literal %1 must only occur once in literal renaming
A literal must only be renamed once when inheriting.
- You are renaming literals in a newtype that inherits from a super newtype, and the old literal names occur more than once in the list of renamings.
- Make sure that the same old literal name only occurs once on the right side of the assignment in the list of renamings.
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 Unexpected remote variable
Remote variable may not be used in [priority] input.
- You are using a remote variable in a way that is not allowed, for instance as if it was a normal signal in an input construct.
- Use the remote variable in a proper way instead: to update the value of the remote variable, use an IMPORT construct instead of trying to receive the value as if it was a signal.
- Change the remote variable to another more proper type for the intended use.
ERROR 102 Expression(s) in number of instances evaluates to error
ERROR 103 More than one sub signal is visible
ERROR 104 Undefined signal, timer, signallist, remote procedure or remote variable
No visible definition with proper entity kind found.
(Z.100: 2.2.2)ERROR 105 Remote procedure definition missing
A definition of the remote procedure is missing.
- You are referring to a procedure with an IMPORTED construct, but the procedure does not exist or is not defined as REMOTE.
- Make sure there is a REMOTE definition of the procedure you are referring to in the IMPORTED construct.
ERROR 106 Recursive definition of synonym
The value of a synonym must not be based on itself, directly or indirectly.
ERROR 107 Gate must be connected
ERROR 108 Type mismatch for variable or formal parameter
ERROR 109 Signal refinement is not supported
ERROR 110 Only one varargs allowed
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.
- You are returning from a procedure without specifying a return value, when the procedure is expected to return a value because of a RETURNS construct in the procedure heading.
- Supply a return value in the RETURN construct.
- Remove the RETURNS construct from the procedure heading and remove any returned values from all RETURN constructs in the same procedure.
ERROR 113 Undefined state %1
A nextstate contains a name of a state which is not defined.
(Z.100: 2.6.7.2.1)ERROR 114 Undefined label %1
Attempt to join an undefined label (connector).
(Z.100: 2.6.8.2.2)ERROR 115 Open range does not match
A range condition does not match the actual context.
(Z.100: 5.3.1.9.1)ERROR 116 Inherited operator %1 is not visible
Operators containing an exclamation cannot be inherited (and renamed).
To remove the error in the above cases, either:
- You have a newtype that inherits from a super newtype, and you try to inherit an operator from the super newtype that does not exist.
To remove the error in the above case, either:
- Make sure that the name of the operator you wants to inherit is correct.
- Remove the name of the non-existing operator from the list of inherited operators.
ERROR 117 Old operator name %1 must only occur once in operator renaming
An operator must only be renamed once when inheriting.
ERROR 118 New operator name %1 must only occur once in operator renaming
All operators renamed in an inheritance must be given unique names.
ERROR 119 Inheritance for %1 is circular
- Break the chain of circular inheritance by removing or changing the super diagram for one of the diagrams in the chain.
ERROR 120 Atleast constraint for %1 is circular
ERROR 121 Recursive sort inheritance
A sort must not inherit from itself, directly or indirectly.
- Break the chain of circular inheritance by removing or changing the super newtype for one of the newtypes in the chain.
ERROR 122 Unexpected connect statement
A connect statement was not supposed to be found at this place.
INFO 123 %1 is one of the possible matches
ERROR 124 Signal expected in output
An output must contain at least one signal.
- Change the name in the output construct to match a visible signal instead.
- Supply the value or variable that you were trying to send as a parameter to a signal.
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.
- Find a correct channel or signal route name and use that instead.
- Add the channel or signal route that you references in the VIA construct.
- Remove the VIA construct, if the VIA construct is not needed and the signal sending path can be determined uniquely anyway.
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.
- You try to set a timer that does not have a default duration without specifying a duration in the SET construct.
- Add a default duration to the timer definition:
TIMER myTimer:=10.- Specify a time in the SET construct: SET(Now+10, myTimer).
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.
- Check that you are using the correct name for the process that you want to create.
- Add a process definition of the process you want to create.
- Remove the process creation construct.
ERROR 129 Created process must belong to the partition block %1
It is only allowed to create a dynamic instance of a process type if the process type definition is in the same block.
- You try to create a process instance in another block than the block that the creating process resides in.
- Make sure that the creating process and the process to be created resides in the same block diagram.
- Make sure that the creating process uses the correct name for the process to be created.
ERROR 130 Remote procedure input and signal list input must not have parameters
It is not allowed to have parameters in a remote procedure input or when inputting a signal list.
- You try to receive parameters by using a pair of parenthesis characters when referring to a remote procedure or a signal list in an INPUT construct.
- Replace the remote procedure or the signal list with ordinary signals
- Remove the parameters and the associated pair of parenthesis characters.
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.
- You are calling a procedure in an inappropriate place, such as in the expression related to a continuous signal.
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.
- You include a name of a non-existing state in the list of exceptions after an asterisk (i.e. for all states) state.
- Check that you are using the correct name for the state that should be excepted.
- Remove the unwanted exception.
- Introduce the missing state in your state machine.
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.
- Make sure that you are not doing exceptions to the asterisk state for all states in the state machine.
- Replace the asterisk state with a normal state not using an asterisk.
ERROR 135 At least one state list must be different from asterisk
A process/procedure/service body cannot only contain asterisk states.
ERROR 136 Several virtual continuous signals in a state with same or no priority
It is not possible to tell which transition would be affected by a redefinition.
- Remove one of the virtual continuous signals.
- Give one of the virtual continuous signals another priority.
ERROR 137 Virtual continuous signal is virtual in super type with same or no priority
It is not possible to tell which transition would be affected by a redefinition.
- You have a virtual continuous signal in both the sub type and the super type and the priority is the same or no priority is given.
- Make the continuous signal in the sub type REDEFINED or FINALIZED instead of VIRTUAL.
- Give different priority to the continuous signal in the sub type than the priority in the super type.
ERROR 138 Redefined continuous signal is not virtual in super type with same or no priority
Cannot find the transition to redefine.
- You redefine a continuous signal transition in a sub type and the same continuous signal transition cannot be found in a super type with the same priority.
- If you intend to redefine an existing continuous signal, make sure the continuous signal you are redefining is starting from the same state and have the same priority.
- If you do not want to redefine an existing continuous signal, remove the REDEFINED or FINALIZED keyword.
ERROR 139 Filter exited with error code
A filter program terminated with a non zero exit code.
ERROR 140 External procedure not allowed
An external procedure cannot be mentioned in a <type expression>, in a <formal context parameter> or in an <atleast constraint>.
- Use a normal procedure instead of the external procedure.
- Make the external procedure a normal procedure.
ERROR 141 Number of block instances not allowed
Number of block instances may only be specified in typebased block definitions.
(Z.100: 6.1.3.3)ERROR 142 No diagram to put definition in
It is not possible to convert something to a text symbol in SDL/GR without a surrounding diagram.
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.
- Use the keyword REDEFINED or FINALIZED for the redefined transition, if you intend to redefine the transition; make sure that the transition you redefine is either marked with VIRTUAL or REDEFINED.
- Remove the definition from the sub type if you do not intend to redefine it.
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.
- You are trying to REDEFINE or FINALIZE the start transition in a sub type when it is declared as FINALIZED in a super type.
- Change the start transition to VIRTUAL or REDEFINED in the closest super type where it is mentioned.
- Remove the start transition from the sub type if you did not intend to redefine the start transition.
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.
- You try to redefine the start transition in a sub type when the start transition is not defined as VIRTUAL in a super type.
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.
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.
- You are declaring a transition to be VIRTUAL in a sub type, when the transition is already VIRTUAL in the super type.
- Use the keyword REDEFINED instead of VIRTUAL in the sub type.
- Make sure the transition is VIRTUAL in a super type.
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.
- You have a redefined transition in a sub type that does not exist in the super type.
- You have a redefined transition in a sub type that is not declared as virtual in the super type.
- Make sure there is a matching virtual transition in the super type.
- Remove the REDEFINED keyword from the transition in the sub type.
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.
- Change the transition from FINALIZED to REDEFINED in the super type.
- Make sure that you are redefining the correct transition.
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.
- You define a transition as REDEFINED in a sub type, when the same transition in the super type is not VIRTUAL.
- Make the transition in the super type VIRTUAL.
- Make sure that you are redefining the correct transition.
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.
- You use the keyword REDEFINED or FINALIZED for a transition that is not declared VIRTUAL in a super type.
- There is no super type.
- Make the transition in the super type VIRTUAL.
- Change the name in the sub type to match the correct transition in the super type
- Make sure the sub type inherits from the correct super 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.
- Change the keyword FINALIZED to REDEFINED in the super type.
- Make sure that you are trying to finalize the correct transition in the sub type.
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.
- You try to define a transition that already exists in a super type, without using the keyword REDEFINED or FINALIZED, or when the transition in the super type is not virtual.
- Add the keyword REDEFINED or FINALIZED to the transition in the sub type.
- Make sure that the transition in the super type is VIRTUAL.
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.
- You have a state in your state machine that has both an asterisk input transition and an asterisk save.
ERROR 155 A state (%1) may only contain one asterisk input
It is only allowed to have one asterisk input to a state.
ERROR 156 A state (%1) may only contain one asterisk save
It is only allowed to have one asterisk save to a state.
ERROR 157 Valid input signal set must be specified (in process/service %1) when no signal routes or channels are specified in the enclosing block/process (%2)
If there are no signal routes or channels specified to the process/service. "Signalset" must be used inside the process/service extended heading to specify the valid input signal set.
- You have a process or service that is not connected with the outer world via signal routes or channels, and you have not specified an input SIGNALSET.
- Add signal routes and channels to connect the process to the outer world.
- Add a SIGNALSET construct to the process and indicate the signals the process can receive.
ERROR 158 Value returning procedure expected
A value returning procedure was expected at this place.
ERROR 159 Type mismatch: sort %2 does not match %1
- You are using an integer where a boolean is expected. For instance, you are using an integer as a type for a parameter in an imported procedure signature that should match a boolean type parameter in a remote procedure signature.
ERROR 160 In/out parameter expected
An in/out parameter was expected according to the definition.
- You are using an IN parameter in an imported procedure signature that should match an IN/OUT parameter in a remote procedure signature.
- Change the imported procedure signature to use an IN/OUT parameter instead.
- Change the remote procedure signature to use an IN parameter instead.
ERROR 161 Missing parameter
A parameter is missing according to the definition.
- You omit a parameter or return value from an imported procedure signature that should match a remote procedure signature.
- Add the missing parameter or return value to the imported procedure signature.
- Remove the not wanted parameter or return value from the remote procedure signature.
ERROR 162 Virtual definitions only allowed in types
It is only allowed to use virtual in a type definition.
- Remove the keyword virtual from the definition of the diagram.
- Make the diagram with the virtual definition a type-based diagram.
ERROR 163 Virtual definition %1 does not conform to its virtuality constraint
ERROR 164 Redefinition of %1 does not conform to the virtuality constraint
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.
- You are using the ADDING construct for a gate in a diagram that does not inherit from another diagram.
- Remove the ADDING construct from the gate definition.
- Make the type-based diagram with the error inherit from another type-based diagram with an appropriate gate that you can use.
ERROR 166 Definition of %1 exists already in super type
An already defined gate cannot be defined again. If you want to add signals to an already existing gate, the word adding must be used.
- You declare a gate in a type that inherits from another type that already has a gate with the same name.
To remove the error in the above case:
- Rename one of the gates to get two gates in the sub type.
- Use the keyword ADDING in the gate in the sub type if you want to redefine the gate in the super type from the sub type.
To remove the error in the above case:
You also get this error either if:
- You try to redefine a finalized procedure in a sub type.
- You try to define a procedure, that has already been defined as virtual in a super type, without using REDEFINED.
To remove the error in the above cases, either:
- Make sure that you are redefining the correct procedure.
- Make sure that you use the REDEFINED keyword in the sub type, if you intend to redefine a procedure.
- Change the name of the procedure in the sub type, if you do not intend to redefine any existing procedure.
- Change the finalized procedure in the super type to be a redefined procedure.
ERROR 167 A gate with addition of signals must already be defined in a super type
Adding in gate definition cannot be used when defining a new gate.
- You declare a gate endpoint constraint with the keyword ADDING, but the gate is not already declared in any super type.
- Make sure that the name of the gate with the ADDING keyword matches the name of a gate in a super type.
- Remove the ADDING keyword to get a new gate that does not depend on any gate in a super type.
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.
- Reverse one of the gates.
- Merge the two gates, i.e. remove one of them, if they are intended to go in the same direction.
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.
- You have two gate endpoint constraints in a type-based diagram that are going in the same direction.
- You have two gate endpoint constraints in a type-based diagram that are not referencing the same outer entity.
- Make sure that the two gate endpoint constraints are going in different directions.
- Make sure that if you reference an outer type-based diagram, the same type-based diagram is referenced in both gate endpoint constraints.
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.
(Z.100: 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.
(Z.100: 2.5.1, 2.5.2)ERROR 173 Selected diagram not in an SDL system
The context must be available when analyzing part of a system.
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
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
ERROR 179 Undefined type %1 in inheritance specification
A type which is inherited is not defined or not visible.
- You in a signal declaration uses the keyword INHERITS and mention another signal that has not yet been defined.
ERROR 180 Undefined type %1 in virtuality constraint
The type %1 used in the virtuality constraint is undefined or not visible.
- Use the name of an existing and matching type-based diagram instead.
- Create a matching type-based diagram.
- Remove the virtuality constraint.
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.
- You have more than one connect statement for a signal route or channel going to or from the environment.
- Remove all but one connect statement going to or from the environment for the signal route or channel in question.
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.
- Merge all CONNECT statements mentioning the same signal route or channel into one CONNECT statement.
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.
(Z.100: 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.
- You connect two signal routes or channels that do not allow the same set of signals to be sent in each direction.
- Add or remove signals from the signal lists in the connected signal routes or channels to get matching signal lists.
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.
- You connect a signal route or channel to a signal route or channel one level up in the diagram hierarchy that does not include all signals of the signal route or channel in this diagram.
- Add the signals you want to send to the appropriate signal lists in the diagrams outside this diagram.
- Remove the not wanted and troublesome signal from the signal list of the channel or signal route that is connected to the world outside this diagram.
ERROR 186 In the implicit connection with %2 signal %1 is 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.
(Z.100: 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.
(Z.100: 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, block or substructure definition
A block definition must at least contain one process or a substructure.
(Z.100: 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.
(Z.100: 2.4.3)ERROR 196 Block definition must contain process or block definition(s) when containing connection(s)
A block definition cannot contain connections when no processes are defined.
(Z.100: 2.4.3)WARNING 197 Expansion of select definition is not yet implemented
The SDL concept select definition is not supported by the SDL Analyzer.
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 SDL to C compilers.
ERROR 198 Substructure definition must contain at least one block definition
At least one block must be defined inside a substructure.
- Add at least one block diagram with one or several processes to the substructure diagram.
- Instantiate a block type diagram in the substructure diagram.
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.
To remove the error in the above case, either:
- Remove the reference to the gate.
- Make the current diagram type-based, if you want to have gates to connect to in the environment.
- Make referenced diagrams instances of type-based diagrams, if you want to have gates to connect to in reference symbols.
- You use the VIA keyword when declaring a signal route or a channel, that is not going to or coming from an instantiation of a type-based diagram, and that is not going to or coming from the environment in a type-based diagram.
To remove the error in the above case:
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
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.
- You have a gate endpoint constraint in the type you try to instantiate, and you connect the gate to an instance that is not of the same type (or a descendant of that type) as the one mentioned in the gate endpoint constraint.
- Connect the gate to an instance of the same type (or a descendant of that type) as the one mentioned in the gate endpoint constraint.
- Remove or change the gate endpoint constraint.
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.
- You declare a channel or a signal route in a type-based diagram going to or coming from the environment without using a VIA keyword to specify the gate to use.
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.
- You declare a signal route or a channel going to or coming from an instantiation of a type-based diagram, without specifying the gate to connect to with a VIA keyword.
- Add a VIA keyword and the name of the gate in the instantiated type-based diagram that you want to connect to.
ERROR 208 Endpoints of the path %1 must be different
A channel/signal route cannot connect a block/process/service with itself.
ERROR 209 Endpoint %1 of channel %2 must be a block or process
A channel must be connected to at least one block!
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.
- You try to connect a signal route or channel to a diagram that is not visible from the current diagram.
- Connect the signal route or channel to the environment or to a diagram one level below the current diagram. If necessary, create more signal routes or channels in other diagrams to reach the diagram you want to communicate with.
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.
- The second FROM-TO-VIA-WITH construct is not going in exactly the reverse direction as compared to the first one.
- Make sure that the same connection item is used after both FROM in the first construct and after TO in the second construct.
- Make sure that the same connection item is used after both TO in the first construct and after FROM in the second construct.
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.
(Z.100: 2.5.2)ERROR 213 Return not allowed here
ERROR 214 Process definition must contain either processbody or service decomposition
Syntax requirement.
(Z.100: 2.4.4)ERROR 215 Process cannot contain timer definition when decomposed into services
ERROR 216 Revealed and exported variables only allowed in process and service
ERROR 217 Complete semantic analysis requires a system
ERROR 218 Procedure cannot contain stop
Syntax requirement.
(Z.100: 2.6.8.2.3)ERROR 219 Undefined view
ERROR 220 Step expression requires a loop variable
It is not allowed to omit the variable indication from a for statement when having a step expression.
- You have a for(x,y,z)-statement where x does not define a loop variable, but z uses a loop variable.
ERROR 221 Break without name or continue are only allowed within a loop
Break terminates a for loop and continue does the next iteration of a for loop. They can only be used in the context of for loops.
- You use a BREAK construct without a name outside a loop.
- You use a CONTINUE construct outside a loop.
- Add a name after the break keyword that matches a label that you want to jump to.
- Remove the break or continue construct.
- Put the break or continue construct within a for loop.
ERROR 222 Variable used before it is defined
A variable may only be used in statements following its definition.
- Move either the variable use or declaration to make sure that the variable declaration comes before the variable use.
- Make sure you are using the correct variable.
ERROR 223 A jump statement must be contained in a labeled statement with the given name
A jump statement is a more restrictive form of a join statement. The intent is to create less convoluted code.
- If the label and the break are on the same level, begin a pair of brackets after the label that contains the break.
ERROR 224 No receiver found
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.
(Z.100: 2.4.5)ERROR 226 Recursive package %1 in use clause
A package must not use itself.
- There is a self-referential chain of uses of packages. For instance package A uses package B, and package B uses package A.
- Break the self-referential chain of uses of packages by removing a USE statement in an appropriate place in the chain.
ERROR 227 Ending type keyword must match starting
A process type must be terminated with endprocess type and not just endprocess, and so on.
ERROR 228 Not Charstring sort and no proper operator (Length, ...)
ERROR 229 Service signal routes cannot be specified when no signal routes are specified in the enclosing block
ERROR 230 Service decomposition must contain at least one service definition
ERROR 231 No proper Length operator found
ERROR 232 Recursive include of file %1
The file is included recursively.
ERROR 233 Qualifier in component command not in SDL system
All parts (components) of a program must belong to the same system.
ERROR 234 More than one system
Can only analyze one system at a time.
ERROR 235 Code generation requires a system
ERROR 236 Valid input signal set cannot contain a timer (%1)
ERROR 237 Two signals (%1 and %2) in the complete valid input signal set are on different refinement levels of the same signal
ERROR 238 Two signals (%1 and %2) among the output-signals of the process are on different refinement levels of the same signal
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.
- You try to receive a signal in an input, but you have not declared that anyone can send that signal to this process.
- Check that you are trying to receive the correct signal.
- Make sure that the signal can be sent to this process via signal routes and channels, or by including the signal in a SIGNALSET construct for this process.
ERROR 241 Error creating directory %1
A message from the operating system is following this and hopefully clarifies the problem.
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 Actual in/out param sort %1 does not match %2
The sort of actual and formal in/out parameters of procedures must be identical on the syntype level.
- Call the procedure with a parameter of the correct type.
- Change the procedure to accept a parameter of the wanted type.
ERROR 244 Call procedure from expression or supply variable parameter
A value returning procedure should be called from an expression.
- Call the value-returning procedure from an expression in a task instead.
- Call another, similar procedure that do not return a value.
- Force the procedure to not return a value.
WARNING 245 Trailing parameter of sort %1 omitted
ERROR 246 Last param of procedure called from expr is not in/out
Actual in/out procedure parameters may not be omitted.
- You are calling a procedure in an expression, and the called procedure does not have a RETURNS statement.
- Add a RETURNS statement to the procedure definition, and make sure the procedure returns a value of the correct type.
ERROR 247 Actual in/out param cannot be omitted
The actual parameter can be omitted if the formal is in.
- You call a procedure without less actual parameters than all formal parameters declared for the procedure.
- Add the missing actual parameters to match all formal parameters declared for the procedure.
- Remove any not wanted formal parameters from the declaration of the procedure.
WARNING 248 License %1 will expire in %2 days
This is a notification that some license will expire in the near future.
ERROR 249 Aborted by exit request
This indicate that the analyzer received a stop message
ERROR 250 Component and Thread commands requires a previous Program command
Issue a program command to set the name of the executable before adding threads or components to it.
ERROR 251 Change directory: %1: %2
An error occurred when changing default (working) directory.
ERROR 252 Get work dir: %1: %2
The analyzer failed to obtain current working directory.
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.
(Z.100: 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.
- You omit a connect statement saying that a channel or signal route is connected to the environment, when the declaration of the channel or signal route indicates that it is connected to the environment.
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.
(Z.100: 2.6.4, 2.6.8.1)ERROR 256 Post Master
A problem occurred when communicating with some other tool using the PostMaster.
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.
(Z.100: 4.9)ERROR 259 Ending name (%1) cannot be qualified (except for remote definitions)
- You are using a qualifier when specifying the name of the diagram at the end of the diagram definition.
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.
(Z.100: 3.2.3)ERROR 261 Answers are not mutually exclusive
Exactly one answer in a decision must match the question. For instance, a boolean decision with more than 2 answers or 2 answers that are both true or both false will produce this message.
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.
(Z.100: 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.
(Z.100: 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.
- You have a connection statement connecting an outer channel or signal route with a non-existing inner channel or signal route.
- Change the name of the second connection point to match an existing inner signal route or channel.
- Add an inner signal route or channel with the correct name.
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.
- You use a signal route or a channel in a CONNECT statement, and the signal route or channel is not connected to the environment.
- Check that the CONNECT statement is connecting the correct signal route or channel in this diagram.
- Change the signal route or channel in this diagram to go to the environment with one of its endpoints.
- Remove the connect statement.
ERROR 266 System definition must contain at least one block or process definition
An SDL system must contain at least one block or process.
- Add at least one block with one or several processes to your SDL system.
- Instantiate any existing block type diagrams.
WARNING 267 Optional parameter of sort %1 omitted
WARNING 268 Gate must be connected
ERROR 269 Expression evaluates to error
ERROR 270 Selected definition not allowed here
ERROR 271 All packages must either be before or after the system
The system should follow the package list according to SDL. For backwards compatibility the analyzer also accepts a package list after the system, but not both at the same time. In the Organizer this means that the icons for all packages used by a system should be above the system icon.
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 SDL to C Compiler 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.
INFO 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.
- You instantiate a block type in a block reference symbol with a number of instances smaller than one.
ERROR 280 Unreachable path %1 in VIA
The path %1 must be connected to the process instance.
- You send a signal from a process and the static structure of the SDL system does not declare that you are allowed to send that signal the way you want.
- Add signal routes and channels as needed (with your signal in the signal lists), to reach the wanted process or the environment.
- Remove the sending of that particular signal.
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.
- You send a signal from a process and the static structure of the SDL system does not declare that you are allowed to send that signal the way you want.
- Add signal routes and channels as needed (with your signal in the signal lists), to reach the wanted process or the environment.
- Remove the sending of that particular signal.
WARNING 282 Several possible paths in VIA list
There are several paths that can convey the signal, one of them will be non deterministically chosen.
WARNING 283 Several possible paths
There are several paths that can convey the signal, one of the paths will be non deterministically chosen during execution.
WARNING 284 Set-Case-Sensitive should be the first command to the analyzer
ERROR 285 Hex string literal must have an even length
This applies to values for types that are strings of bytes.
ERROR 286 Bit string literal must have a length modulo 8
This applies to values for types that are strings of bytes.
ERROR 287 Literal must be one octet long
This applies to values for types that are one byte.
WARNING 288 No matching answer for %2
If a decision (or transition option) is executed with a question not covered by any answer it will be an error. (Z.100:2.7.5 and 4.3.4)
ERROR 289 Expression in transition option evaluates to error
One of the expressions in a transition option is erroneous.
(Z.100: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
- Change the value to one of the allowed ones.
- Change the syntype to allow the value.
- Use a different sort allowing the value.
ERROR 292 Maximal number of instances equals zero
A process should have at least one instance.
- Change the maximum number of instances to one or more.
- Remove the diagram with maximum number of instances set to zero.
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.
- Increase the maximum number of instances to at least the initial number of instances.
- Decrease the initial number of instances to less than or equal to the maximum number of instances.
ERROR 294 Not allowed to change remote procedure in redefinition
WARNING 295 Consider adding else answer
If a decision (or transition option) is executed with a question not covered by any answer it will be an error. (Z.100:2.7.5 and 4.3.4)
ERROR 296 Redefined or finalized procedure must be exported when base is
INFO 297 Error limit reached, terminating
The number of diagnostics that the Analyzer has reported exceeds the value of the limit.
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 Remote entity may only be exported once in a process
This applies to exported procedures and variables.
ERROR 306 No input specified
There is no input set to the Analyzer using the set-input command.
WARNING 307 %1: unknown, line ignored!
ERROR 308 More than one package match use statement
Use Modules to group systems together with their package lists to make package names unique within a module.
INFO 309 Location of the shadowed definition
ERROR 310 Selected item %1 is not connected to a file
The Organizer has ordered to analyze a diagram that is not connected to a file.
ERROR 311 Signal %1 found in opposite direction in connection
- You connect two signal routes or channels where a signal is defined according to the signal lists to go in different directions on the inside and on the outside of the connection.
- Reverse the direction of one of the signal routes or channels, at least for the signal that caused the error.
ERROR 312 Syntax error in rule %1, symbol %2 found but one of the following expected:
ERROR 313 Syntax error, symbol %1 found but one of the following expected:
ERROR 314 Lexical error in rule %1, symbol %2 found but one of the following expected:
- You have typed a character or keyword that is not allowed in a CHARSTRINGLITERAL in a place where the syntax checker thinks there should be a CHARSTRINGLITERAL.
- You have used an SDL keyword as a name for a variable.
To remove the error in the above cases, either:
- Examine the pointed out character or keyword to see if it really belongs there.
- Try to find out why the syntax checker expects a CHARSTRINGLITERAL; did you intend to have a CHARSTRINGLITERAL there?.
- Rename any variable that you have given the same name as an SDL keyword.
- You have constructed a word or token out of single characters that does not match allowed word or tokens in SDL.
To remove the error in the above case:
ERROR 315 Lexical error, symbol %1 found but one of the following expected:
ERROR 316 File %1 not found in environment variable %2 %3, check installation!
Check the installation. If the error persists, contact IBM Rational Customer Support. Contact information for IBM Rational Customer Support can be found in How to Contact Customer Support.
ERROR 317 Outside connect item %1 is locally defined
- Your connect statement mentions an inner channel or signal route instead of a channel or signal route outside the current diagram as the first connect item.
- Swap places (if the second connect item is wrong too) on the inner and outer channel or signal route in the connect statement.
- If there is a name conflict with a locally defined item, then add a qualifier to the outer connect item.
WARNING 318 %1 : signal not used
Here is a small explanation valid for all <entity> not used warning messages:
- Remove the declaration.
- Start using the entity.
- Rename the entity in the declaration to match a used entity of the same type that does not have a declaration.
- Change the type in the declaration to match a used entity with the same name but with a different type (that does not have a declaration).
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 : remote variable not used
The remote variable %1 should be used.
WARNING 327 %1 : sort not used
WARNING 328 %1 : generator not used
The generator %1 should be used.
WARNING 329 %1 : label not used
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
ERROR 336 Input to Instance generator must be a system
ERROR 337 Operator diagram/definition not allowed where constant required
- You call an operator in a place where a constant is required, for instance in a declaration of a variable.
- Remove the operator call, and replace it with a constant if needed.
- Call a non operator definition operator.
WARNING 338 %1 : operator diagram/definition not used
WARNING 339 %1 : operator not used
WARNING 340 %1 : remote procedure not used
ERROR 341 No matching variable, formal parameter, synonym or literal
ERROR 342 Literal %1 in literal renaming is not defined in parent sort
ERROR 343 No matching field selection, array element access or prefix operator
ERROR 344 No matching quoted operator
- Check that you are using two arguments for infix operators and one argument for monadic operators.
- Check that the operators you are using are of the correct type.
ERROR 345 No matching (. .)
ERROR 346 No visible variable or formal parameter with this name
ERROR 347 Type mismatch in component selection of variable or formal parameter
ERROR 348 No matching monadic operator
ERROR 349 No matching infix operator
INFO 350 %1 is one of the possible matching types
ERROR 351 No matching remote variable in variable definition
INFO 352 %1 is one of the visible definitions
WARNING 353 Type mismatch between actual and formal parameter
The types of the actual and formal parameters are implemented with different typedef, i.e. they may be of different size. Only checked for functions that cannot handle length mismatch.
ERROR 354
ERROR 355 No matching remote variable in import definition
ERROR 356
ERROR 357 No matching character string
ERROR 358 No matching choice primary
ERROR 359 Now not allowed where constant required
ERROR 360 No matching now expression
ERROR 361 Import expression not allowed where constant required
ERROR 362 PId expression not allowed where constant required
ERROR 363 No matching PId expression
ERROR 364 View expression not allowed where constant required
ERROR 365 Timer active expression not allowed where constant required
ERROR 366 Any expression not allowed where constant required
ERROR 367 No matching dereferencing operator
ERROR 368 Data base error
An internal error occurred in the Analyzer. Please send a report to IBM Rational Customer Support. Contact information for IBM Rational Customer Support can be found in How to Contact Customer Support.
ERROR 369 No matching field selection
- You try to access a field in a struct using a name that does not represent any field in the struct.
- You try to access a field in a struct whose sort does not match the one expected.
- Make sure you are using the correct name to access a field in the struct.
- Add a field in the struct with the wanted name.
- If required, reference a conversion operator to have the field match the sort required.
ERROR 370 Type mismatch for procedure return value
ERROR 371 Type mismatch for variable, formal parameter, synonym or literal
ERROR 372 No visible variable, formal parameter, synonym, literal or operator with this name
- You use the name of a variable, formal parameter, synonym, literal or operator that is not defined in the current scope.
ERROR 373 No visible synonym or literal with this name
- Correct the spelling mistake, if it was not meant to be a synonym or literal.
- Add a synonym or literal with the given name.
ERROR 374 Variable or formal parameter not allowed where constant required
ERROR 375 Type mismatch for synonym or literal
ERROR 376 Only one reference to each diagram allowed
Several diagrams connected to the same file.
ERROR 377 Keyword call required for procedure call
ERROR 378 Several macrodefinitions have the same name %1
The name of a macro must be unique.
WARNING 379 Macrodefinition %1 was never called
ERROR 380 Names separated by %, %1%%2, where neither is a formal parameter nor MACROID in macrodefinition %3
WARNING 381 Formal parameter %1 is never used in macrodefinition %2
The formal parameter %1 should be used in the macro definition
ERROR 382 The macrodefinition name is %1, but the endmacro name is %2
The names in the macro definition and the endmacro must be equal.
ERROR 383 Two formal parameters with the same name %1 in macrodefinition %2
Two formal parameters of a macro cannot have the same name.
ERROR 384 No matching macrodefinition found
The corresponding macro definition is missing.
ERROR 385 A macro may not call itself
A macro definition cannot be circular.
WARNING 386 No macro found
The system does not contain any macros or calls.
ERROR 387 Start transition expected
A process or procedure definition must begin with a start transition.
ERROR 388 Illegal redeclaration of operator definition
- Rename one of the operators if they are different and you need them both.
- Remove one of the operator definitions.
ERROR 389 No matching operator signature found
The operator must be defined for this signature.
ERROR 390 This unexpected
The keyword this is only allowed in a procedure call, process create or "output to".
ERROR 391 Context parameter %1 not allowed
ERROR 392 Call this invalidated by adding parameters to sub type
Call this cannot be used when formal parameters are added in the subtype.
- You use the keyword THIS in a procedure call and the called procedure is a super type to a sub type that adds parameters to be used in a procedure call.
- Make both the sub type and the super type use the same set of parameters by declaring all parameters in the super type if you intend to call the sub type.
- Remove the THIS keyword if you intend not to call the sub type.
INFO 393 Instance path to the problem in previous message
This message provides additional information that may be used to locate the source of error in the previous message. This message may appear repeated times, depending on the depth of the SDL structure where the previous error is detected.
ERROR 394 Package Predefined expected, check installation
File predef.sdl does not contain the package Predefined. The error message appears only when you have altered the installation in an improper way.
ERROR 395 Type mismatch for view expression
- You view a variable of the wrong type. For instance, you assign a variable of type boolean the value of a viewed variable of type integer.
- Change the type either of the assigned variable or the viewed variable to match each other.
- View another variable instead, that has the correct type.
- Assign to another variable instead, that has the correct type.
ERROR 396 Viewed variable %1 is not revealed in block %2
The viewed variable must be declared as revealed in block %2.
ERROR 397 Context parameters are not supported
Context parameters are not implemented. Consider using an alternative approach.
WARNING 398 One line external formalism name expected on same line as alternative keyword
Syntax error! When using alternative the name of the alternative data formalism must occur on the same line as the alternative keyword.
ERROR 399 Type mismatch for timer active expression
ERROR 400 Type mismatch for any expression
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |