TOP

Errors (0001-0499) | Errors (0500-0999) | Errors (1000-1299) | Errors (1300-9999)

Compiler Errors Reference (0001-0499)

A0001W

Message Format

A0001W: 'type reference' is incorrectly tagged. The APPLICATION tag number has already been used.

Message Cause

Under ASN.1:1990 syntax rules, APPLICATION tags must be unique within a module. A particular APPLICATION tag number has been used more than once.

Example

Module-A0001W DEFINITIONS ::= BEGIN
   Code1 ::= [APPLICATION 1] INTEGER
   Code2 ::= [APPLICATION 1] REAL
END

Error Message

"a0001w.asn", line 3 (Module-A0001W): A0001W: 'Code2' is incorrectly tagged.  The APPLICATION tag number has already been used.

Possible Solution

Each tag number must be unique. Remove the duplicate tag number and add a unique number.

C0002E

Message Format

C0002E: COMPILER ERROR #20.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

A0003E

Message Format

A0003E: 'type reference' contains a circular definition.

Message Cause

One or more types are circularly defined.

Example

Module-A0003E DEFINITIONS ::= BEGIN
   Name1 ::= Name2
   Name2 ::= Name1
END

Error Message

"a0003e.asn", line 2 (Module-A0003E): A0003E: 'Name1' contains a circular definition.


"a0003e.asn", line 3 (Module-A0003E): A0003E: 'Name2' contains a circular definition.

Possible Solution

Remove the circular reference.

A0004E

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

A0008E

Message Format

A0008E: The element 'identifier' has an ANY DEFINED BY identifier 'identifier' which is not defined.

Message Cause

The identifier referred to by the ANY DEFINED BY is not found within the same SEQUENCE as the ANY DEFINED BY. This error usually occurs when the identifier is either misspelled or is defined outside the SEQUENCE.

Example

Module-A0008E DEFINITIONS ::= BEGIN
   OperationPDU ::= SEQUENCE {
      priority    INTEGER,
      parameters  ANY DEFINED BY number
   }
END

Error Message

"a0008e.asn", line 4 (Module-A0008E): A0008E: The element 'parameters' has an ANY DEFINED BY identifier 'number' which is not defined.

Possible Solution

Consider the following solutions:

Replace the identifier with one that belongs to the same SET or SEQUENCE as contains the ANY DEFINED BY.
Correct the spelling of the identifier.

A0009E

Message Format

A0009E: The ANY DEFINED BY identifier 'identifier' is not defined.

Message Cause

This error is generated when an ANY DEFINED BY references an identifier that is not defined.

Example

Module-A0009E DEFINITIONS ::= BEGIN
   OperationPDU ::= SEQUENCE {
      priority  INTEGER,
                ANY DEFINED BY number
   }
END

Error Message

"a0009e.asn", line 4 (Module-A0009E): A0009E: The ANY DEFINED BY identifier 'number' is not defined.

Possible Solution

Replace the undefined identifier with one that is defined in the input ASN.1 syntax.

A0010E

Message Format

A0010E: The element 'identifier' has an ANY DEFINED BY with identifier 'identifier' which is optional.

Message Cause

The type referenced by an ANY DEFINED BY is used as a key to determine how the ANY DEFINED BY is handled. Therefore it must be present and cannot be specified as optional.

Example

Module-A0010E DEFINITIONS ::= BEGIN
   OperationPDU ::= SEQUENCE {
      priority    INTEGER OPTIONAL,
      parameters  ANY DEFINED BY priority
   }
END

Error Message

"a0010e.asn", line 4 (Module-A0010E): A0010E: The element 'parameters' has an ANY DEFINED BY with identifier 'priority' which is optional.

Example

Module-A0014E DEFINITIONS ::= BEGIN
   Name ::= OCTET STRING (SIZE(-2..10))
END

Error Message

"a0014e.asn", line 2 (Module-A0014E): A0014E: The size constraint for 'Name' must be defined as a non-negative integer.

Possible Solution

Remove all negative integers from the size constraint and make sure you define only positive integers.

A0015E

Message Format

A0015E: Value 'value reference' must be an object identifier value.

Message Cause

A node in an object identifier is neither an INTEGER value nor an object identifier value. It is the wrong type.

Example

Module-A0015E DEFINITIONS ::= BEGIN
   OperationID ::= OBJECT IDENTIFIER
   iso2 GeneralString ::= "{ 1 0 }"
   ftam1 OperationID  ::= { iso2 8571 2 1 }
END

Error Message

"a0015e.asn", line 4 (Module-A0015E): A0015E: Value 'iso2' must be an object identifier value.

Possible Solution

Ensure that all nodes are specified as OBJECT IDENTIFIERs or INTEGERs.

A0016E

Message Format

A0016E: The object identifier value 'value reference' is not defined.

Message Cause

A node in an object identifier value is not defined.

Example

Module-A0016E DEFINITIONS ::= BEGIN
   ModuleOI ::= OBJECT IDENTIFIER
   b ModuleOI ::= { i 4 5 6 7 }
END

Error Message

"a0016e.asn", line 3 (Module-A0016E): A0016E: The object identifier value 'i' is not defined.

Possible Solution

Replace the undefined node identifier with one that is defined.

A0017W

Message Format

A0017W: 'identifier' is an incorrect identifier for number.

Message Cause

The ASN.1 standard allows OBJECT IDENTIFIERs beginning with { 0 0 } to have a third node. The third node can be a letter a through z that optionally has a corresponding number, namely, a(1), b(2), c(3), d(4), ..., z(26). The flagged OBJECT IDENTIFIER uses one of the letters but with an incorrect number, for example, a(5).

Example

Module-A0017W DEFINITIONS ::= BEGIN
   ModuleOI ::= OBJECT IDENTIFIER
   b ModuleOI ::= { 0 0 a(2) }
END

Error Message

"a0017w.asn", line 3 (Module-A0017W): A0017W: 'a' is an incorrect identifier for 2.

Possible Solution

Replace the number in the third node with its corresponding predefined value. In this case, a(2) is replaced with a(1).

C0018W

Message Format

C0018W: Runtime constraint checking for 'type reference' will be disabled since one or more values used as SingleValueConstraints have a C representation that differs from the C representation of the type being constrained.

Message Cause

The value specified in a SingleValueConstraint is incompatible with the type constrained. The OSS run-time constraint checking routines require that values in SingleValueConstraints have the same C representation as the type constrained (for complex types such as SEQUENCE).

Example

Module-C0018W DEFINITIONS ::= BEGIN
   A  ::= SEQUENCE { a INTEGER --<SHORT>--}
   a A ::= { a 2 }
   B  ::= SEQUENCE { a INTEGER --<LONG>--} (a)
END

Error Message

"c0018w.asn", line 4 (Module-C0018W): C0018W: Runtime constraint checking for 'B' will be disabled since one or more values used as SingleValueConstraints have a C representation that differs from the C representation of the type being constrained.

Possible Solution

Consider the following solutions:

Remove the SingleValueConstraint, which in this case is (a).
Replace the type of the value in the SingleValueConstraint with one that has the same representation as the type constrained.

A0019E

Message Format

A0019E: 'identifier' is incorrect identifier for the third component of the object identifier value.

Message Cause

An OBJECT IDENTIFIER value begins with { 0 0 } and the NameNumber pair in the third position conflicts with one of the preset NameNumber pairs for values that begin with { 0 0 }. The preset pairs are:

a(1), b(2), c(3), d(4), ..., z(26).

A0020E

Message Format

A0020E: Nameform not allowed for component index 'identifier' of the object identifier value.

Message Cause

The input ASN.1 syntax contains an OBJECT IDENTIFIER value with nodes that are required to be numbers (e.g., in: {iso standard 8571 abstract-syntax ftam-pci ...}, the third component must be a number), but are not found to be so.

A0021E

Message Format

A0021E: Time value "time value" should begin with a two-digit/four-digit year.

Message Cause

The year position of the flagged time value contains a non-numeric character. For GeneralizedTime the year is found in positions 1-4; for UTCTime the year is found in positions 1-2.

Example

Module-A0021E DEFINITIONS ::= BEGIN
   time1 UTCTime         ::= "DC9310252013.31Z"  -- Invalid
   time2 GeneralizedTime ::= "DC199310252013.31" -- Invalid
   time3 GeneralizedTime ::= "199310252013.31"   -- Valid
END

Error Message

"a0021e.asn", line 2 (Module-A0021E): A0021E: Time value "DC9310252013.31Z" should begin with a two-digit year.


"a0021e.asn", line 3 (Module-A0021E): A0021E: Time value "DC199310252013.31" should begin with a four-digit year.

Possible Solution

Change the incorrect time values to start with a two-digit or four-digit year.

A0022E

Message Format

A0022E: The time component in time value "time value" must be between lower boundary and upper boundary.

Message Cause

This error occurs when the time value of one or more components is outside the accepted range of values.

Example

Module-A0022E DEFINITIONS ::= BEGIN
   StartTime ::= GeneralizedTime
   time1 StartTime ::= "199331232021.06"          -- Invalid month
   time2 StartTime ::= "199310322021.06"          -- Invalid day
   time3 StartTime ::= "199310232521.06"          -- Invalid hour
   time4 StartTime ::= "199310232061.06"          -- Invalid minutes
   time5 StartTime ::= "19931023205165.06"        -- Invalid seconds
   time6 StartTime ::= "19931023205155.06-24"     -- Invalid hour diff
   time7 StartTime ::= "19931023205155.06-0865"   -- Invalid minute diff
END

Error Message

"a0022e.asn", line 3 (Module-A0022E): A0022E: The month in time value "199331232021.06" must be between 01 and 12.


"a0022e.asn", line 4 (Module-A0022E): A0022E: The day in time value "199310322021.06" must be between 01 and 31.

 
"a0022e.asn", line 5 (Module-A0022E): A0022E: The hour in time value "199310232521.06" must be between 00 and 23.


"a0022e.asn", line 6 (Module-A0022E): A0022E: The minutes in time value "199310232061.06" must be between 00 and 59.


"a0022e.asn", line 7 (Module-A0022E): A0022E: The seconds in time value "19931023205165.06" must be between 00 and 59.


"a0022e.asn", line 8 (Module-A0022E): A0022E: The hour differential in time value "19931023205155.06-24" must be between 00 and 23.


"a0022e.asn", line 9 (Module-A0022E): A0022E: The minute differential in time value "19931023205155.06-0865" must be between 00 and 59.

Possible Solution

Make sure the time value components are valid.

A0023E

Message Format

A0023E: The fractional part of the minutes in the time value "time value" must have at least 1 digit.

Message Cause

The period (".") at the end of the time value indicates that a fractional component is going to be used and it must be followed by a sequence of one or more digits.

Example

Module-A0023E DEFINITIONS ::= BEGIN
   StartTime ::= GeneralizedTime
   time1 StartTime ::= "199310232051."
   time2 StartTime ::= "19931023205122."
END

Error Message

"a0023e.asn", line 3 (Module-A0023E): A0023E: The fractional part of the minutes in the time value "199310232051." must have at least 1 digit.


"a0023e.asn", line 4 (Module-A0023E): A0023E: The fractional part of the seconds in the time value "19931023205122." must have at least 1 digit.

Possible Solution

Remove the decimal point at the end of the time value or add a numeric fractional component.

A0024W

Message Format

A0024W: The extra characters at the end of the time value "time value" will be ignored.

Message Cause

The compiler found and ignored extra characters that follow a time value.

Example

Module-A0024W DEFINITIONS ::= BEGIN
   StartTime ::= UTCTime
   time1 StartTime ::= "9310251421Z-0500"
   time2 GeneralizedTime ::= "19931025142122.56PM"
END

Error Message

"a0024w.asn", line 3 (Module-A0024W): A0024W: The extra characters at the end of the time value "9310251421Z-0500" will be ignored.


"a0024w.asn", line 4 (Module-A0024W): A0024W: The extra characters at the end of the time value "19931025142122.56PM" will be ignored.

Possible Solution

Remove the extra characters.

A0025E

Message Format

A0025E: The UTCTime value "time value" must end with either a 'Z' or a time differential.

Message Cause

The UTCTime time value does not end in uppercase Z.

Example

Module-A0025E DEFINITIONS ::= BEGIN
   StartTime ::= UTCTime
   time1 StartTime ::= "9301232021z"
   time2 StartTime ::= "9301232021"
END

Error Message

"a0025e.asn", line 3 (Module-A0025E): A0025E: The UTCTime value "9301232021z" must end with either a 'Z' or a time differential.


"a0025e.asn", line 4 (Module-A0025E): A0025E: The UTCTime value "9301232021" must end with either a 'Z' or a time differential.

Possible Solution

Make sure the last character of the UTCTime value is uppercase Z.

A0026E

Message Format

A0026E: Circular definitions are not supported for ContainedSubtype (detected in 'type reference').

Message Cause

Two or more ContainedSubtypes form a circular reference.

Example

Module-A0026E DEFINITIONS ::= BEGIN
   OperationCode ::= PrintableString (INCLUDES Code)
   Code          ::= PrintableString ("M"|"R"|INCLUDES OperationCode)
END

Error Message

"a0026e.asn", line 3 (Module-A0026E): A0026E: Circular definitions are not supported for ContainedSubtype (detected in 'Code').

  
"a0026e.asn", line 2 (Module-A0026E): A0026E: Circular definitions are not supported for ContainedSubtype (detected in 'OperationCode').

Possible Solution

Remove the circular reference from the ContainedSubtypes.

A0027E

Message Format

A0027E: 'type reference' is defined with INCLUDES of the wrong type.

Message Cause

The input ASN.1 syntax contains an included type that is not compatible with the parent type.

NOTE: This message may also be issued for information object instances that do not conform to their WITH SYNTAX specifications. For example, an IDENTIFIED BY is missing in an ABSTRACT-SYNTAX class instance.

Example

Module-A0027E DEFINITIONS ::= BEGIN
   OperationCode ::= PrintableString ("1"|"40")
   Code          ::= OCTET STRING (INCLUDES OperationCode)
END

Error Message

"a0027e.asn", line 3 (Module-A0027E): A0027E: 'Code' is defined with INCLUDES of the wrong type.

Possible Solution

Make sure the included subtype matches the parent type.

A0028E

Message Format

A0028E: 'type reference' contains a ValueRange subtype, but ValueRange can only be applied to INTEGER or REAL types.

Message Cause

A ValueRange subtype is applied to types that do not support it. A ValueRange subtype can be applied only to an INTEGER or a REAL type.

Example

Module-A0028E DEFINITIONS ::= BEGIN
   A ::= PrintableString ("Antelope" .. "Zebra")
END

Error Message

"a0028e.asn", line 2 (Module-A0028E): A0028E: 'A' contains a ValueRange subtype, but ValueRange can only be applied to INTEGER or REAL types.

Possible Solution

Remove the ValueRange subtype or replace it with a SingleValue or another subtype.

A0029E

Message Format

A0029E: It is invalid to apply the SIZE constraint to type reference.

Message Cause

A SIZE constraint is applied to types that do not support it. A SIZE constraint can be applied to a BIT STRING, OCTET STRING, character string, SET OF, or SEQUENCE OF.

Example

Module-A0029E DEFINITIONS ::= BEGIN
   Password ::= VisibleString (SIZE(6..20)) -- Valid
   Hundreds ::= INTEGER (SIZE(100..999))    -- Invalid
END

Error Message

"a0029e.asn", line 3 (Module-A0029E): A0029E: It is invalid to apply the SIZE constraint to Hundreds.

Possible Solution

Remove the SIZE constraint or replace it with a ValueRange or another subtype.

A0030E

Message Format

A0030E: 'type reference' is defined with an illegal size constraint.

Message Cause

A SIZE constraint does not conform to the ASN.1 standard. The constraint must be a subtype of INTEGER (0 .. MAX).

Example

Module-A0030E DEFINITIONS ::= BEGIN
   Evens         ::= INTEGER (2 | 4 | 6 | 8 | 10)
   Vowels        ::= [1] VisibleString ("A" | "E" | "I" | "O" | "U")
   EvenStrings   ::= [2] VisibleString (SIZE(INCLUDES Vowels)) -- Invalid
   OddStrings    ::= BIT STRING (SIZE(1 | 3 | 5 | 7 | 9))
   Password      ::= [3] VisibleString (SIZE(6..20))           -- Valid
END

Error Message

"a0030e.asn", line 4 (Module-A0030E): A0030E: 'EvenStrings' is defined with an illegal size constraint.

Possible Solution

Redefine the SIZE constraint with valid INTEGER values.

A0031E

Message Format

A0031E: 'type reference' is defined using FROM incorrectly.

Message Cause

A FROM subtype constraint does not contain characters or it contains an invalid set of characters.

Example

Module-A0031E DEFINITIONS ::= BEGIN
   A ::= [0] VisibleString (FROM ("A" | "E" | "I" | "O" | "U")) -- Valid
   B ::= [1] VisibleString (FROM (INCLUDES A))                  -- Valid
   D ::= [2] VisibleString (FROM (SIZE(5)))                     -- Invalid
   E ::= [3] VisibleString (FROM (FROM(INCLUDES A)))            -- Invalid
   F ::= INTEGER (FROM (SIZE(5)))                               -- Invalid
END

Error Message

"a0031e.asn", line 4 (Module-A0031E): A0031E: 'D' is defined using FROM incorrectly.


"a0031e.asn", line 5 (Module-A0031E): A0031E: 'E' is defined using FROM incorrectly.


"a0031e.asn", line 6 (Module-A0031E): A0031E: 'F' is defined using FROM incorrectly.

Possible Solution

Replace the invalid contents of the FROM subtype with valid characters or remove the subtype.

A0032E

Message Format

A0032E: FROM is used incorrectly with 'type reference'. The permitted alphabet subtype (FROM) can only be applied to character string types, or types formed from them by tagging.

Message Cause

A FROM subtype constraint is applied to a non-character string type.

Example

Module-A0032E DEFINITIONS ::= BEGIN
   Type1 ::= INTEGER (FROM (1|2|3))
END

Error Message

"a0032e.asn", line 2 (Module-A0032E): A0032E: FROM is used incorrectly with 'Type1'. The permitted alphabet subtype (FROM) can only be applied to character string types, or types formed from them by tagging.

Example

Module-A0037W DEFINITIONS ::= BEGIN
   number INTEGER ::= 5
   Code  ::= CHOICE {
      int  INTEGER,
      real REAL
   }
   value  Code ::= number         -- ok, but discouraged
   value2 Code ::= int : number   -- preferred
END

Error Message

"a0037w.asn", line 4 (Module-A0037W): A0037W: Assuming 'number' is the choice value for element 'int'.


value Code ::= number -- ok, but discouraged

Possible Solution

Replace the value assignment with an identifier-colon-value on the right-hand side.

A0038W

Message Format

A0038W: Assuming 'value' is the choice value for element #x.

Message Cause

A value assignment of a CHOICE type does not have an identifier associated with it.

Example

Module-A0038W DEFINITIONS ::= BEGIN
   number INTEGER ::= 5
   Code ::= [0] CHOICE { INTEGER, REAL }
   value Code ::= number
END

Error Message

"a0038w.asn", line 4 (Module-A0038W): A0038W: Assuming 'number' is the choice value for element #1.

value Code ::= number

Example

Module-C0042E DEFINITIONS ::= BEGIN
   Name2 ::= CHOICE {
      a INTEGER --<NULLTERM>--,
      b VisibleString
   }
END

Error Message

"c0042e.asn", line 3 (Module-C0042E): C0042E: 'a' is the wrong type for the NULLTERM directive.

Possible Solution

To find out more information, see Compiler Directives.

C0043I

Message Format

C0043I: x error messages, y warning messages and z informatory messages issued.

Message Cause

This message contains information about the number of error, warning, and informatory messages issued.

Example

Module-C0043I DEFINITIONS ::= BEGIN
   MySet ::= SET {
      a  [1] INTEGER
      b  [2] BOOLEAN
   }
END

Error Message

"c0043i.asn", line 4 (Module-C0043I): A0120E: Parsing error: expecting '}' or a ',' but found value reference or identifier.

b [2] BOOLEAN


"c0043i.asn", line 4 (Module-C0043I): C0246I: Skipping to line 6.

END


C0043I: 1 error messages, 0 warning messages, and 1 informatory messages issued.

Possible Solution

To ignore the messages, specify the -suppress 0043 option.

C0044E

Message Format

C0044E: UTF8String characters in the range from {0,0,216,0} to {0,0,223,255}, from {0,0,255,254} to {0,0,255,255} and from {128,0,0,0} to {255,255,255,255} are not valid.

Message Cause

The input ASN.1 syntax contains value notation for a UTF8String, but one or more of the characters assigned falls in the reserved character range as defined by the ASN.1 standard.

Example

Module-C0044E DEFINITIONS ::= BEGIN
   UString ::= UTF8String
   myName UString ::= {{0,0,0,65}, {0, 0,255,254}}
END

Error Message

"c0044e.asn", line 3 (Module-C0044E): C0044E: UTF8String characters in the range from {0,0,216,0} to {0,0,223,255}, from {0,0,255,254} to {0,0,255,255} and from {128,0,0,0} to {255,255,255,255} are not valid. myName UString ::= {{0,0,0,65}, {0, 0,255,254}}

Possible Solution

Replace the invalid characters from the string with values that are allowed for UTF8String types.

C0045E

Message Format

C0045E: The LONGLONG and HUGE directives are not permitted on the OBJECT IDENTIFIER type 'type reference'.

Message Cause

The input ASN.1 syntax contains an invalid compiler directive application to the OBJECT IDENTIFIER type.

Possible Solution

Remove the invalid directive application.

A0046E

Message Format

A0046E: Type 'type reference' has an element 'identifier' which must exist.

Message Cause

A WITH COMPONENTS constraint does not include all the elements specified in the SET type.

Example

Module-A0046E DEFINITIONS ::= BEGIN
   Set  ::= SET {
      d BOOLEAN,
      e INTEGER,
      f VisibleString
   }
   Set1 ::= Set (WITH COMPONENTS {f, d})
END

Error Message

"a0046e.asn", line 7 (Module-A0046E): A0046E: Type 'Set1' has an element 'e' which must exist.

Possible Solution

Use OPTIONAL in the parent type for the type that is omitted from the WITH COMPONENTS constraint.

A0047E

Message Format

A0047E: The tag of 'type reference' must be a non-negative integer value which does not exceed 16383.

Message Cause

The type-tag is negative or greater than the maximum allowed value, as specified in the ASN.1 standard.

Example

Module-A0047E DEFINITIONS ::= BEGIN
   A ::= [16383] INTEGER      -- Valid
   B ::= [16384] INTEGER      -- Invalid
   negnum INTEGER ::= -2
   C ::= [negnum] INTEGER     -- Invalid
END

Error Message

"a0047e.asn", line 3 (Module-A0047E): A0047E: The tag of 'B' must be a non-negative integer value which does not exceed 16383.


"a0047e.asn", line 5 (Module-A0047E): A0047E: The tag of 'C' must be a non-negative integer value which does not exceed 16383.

Possible Solution

Make sure the tag number is positive and does not exceed the maximum allowed limit.

A0048E

Message Format

A0048E: 'type reference' is incorrectly tagged.

Message Cause

The input ASN.1 syntax contains a type whose tag conflicts with one predefined by the ASN.1 standard.

Example

Module-A0048E DEFINITIONS ::= BEGIN
   WrongTag1 ::= [UNIVERSAL 8] CHOICE { a INTEGER, b BOOLEAN }
   WrongTag2 ::= [UNIVERSAL 8] ANY
END

Error Message

"a0048e.asn", line 2 (Module-A0048E): A0048E: 'WrongTag1' is incorrectly tagged.


"a0048e.asn", line 3 (Module-A0048E): A0048E: 'WrongTag2' is incorrectly tagged.

Possible Solution

Change the class of the tag from UNIVERSAL to PRIVATE or to context-specific.

A0049E

Message Format

A0049E: 'type reference' is incorrectly tagged. The tag number should be x.

Message Cause

A UNIVERSAL tag is applied to a built-in type that has a predefined UNIVERSAL tag.

Example

Module-A0049E DEFINITIONS ::= BEGIN
   Code ::= [UNIVERSAL 8] INTEGER
END

Error Message

"a0049e.asn", line 2 (Module-A0049E): A0049E: 'Code' is incorrectly tagged. The tag number should be 2.

Possible Solution

To correct this error, remove the UNIVERSAL tag. Optionally, you can specify the -ignoreError 49 option.

A0050E

Message Format

A0050E: 'type reference' is used as a type, but is not defined.

C0051E

Example

Module-A0056E DEFINITIONS ::= BEGIN
   PlaceHolder         ::= NULL
   number INTEGER      ::= 1
   avalue PlaceHolder  ::= number       -- invalid       
END

Error Message

"a0056e.asn", line 4 (Module-A0056E): A0056E: Type-value mismatch: the value of 'avalue' is not a suitable value for type 'PlaceHolder'.

Possible Solution

Replace the incompatible type with one that is compatible with the value or vice versa.

A0057E

Message Format

A0057E: The COMPONENTS OF element 'type reference' is of the wrong type.

Message Cause

The COMPONENTS OF clause is trying to import items from an incompatible structure. In this case, the COMPONENTS OF clause within a SET is trying to import items from a SEQUENCE or vice versa.

Example

Module-A0057E DEFINITIONS ::= BEGIN
   Set1  ::= SET {
                d BOOLEAN,
                e INTEGER,
                f VisibleString,
             }
   Seq1  ::= SEQUENCE {
                g BOOLEAN,
                h INTEGER,
                i VisibleString,
                COMPONENTS OF Set1        -- invalid
             }
END

Error Message

"a0057e.asn", line 7 (Module-A0057E): A0057E: The COMPONENTS OF element 'Set1' is of the wrong type.

Possible Solution

Make sure that the structure that contains the COMPONENTS OF clause and the one that is referenced by the COMPONENTS OF clause are of the same type.

A0058E

Message Format

A0058E: 'type reference' is defined using WITH COMPONENTS but one of the elements does not have an identifier.

Message Cause

The WITH COMPONENTS clause from the input ASN.1 syntax contains an item that doesn't have an identifier.

Example

Module-A0058E DEFINITIONS ::= BEGIN
   Record ::= SEQUENCE {
      name     PrintableString,
      age      INTEGER       OPTIONAL,
      address  GeneralString OPTIONAL
   }
   Rec ::= Record (WITH COMPONENTS {name, ABSENT, address})       
END

Error Message

"a0058e.asn", line 7 (Module-A0058E): A0058E: 'Rec' is defined using WITH COMPONENTS but one of the elements does not have an identifier.

Possible Solution

Specify the identifier of the component you want to use in the WITH COMPONENTS clause.

A0059E

Message Format

A0059E: 'identifier' is not an element of the SEQUENCE 'type reference'.

Message Cause

The WITH COMPONENTS clause is trying to access a component that is not present in the parent type.

Example

Module-A0059E DEFINITIONS ::= BEGIN
   ParameterList ::= SEQUENCE {
      requestID  INTEGER,
      command    PrintableString
   }
   RequestParams ::= ParameterList
      (WITH COMPONENTS {requestID, command, result PRESENT})    -- invalid         
END

Error Message

"a0059e.asn", line 6 (Module-A0059E): A0059E: 'result' is not an element of the SEQUENCE 'RequestParams'.

Possible Solution

Make sure the reference is spelled correctly or add a component to the source type with the same spelling as the reference.

A0060E

Message Format

A0060E: 'type reference' is defined using WITH COMPONENTS but the element 'command' is not the next element in the SEQUENCE being constrained.

Message Cause

The COMPONENTS OF clause is trying to import items from a structure, but the list order of the items in the COMPONENTS OF clause does not match the list order of the items in their original structure.

Example

Module-A0060E DEFINITIONS ::= BEGIN
   ParameterList ::= SEQUENCE {
      requestID    INTEGER,
      command      PrintableString
   }
   WrongSeq ::= ParameterList (WITH COMPONENTS {command, requestID})          
END

Error Message

"a0060e.asn", line 6 (Module-A0060E): A0060E: 'WrongSeq' is defined using WITH COMPONENTS but the element 'command' is not the next element in the SEQUENCE being constrained.

Possible Solution

Make sure the order of the list items in the COMPONENTS OF clause is the same as the order of the list items in the original structure.

A0061E

Message Format

A0061E: 'type reference' is defined using WITH COMPONENTS and has a non-OPTIONAL element 'identifier' which has a constraint type constraint.

Message Cause

The WITH COMPONENTS constraint uses an ABSENT/OPTIONAL keyword for a component that is not marked as optional in its original definition or is defined with a DEFAULT value and the -designerWarnings command-line option was specified.

Example

  Module-A0061E DEFINITIONS ::= BEGIN
   ParameterList ::= SEQUENCE {
      requestID      INTEGER,
      command        PrintableString
   }
   OneParam ::= ParameterList
               (WITH COMPONENTS {requestID, command ABSENT})      
END

Error Message

"a0061e.asn", line 6 (A0061E): A0061E: 'OneParam' is defined using WITH COMPONENTS and has a non-OPTIONAL element 'command' which has an absence constraint.

Possible Solution

Use the OPTIONAL keyword for the component or remove the DEFAULT value for that field.

A0062W

Message Format

A0062W: 'type reference' is defined using WITH COMPONENTS and has a non-OPTIONAL element 'identifier' which has a presence constraint.

Message Cause

The WITH COMPONENTS constraint in the input ASN.1 syntax uses a PRESENT keyword for a type that is not optional. This keyword can be applied only to optional components.

Example

Module-A0062W DEFINITIONS ::= BEGIN
   ParameterList ::= SEQUENCE {
      requestID      INTEGER,
      command        PrintableString
   }
   OneParam ::= ParameterList
               (WITH COMPONENTS {requestID, command PRESENT})        
END

Error Message

"a0062w.asn", line 6 (Module-A0062W): A0062W: 'OneParam' is defined using WITH COMPONENTS and has a non-OPTIONAL element 'command' which has a presence constraint.

Possible Solution

Mark the type as OPTIONAL in its original definition.

A0063E

Message Format

A0063E: 'type reference' is defined using WITH COMPONENTS, but the element 'identifier' is not an element of the parent type.

Message Cause

The WITH COMPONENTS constraint references an identifier that is not present in the parent type.

Example

Module-A0063E DEFINITIONS ::= BEGIN
   ParameterList ::= SET {
      requestID      INTEGER,
      command        PrintableString
   }
   OneParam      ::= ParameterList
               (WITH COMPONENTS {requestID, command, list ABSENT})     
END

Error Message

Messages usually superseded by A0136E.

Possible Solution

Remove the identifier.

C0064I

Message Format

C0064I: There are unused standard or OSS-specific directives. Look at all lines containing "WARNING:" in the .gen file.

Message Cause

OSS-specific or ASN.1 standard compiler directives could not be applied to any part of the schema, most likely because the absolute reference provided does not exist.

Example

--<OSS.HUGE Module-C0064I.HugeINT>--
Module-C0064I DEFINITIONS ::= BEGIN
   HugeInt ::= INTEGER              --Note the difference in letter-case   
END

Error Message

C0064I: There are unused standard or OSS-specific directives. Look at all lines containing "WARNING:" in the .gen file.

Possible Solution

Replace the absolute reference provided in the compiler directive with an identical type or remove the compiler directive.

C0065W

Message Format

C0065W: The INDEFINITE directive is not yet supported for the time-optimized encoder and is being ignored.  Please use the -soed option to encode data using indefinite-length encoding.

Message format when using the compiler GUI

C0065W: The INDEFINITE directive is not yet supported for the time-optimized encoder/decoder and is being ignored. To encode data using indefinite-length encoding, please check "RBUTTON_SOED".

Message Cause

You have specified the OSS.INDEFINITE compiler directive, but it does not support the -toed option.

Example

--<OSS.INDEFINITE>--
Module-C0065W DEFINITIONS ::= BEGIN
   Name1 ::= SEQUENCE {
      a      INTEGER,
      b      VisibleString }
   Name2 ::= SET {
      c      INTEGER,
      d      VisibleString } --<DEFINITE>--      
END

Error Message

C0065W: The INDEFINITE directive is not yet supported for the time-optimized encoder and is being ignored.  Please use the -soed option to encode data using indefinite-length encoding.

Possible Solution

Specify the -soed option and recompile your syntax.

C0066W

Message Format

C0066W: The directive from the implementation-specific scope is ignored.

Message Cause

The input ASN.1 syntax contains an implementation-specific compiler directive (--<DSET., --<HP., --<TCSI., --<IBM., --<CMIS., --<GDMO., --<XMP., --<XOM., etc.). The OSS ASN.1 compiler ignores these types of directives.

Example

--<HP.DirectiveName>--
Module-C0066W DEFINITIONS ::= BEGIN
   A ::= INTEGER     
END

Error Message

"c0066w.asn", line 1 (): C0066W: The directive from the HP scope is ignored.

--<HP.DirectiveName>--

Possible Solution

Remove the implementation-specific directive.

A0067E

Message Format

A0067E: The identifier 'identifier' is used more than once.

Message Cause

This error occurs if you use identical identifiers in the input ASN.1 syntax. According to the ASN.1 standard, the identifiers across SETs, SEQUENCEs, and CHOICEs must be unique within a specified scope.

Example

Module-A0067E DEFINITIONS ::= BEGIN
   Name1 ::= CHOICE { name [0] PrintableString, NULL }
   Name2 ::= SET    { name [1] PrintableString, Name1 }       
END

Message Cause

The input ASN.1 syntax contains an invalid circular reference.

Example

Module-A0070S DEFINITIONS ::= BEGIN
   TCLASS ::= INSTANCE OF TCLASS
   Dummy  ::= INTEGER      
END

A0073E: 'identifier', not 'identifier', is the standard identifier for number. A0073W: 'identifier', not 'identifier', is the standard identifier for number.

Message Cause

An OBJECT IDENTIFIER value has an identifier(number) node, but identifier is not predefined for number in Rec. ITU-T X.660 | ISO/IEC 9834-1. When identifier is predefined for a different number at this level in the OBJECT IDENTIFIER tree, the compiler issues an error message. Otherwise, when identifier is not predefined, the compiler issues a warning message.

Example

Module-A0073W DEFINITIONS ::= BEGIN
   OperationID ::= OBJECT IDENTIFIER
   ftam1 OperationID ::= {iso(0) newname(2) 2 1}
END

Error Message

"a0073w.asn", line 3 (Module-A0073E): A0073W: 'itu-t', not 'iso', is the standard identifier for 0.

   
"a0073w.asn", line 3 (Module-A0073W): A0073W: 'administration', not 'newname', is the standard identifier for 2.

Possible Solution

To remove the warning message, make sure the renaming is intentional.

To remove the error message, avoid the name conflict.

A0074E

Message Format

A0074E: 'identifier' must be either a defined value or one of the standard node identifiers.

Message Cause

The name of the second node of the OBJECT IDENTIFIER tree conflicts with a predefined name or has not been defined in the syntax.

NOTE: The value of component #2 of an object identifier is determined by the value of the first component. You can either use the predefined identifiers of the object identifier tree or define your own.

Example

Module-A0074E DEFINITIONS ::= BEGIN
   OperationID ::= OBJECT IDENTIFIER
   ftam1 OperationID ::= { 0 standard 2 1 }       
END

Error Message

"a0074e.asn", line 3 (Module-A0074E): A0074E: 'standard' must be either a defined value or one of the standard node identifiers.

Possible Solution

Replace the incorrect node name with one accepted in the ASN.1 standard.

A0075E

Message Format

A0075E: 'identifier' is component #x of an object identifier value and must be of type INTEGER.

Message Cause

You have not assigned an INTEGER value to a node of the OBJECT IDENTIFIER tree. All nodes of the OBJECT IDENTIFIER tree must have INTEGER values.

Example

Module-A0075E DEFINITIONS ::= BEGIN
   a BOOLEAN ::= TRUE
   b INTEGER ::= 2
   c OBJECT IDENTIFIER ::= { ccitt question a b }       
END

Error Message

"a0075e.asn", line 4 (Module-A0075E): A0075E: 'a' is component #3 of an object identifier value and must be of type INTEGER.

Possible Solution

Replace the non-integer value with an INTEGER one.

A0076E

Message Format

A0076E: Component 3 of the object identifier value with NumberForm 29 should be between 1 and 26, inclusive.

Message Cause

The value of the third node of the OBJECT IDENTIFIER tree is not defined correctly. For OBJECT IDENTIFIERS, the correct values are defined as follows: a(1), b(2), ..., z(26).

Example

Module-A0076E DEFINITIONS ::= BEGIN
  ModuleOI ::= OBJECT IDENTIFIER
  b ModuleOI ::= { 0 0 29 }     
END

Error Message

"a0076e.asn", line 3 (Module-A0076E): A0076E: Component 3 of the object identifier value with NumberForm 29 should be between 1 and 26, inclusive.

Possible Solution

Replace the invalid value with one between 1 and 26, inclusive, or specify the -ignoreError 76 command-line option.

A0077E

Message Format

A0077E: Component #x of an object identifier value has NumberForm y, but its value should be between a and b, inclusive.

Message Cause

The value of a node of the OBJECT IDENTIFIER tree exceeds the accepted range of the values.

NOTE: One or more arcs of the OBJECT IDENTIFIER tree have predefined values. The root of the tree is divided into 3 arcs labeled 0, 1, and 2. Additionally, the arc labeled 1 is divided into 4 arcs labeled 0, 1, 2, and 3. The other initial branches work similarly. This error message is displayed when using other values that are not predefined.

Example

Module-A0077E DEFINITIONS ::= BEGIN
   OID ::= OBJECT IDENTIFIER
   v OID ::= { 55 44 55 66 }
   w OID ::= { 1 44 55 66 }    
END

Error Message

"a0077e.asn", line 3 (Module-A0077E): A0077E: Component #1 of an object identifier value has NumberForm 55, but its value should be between 0 and 2, inclusive.


"a0077e.asn", line 4 (Module-A0077E): A0077E: Component #2 of an object identifier value has NumberForm 44, but its value should be between 0 and 3, inclusive.

Example

Module-A0080W DEFINITIONS ::= BEGIN
   BitString ::= BIT STRING { a(0) }
   b BitString ::= { a }
   c BitString ::= a    
END

Error Message

"a0080w.asn", line 4 (Module-A0080W): A0080W: NamedBit 'a' should be within {}.

Possible Solution

Place the NamedBit inside braces.

A0081W

Message Format

A0081W: 'identifier' is already defined on the enumerated list.

Message Cause

The value reference in an ENUMERATED type value assignment has the same name as one of the bits in the NamedNumberList.

Example

Module-A0081W  DEFINITIONS ::= BEGIN
  ColorCode ::= ENUMERATED { red(1), blue(2) }
  red ColorCode ::= blue   
END

Error Message

"a0081w.asn", line 3 (Module-A0081W): A0081W: 'red' is already defined on the enumerated list.

Possible Solution

Rename the value reference.

A0082E

Message Format

A0082E: Parsing error: missing symbol string of symbols.

Message Cause

One of the following keywords is missing from the input ASN.1 syntax: IMPLICIT, EXPLICIT, or AUTOMATIC.

Example

Module-A0082E DEFINITIONS TAGS ::= BEGIN
   A ::= INTEGER
END

Error Message

"a0082e.asn", line 1 (Module-A0082E): A0082E: Parsing error: missing symbol 'EXPLICIT', 'IMPLICIT' or 'AUTOMATIC'.

Module-A0082E DEFINITIONS TAGS ::= BEGIN

Possible Solution

Add the missing keyword.

A0083E

Message Format

A0083E: 'name' is not a legal typereference. It must start with an uppercase letter.

Message Cause

The type reference name does not begin with an uppercase letter.

Example

Module-A0083E DEFINITIONS ::= BEGIN
   c     ::= INTEGER { c(4) }
   Dummy ::= BOOLEAN
END

Error Message

"a0083e.asn", line 2 (Module-A0083E): A0083E: 'c' is not a legal typereference. It must start with an uppercase letter.

c ::= INTEGER { c(4) }

Possible Solution

Replace the lowercase letter of the type reference with an uppercase letter.

A0084E

Message Format

A0084E: 'name' is not a legal valuereference or objectreference. It must start with a lowercase letter.

Message Cause

The value reference or the object reference does not begin with a lowercase letter.

Example

Module-A0084E DEFINITIONS ::= BEGIN
   Value BOOLEAN ::= TRUE
END

Error Message

"a0084e.asn", line 2 (Module-A0084E): A0084E: 'Value' is not a legal valuereference or objectreference. It must start with a lowercase letter.

Value BOOLEAN ::= TRUE

Possible Solution

Replace the uppercase letter of the value or the object reference with a lowercase letter.

A0085W

Message Format

A0085W: 'type reference' is not permitted to have IMPLICIT tagging. EXPLICIT tagging is being used instead.

Message Cause

One of the following types in the input ASN.1 syntax uses implicit tagging instead of explicit tagging: CHOICE, ANY or ANY DEFINED BY.

Possible Solution

Replace the implicit tag of the type with an explicit tag.

A0086E

Message Format

A0086E: Parsing error: missing modulereference.

Message Cause

A module definition does not have a name.

Example

{iso(1) identified-organization(3) oss(1) module-5(5)} DEFINITIONS ::= BEGIN
   A ::= INTEGER
END

Error Message

"a0086e.asn", line 1 (): A0086E: Parsing error: missing modulereference.

  {iso(1) identified-organization(3) oss(1) module-5(5)} DEFINITIONS ::=

Possible Solution

Add a name at the beginning of the defined module in accordance with the guidelines of the ASN.1 standard.

A0087E

Message Format

A0087E: Parsing error: the name 'name' is not a kind of symbol that can be exported from module 'module reference'.

Message Cause

The IMPORTS statement contains one or more arguments that are not valid.

Possible Solution

Remove the arguments from the IMPORTS statement.

C0088W

Message Format

C0088W: Duplicate export: 'A'.

Message Cause

The EXPORTS statement in the input ASN.1 syntax contains two or more identical arguments.

Example

DupExp DEFINITIONS ::= BEGIN
   EXPORTS A, A;
   IMPORTS B FROM X;
   A ::= INTEGER
END

   X DEFINITIONS ::= BEGIN
   B ::= BOOLEAN
END

Error Message

"c0088w.asn", line 2 (DupExp): C0088W: Duplicate export: 'A'.

Possible Solution

Remove the duplicate argument from the EXPORTS statement.

A0089E/A0089W

Message Format

A0089E: 'type reference' was not exported from module module reference.

Message Cause

An IMPORTS statement s trying to import a type from the source module, but the type is not present. This error often occurs when the argument is misspelled.

Example

Common DEFINITIONS ::= BEGIN
   Responder ::= [PRIVATE 1] GeneralizedTime
END

Module-A0089E DEFINITIONS ::= BEGIN
   IMPORTS Responde FROM Common;
   InvokePDU ::= SEQUENCE {
      Responde
   }
END

Error Message

"a0089e.asn", line 6 (Module-A0089E): A0089E: 'Responde' was not exported from module Common.

IMPORTS Responde FROM Common;

Possible Solution

Make sure the arguments in the IMPORTS statement are spelled correctly.

NOTE: Starting with version 8.1.2, if you specify the -ignoreIncompleteItems option, the ASN.1 syntax checker displays a warning instead of an error message.

A0090W

Message Format

A0090W: 'identifier' is referenced by another module but is not on the current module's export list.

Message Cause

An IMPORTS statement is trying to import an item from another module that does not include an EXPORT statement with a list of items.

NOTE: According to the ASN.1 standard, if a module includes an explicit EXPORTS clause, you can export only the types listed as arguments, otherwise, all items are implicitly marked as exportable.

Example

Import1 DEFINITIONS ::= BEGIN
   IMPORTS Ex1, c, Ex2 FROM Export1;
   T     ::= Ex1
   e T   ::= c
   a Ex2 ::= 3
END

            
Export1 DEFINITIONS ::= BEGIN
   EXPORTS Ex1, Ex2;
   IMPORTS T, a FROM Import1;
   Ex1   ::= BOOLEAN
   Ex2   ::= INTEGER
   b Ex2 ::= a
   c T   ::= TRUE
END

Error Message

"a0090w.asn", line 14 (Export1): A0090W: 'c' is referenced by another module but is not on the current module's export list.

Possible Solution

Add the item to the EXPORTS statement of the source module or remove the EXPORTS statement.

A0091E

Message Format

A0091E: Parsing error: unresolved typereference: 'type reference'.

Message Cause

The ASN.1 compiler cannot resolve the type reference in the input ASN.1 syntax.

Possible Solution

Make sure the type reference is a basic ASN.1 type or another representable structure.

L0092W

Message Cause

This message code is used by OSS Nokalva for internal purposes.

C0093E

Message Format

C0093E: 'macro reference' is a macro and can not be referenced before it is defined.

Message Cause

The macro referenced in the input ASN.1 syntax has not been defined.

Possible Solution

Make sure you define the macro first.

A0094E

Message Format

A0094E: Parsing error: missing ModuleIdentifier.

Message Cause

The input ASN.1 syntax contains a module definition that does not have a module name.

Example

DEFINITIONS ::= BEGIN
   A ::= INTEGER
END

Error Message

"a0094e.asn", line 1 (): A0094E: Parsing error: missing ModuleIdentifier.

  DEFINITIONS ::= BEGIN

Possible Solution

Specify a name for the module.

A0095E

Message Format

A0095E: 'FROM' or ',' is missing. Ignoring the rest of the imported symbols list.

Message Cause

An IMPORTS statement contains arguments which are not separated by comma or the keyword FROM is missing from the statement.

Example

Module-A0095E DEFINITIONS ::= BEGIN
   EXPORTS Timestamp;
   IMPORTS Responder;
   Timestamp ::= Responder
END

Error Message

"a0095e.asn", line 3 (Module-A0095E): A0095E: 'FROM' or ',' is missing.  Ignoring the rest of the imported symbols list.
 
IMPORTS Responder;

Possible Solution

Add the missing comma or the keyword FROM.

C0096E

Message Cause

This message code is used by OSS Nokalva for internal purposes.

A0097E

Message Format

A0097E: The type 'type reference' is used but is not defined.

Message Cause

The type that is referenced is not defined or the macro is defined after being referenced.

Example

  Module-A0097E DEFINITIONS ::= BEGIN
   ERROR1 MACRO ::= ERROR

   ERROR MACRO  ::= BEGIN
      TYPE NOTATION  ::= "PARAMETER" NamedType | empty
      VALUE NOTATION ::= value(VALUE INTEGER)
      NamedType ::= identifier type | type
   END
END

Error Message

"a0097e.asn", line 2 (Module-A0097E): A0097E: The macroreference 'ERROR' is used but is not defined.
 
ERROR1 MACRO ::= ERROR

Possible Solution

Make sure all referenced types are defined and all macros are precisely rendered before they are used.

A0098E

Message Format

A0098E: ANY 'identifier' is used in an ambiguous context within type reference.

Message Cause

An ANY type might cause tag conflicts within a SET, CHOICE, or other tag-sensitive context.

Example

Module-A0098E DEFINITIONS ::= BEGIN
   L ::= SET {
      seq SEQUENCE OF CHOICE {
         sharp  INTEGER,
         eyes   ANY
      }
   }
END

Error Message

"a0098e.asn", line 2 (Module-A0098E): A0098E: ANY 'eyes' is used in an ambiguous context within L.

Possible Solution

Add an explicit tag to the ambiguous ANY type.

C0099E

Message Format

C0099E: Field 'identifier' of CHOICE 'type reference' has ambiguous tags.  Check for a CHOICE without a tag included within itself, or an ANY without a tag within a CHOICE.

Message Cause

One or more components in a CHOICE type might cause a possible tag conflict.

Example

Module-C0099E DEFINITIONS ::= BEGIN
   Name1 ::= CHOICE {
      name  PrintableString,
      id    INTEGER,
      next  Name1
   }
END

Error Message

"c0099e.asn", line 5 (Module-A0099E): C0099E: Field 'next' of CHOICE 'Name1' has ambiguous tags.  Check for a CHOICE without a tag included within itself, or an ANY without a tag within a CHOICE.

Possible Solution

Add an explicit tag.

A0100E

Message Format

A0100E: Duplicate tag in type type reference: element identifier (line x) and element identifier (line y).

Message Cause

The input ASN.1 syntax contains duplicate tags that will cause ambiguity problems in decoding.

Example

A0100E DEFINITIONS ::= BEGIN
   MySet ::= SET {
      a  [1] INTEGER,
      b  [1] BOOLEAN
   }
END

Error Message

"a0100e.asn", line 4 (A0100E): A0100E: Duplicate tag in type MySet: element a (line 3) and element b (line 4).

Possible Solution

Consider the following solutions:

Make sure all components have unique tags.
Remove the tags and add the AUTOMATIC TAGS keyword at the beginning of the module definition.

C0101E

Message Format

C0101E: Duplicate PDU tag: type 'type reference' (line x) and type 'type reference' (line y).

Message Cause

The input ASN.1 syntax contains duplicate tags that will cause ambiguity problems in decoding. This message is issued if the -unique option is specified.

Example

Module-C0101E DEFINITIONS ::= BEGIN
   C ::= BOOLEAN
   D ::= CHOICE {
      e  INTEGER,
      f  BOOLEAN
   }
END

Message Cause

The input ASN.1 syntax contains a MACRO keyword, but the macro definition is missing.

Example

Module-A0106E DEFINITIONS ::= BEGIN
   ERROR MACRO ::= 5
END

Error Message

"a0106e.asn", line 2 (Module-A0106E): A0106E: Expecting a MacroSubstance.
  

ERROR MACRO ::= 5

Possible Solution

Add a macro definition after the MACRO keyword.

A0107E

Message Format

A0107E: Found a production reference while expecting the keyword VALUE.

Message Cause

The input ASN.1 syntax contains a macro with a TYPE production but the VALUE production is missing.

Example

Module-A0107E DEFINITIONS ::= BEGIN
   ERROR MACRO ::= BEGIN
      TYPE NOTATION  ::= "PARAMETER" NamedType | empty
      Value NOTATION ::= value(VALUE INTEGER)
      NamedType      ::= identifier type       | type
   END
END

Error Message

"a0107e.asn", line 4 (Module-A0107E): A0107E: Found a production reference while expecting the keyword VALUE.

Value NOTATION ::= value(VALUE INTEGER)

Possible Solution

Make sure the keyword VALUE is spelled correctly or, in case there isn't one, add a VALUE production.

A0108E

Message Format

A0108E: Expected a SymbolElement.

Message Cause

A macro contains one or more productions that do not end in a token (SymbolElement).

Example

A0108E DEFINITIONS ::= BEGIN
   ERROR MACRO ::= BEGIN
      TYPE NOTATION  ::= "PARAMETER" NamedType | empty |
      VALUE NOTATION ::= value(VALUE INTEGER)    empty
      NamedType      ::= identifier type  --   | type
      NamedType      ::= type
   END
END

Error Message

"a0108e.asn", line 4 (A0108E): A0108E: Expected a SymbolElement.

VALUE NOTATION ::= value(VALUE INTEGER) empty

Possible Solution

Remove the extra "|" characters at the end of the production or add another token.

A0109E

Message Format

A0109E: 'macro reference' is not a legal macroreference.  It should begin with an uppercase letter and contain only uppercase letters, digits or hyphens.

Message Cause

The name of the macro does not conform to the ASN.1 standard.

Example

Module-A0109E DEFINITIONS ::= BEGIN
   ErrOR MACRO ::= BEGIN
      TYPE NOTATION  ::= "PARAMETER" NamedType | empty
      VALUE NOTATION ::= value(VALUE INTEGER)
      NamedType      ::= identifier type       | type
   END
END

Error Message

"a0109e.asn", line 2 (Module-A0109E): A0109E: 'ErrOR' is not a legal macroreference.  It should begin with an uppercase letter and contain only uppercase letters, digits or hyphens.

ErrOR MACRO ::= BEGIN

Possible Solution

Make sure the name of the macro contains uppercase, digits, or hyphens.

A0110E

Message Format

A0110E: Duplicate definition for productionreference 'production reference'.

Message Cause

A production reference in the input ASN.1 syntax is used more than once in the same macro definition.

Example

Module-A0110E DEFINITIONS ::= BEGIN
   ERROR MACRO ::= BEGIN
      TYPE NOTATION  ::= "PARAMETER" NamedType | empty
      VALUE NOTATION ::= value(VALUE INTEGER)    empty
      NamedType      ::= identifier type
      NamedType      ::= type
   END
END

Error Message

"a0110e.asn", line 6 (Module-A0110E): A0110E: Duplicate definition for productionreference 'NamedType'.

NamedType ::= type

Possible Solution

Use only distinct names for productions.

C0111S

Message Format

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

C0114S

Message Format

C0114S: COMPILER ERROR #6.

Message Cause

Your input ASN.1 syntax has caused an internal discrepancy in the ASN.1 compiler. The most likely cause of this message is a serious syntax error in your input.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

C0115E

Message Format

C0115E: Expecting the element 'identifier' to be defined in type 'type reference'.

Message Cause

The input ASN.1 syntax contains a derived type that is not consistent with the parent type.

Example

C0115E DEFINITIONS ::= BEGIN
   A      ::= INTEGER {one(1),two(2),three(3)}
   UseG   ::= G (WITH COMPONENT (MIN..five))
   G      ::= SET OF A
   five A ::= 5
   UseE   ::= E (WITH COMPONENTS {...,c (thirtythree) })
   E      ::= SEQUENCE {a A, b BOOLEAN OPTIONAL}
END

Error Message

"c0115e.asn", line 7 (C0115E): C0115E: Expecting the element 'c' to be defined in type 'E'.

E ::= SEQUENCE {a A, b BOOLEAN OPTIONAL}

Possible Solution

Make sure all derived types are consistent with their parent types.

C0116E

Message Format

C0116E: Type mismatch: 'type reference' has been referred to as a data type type elsewhere.

Message Cause

A forward reference to a user-defined type is inconsistent with its actual definition.

Example

Module-C0116E DEFINITIONS ::= BEGIN
   hydrogen Element ::= "H"
   Element ::= CHOICE {
      atomicNumber   INTEGER (1..109),
      symbol         PrintableString (SIZE(1..2))
   }
END

Error Message

"c0116e.asn", line 6 (C0116E): C0116E: Type mismatch: 'Element' has been referred to as a character string type elsewhere.

}

Possible Solution

Make sure all forward references are consistent with the definition of the type referenced.

C0117S

Message Format

C0117S: COMPILER ERROR #7.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

C0118E

Message Format

C0118E: COMPILER ERROR #12.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

C0119S

Message Format

C0119S: 'type reference' must be previously defined.

NOTE: This message is outdated.

A0120E

Message Format

A0120E: Parsing error: expecting 'symbol 1' but found ASN.1 component(s).

Message Cause

A symbol (a comma, a word etc.) is missing, is placed in an inappropriate location, or is substituted by another symbol. In general, this error occurs when you redefine or misplace predefined ASN.1 reserved words (APPLICATION, MAX, OBJECT, WITH).

Example

Module-A0120E DEFINITIONS ::= BEGIN
   hydrogen Element ::= "H"
   Element ::= CHOICE {
      atomicNumber   INTEGER (1..109),
      symbol         PrintableString (SIZE(1..2))
   }
END

Error Message

"a0120e.asn", line 4 (Module-A0120E): A0120E: Parsing error: expecting '}' or a ',' but found valuereference or identifier.

b  [1] BOOLEAN

Example

Module-A0123E DEFINITIONS ::= BEGIN
     S ::= SET { a INTEGER, b VisibleString, INTEGER OPTIONAL,
                   VisibleString OPTIONAL}
   x S ::= { 3 , "Yes" }
END

Error Message

"a0123e.asn", line 4 (A0123E): A0123E: Parsing error: expected a value for 'a'.

   x S ::= { 3 , "Yes" }


"a0123e.asn", line 4 (A0123E): A0123E: Parsing error: expected a value for 'b'.
   x S ::= { 3 , "Yes" }

Possible Solution

Add identifiers to all the components in the parent type and use the identifier-colon-value notation on the right side of the value assignment.

A0125S

Message Format

A0125S: Parsing error: type is being used in an invalid context.

NOTE: This message is superseded by A0247E.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

A0126S

Message Format

A0126S: The SelectionType 'identifier' is incorrectly defined. Element 'identifier' was not found.

Message Cause

A selection type is trying to extract an item that is not present in the parent type.

Example

Module-A0126S DEFINITIONS ::= BEGIN
   Choice1 ::= CHOICE {
      a INTEGER,
      b BOOLEAN
   }
   Seq1    ::= SEQUENCE {
      a INTEGER,
      b NULL,
      c d < Choice1 }
END

Error Message

"a0126s.asn", line 9 (Module-A0126S): A0126S: The SelectionType 'c' is incorrectly defined. Element 'd' was not found.

Possible Solution

Make sure the item is defined in the parent type.

C0127E

Message Format

C0127E: COMPILER ERROR #2.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

A0128E

Message Format

A0128E: The values for all enumerations which follow an ellipsis (...) must be in ascending order, but the value of 'identifier(x)' is less than 'y', the value of the preceding AdditionalEnumeration.

Message Cause

An ENUMERATED type has a NamedNumberList in which the NameNumbers following the ellipsis are listed in descending order. The values must be in ascending order.

Example

Module-A0128E DEFINITIONS ::= BEGIN
   EnumType ::= ENUMERATED {a(1), b(2), c(3), ..., d(5), e(4)}
END

Error Message

"a0128e.asn", line 2 (Module-A0128E): A0128E: The values for all enumerations which follow an ellipsis (...) must be in ascending order, but the value of 'e(4)' is less than '5', the value of the preceding AdditionalEnumeration.

Example

Module-A0134E DEFINITIONS ::= BEGIN
   FlagCode ::= INTEGER (1..20)
   FlagName ::= PrintableString
   FlagInfo ::= SET {
      code  FlagCode,
      name  FlagName OPTIONAL
   }
   Flags ::= FlagInfo (WITH COMPONENT{code})
END

Error Message

"a0134e.asn", line 8 (Module-A0134E): A0134E: WITH COMPONENT is not valid on this parent type.  Use WITH COMPONENT only on SET OF and SEQUENCE OF types.

Flags ::= FlagInfo (WITH COMPONENT{code})

Possible Solution

Make sure you apply the WITH COMPONENT constraint only to types based on SET OF or SEQUENCE OF.
For SET and SEQUENCE types, use the WITH COMPONENTS (with an 'S') clause.

A0135E

Message Format

A0135E: WITH COMPONENTS is not valid on this parent type.  Use WITH COMPONENTS only on SET, SEQUENCE and CHOICE types.T OF and SEQUENCE OF types.

Message Cause

A WITH COMPONENTS subtype constraint is applied to a type that is not a SET, a SEQUENCE, or a CHOICE type.

Example

Module-A0135E DEFINITIONS ::= BEGIN
   FlagCode ::= INTEGER (1..20)
   FlagName ::= PrintableString
   FlagInfo ::= SET OF SET {
      code  FlagCode,
      name  FlagName OPTIONAL
   }
   Flags ::= FlagInfo (WITH COMPONENTS {code})
END

Error Message

"a0135e.asn", line 8 (Module-A0135E): A0135E: WITH COMPONENTS is not valid on this parent type.  Use WITH COMPONENTS only on SET, SEQUENCE and CHOICE types.

Flags ::= FlagInfo (WITH COMPONENTS {code})

Possible Solution

Make sure you apply the WITH COMPONENTS constraint only to types based on SET, SEQUENCE, or CHOICE.
For SET OF and SEQUENCE OF types, use the WITH COMPONENT (without an 'S') clause.

A0136E

Message Format

A0136E: No match for identifier 'identifier'.

Message Cause

One or more components of a WITH COMPONENTS subtype constraint are not present in the parent type.

Example

Module-A0136E DEFINITIONS ::= BEGIN
   FlagCode ::= INTEGER (1..20)
   FlagName ::= PrintableString
   FlagInfo ::= SET { code FlagCode, name FlagName OPTIONAL }
   Flags ::= FlagInfo (WITH COMPONENTS {code, names ABSENT, another})
END

Error Message

"a0136e.asn", line 5 (Module-A0136E): A0136E: No match for identifier 'names'.

Flags ::= FlagInfo (WITH COMPONENTS {code, names ABSENT, another})


"a0136e.asn", line 5 (Module-A0136E): A0136E: No match for identifier 'another'.

Flags ::= FlagInfo (WITH COMPONENTS {code, names ABSENT, another})

Possible Solution

Ensure that the components listed in the WITH COMPONENTS constraint and the ones in the parent type have the same spelling.

A0137E

Message Format

A0137E: Tags for extensions in CHOICE types must be in canonical order, but the tag for 'identifier' is not canonically greater than the tag of the previous element.

Message Cause

According to the ASN.1 standard, the fields following an extension marker ( '...' ) in a CHOICE type must have tags listed in ascending order.

Example

Module-A0137E DEFINITIONS ::= BEGIN
   FlagCode ::= CHOICE {
      a [0] INTEGER,
      b [1] INTEGER,
      ...,
      c [5] INTEGER,
      d [4] INTEGER
   }
END

Error Message

"a0137e.asn", line 7 (Module-A0137E): A0137E: Tags for extensions in CHOICE types must be in canonical order, but the tag for 'd' is not canonically greater than the tag of the previous element.

Possible Solution

Make sure the tags following the extension marker are listed in ascending order.

A0138E

Message Format

A0138E: Only values of BMPString and UniversalString may contain Quadruples, but the value for 'identifier' contains a Quadruple.

Message Cause

The input ASN.1 syntax contains a quadruple-type value assignment to a simple one byte character string.

Possible Solution

Replace the quadruple-type value assignment with a regular value assignment.

A0139W

Message Format

A0139W: The named bit 'c' is defined as '7' which exceeds the size constraint for the element 'd'.

Message Cause

A value in a value assignment of a BIT STRING type exceeds the maximum value of an applied size constraint.

Example

Module-A0139W DEFINITIONS ::= BEGIN
   B   ::= BIT STRING {a(3), b(5), c(7)}  (SIZE(1..5))
   d B ::= { c }
END

Error Message

"a0139w.asn", line 3 (Module-A0139W): A0139W: The named bit 'c' is defined as '7' which exceeds the size constraint for the element 'd'.

Possible Solution

Change the assigned value to fall within the minimum and maximum values of the size constraint.

C0140E

Message Format

C0140E: Unrecognized local directive 'directive name'.

Message Cause

The directive used is not one of the known directives supported by the compiler.

Example

Module-C0140E DEFINITIONS ::= BEGIN
   Name1 ::= [0] OBJECT IDENTIFIER
   Name2 ::= [1] OBJECT IDENTIFIER --<OBJID 10>--
END

Error Message

"c0140e.asn", line 3 (Module-C0140E): C0140E: Unrecognized local directive 'OBJID'.

 Name2 ::= [1] OBJECT IDENTIFIER --<OBJID 10>--

Example

--<OBJID 10>--
C0145E DEFINITIONS ::= BEGIN
   Name1 ::= [0] OBJECT IDENTIFIER
   Name2 ::= [1] OBJECT IDENTIFIER --<OBJECTID 8>-- 
END

Error Message

"c0145e.asn", line 1 (): C0145E: Unrecognized global directive 'OBJID'.


--<OBJID 10>--

Possible Solution

Check the spelling of the directive name. Also, make sure the directive can be applied globaly. For more information, see Compiler Directives.

A0146E

Message Format

A0146E: Type 'type reference' is illegally redefined.

Message Cause

Two or more type definitions have the same name.

Example

Module-A0146E DEFINITIONS ::= BEGIN
   Name1 ::= INTEGER
   Name1 ::= BOOLEAN
END

Error Message

"a0146e.asn", line 3 (Module-A0146E): A0146E: Type 'Name1' is illegally redefined.

Name1 ::= BOOLEAN

Possible Solution

Change the duplicate type name to be unique within its scope.

A0147E

Message Format

A0147E: Expecting a typereference, but found ASN.1 component.

Message Cause

An IMPORTS clause has one or more invalid arguments.

Possible Solution

Remove the invalid element from the IMPORTS clause.

A0148E

Message Format

A0148E: 'identifier' can not be redefined.

Message Cause

Two or more bits or numbers in a NamedBitList or a NamedNumberList have the same identifier associated with them.

Example

Module-A0148E DEFINITIONS ::= BEGIN
   B ::= BIT STRING {a(1), b(5), a(6)}
END

Error Message

"a0148e.asn", line 2 (Module-A0148E): A0148E: 'a' can not be redefined.

   B ::= BIT STRING {a(1), b(5), a(6)}


   "a0148e.asn", line 3 (Module-A0148E): A0148E: 'a' can not be redefined.

   I ::= INTEGER {a(20), b(30), a(40)}

Possible Solution

Change the duplicate name to be unique within its scope.

A0149E

Message Format

A0149E: 'identifier' has already been defined.

Message Cause

Two or more components in a SET, SEQUENCE, or a CHOICE type have the same name.
This error may also occur if you attempt to use a a non-parameterized type as a parameterized type.

Example

Module-A0149E DEFINITIONS ::= BEGIN
   Choice ::= CHOICE {
      b INTEGER,
      c OCTET STRING,
      c BOOLEAN
   }
END

Error Message

"a0149e.asn", line 5 (Module-A0149E): A0149E: 'c' has already been defined.

   c BOOLEAN

Possible Solution

Change the duplicate name to be unique within its scope.

A0150E

Message Format

A0150E: ANY DEFINED BY must be a component of a SET or SEQUENCE.

Message Cause

An ANY DEFINED BY type is defined outside a SET or SEQUENCE. ANY DEFINED BY must be a component of a SET or SEQUENCE.

Example

Module-A0150E DEFINITIONS ::= BEGIN
   id INTEGER ::= 10
   Y ::= ANY DEFINED BY id
   Information ::= SEQUENCE {
      source       OCTET STRING,
      destination  OCTET STRING,
      info         ANY DEFINED BY source
   }
END

Error Message

"a0150e.asn", line 3 (Module-A0150E): A0150E: ANY DEFINED BY must be a component of a SET or SEQUENCE.

   Y ::= ANY DEFINED BY id

Possible Solution

Place the ANY DEFINED BY inside a SET or a SEQUENCE.

A0151E

Message Format

A0151E: 'name' is being used as a typereference, but does not start with an uppercase letter.

Message Cause

The input ASN.1 syntax contains a token that does not begin with an uppercase letter in the place where a type reference was expected. According to the ASN.1 standard, all type references must begin with an uppercase letter.

Example

Module-A0151E DEFINITIONS ::= BEGIN
   employee  VisibleString ::= "John E. Doe"
   Seq1 ::= SEQUENCE {
      id    INTEGER,
      name  employee
   }
END

Error Message

"a0151e.asn", line 5 (Module-A0151E): A0151E: 'employee' is being used as a typereference, but does not start with an uppercase letter.

  name employee

Possible Solution

Capitalize the first letter of the name or replace the name with a predefined ASN.1 type reference.

C0152S

Message Format

C0152S: COMPILER ERROR #26 (number).

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

A0153E

Message Format

A0153E: Value 'value reference' is being redefined.

Message Cause

The input ASN.1 syntax contains a value reference that is assigned a value two more times in the same context.

Example

Module-A0151E DEFINITIONS ::= BEGIN
   filename  VisibleString ::= "John E. Doe"
   Seq1 ::= SEQUENCE {
      id  INTEGER,
      name  employee
   }
END

Error Message

"a0152e.asn", line 3 (Module-A0152E): A0153E: Value 'employee' is being redefined.

  employee  IA5String     ::= "Mary J. Doe"

Possible Solution

Change the first letter of the name to be an uppercase letter or replace it with a pre-defined ASN.1 type reference.

A0154E

Message Format

A0154E: Expecting a type, not a number.

Message Cause

The input ASN.1 syntax contains a number where a type reference was expected.

Possible Solution

Replace the number with a type reference.

A0155E

Message Format

A0155E: Expecting an identifier from the BIT STRING NamedBitList, but found 'identifier'.

Message Cause

The input ASN.1 syntax contains a reference to a NamedBitList, but one of the identifiers listed does not match any of the NamedBits in the BIT STRING type's definition.

Example

A0155E DEFINITIONS ::= BEGIN
   RequestPDU ::= [PRIVATE 3] IMPLICIT SEQUENCE {
      parameters  SEQUENCE {
         request  BIT STRING {startup(0),
                             shutdown(1),
                               status(2)}
         }
   }
   echo RequestPDU ::= {
      parameters {request {go, status}}
   }
END

Error Message

"a0155e.asn", line 10 (A0155E): A0155E: Expecting an identifier from the BIT STRING NamedBitList, but found 'go'.

  parameters {request {go, status}}

Possible Solution

Remove the identifier from the reference to the NamedBitList.

A0156E

Message Format

A0156E: 'identifier' is being redefined.

Message Cause

A value reference within a structured type is defined more than once.

Example

A0156E DEFINITIONS ::= BEGIN
   Building ::= SET {
      address   VisibleString,
      occupied  BOOLEAN
   }
   headquarters Building ::= {
      address   "100 Central Avenue",
      address   "New Address",
      occupied   TRUE
   }
END

Error Message

"a0156e.asn", line 8 (A0156E): A0156E: 'address' is being redefined.

  address "New Address",

Possible Solution

Remove the value reference or rename it.

A0157E

Message Format

A0157E: Expecting the identifier 'identifier' of the SEQUENCE and its value.

Message Cause

One or more non-optional components are missing from a value assignment to a SEQUENCE type.

Example

Module-A0157E DEFINITIONS ::= BEGIN
   PersonalRecord ::= SEQUENCE {
      name      VisibleString,
      location  INTEGER {homeOffice(0), fieldOffice(1)},
      age       INTEGER
   }
   rockStar1 PersonalRecord ::= {
      name  "John Brown",
      age    26
   }
END

Error Message

"a0157e.asn", line 9 (Module-A0157E): A0157E: Expecting the identifier 'location' of the SEQUENCE and its value.

  age 26

Possible Solution

Add the missing component in the value assignment.

A0158E

Message Format

A0158E: Expecting a SEQUENCE component value of a different type.

Message Cause

One or more unnamed non-optional components are missing from a value assignment to a SEQUENCE type.

Example

Module-A0158E DEFINITIONS ::= BEGIN
   PersonalRecord ::= SEQUENCE {
      name VisibleString,
      INTEGER {homeOffice(0), fieldOffice(1)},
      age INTEGER
   }
   rockStar1 PersonalRecord ::= {
      name "John Brown",
      age 26
   }
END

Error Message

"a0158e.asn", line 9 (Module-A0158E): A0158E: Expecting a SEQUENCE component value of a different type.

  age 26

Possible Solution

Add the value of the missing component to the value assignment.
Additionally, to update your ASN.1 specifications, assign a unique identifier to all SEQUENCE components.

A0159E

Message Format

A0159E: 'identifier' does not match any of the choice elements.

Message Cause

Example

Module-A0159E DEFINITIONS ::= BEGIN
   Code ::= CHOICE {a BOOLEAN, b OBJECT IDENTIFIER}
   code1 INTEGER ::= 4
   name1 Code ::= code1
END

Error Message

"a0159e.asn", line 4 (Module-A0159E): A0159E: 'code1' does not match any of the choice elements.

  name1 Code ::= code1

Possible Solution

Replace the incompatible value reference with a compatible one.

A0160E

Message Format

A0160E: The base of a REAL value must be 2 or 10.

Message Cause

The input ASN.1 syntax contains a value assignment to a REAL type, but the base specified in the assigned value is not 2 or 10. The base of a REAL value must be 2 or 10.

Example

Module-A0160E DEFINITIONS ::= BEGIN
   CarSpeed ::= REAL
   limit1 CarSpeed::= {55, 20, 1}
END

Error Message

"a0160e.asn", line 3 (Module-A0160E): A0160E: The base of a REAL value must be 2 or 10.

  limit1 CarSpeed::= {55,20,1}

Example

Module-C0172E DEFINITIONS ::= BEGIN
   Name1 ::= VisibleString --<PADDED>--
   Name2 ::= PrintableString (SIZE(30)) --<PADDED>--
END

Error Message

"c0172e.asn", line 2 (C0172E): C0172E: 'Name1' has a PADDED directive which requires a SIZE constraint.

Possible Solution

Add the size constraint.

C0173S

Message Format

C0173S: 'type reference' has an ARRAY directive which requires using the OBJECTID directive or the POINTER directive.

Message Cause

An OSS.ARRAY compiler directive is applied to an OBJECT IDENTIFIER type that does not have a POINTER or an OBJECTID representation.

Example

Module-C0173S DEFINITIONS ::= BEGIN
   Name1 ::= [0] OBJECT IDENTIFIER
   Name2 ::= [1] OBJECT IDENTIFIER --<ARRAY | NOPOINTER>--
END

Error Message

"c0173s.asn", line 3 (Module-C0173S): C0173S: 'Name2' has an ARRAY directive which requires using the OBJECTID directive or the POINTER directive.

Possible Solution

Remove the OSS.NOPOINTER directive or apply the OSS.OBJECTID directive to the type.

A0174S

Message Format

A0174S: The element 'identifier' has an ANY DEFINED BY identifier 'identifier' which is not an INTEGER, an OBJECT IDENTIFIER, or ENUMERATED.

Message Cause

An ANY DEFINED BY references an inappropriate type.

Example

Module-A0174S DEFINITIONS ::= BEGIN
   OperationPDU ::= SEQUENCE {
      priority     OCTET STRING,
      parameters   ANY DEFINED BY priority
   }
END

Error Message

"a0174s.asn", line 4 (Module-A0174S): A0174S: The element 'parameters' has an ANY DEFINED BY identifier 'priority' which is not an INTEGER, an OBJECT IDENTIFIER, or ENUMERATED.

Possible Solution

Make sure that ANY DEFINED BY only references INTEGER, OBJECT IDENTIFIER, and ENUMERATED types.

C0175S

Message Format

C0175S: 'type reference' is the wrong type for the SHORT, INT, LONG, LONGLONG, HUGE, or ASN1.HugeInteger directive.

Message Cause

An OSS.SHORT, OSS.INT, OSS.LONG, OSS.LONGLONG, OSS.HUGE, or ASN1.HugeInteger compiler directive is applied to an incompatible type.

Example

Module-C0175S DEFINITIONS ::= BEGIN
   Name1 ::= INTEGER
   Name2 ::= VisibleString --<INT>--
END

Error Message

"c0175s.asn", line 3 (Module-C0175S): C0175S: 'Name2' is the wrong type for the SHORT, INT, LONG, LONGLONG, HUGE, or ASN1.HugeInteger directive.

Possible Solution

Remove the directive.

C0176S

Message Format

C0176S: 'type reference' is the wrong type for the FLOAT, DOUBLE, DECIMAL, or MIXED directive.

Message Cause

An OSS.FLOAT, OSS.DOUBLE, OSS.DECIMAL, or OSS.MIXED compiler directive is applied to an incompatible type.

Example

Module-C0176S DEFINITIONS ::= BEGIN
   Name1     ::= [0] INTEGER --<LONG>--
   IntType   ::= [1] INTEGER --<FLOAT>--
END

Error Message

"c0176s.asn", line 3 (Module-C0176S): C0176S: 'IntType' is the wrong type for the FLOAT, DOUBLE, DECIMAL, or MIXED directive.

Possible Solution

Remove the directive.

C0177W

Message Format

C0177W: Item truncated: token .... Item too long!

Message Cause

The size of a token (symbol) exceeds the allowed maximum limit of 1024 characters.

Possible Solution

Truncate the token.

A0178W

Message Format

A0178W: The first digit should not be zero unless the number is a single digit.

Message Cause

This error occurs if you add a leading zero to a number that contains more than one digit.

Example

Module-A0178W DEFINITIONS ::= BEGIN
   A ::= INTEGER
   a A ::= 08
END

Error Message

"a0178w.asn", line 3 (Module-A0178W): A0178W: The first digit should not be zero unless the number is a single digit.
  a A ::= 08

Possible Solution

Remove the leading zero.

L0179S

Message Format

L0179S: An errorfile name must be specified whenever -errorfile is specified.

Message Cause

The -errorFile command-line option was specified, but no filename argument was given.

Possible Solution

Add a filename argument after the -errorFile option.

A0180W

Message Format

A0180W: cstring terminated by end of file. Quote assumed.

Message Cause

A character string is missing the closing quotation marks. Character strings must be enclosed in quotation marks.

Example

Module-A0180W DEFINITIONS ::= BEGIN
   a PrintableString ::= "free"

Error Message

"a0180w.asn", line 3 (Module-A0106E): A0180W: cstring terminated by end of file. Quote assumed.

Possible Solution

Add the closing quotation marks.

A0181W

Message Format

A0181W: 1990 ASN.1 does not permit a cstring to span multiple lines.

Message Cause

Under ASN.1:1990 syntax rules, a character string cannot span multiple lines. This error generally indicates that the closing quotation marks are missing.

Example

Module-A0181W DEFINITIONS ::= BEGIN
   Str ::= VisibleString (SIZE (1 .. 20))
   str1 Str ::= "String Not Closed
END

Error Message

"a0181w.asn", line 3 (Module-A0181W): A0181W: 1990 ASN.1 does not permit a cstring to span multiple lines.

 str1 Str ::= "String Not Closed

Possible Solution

Add the closing quotation marks or make sure the string doesn't span multiple lines.

A0182W

Message Format

A0182W: String terminated by end of file. Hstring assumed.

Message Cause

A hexadecimal string is missing the closing quotation marks. Hexadecimal strings must be enclosed in quotation marks.

Example

Module-A0182W DEFINITIONS ::= BEGIN
   str1 OCTET STRING ::= '01AF

Error Message

"a0182w.asn", line 3 (Module-A0182W): A0182W: String terminated by end of file. Hstring assumed.

Possible Solution

Add the closing quotation marks.

A0183W

Message Format

A0183W: String terminated by end of line. Hstring assumed.

Message Cause

A hexadecimal string is missing the closing quotation marks. Hexadecimal strings must be enclosed in quotation marks.

Possible Solution

Add the closing quotation marks.

A0184W

Message Format

A0184W: Invalid end of string indicator 'b'. End of string indicator 'B' assumed.

Message Cause

A binary string is followed by a lowercase letter "b". According to the ASN.1 standard, a binary string must be followed by an uppercase letter "B".

Example

Module-A0184W DEFINITIONS ::= BEGIN
   BitStr ::= BIT STRING
   bits BitStr ::= '01'b
END

Error Message

"a0184w.asn", line 3 (Module-A0184W): A0184W: Invalid end of string indicator 'b'.  End of string indicator 'B' assumed.

  bits BitStr ::= '01'b

Possible Solution

Change the lowercase letter "b" to uppercase "B".

A0185W

Message Format

A0185W: Invalid end of string indicator 'h'. End of string indicator 'H' assumed.

Message Cause

A hexadecimal string is followed by a lowercase letter "h". According to the ASN.1 standard, a hexadecimal string must be followed by an uppercase letter "H".

Example

Module-A0185W DEFINITIONS ::= BEGIN
   Octet ::= OCTET STRING
   octs Octet ::= '1ACF'h
END

Error Message

"a0185w.asn", line 3 (Module-A0185W): A0185W: Invalid end of string indicator 'h'.  End of string indicator 'H' assumed.

  octs Octet ::= '1ACF'h

Example

Module-A0188W DEFINITIONS ::= BEGIN
   BitStr   ::= BIT STRING
   hexas BitStr ::= 'FA01F'd
END

Error Message

"a0188w.asn", line 3 (Module-A0188W): A0188W: Invalid end of string indicator 'd'.  End of string indicator 'H' is assumed.

  hexas BitStr ::= 'FA01F'd

Possible Solution

Replace the character with uppercase "B" or uppercase "H".

C0189W

Message Format

C0189W: Unable to continue directive, due to reason.

Message Cause

A compiler directive is missing a greater than sign (">") before the two consecutive hyphens.

Example

--<OSS.PADDED --
Module-A0189W DEFINITIONS ::= BEGIN
   BitStr   ::= BIT STRING
   hexas BitStr ::= 'FA01F'H
END

Error Message

"a0189w.asn", line 2 (): C0189W: Unable to continue directive, due to text before next comment.

  Module-A0188W DEFINITIONS ::= BEGIN

Possible Solution

Add the greater than symbol before the two consecutive hyphens at the end of the directive.

A0190E

Message Format

A0190E: Illegal hex character: 'c'.

Message Cause

A hexadecimal string contains one or more characters that are not hexadecimal values.

Example

Module-A0190E DEFINITIONS ::= BEGIN
   BitStr   ::= BIT STRING
   hexas BitStr ::= 'FA0o1F'H
END

Error Message

"a0190e.asn", line 3 (A0190E): A0190E: Illegal hex character: 'o'.

  hexas BitStr ::= 'FA0o1F'H

Possible Solution

Make sure that all characters in a hexadecimal string are either between 0 to 9 or between A to F.

A0191E

Message Format

A0191E: Illegal bit character: 'c'.

Message Cause

One or more characters in a binary string are not binary values.

Example

Module-A0191E DEFINITIONS ::= BEGIN
   BitStr   ::= BIT STRING
   bits BitStr ::= '01l'B
END

Error Message

"a0191e.asn", line 3 (Module-A0191E): A0191E: Illegal bit character: 'l'.

  bits BitStr ::= '01l'B

Possible Solution

Make sure that all characters in a binary string are either 0 or 1.

A0192E

Message Format

A0192E: 'macro reference' cannot be redefined as a MACRO since it has already been used in the current module.

Message Cause

A macro name is defined more than once.

Example

Module-A0192E DEFINITIONS ::= BEGIN
   ERROR MACRO ::= BEGIN
      TYPE NOTATION ::= "PARAMETER" NamedType | empty
      VALUE NOTATION ::= value(VALUE INTEGER)
      NamedType ::= identifier type | type
   END

   ERROR MACRO ::= BEGIN
      TYPE NOTATION ::= "PARAMETER" NamedType | empty
      VALUE NOTATION ::= value(VALUE BOOLEAN)
      NamedType ::= identifier type | type
   END
END

Error Message

"a0192e.asn", line 8 (Module-A0192E): A0192E: 'ERROR' cannot be redefined as a MACRO since it has already been used in the current module.

  ERROR MACRO ::= BEGIN

Possible Solution

Rename the macro reference.

A0193W

Message Format

A0193W: No assignment to VALUE in the definition of macro 'macro reference'.

Message Cause

A macro contains a VALUE NOTATION production that does not specify which ASN.1 type is valid for assignment.

Example

Module-A0193W DEFINITIONS ::= BEGIN
   ERROR MACRO ::= BEGIN
      TYPE NOTATION ::= "PARAMETER" NamedType | empty
      VALUE NOTATION ::= value(VALUEINTEGER)
      NamedType ::= identifier type | type
   END
END

Error Message

"a0193w.asn", line 6 (Module-A0193W): A0193W: No assignment to VALUE in the definition of macro 'ERROR'.

  END

Possible Solution

Add a space between VALUE and the ASN.1 type in the value(VALUE ) clause.

A0194W

Message Format

A0194W: The localvaluereference should start with an uppercase letter.

Message Cause

A local value reference in a macro definition starts with a lowercase letter.

Example

A0194W DEFINITIONS ::= BEGIN
   PAIR MACRO ::= BEGIN
      TYPE NOTATION ::= "Typex" "=" type(LocalType1)
                        "Typey" "=" type(LocalType2)
      VALUE NOTATION ::= "(" "X" "=" value(LocalValue1 LocalType1) ","
                         "Y" "=" value(LocalValue2 LocalType2)
                         <vALUE SEQUENCE {LocalType1, LocalType2} ::=
                         {LocalValue1, LocalValue2}> "]"
   END
END

Error Message

"a0194w.asn", line 7 (A0194W): A0194W: The localvaluereference should start with an uppercase letter.

  <vALUE SEQUENCE {LocalType1, LocalType2} ::=

Possible Solution

Capitalize the first letter of the local value reference.

C0195W

Message Format

C0195W: It is ambiguous whether an some ASN.1 component or some ASN.1 component is meant (choosing the former).

Message Cause

The input ASN.1 syntax contains ambiguous notation in a macro definition. A symbol in the local productions may be interpreted in more that one way.

Example

Module-C0195W DEFINITIONS ::= BEGIN
   OBJECT-CLASS MACRO ::= BEGIN
      TYPE NOTATION  ::= "{"Attributes"}"
      VALUE NOTATION ::= value (VALUE OBJECT IDENTIFIER)
      Attributes     ::= Att | Attributes "," Att
      Att  ::= Att1 | Att2
      Att1 ::= value(ATTRIBUTE)
      Att2 ::= value(ATTRIBUTE-SET)
   END
   Top ::= OBJECT-CLASS {objectClass}
END

Error Message

"c0195w.asn", line 11 (Module-C0195W): C0195W: It is ambiguous whether an anonymous local value or an anonymous local value is meant (choosing the former).

  Top ::= OBJECT-CLASS {objectClass}

Possible Solution

Remove the ambiguity.

C0196W

Message Format

C0196W: The recent input can be interpreted as either 'macro production 1' or 'macro production 2'.

Message Cause

The input ASN.1 syntax contains two or more productions in a macro definition that cause ambiguity problems in macro instances.

Example

Module-C0196W DEFINITIONS ::= BEGIN
   OBJECT-CLASS MACRO ::= BEGIN
      TYPE NOTATION  ::= "{"Attributes"}"
      VALUE NOTATION ::= value (VALUE OBJECT IDENTIFIER)
      Attributes     ::= Att | Attributes "," Att
      Att  ::= Att1 | Att2
      Att1 ::= value(ATTRIBUTE)
      Att2 ::= value(ATTRIBUTE-SET)
   END
   Top ::= OBJECT-CLASS {objectClass}
END

Error Message

"c0196w.asn", line 10 (Module-C0196W): C0196W: The recent input can be interpreted as either 'Att1' or 'Att2'.

  Top ::= OBJECT-CLASS {objectClass}

Possible Solution

Define the parts of the ambiguous productions.

A0197W

Message Format

A0197W: Macro 'macro reference' is used without arguments.

Message Cause

A required argument is missing from a macro instance.

Example

Module-A0197W DEFINITIONS ::= BEGIN
   OBJECT-CLASS MACRO ::= BEGIN
     TYPE NOTATION  ::= "{"Attributes"}"
     VALUE NOTATION ::= value (VALUE OBJECT IDENTIFIER)
     Attributes     ::= Att | Attributes "," Att
     Att  ::= Att1 | Att2
     Att1 ::= value(ATTRIBUTE)
     Att2 ::= value(ATTRIBUTE-SET)
  END
  Top1 ::= OBJECT-CLASS
END

Error Message

"a0197w.asn", line 11 (Module-A0197W): A0197W: Macro 'OBJECT-CLASS' is used without arguments.

Possible Solution

Add the argument to the macro instance.

C0198E

Message Format

A0198E: No more than two occurrences of '...' are permitted in each SET or SEQUENCE.

Message Cause

This error message is generated when the extension marker '...' is used in more than two locations in each SET or SEQUENCE.

Example

Module-A0198E DEFINITIONS ::= BEGIN
   Type1 ::= SET {
      a  INTEGER,
      b  BOOLEAN,
      ... ,
      c  OCTET STRING,
      ... ,
      d  BIT STRING,
      ...
   }
END

Error Message

"a0198e.asn", line 9 (Module-A0198E): A0198E: No more than two occurrences of '...' are permitted in each SET or SEQUENCE.

Possible Solution

Make sure you do not have more than two extension marker fields in a SEQUENCE or a SET.

L0199W

Message Format

L0199W: Ignoring filename: filename 1. Error file output will be written to filename 2.

Message Cause

The -errorFile option is specified more than once on a command line.

Possible Solution

Make sure you specify the -errorFile option on the command line only once.

A0200E

Message Format

A0200E: 'component identifier' contains a constraint in which an Object Class is being used as an ObjectSet.

Message Cause

A constraint requires an object set reference, but an object class reference was found instead.

Example

Module-A0200E DEFINITIONS AUTOMATIC TAGS ::= BEGIN

TCIP-CLASS ::= CLASS {
        &Type,          -- ASN.1 Name
        &description    IA5String OPTIONAL,
        &id             OBJECT IDENTIFIER UNIQUE
}  WITH SYNTAX {
        &Type   IDENTIFIED BY &id
        [WITH DESCRIPTION &description]
}

Msg ::= SEQUENCE {
            msgName         IA5String,
            tcipId          TCIP-CLASS.&id ({TCIP-CLASS}),
            tcipType        TCIP-CLASS.&Type ({TCIP-CLASS}{@tcipId})
        }

END

Error Message

"a0200e.asn", line 14 (Module-A0200E): A0200E: 'tcipId' contains a constraint in which an Object Class is being used as an ObjectSet.

"a0200e.asn", line 15 (Module-A0200E): A0200E: 'tcipType' contains a constraint in which an Object Class is being used as an ObjectSet.

Possible Solution

Replace the object class reference with an object set reference.

A0201E

Message Format

A0201E: 'item name' is being used as a typereference, but has been used elsewhere in the current module as a ASN.1 component.

Message Cause

This error occurs when you use a symbol that is not a type reference instead of a type reference.

Example

Module-A0201E DEFINITIONS AUTOMATIC TAGS ::= BEGIN
   T4{Y} ::= SEQUENCE {
      a INTEGER,
      b Y
   }
   A ::= T4
END

Error Message

"a0201e.asn", line 6 (Module-A0201E): A0201E: 'T4' is being used as a typereference, but has been used elsewhere in the current module as a parameterized typereference.

  A ::= T4

Possible Solution

Replace the symbol with a type reference.

A0202E

Message Format

A0202E: The Literal 'literal' must be different from the first Literal of all immediately preceding OptionalGroups.

Message Cause

This error occurs when you use the same literal for more than one optional group specification.

Example

Module-A0202E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR ::= CLASS {
      &ParameterType OPTIONAL,
      &errorCode INTEGER OPTIONAL
   }
   WITH SYNTAX
   {
      [PARAMTYPE &ParameterType]
      [PARAMTYPE &errorCode]
   }
END

Error Message

"a0202e.asn", line 10 (Module-A0202E): A0202E: The Literal 'PARAMTYPE' must be different from the first Literal of all immediately preceding OptionalGroups.

  [PARAMTYPE &errorCode]

Possible Solution

Rename the literal.

A0203E/A0203W

Message Format

A0203E: 'type reference or identifier' is exported but is not defined.

Message Cause

The EXPORTS statement contains one or more undefined arguments.

Example

Module-A0203E DEFINITIONS ::= BEGIN
   EXPORTS Timestam, 
   Timestamp ::= GeneralizedTime
END

Error Message

"a0203e.asn", line 2 (Module-A0203E): A0203E: 'Timestam' is exported but is not defined.

Possible Solution

To correct this error, check the spelling of the arguments in the EXPORTS statement and make sure it matches the spelling of the arguments in its initial definition.

NOTE: Starting with version 8.1.2, if you specify the -ignoreIncompleteItems option, the ASN.1 syntax checker displays a warning instead of an error message.

A0204W

Message Format

A0204W: Module 'module reference' is not defined.

Message Cause

An IMPORTS statement contains a source that has not been defined in the input.

Example

Module-A0204W DEFINITIONS ::= BEGIN
   IMPORTS Response FROM ModF;
   Timestamp ::= GeneralizedTime
END

Error Message

"a0204w.asn", line 2 (Module-A0204W): A0204W: Module 'ModF' is not defined.

Possible Solution

Define the source module in the input.

A0205W

Message Format

A0205W: Redefinition of module 'module reference'.

Message Cause

Two or more modules in the input ASN.1 syntax have the same name.

Example

Module-A0205W DEFINITIONS ::= BEGIN
   Timestamp ::= GeneralizedTime
END

Module-A0205W DEFINITIONS ::= BEGIN
   Timestamp2 ::= GeneralizedTime
END

Error Message

"a0205w.asn", line 6 (Module-A0205W): A0205W: Redefinition of module 'Module-A0205W'.

  Module-A0205W DEFINITIONS ::= BEGIN

Possible Solution

Make sure all modules names are unique.

C0206W

Message Format

C0206W: Ranges must be in increasing order. Assuming x..y instead of y..x.

Message Cause

The interval boundaries in the ValueRange constraint are not specified correctly. The lower limit must be specified after the opening parenthesis and the upper limit must be specified before the closing parenthesis.

Example

Module-C0206W DEFINITIONS ::= BEGIN
   ApplicationNo ::= INTEGER (4..2)
END

Error Message

"c0206w.asn", line 2 (Module-C0206W): C0206W: Ranges must be in increasing order. Assuming 2..4 instead of 4..2.

Possible Solution

To correct this error, reverse the order of the limits in the ValueRange constraint.

A0207W

Message Format

A0207W: Illegal subset: 'x' is not a value of the parent type.

Message Cause

A subset constraint contains values that are not present in the parent type.

Example

Module-A0207W DEFINITIONS ::= BEGIN
   Positive ::= INTEGER (0<..MAX)
   Int ::= [1] Positive (-5 .. 10)
END

Error Message

"a0207w.asn", line 3 (Module-A0207W): A0207W: Illegal subset: '-5' is not a value of the parent type.

Possible Solution

Ensure that all values in a subset constraint exist in the parent type.

A0208W

Message Format

A0208W: The component referenced by a ComponentRelationConstraint (using the AtNotation) must be textually within the same type though possibly at a different level of nesting.  The reference through field 'identifier' of type 'type reference' is not permitted.

Message Cause

A component relation constraint is defined with a field that references another field defined outside of the structure that contains the component relation constraint.

Example

Module-A0208W DEFINITIONS ::= BEGIN

 . . . .

 ExternSeq ::= SEQUENCE {
   tcipId       TCIP-CLASS.&id ({TCIP-ObjSet}),
   nameField    IA5String
 }

 Msg ::= SEQUENCE {
   msgName      IA5String,
   externRef    ExternSeq,
   tcipType     TCIP-CLASS.&Type ({TCIP-ObjSet}{@externRef.tcipId})
 }
END

Error Message

"a0208W.asn", line 64 (Module-A0208W): A0208W: The component referenced by a ComponentRelationConstraint (using the AtNotation) must be textually within the same type though possibly at a different level of nesting.  The reference through field 'externRef' of type 'ExternSeq' is not permitted.

Possible Solution

Place the referenced field inside the structure that contains the component relation constraint.

A0209W

Message Format

A0209W: The element 'identifier' has an ANY DEFINED BY identifier 'identifier' which is a CHOICE.

Message Cause

An ANY DEFINED BY references a CHOICE type.

Example

Module-A0209W DEFINITIONS ::= BEGIN
   TestType   ::= CHOICE {
      errorMessage INTEGER(101| 102),
      rating ENUMERATED { good(0), bad(1) }
   }
   TestRecord ::= SEQUENCE {
      testCode INTEGER,
      result1 TestType,
      result2 ANY DEFINED BY result1
   }
END

Error Message

"a0209w.asn", line 9 (Module-A0209W): A0209W: The element 'result2' has an ANY DEFINED BY identifier 'result1' which is a CHOICE.

Possible Solution

Change the identifier following the ANY DEFINED BY.

C0210W

Message Format

C0210W: There is an ANY DEFINED BY identifier 'identifier' which is a CHOICE.

Message Cause

An unnamed ANY DEFINED BY references a CHOICE type.

Example

Module-C0210W DEFINITIONS ::= BEGIN
   MessageType1 ::= CHOICE {
      name OBJECT IDENTIFIER,
      code INTEGER
   }
   MessageType2 ::= SET {
      name1 MessageType1,
            [1] ANY DEFINED BY name1
   }
END

Error Message

"c0210w.asn", line 8 (Module-C0210W): C0210W: There is an ANY DEFINED BY identifier 'name1' which is a CHOICE.

Possible Solution

Change the identifier following the ANY DEFINED BY.

A0211W

Message Format

A0211W: It is not clear which element of the SET or CHOICE the value belongs to. Assuming element #x.

Message Cause

The input ASN.1 syntax contains an ambiguous value assignment of CHOICE or SET type.

Example

Module-A0211W DEFINITIONS ::= BEGIN
   E ::= SET { INTEGER OPTIONAL, INTEGER }
   y E ::= { 211 }
END

Error Message

"a0211w.asn", line 3 (Module-A0211W): A0211W: It is not clear which element of the SET or CHOICE the value belongs to. Assuming element #2.

  y E ::= { 211 }

Example

Module1 DEFINITIONS ::= BEGIN
   B ::= INTEGER
END

Module2 DEFINITIONS ::= BEGIN
   IMPORTS B FROM Module1;
   B ::= BOOLEAN
   C ::= SEQUENCE {
      B,
      Module1.B
   }
END

Error Message

"c0214i.asn", line 7 (Module2): C0214I: The imported type 'B' is being redefined.

  B ::=  BOOLEAN

Possible Solution

Make sure imported types are not redefined in the importing module.

C0215I

Message Format

C0215I: The imported value 'value reference' is being redefined.

Message Cause

This error is generated if you redefine an imported value inside a module that contains an IMPORTS statement.

Example

Module1 DEFINITIONS ::= BEGIN
  R ::= REAL
  pi R ::= {3142, 10, -3}
END

Module2 DEFINITIONS ::= BEGIN
  IMPORTS pi, R FROM Module1;
  B ::= BOOLEAN
  p REAL ::= pi
  pi R ::= {314, 10, -2}
END

Error Message

"c0215i.asn", line 10 (Module2): C0215I: The imported value 'pi' is being redefined.

  pi R ::= {314, 10, -2}

Possible Solution

Make sure imported values are not redefined in the importing module.

C0216E

Message Format

C0216E: COMPILER ERROR #50.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

A0217W

Message Format

A0217W: The identifier 'identifier' is missing from the value and is assumed.

Message Cause

One or more values assigned in a value assignment of a structured type are not accompanied by the identifier of the intended component.

Example

Module-A0217W DEFINITIONS ::= BEGIN
   Seq ::= SEQUENCE {
      int   INTEGER,
      bool  BOOLEAN,
      real  REAL
   }
   mySeq Seq ::= {int  5, bool TRUE, {3142, 10, -3}}
END

Error Message

"a0217w.asn", line 7 (Module-A0217W): A0217W: The identifier 'real' is missing from the value and is assumed.

  mySeq Seq ::= {int  5, bool TRUE, {3142, 10, -3}}

Possible Solution

Add the identifier of the intended component before the value on the right side of the value assignment.

A0218W

Message Format

A0218W: 'identifier' is not a standard identifier for component 1.

Message Cause

The first identifier of an OBJECT IDENTIFIER value is not defined by the ASN.1 standard.

Possible Solution

Replace the identifier of the first node with one defined by the ASN.1 standard.

A0219E

Message Format

A0219E: No root alternatives are permitted after a pair of '...' in each CHOICE.

Message Cause

The alternatives of a CHOICE type are listed after the two extensibility markers.

Example

Module-A0219E DEFINITIONS ::= BEGIN
   A ::= CHOICE {
         c BOOLEAN,
         ... ,
         ... ,
         d OCTET STRING
      }
END

Error Message

"a0219e.asn", line 5 (Module-A0219E): A0219E: No root alternatives are permitted after a pair of '...' in each CHOICE.

  ...,

Possible Solution

Remove the alternatives or add them before the extensibility markers.

C0220I

Message Format

C0220I: No PDUs in abstract syntax.

Message Cause

The input ASN.1 syntax does not contain unreferenced ASN.1 data types that can be encoded/decoded as separate units.

Example

Module-C0220I DEFINITIONS ::= BEGIN
   a INTEGER ::= 3
END

Error Message

"c0220i.asn" (Module-C0220I): C0220I: No PDUs in abstract syntax.

Possible Solution

Add unreferenced ASN.1 data types to the input specification.

C0221E

Message Format

C0221E: Forward references within selection values and within inner subtypes are not supported.

Message Cause

A forward reference involves a selection value or an inner subtype. This is not supported by the ASN.1 compiler.

Example

Module-C0221E DEFINITIONS ::= BEGIN
   UseE ::= E (WITH COMPONENTS {...,b (TRUE) })
   E ::= [0] SEQUENCE {a INTEGER, b BOOLEAN OPTIONAL}
   c CurrentAttributes ::=
   {
       date-last-used      27,
       file-name           "PROGRAM"
   }
   CurrentAttributes ::= [1] SEQUENCE
   {
       date-last-used < FileAttribute,
       file-name      < FileAttribute
   }
   FileAttribute ::= CHOICE
   {
       date-last-used  INTEGER,
       file-name       VisibleString
   }
END

Error Message

"c0221e.asn", line 6 (Module-C0221E): C0221E: Forward references within selection values and within inner subtypes are not supported.

  date-last-used      27,

Possible Solution

Place the definition of referenced types before the types that reference them.

A0222W

Message Format

A0222W: 'value reference' is already defined on the integer list.

Message Cause

The INTEGER NamedNumber specified on the left side of a value assignment already exists.

Example

Module-A0222W DEFINITIONS ::= BEGIN
   Code1 ::= INTEGER {ten(10), nine(9)}
   ten Code1 ::= 10
END

Error Message

"a0222w.asn", line 3 (Module-A0222W): A0222W: 'ten' is already defined on the integer list.

Possible Solution

Rename the value reference so that it does not conflict with an already-defined NamedNumber.

C0223E

Message Format

C0223E: Forward references within selection values are not supported.

Message Cause

A forward reference involves a selection type. This is not supported by the ASN.1 compiler.

Example

Module-C0223E DEFINITIONS ::= BEGIN
   oxygen SymbolicForm ::=  "O"
   SymbolicForm ::= symbol < Element
   Element ::= CHOICE {
      atomicNumber   INTEGER (1..109),
      symbol         PrintableString (SIZE(1..2))
   }
END

Error Message

"c0223e.asn", line 4 (Module-C0223E): C0223E: Forward references within selection values are not supported.

  Element ::= CHOICE {

Example

Module-A0226E ::= BEGIN
   Testseq ::= SEQUENCE {
      a  INTEGER,
      b  VisibleString,
      c  OCTET STRING
   }
END

Error Message

"a0226e.asn", line 1 (Module-A0226E): A0226E: Symbol, DEFINITIONS, is missing.  Symbol assumed.

  Module-A0226E ::= BEGIN

Possible Solution

Add an unreferenced ASN.1 data type to the input specification.

A0227E

Message Format

A0227E: Can't export an imported name: name.

Message Cause

An EXPORTS statement contains an item that was imported using an IMPORTS statement in the same module. According to the ASN.1:1990 standard, this is not allowed.

Example

Application DEFINITIONS ::= BEGIN
   Responder ::= BOOLEAN
END

Common DEFINITIONS ::= BEGIN
   EXPORTS Timestamp, Responder;
   IMPORTS Responder FROM Application;
   Timestamp ::= GeneralizedTime
   Result ::= Responder
END

Error Message

"a0227e.asn", line 6 (Common): A0227E: Can't export an imported name: Responder.

Possible Solution

Specify the -2021 option and compile your syntax.

A0228E

Message Format

A0228E: 'module reference' is not a legal modulereference (must start with uppercase letter).

Message Cause

The first letter of a module's name is not an uppercase letter.

Example

module-A0228E DEFINITIONS ::= BEGIN
   Responder ::= BOOLEAN
END

Error Message

"a0228e.asn", line 1 (): A0228E: 'module-A0228E' is not a legal modulereference (must start with uppercase letter).

  module-A0228E DEFINITIONS ::= BEGIN

Example

Module-A0222W DEFINITIONS ::= BEGIN
   Code1 ::= INTEGER {ten(10), nine(9)}
   ten Code1 ::= 10
END

Error Message

"a0238w.asn", line 1 (Module-A0238W): A0238W: 'DEFINTIONS' is assumed to be a misspelling of 'DEFINITIONS'.

  Module-A0238W DEFINTIONS ::= BEGIN

Possible Solution

Correct the spelling of the word.

A0239W

Message Format

A0239W: The component 'identifier' is referenced by componentRelationConstraint (using the AtNotation), and therefore must be constrained with a TableConstraint.

Message Cause

In a component relation constraint the component that follows the '@' symbol is not constrained with a table constraint.

Example

Module-A0239W DEFINITIONS ::= BEGIN
  . . . .

  TCIP-ObjSet TCIP-CLASS ::= {
    cpt-ActivationDate |
    cpt-ActivationStatus |
    cpt-ActivationTime,
    ...
  }

  Msg ::= SEQUENCE {
    msgName         IA5String,
    tcipId          TCIP-CLASS.&id,
    tcipType        TCIP-CLASS.&Type ({TCIP-ObjSet}{@tcipId})
  }
END

Error Message

"a0239w.asn", line 60 (Module-A0239W): A0239W: The component 'tcipId' is referenced by a ComponentRelationConstraint (using the AtNotation), and therefore must be constrained with a TableConstraint.

Possible Solution

Add a table constraint to the component. For example, you can use: tcipId TCIP-CLASS.&id ({TCIP-ObjSet}).

C0240S

Message Format

C0240S: COMPILER ERROR #21.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

A0241E

Message Format

A0241E: In parsing an instance of the macro 'macro reference', expecting one of the following:  expected ASN.1 component.

Message Cause

A macro instance contains an invalid symbol.

Example

Module-A0241E DEFINITIONS ::= BEGIN
   OBJECT-CLASS MACRO ::= BEGIN
      TYPE NOTATION    ::= "{"Attributes"}"
      VALUE NOTATION   ::= value (VALUE OBJECT IDENTIFIER)
      Attributes       ::= Att | Attributes "," Att
      Att  ::= Att1 | Att2
      Att1 ::= value(ATTRIBUTE)
      Att2 ::= value(ATTRIBUTE-SET)
   END
   bTop OBJECT-CLASS ::= 5
END

Error Message

"a0241e.asn", line 10 (Module-A0241E): A0241E: In parsing an instance of the macro 'OBJECT-CLASS', expecting one of the following: a value of type _ObjectID.

  bTop OBJECT-CLASS ::= 5

Possible Solution

Verify the ASN.1 compiler's recommendation and change the symbol.

A0242E

Message Format

A0242E: The element 'identifier' is defined recursively and therefore must be OPTIONAL.

Message Cause

The input ASN.1 syntax contains a recursive definition of a component of a SET or SEQUENCE that is not marked as OPTIONAL.

Example

Module-A0242E  DEFINITIONS ::= BEGIN
   E1 ::= [1] SET { a INTEGER OPTIONAL,  b E1 }
   E2 ::= [2] SET { a INTEGER OPTIONAL,  c E2 OPTIONAL}
   y E2 ::= {a 1, c{a 2, c{c {a 3}}}}
END

Error Message

"a0242e.asn", line 2 (Module-A0242E): A0242E: The element 'b' is defined recursively and therefore must be OPTIONAL.

Possible Solution

Mark the component as OPTIONAL.

C0243S

Note

Contact Technical Support ‹support@oss.com›.

C0244I

Message Format

C0244I: No types to print, so [header file] / [Java classes] was/were not created.

Message Cause

The input ASN.1 syntax does not contain unreferenced ASN.1 types which can be represented as PDUs in the output generated files.

Possible Solution

To mark the types you want in the header file, use the OSS.PDU directive.

C0245I

Message Format

C0245I: x warning message(s) suppressed, y informatory message(s) suppressed. To see the suppressed messages use the option -warningMessages.

Message Cause

The messages cannot be displayed because one or more of the following options are specified:

The -suppress option or the OSS.SUPPRESS compiler directive
The -nowarningMessages option
The -relaxedMode option

Possible Solution

To view the suppressed messages, specify the -warningMessages option and remove the -suppress option and/or the OSS.SUPPRESS compiler directive.

C0246I

Message Format

C0246I: Skipping to line x.

Message Cause

The input ASN.1 specification was processed with difficulty due to an non-severe error, therefore the ASN.1 compiler skipped to the specified line and continued syntax checking from there.

Possible Solution

Check the lines before the specified line number for syntax errors.

A0247E

Message Format

A0247E: Expecting identifier's selection type to be a choice type.

Message Cause

This error occurs when a selection type is not based on a CHOICE type.

Example

Module-A0247E DEFINITIONS ::= BEGIN
   Choice1 ::= SEQUENCE {
      a INTEGER,
      b BOOLEAN
   }
   Seq1    ::= SEQUENCE {
      a INTEGER,
      b NULL,
      c b < Choice1
   }
END

Error Message

"a0247e.asn", line 9 (A0247E): A0247E: Expecting c's selection type to be a choice type.

Possible Solution

Use CHOICE as a type for the selection type.

A0248E

Message Format

A0248E: Can't use module 'module reference' within itself.

Message Cause

You are trying to import a type from the current module using the module-dot-component notation.

Example

Module-A0248E DEFINITIONS ::= BEGIN
   Timestamp ::= [PRIVATE 0] OCTET STRING
   Responder ::= [PRIVATE 1] Module-A0248E.Timestamp
END

Error Message

"a0248e.asn", line 3 (Module-A0248E): A0248E: Can't use module 'Module-A0248E' within itself.

  Responder ::= [PRIVATE 1] Module-A0248E.Timestamp

Possible Solution

Remove the module name and the period (".") from the reference.

A0249E

Message Format

A0249E: Enumerated value for 'identifier' is incorrectly defined.

Message Cause

One of the values specified in an ENUMERATED value assignment is not present in the parent type.

Example

Module-A0249E DEFINITIONS ::= BEGIN
   Result ::=  ENUMERATED {success(1), failure(0), unknown(2)}
   ParameterList ::=SEQUENCE {
       requestID INTEGER,
       command   PrintableString,
       result    ENUMERATED {success(1), failure(0)}
   }
   result1  Result        ::=  unknown
   parms    ParameterList ::= { requestID 1, command "a", result result1 }
END

Error Message

"a0249e.asn", line 9 (Module-A0249E): A0249E: Enumerated value for 'result' is incorrectly defined.

Possible Solution

Make sure all values specified in an ENUMERATED value assignment exist in the parent type.

A0250W

Message Format

A0250W: Enumerated value for 'identifier' is defined by an INTEGER type.

Message Cause

The input ASN.1 syntax contains a value assignment to an ENUMERATED type, but the value specified is of INTEGER type.

Example

Module-A0250W DEFINITIONS ::= BEGIN
   ParameterList ::= SEQUENCE {
      requestID INTEGER,
      command PrintableString OPTIONAL,
      result ENUMERATED {success(0), failure (1)} OPTIONAL
   }
   noresponse INTEGER ::= 1
   p ParameterList ::= {
      requestID 2,
      command "Come here and eat",
      result noresponse
   }
END

Error Message

"a0250w.asn", line 11 (Module-A0250W): A0250W: Enumerated value for 'result' is defined by an INTEGER type.

Possible Solution

Replace the INTEGER type value with an ENUMERATED type value.

L0251S

Message Format

L0251S: Message number to be suppressed, ignored or allowed, number, is invalid.

Message Cause

The argument of a -suppress option is an invalid message number.

NOTE: You may suppress only informatory and warning messages (message codes end in "I" or "W"). You may not suppress non-severe or severe error messages (message codes end in "E" or "S").

Possible Solution

Specify a valid message number to suppress (0064, for instance).

A0252W

Message Format

A0252W: Identifiers in the OBJECT IDENTIFIER values of the ModuleIdentifier do not match: 'node name' (in module Module1) and 'node name' (in this module).

Message Cause

An OBJECT IDENTIFIER value is associated with an ASN.1 module, but a reference to the same module lists a different associated OBJECT IDENTIFIER value.

Example

Module1 {joint-iso-ccitt node1(1) node2(2)} DEFINITIONS ::= BEGIN
   A ::= INTEGER
END

Module2 DEFINITIONS ::= BEGIN
   IMPORTS A FROM Module1
   B FROM Module1 {joint-iso-ccitt newNode1(1) newNode2(2)};
   a A ::= 2
END

Error Message

"a0252w.asn", line 7 (Module2): A0252W: Identifiers in the OBJECT IDENTIFIER values of the ModuleIdentifier do not match: 'node1' (in module Module1) and 'newNode1' (in this module).

  B FROM Module1 {joint-iso-ccitt newNode1(1) newNode2(2)};

Possible Solution

Make sure both OBJECT IDENTIFIER values are identical.

C0253E

Message Format

C0253E: Using "[" as an astring is not supported.

Message Cause

This error occurs when you use the character "[" in a macro definition. The OSS ASN.1 compiler does not support this character in macro definitions.

Example

Module-C0253E DEFINITIONS ::= BEGIN
   ERROR MACRO ::= BEGIN
      TYPE NOTATION ::= "[" "PARAMETER" NamedType "]" | empty
      VALUE NOTATION ::= value(VALUE INTEGER)
      NamedType ::= identifier type | type
   END
END

Error Message

"c0253e.asn", line 3 (Module-C0253E): C0253E: Using "[" as an astring is not supported.

  TYPE NOTATION ::= "[" "PARAMETER" NamedType "]" | empty

Possible Solution

Remove the "[" character from the macro definition.

L0254W

Message Format

L0254W: 'keyword 1' option overridden by 'keyword 2' option.

Message Cause

This error message is generated when you specify two mutually exclusive options on the command line (-controlFile and -codeFile, for instance). The ASN.1 compiler will use the last option specified.

Possible Solution

Remove one of the options from the command line.

C0255W

Message Format

C0255W: Number (large number) is too large to fit in x bytes. It is being truncated to smaller number.

Message Cause

A subtype constraint of an INTEGER type is too large for the chosen representation.

Example

Module-C0255W DEFINITIONS ::= BEGIN
   B ::= [2] INTEGER (2147483648) --<SHORT>--
END

Error Message

"c0255w.asn", line 2 (Module-C0255W): C0255W: Number (2147483648) is too large to fit in 2 bytes. It is being truncated to 65535.

Possible Solution

Apply the OSS.LONG or OSS.LONGLONG compiler directive to the type.

A0256W

Message Format

A0256W: 'item' is referenced, but is not defined.

Message Cause

This error occurs when you use an identifier, type reference, macro reference, or other item that is not defined.

Example

Module-A0256W DEFINITIONS ::= BEGIN
   aOne INTEGER ::= one
   code Code ::= 5
   MAC ::= AMACRO
END

Error Message

"a0256w.asn", line 4 (Module-A0256W): A0256W: 'AMACRO' is referenced, but is not defined.


  "a0256w.asn", line 3 (Module-A0256W): A0256W: 'Code' is referenced, but is not defined.


  "a0256w.asn", line 2 (Module-A0256W): A0256W: 'one' is referenced, but is not defined.

Possible Solution

Add a definition for the type in the module or import the definition from another module.

A0257W

Message Format

A0257W: 'item' is being imported from module 'module reference' but is not exported by module 'module reference'.

Message Cause

The input ASN.1 syntax contains an attempt to import a type from a module that does not exist in the source module.

Example

Module-A0257W DEFINITIONS ::= BEGIN
   IMPORTS one FROM Common;
   A ::= INTEGER
   a INTEGER ::= one
END

Common DEFINITIONS ::= BEGIN
   oNe INTEGER ::= 1
END

Error Message

"a0257w.asn", line 2 (Module-A0257W): A0257W: 'one' is being imported from module 'Common' but is not exported by module 'Common'.

Possible Solution

Ensure that the type in the source module and the one in the IMPORTS statement both use the same spelling.

C0258W

Message Format

C0258W: The size constraint is less than the maximum named bit for the element 'identifier'.

Message Cause

The size constraint applied to a BIT STRING is smaller than the value of the largest bit.

Example

Module-C0258W DEFINITIONS ::= BEGIN
   A ::= SEQUENCE {
      a BIT STRING {bit-a(2000)} (SIZE(4)),
      b INTEGER (1..123) --<SHORT>--
   }
END

Error Message

"c0258w.asn", line 3 (Module-C0258W): C0258W: The size constraint is less than the maximum named bit for the element 'a'.

Possible Solution

Increase the size constraint to include the largest bit value.

A0259E

Message Format

A0259E: Element #x is defined recursively and therefore must be OPTIONAL.

Message Cause

A recursive element in a structured type is not marked as OPTIONAL.

Example

Module-A0259E  DEFINITIONS ::= BEGIN
   E1 ::= [1] SET {  INTEGER OPTIONAL,   E1 }
   E2 ::= [2] SET {  INTEGER OPTIONAL,  E2 OPTIONAL}
   y E2 ::= { 1, { 2, { { 3}}}}
END

Error Message

"a0259e.asn", line 2 (Module-A0259E): A0259E: Element #2 is defined recursively and therefore must be OPTIONAL.

Possible Solution

Mark the element as OPTIONAL.

C0260E

Message Format

C0260E: The OBJECTID directive must have a value that is equal to 2 or greater.

Message Cause

The argument of an OSS.OBJECTID directive is less than 2. The argument specifies how many octets the BER-encoded OBJECT IDENTIFIER value must store and must be between 2 and 32,767.

Example

Module-C0260E  DEFINITIONS ::= BEGIN
   Name1 ::= [0] OBJECT IDENTIFIER --<OBJECTID 1>--
   Name2 ::= [1] OBJECT IDENTIFIER --<OBJECTID 10>--
END

Error Message

"c0260e.asn", line 2 (Module-C0260E): C0260E: The OBJECTID directive must have a value that is equal to 2 or greater.

  Name1 ::= [0] OBJECT IDENTIFIER --<OBJECTID 1>--

Possible Solution

Make sure the argument of the OSS.OBJECTID directive does not exceed the accepted range (between 2 and 32,767).

A0261E

Message Format

A0261E: The object identifier value for module 'Module2' and 'Module1' are the same.

Message Cause

Two modules have the same OBJECT IDENTIFIER. The OBJECT IDENTIFIER for each module must be unique.

Example

Module1 {joint-iso-ccitt node1(1) node2(2)} DEFINITIONS ::= BEGIN
   A ::= INTEGER
END

Module2 {joint-iso-ccitt node1(1) node2(2)} DEFINITIONS ::= BEGIN
   a INTEGER ::= 2
END

Error Message

"a0261e.asn", line 5 (Module2): A0261E: The object identifier value for module 'Module2' and 'Module1' are the same.

  Module2 {joint-iso-ccitt node1(1) node2(2)} DEFINITIONS ::= BEGIN

Possible Solution

Make sure the OBJECT IDENTIFIER values are unique.

A0262W

Message Format

A0262W: More than one assignment to VALUE in macro instance.

Message Cause

A macro instance has more than one value assignment.

Possible Solution

Remove the extra value assignments.

C0263E/C0263W

Message Format

C0263E: 'module reference' is on the ROOT module list but has no assignments.

Message Cause

The OSS.ROOT compiler directive lists the name of a module that is not defined in the input.

Example

--<OSS.ROOT Root1, Root2>--

Module-C0263E DEFINITIONS ::= BEGIN
   Az ::= INTEGER
END

Root1 DEFINITIONS ::= BEGIN
   Root1z ::= ENUMERATED {a(223)}
END

Error Message

"c0263e.asn", line 1 (Module-C0263E): C0263E: 'Root2' is on the ROOT module list but has no assignments.

Possible Solution

Add a definition for the missing module in the input specification.

NOTE: Starting with version 8.1.2, if you specify the -ignoreIncompleteItems option, instead of displaying an error message, the ASN.1 syntax checker displays a warning.

C0264E

Message Format

C0264E: The control table external name 'name' conflicts with a reserved word.  Use the EXTERNALNAME compiler parameter to change this name.

Message format when using the compiler GUI:

C0264E: The control table external name 'name' conflicts with a reserved word. To change this name, please type the new name in the "Control table external name" edit box in the "Code Generation" tab of the "Compiler Options" window.

Message Cause

The default name (taken from the last input ASN.1 file) or the name specified using the -externalName command-line option conflicts with a reserved word in the target programming language.

Possible Solution

Change the name of the variable that references the control table or code file entry points with the -externalName ASN.1 compiler option.

C0265E

Message Format

C0265E: Found recursively defined CHOICE 'identifier' which contains no non-recursive elements.

Message Cause

One or more non-recursive elements are missing from a recursive element in a CHOICE type.

Example

Module-C0265E DEFINITIONS ::= BEGIN
   G ::= CHOICE {
      g G
   }
END

Error Message

"c0265e.asn", line 3 (Module-C0265E): C0265E: Found recursively defined CHOICE 'g' which contains no non-recursive elements.

Possible Solution

Add non-recursive elements to the CHOICE type.

L0266W

Message Format

L0266W: Ignoring filename: filename 1. Code file output will be written to filename 2.

Message Cause

Two or more instances of the -codeFile option are followed by different filename arguments on the command line. The ASN.1 compiler will use the last filename specified.

Possible Solution

Remove the extra -codeFile options and their arguments.

C0267E

Message Format

C0267E: Number large number is too large.

Message Cause

This error occurs when a given number is too large for the specified value.

Example

Module-C0267E DEFINITIONS ::= BEGIN
   pi REAL ::= {3141592653589793238462643383279, 10, -30}
END

Error Message

"c0267e.asn" (Module-C0267E): C0267E: Number 3141592653589793238462643383279 is too large.

Possible Solution

Choose a smaller number or use a different representation.

C0268E

Message Format

C0268E: Negative number negative number found where positive number is needed.

Message Cause

This error occurs when you use a negative number where a positive one is required.

Possible Solution

Replace the negative number with a positive one.

C0269W

Message Format

C0269W: directive name directive ignored because -soed option was specified.

Message format when using the compiler GUI:

C0269W: directive name directive ignored because the "Generate space-optimized encoder/decoder (SOED)" radio button in the "Runtime Control" tab of the "Compiler Options" window is checked.

Message Cause

A compiler directive could not be used because it is incompatible with the -soed option that was specified.

Possible Solution

Remove the incompatible compiler directive.

A0270E

Message Format

A0270E: Unmatched braces detected in the previous assignment statement.

Message Cause

One or more opening braces ("{") do not have corresponding closing braces ("}").

Example

Module-A0270E DEFINITIONS ::= BEGIN
   Employee5 ::= SEQUENCE  {
      name       VisibleString,
      nickname   VisibleString  OPTIONAL,
      groupno    INTEGER  DEFAULT 33000
      emp1 Employee5 ::= {name "Brown", nickname "Half Pint", groupno 5
      emp2 Employee5 ::= {name "John", nickname "none", groupno 10}
END

Error Message

"a0270e.asn", line 7 (OneBrace): A0270E: Unmatched braces detected in the previous assignment statement.

  emp2 Employee5 ::= {name "John", nickname "none", groupno 10}

Example

--<ASN1.Remove Module-C0279W.S2.gStr>--
--<OSS.UseThis Module-C0279W.S1 Module-C0279W.S2>--

Module-C0279W DEFINITIONS ::= BEGIN
  S1 ::= SEQUENCE {
     tStr TeletexString --<UNBOUNDED>--,
     gStr GraphicString
  }
  S2 ::= SEQUENCE {
     tStr TeletexString --<UNBOUNDED>--,
     gStr GraphicString OPTIONAL
  }
END

Error Message

"c0279w.asn", line 2 (Module-C0279W): C0279W: The OSS.UseThis directive was not applied to the type with the absolute reference 'Module-C0279W.S1' because the type with the absolute reference 'Module-C0279W.S2' was marked for removal or contains fields marked for removal.

Possible Solution

Remove the directive.

x0280x

Note

This message number is reserved for future use.

An argument of an OSS.OBJECTID directive exceeds the maximum allowed number (i.e. 32767).

Example

Module-C0289W DEFINITIONS ::= BEGIN
   Name1 ::= [1] OBJECT IDENTIFIER --<OBJECTID 40000>--
   ftam1 Name1 ::= {1 2 4 67 3}
END

Error Message

"c0289w.asn", line 2 (Module-C0289W): C0289W: OBJECTID 40000 exceeds maximum allowed for type 'Name1'. OBJECTID value changed to 32767.

Possible Solution

Make sure you use values that fall within the accepted range.

A0290E

Message Format

A0290E: Not expecting any more values in the ASN.1 data type.

Message Cause

In a value assignment to a multiple component ASN.1 type there are more values than elements.

Example

Module-A0290E DEFINITIONS ::= BEGIN
   Building ::= SET {
      address   VisibleString,
      occupied  BOOLEAN
   }
   headquarters Building ::= {
      address  "100 Central Avenue",
      occupied TRUE,
      123
   }
END

Error Message

"a0290e.asn", line 9 (Module-A0290E): A0290E: Not expecting any more values in the SET.

  123

Possible Solution

Remove the extra values at the end of the value assignment.

C0291W

Message Format

C0291W: The integer value (large number) exceeds the directive or subtype constraints for type 'type reference'.

Message Cause

The specified value of an INTEGER type exceeds its subtype constraint or the maximum value of its representation.

Example

Module-C0291W DEFINITIONS ::= BEGIN
   B ::= [0] INTEGER (1..123456789) --<SHORT>--
END

Error Message

"c0291w.asn", line 2 (Module-C0291W): C0291W: The integer value (123456789) exceeds the directive or subtype constraints for type 'B'.

Possible Solution

Type a value that does not exceed its subtype constraint or use a different representation.

C0292W

Message Format

C0292W: In this context the SIZE constraint should not be enclosed in parentheses.

Message Cause

A SIZE constraint is enclosed in parentheses that are not appropriate for the specific context in which they appear.

Possible Solution

Remove the extra parentheses.

C0293E

Message Format

C0293E: macro astring cannot start with '--'.

Message Cause

A macro definition contains a string enclosed in quotation marks andprefixed by two hyphens ("--"). This may cause ambiguities between the macro instance and the start of a user comment.

Example

Module-C0293E DEFINITIONS ::= BEGIN
   ERROR MACRO ::= BEGIN
      TYPE NOTATION ::= "--PARAMETER" NamedType | empty
      VALUE NOTATION ::= value(VALUE INTEGER)
      NamedType ::= identifier type | type
   END
END

Error Message

"c0293e.asn", line 3 (Module-C0293E): C0293E: macro astring cannot start with '--'.

  TYPE NOTATION ::= "--PARAMETER" NamedType | empty

Possible Solution

Remove the two hyphens.

C0294W

Message Format

C0294W: Workfile 'filename' not deleted: string

Message Cause

The ASN.1 compiler could not remove the temporary workfile that it created at the same time as the time-optimized encoder/decoder code file.

Possible Solution

Remove the workfile manually.

A0295W

Message Format

A0295W: 'item' is being imported by this module but is not defined in module module reference.

Message Cause

The input ASN.1 syntax contains an attempt to import a type from a module that it is not defined in the source module.

Example

Module-A0295W DEFINITIONS ::= BEGIN
   IMPORTS J FROM A;
   i A.B ::= A.c
END

A DEFINITIONS ::= BEGIN
   EXPORTS;
   Q ::= INTEGER
   q Q ::= 3
END

Error Message

"A0295w.asn", line 2 (A): A0295W: 'J' is being imported by this module but is not defined in module A.


  "A0295w.asn", line 3 (A): A0295W: 'B' is being imported by this module but is not defined in module A.


  "A0295w.asn", line 3 (A): A0295W: 'c' is being imported by this module but is not defined in module A.

Possible Solution

Remove the invalid import attempts.

C0296W

Message Format

C0296W: Missing ':' in CHOICE value; colon assumed.

Message Cause

In a value assignment to a CHOICE type, the element identifier and the value on the right side are not separated by a colon.

NOTE: This warning is generated only if you have previously specified the -1993 option (or a later ASN.1 syntax standard).

Example

Module-C0296W DEFINITIONS ::= BEGIN
   Ch ::= CHOICE {
      a INTEGER,
      b BOOLEAN
   }
   ch Ch ::= a 5
END

Error Message

"c0296w.asn", line 6 (Module-C0296W): C0296W: Missing ':' in CHOICE value; colon assumed.

ch Ch ::= a 5

Possible Solution

If you are using ASN.1:2021 syntax standard, add a colon between the element identifier and its value.
If you are using ASN.1:1990 syntax standard, specify the -1990 compiler option.

C0297W

Message Format

C0297W: SET as a synonym for SET OF ANY is illegal; assuming SET OF ANY.

Message Cause

The input ASN.1 syntax contains an illegal attempt to use a built-in ASN.1 type as an ANY type.

Example

Module-C0297W DEFINITIONS ::= BEGIN
   SetofAny ::= SET
END

Error Message

"c0297w.asn", line 2 (Module-C0297W): C0297W: SET as a synonym for SET OF ANY is illegal; assuming SET OF ANY.

SetofAny ::= SET

Possible Solution

Remove the illegal ANY type simulation attempt.

C0298S

Message Format

C0298S: Parsing stack overflowed in instance of macro 'macro reference'.

Message Cause

The ASN.1 compiler ran out of parsing stack space while processing a macro instance. This error occurs if the complexity of the macro instance exceeds the implementation limitation of the ASN.1 compiler or if the macro definition is flawed.

Note that the OSS ASN.1 compiler successfully parses ASN.1 specifications that use macros (e.g., X.400, X.500, etc.). The most likely cause of this error is a flawed macro definition.

Example

Module-C0298S DEFINITIONS ::= BEGIN
   ERROR MACRO ::= BEGIN
      TYPE NOTATION  ::= empty
      VALUE NOTATION ::= value(VALUE ERROR)
   END
   error ERROR ::= 5
END

Error Message

"c0298s.asn", line 6 (Module-C0298S): C0298S: Parsing stack overflowed in instance of macro 'ERROR'.

error ERROR ::= 5

Possible Solution

Make sure the macro definition does not contain any infinitely recursive or faulty notations.

A0299E

Message Format

A0299E: The ANY type which is element 2 within a SET/SEQUENCE/CHOICE (within type reference) is used in an ambiguous context.

Message Cause

An ANY type might cause a tag conflict within a SET, SEQUENCE, or CHOICE.

Example

Module-A0299E DEFINITIONS ::= BEGI
   L ::= SET {
      seq SEQUENCE OF CHOICE {
         sharp INTEGER,
         ANY
      }
   }
END

Error Message

"a0299e.asn", line 5 (Module-A0299E): A0299E: The ANY type which is element 2 within a SET/SEQUENCE/CHOICE (within L) is used in an ambiguous context.

Possible Solution

Add an explicit tag to the ANY type.

C0300W

Message Format

C0300W: The USERFIELD directive is permitted only on an element which is OPTIONAL or has a DEFAULT value.  It is not valid on element 'identifier'.

Message Cause

An OSS.USERFIELD is applied to a component of a SET or SEQUENCE that is not marked as OPTIONAL or DEFAULT.

Example

Module-C0300W  DEFINITIONS ::= BEGIN
   Name1 ::= SET {
      name VisibleString,
      next INTEGER --<USERFIELD>--
   }
END

Error Message

"c0300w.asn", line 4 (Module-C0300W): C0300W: The USERFIELD directive is permitted only on an element which is OPTIONAL or has a DEFAULT value.  It is not valid on element 'next'.

Possible Solution

Make sure you apply the OSS.USERFIELD directive only to OPTIONAL or DEFAULT components of SET or SEQUENCE types.

C0301W

Message Format

C0301W: The USERFIELD directive is permitted only on an element which is OPTIONAL or has a DEFAULT value.

Message Cause

An OSS.USERFIELD is applied to a component of a SET or SEQUENCE that is not marked as OPTIONAL or DEFAULT.

Example

Module-C0301W  DEFINITIONS ::= BEGIN
   Name1 ::= SEQUENCE {
      name VisibleString,
           INTEGER --<USERFIELD>--
   }
END

Error Message

"c0301w.asn", line 4 (Module-C0301W): C0301W: The USERFIELD directive is permitted only on an element which is OPTIONAL or has a DEFAULT value.

Possible Solution

Make sure you apply the OSS.USERFIELD directive only to OPTIONAL or DEFAULT components of SET or SEQUENCE types.

C0302E

Message Format

C0302E: The USERFIELD directive is not valid on 'identifer'. It is valid only on an element of a SET or SEQUENCE.

Message Cause

An OSS.USERFIELD is applied to a component of a SET or SEQUENCE that is not marked as OPTIONAL or DEFAULT.

Example

Module-C0302E  DEFINITIONS ::= BEGIN
   Name1 ::= CHOICE {
      name VisibleString,
      next INTEGER --<USERFIELD>--
   }
END

Error Message

"c0302e.asn", line 4 (Module-C0302E): C0302E: The USERFIELD directive is not valid on 'next'.  It is valid only on an element of a SET or SEQUENCE.

Possible Solution

Make sure you apply the OSS.USERFIELD directive only to OPTIONAL or DEFAULT components of SET or SEQUENCE types.

C0303E

Message Format

C0303E: The USERFIELD directive is not valid on the Type specified in the SET OF Type.  It is valid only on an element of a SET or SEQUENCE.

Message Cause

An OSS.USERFIELD is applied to a component of a SET or SEQUENCE that is not marked as OPTIONAL or DEFAULT.

Example

Module-C0303E  DEFINITIONS ::= BEGIN
   Name1 ::= SET OF INTEGER --<USERFIELD>--
END

Error Message

"c0303e.asn", line 2 (Module-C0303E): C0303E: The USERFIELD directive is not valid on the Type specified in the SET OF Type.  It is valid only on an element of a SET or SEQUENCE.

Possible Solution

Make sure you apply the OSS.USERFIELD directive only to OPTIONAL or DEFAULT components of SET or SEQUENCE types.

C0304E

Message Format

C0304E: 'the Type specified in the ASN.1 type Type' uses both the directive name and PADDED directive which cannot be combined for ASN.1 type.

Message Cause

An OSS.PADDED and an incompatible compiler directive are applied to an ASN.1 type.

Example

Module-C0304E DEFINITIONS ::= BEGIN
   Name1 ::= SET OF BIT STRING (SIZE (4)) --<LINKED | PADDED>--
END

Error Message

"c0304e.asn", line 2 (Module-C0304E): C0304E: 'the Type specified in the SET OF Type' uses both the LINKED and PADDED directive which cannot be combined for BIT STRINGS.

Possible Solution

Remove one of the compiler directives.

A0305E

Message Format

A0305E: It is invalid to use 'UNIVERSAL' as a tag class in ASN.1 abstract syntaxes.

Message Cause

The input ASN.1 syntax contains an illegal attempt to mark a type with the UNIVERSAL tag class. This tag class is reserved for official built-in types.

Example

Module-A0305E DEFINITIONS ::= BEGIN
   T1 ::= [UNIVERSAL  99] INTEGER
END

Error Message

"a0305e.asn", line 2 (Module-A0305E): A0305E: It is invalid to use 'UNIVERSAL' as a tag class in ASN.1 abstract syntaxes.T1 ::= [UNIVERSAL  99] INTEGER

Possible Solution

Remove the UNIVERSAL keyword from the tag or specify the -ignoreError 309 option.

A0306W

Message Format

A0306W: Definition of module 'module reference' in ROOT directive is ambiguous.

Message Cause

An OSS.ROOT directive references a module name that was defined more than once.

Example

--<OSS.ROOT A>--

A DEFINITIONS ::= BEGIN
  Apples ::= [2] Bananas --<PDU>--
  Bananas ::= VisibleString
END

A DEFINITIONS ::= BEGIN
  Cantelope ::= BOOLEAN
  Dates ::= [1] ANY
END

Error Message

"a0306w.asn", line 8 (A): A0306W: Definition of module 'A' in ROOT directive is ambiguous

  A DEFINITIONS ::= BEGIN

Possible Solution

To avoid a name conflict, rename one of the modules.

A0307W

Message Format

A0307W: OSS has relaxed the standards to allow the definition of a type with tag [UNIVERSAL 8].  This is normally invalid ASN.1.

Message Cause

The input ASN.1 syntax contains an illegal attempt to use the UNIVERSAL tag class.

Example

Module-A0307W DEFINITIONS ::= BEGIN
   External ::= [UNIVERSAL 8] IMPLICIT SEQUENCE {
      direct-reference          OBJECT IDENTIFIER OPTIONAL,
      indirect-reference        INTEGER OPTIONAL,
      data-value-descriptor     ObjectDescriptor OPTIONAL,
      encoding CHOICE {
         single-ASN1-type   [0] ANY --<LINKED>--,
         octet-aligned      [1] IMPLICIT OCTET STRING,
         arbitrary          [2] IMPLICIT BIT STRING
      }
   }
END

Error Message

"a0307w.asn", line 2 (Module-A0307W): A0307W: OSS has relaxed the standards to allow the definition of a type with tag [UNIVERSAL 8].  This is normally invalid ASN.1.

Possible Solution

Remove the UNIVERSAL keyword from the tag.

A0308E

Message Format

A0308E: Premature end of ASN.1 type value.

Message Cause

This error may occur in case you specify that a component has a default value, but you do not supply the required value after the DEFAULT keyword.

Example

Module-A0308E DEFINITIONS ::= BEGIN
   Seq1 ::= SEQUENCE {
      a ParmType {INTEGER} DEFAULT,
      b BOOLEAN
   }

   ParmType {X} ::= SEQUENCE {
      a X,
      b INTEGER
   }

END

Error Message

"a0308e.asn", line 5 (Module-A0308E): A0308E: Premature end of open type value.

  }

Possible Solution

Add the required value after the DEFAULT keyword.

A0309E

Message Format

A0309E: Type in macro instance is circularly defined.

Message Cause

A macro definition has a circular definition.

Example

Module-A0309E DEFINITIONS ::= BEGIN
   ERROR MACRO ::= BEGIN
      TYPE NOTATION  ::= empty
      VALUE NOTATION ::= value(VALUE ERROR)

   END
   NewError ::= ERROR
   ErrorRecord ::= SEQUENCE {
      rectype ERROR,
      sector  INTEGER
   }
END

Message Cause

An OSS.SUPPRESS directive has an invalid argument. This error often occurs in case the message number does not exist or corresponds to a message that cannot be suppressed.

NOTE: You can suppress only informatory and warning messages (message codes end in "I" or "W"). You cannot suppress non-severe or severe error messages (message codes end in "E" or "S").

Example

--<SUPPRESS A0120E>--

Module-C0313E DEFINITIONS ::= BEGIN
   Name1 ::= INTEGER !Oops!
END

Error Message

""c0313e.asn", line 1 (): C0313E: Message number to be suppressed, A0120E, is invalid.

  --<SUPPRESS A0120E>--


  "c0313e.asn", line 4 (Module-C0313E): A0120E: Parsing error: expecting an assignment statement or 'END' but found '!'.

  Name1 ::= INTEGER !Oops!

Possible Solution

Remove the OSS.SUPPRESS directive.

C0314W

Message Format

C0314W: The object identifier value exceeds the OBJECTID directive constraint for the element 'identifier'.

Message Cause

An OBJECT IDENTIFIER value has more nodes than an applied OSS.OBJECTID directive allows for.

Example

Module-C0314W DEFINITIONS  ::= BEGIN
   Name1 ::= [1] OBJECT IDENTIFIER --<OBJECTID 4>--
   ftam1 Name1 ::= {1 2 4 67 3}
END

Error Message

"c0314w.asn", line 3 (Module-C0314W): C0314W: The object identifier value exceeds the OBJECTID directive constraint for the element 'ftam1'.

Possible Solution

Increase the argument of the applied OSS.OBJECTID directive to accommodate all of the nodes of the OBJECT IDENTIFIER value.

C0315E

Message Format

C0315E: Unrecognized module directive 'directive name'.

Message Cause

An unrecognized compiler directive is used with a module scope. Note that not all compiler directives may be used on the module level.

Example

Module-C0315E  DEFINITIONS  --<PDUS>--  ::= BEGIN
    Officers  ::=   SET {
       president     [0] VisibleString,
       vicePresident [1] VisibleString,
       treasurer     [2] VisibleString,
       secretary     [3] VisibleString
    }
END

Error Message

"c0315e.asn", line 1 (Module-C0315E): C0315E: Unrecognized module directive 'PDUS'.

  Module-C0315E  DEFINITIONS  --<PDUS>--  ::= BEGIN

Possible Solution

Check the spelling of the module directive. For more information, see Directives.

C0316W

Message Format

C0316W: The 'directive name' directive is no longer supported as a module directive.  It is being treated as a global directive.

Message Cause

The specified compiler directive cannot be applied at module level. Currently, the module directives that are supported are: OSS.ASN1VER, OSS.PDU, OSS.NOPDU, OSS.VALUE, OSS.NOVALUE, OSS.SUPPRESS.

Example

Module-C0316W DEFINITIONS  --<INDEFINITE>--  ::= BEGIN
    Officers  ::=   SET {
       president     [0] VisibleString,
       vicePresident [1] VisibleString,
       treasurer     [2] VisibleString,
       secretary     [3] VisibleString
    }
END

Error Message

"c0316w.asn", line 1 (Module-C0316W): C0316W: The 'INDEFINITE' directive is no longer supported as a module directive.  It is being treated as a global directive.

Possible Solution

Remove the module directive.

C0317E

Message Format

C0317E: Global directives must be placed before the first module.

Message Cause

A global OSS-specific compiler directive appears after the start of the first ASN.1 input module.

Possible Solution

Place the the global compiler directive before the first module. Alternatively, you can create a separate file that contains only global compiler directives and pass this file on the ASN.1 compiler command line before the other .asn files.

A0318E

Message Format

A0318E: The UTCTime value 'time value' must not contain a fractional part for minutes or seconds.

Message Cause

A time value for a UTCTime type contains a fractional part for its minutes or seconds component.

Example

Module-A0318E DEFINITIONS ::= BEGIN
   StartTime ::= UTCTime
   time StartTime ::= "9301232021.06"
END

Error Message

"c0318e.asn", line 3 (Module-A0318E): A0318E: The UTCTime value '9301232021.06' must not contain a fractional part for minutes or seconds.

Possible Solution

Remove the fractional part.

A0319E

Message Format

A0319E: The ASN.1 type value contains at least one invalid character for the element 'identifier'.  The first invalid character is 'c'.

Message Cause

One of the characters assigned in a value assignment of a character string type is not valid for that particular type, for example, a letter placed in a NumericString value.

Example

Module-A0319E DEFINITIONS ::= BEGIN
   PersonalRecord ::= CHOICE {
      name     PrintableString,
      numberID NumericString
   }
   topStudent1 PersonalRecord ::= name "John Doe"
   topstudent2 PersonalRecord ::= numberID "1293N"
END

Error Message

"a0319e.asn", line 7 (Module-A0319W): A0319E: The NumericString value contains at least one invalid character for the element 'numberID'.  The first invalid character is 'N'.

Possible Solution

Remove the invalid characters. Alternatively, you can specify the -ignoreError 319 option.

C0320E

Message Format

C0320E: The CODESEG directive must have a value between 1 and 256 inclusive.

Message Cause

The argument of a CODESEG directive is outside the valid range (1 to 256, inclusive).

Example

--<CODESEG 732672364826824682>--

Module-C0320E DEFINITIONS ::= BEGIN
   StartTime ::= UTCTime
   time StartTime ::= "9301232021.06"
END

Error Message

"c0320e.asn", line 1 (): C0320E: The CODESEG directive must have a value between 1 and 256 inclusive.

  --<CODESEG 732672364826824682>--

Example

Module1 definitiveIdentifier DEFINITIONS ::= BEGIN
   IMPORTS definitiveIdentifier FROM Module2;
   Code ::= INTEGER
END

Module2 DEFINITIONS ::= BEGIN
   IMPORTS Code FROM Module1;
   definitiveIdentifier OBJECT IDENTIFIER ::= {joint-iso-ccitt 5 4}
   thisCode Code ::= 15
END

Error Message

"a0324w.asn", line 1 (): A0324W: Defined values are not permitted in the DefinitiveIdentifier of a module.

  Module1 definitiveIdentifier DEFINITIONS ::= BEGIN

Possible Solution

Replace the defined value with an explicit OBJECT IDENTIFIER value placed inside braces.

A0325W

Message Format

A0325W: The identifier is missing from the NamedType.

Message Cause

One or more components in a SET, SEQUENCE, or CHOICE do not have identifiers. According to the ASN.1:1993 standard, this is not allowed.

Example

Module-A0325W DEFINITIONS ::= BEGIN
   PersonalRecord ::= SEQUENCE {
      VisibleString,
      BOOLEAN
   }
END

Error Message

"a0325w.asn", line 3 (Module-A0325W): A0325W: The identifier is missing from the NamedType.

  VisibleString,


  "a0325w.asn", line 4 (Module-A0325W): A0325W: The identifier is missing from the NamedType.

  BOOLEAN

Possible Solution

Add the missing identifiers.

A0326W

Message Format

A0326W: The identifier is missing from the NamedConstraint.

Message Cause

One or more NamedConstraint components in a TypeConstraints do not have identifiers. According to the ASN.1:1993 standard, this is not allowed.

Example

Module-A0326W DEFINITIONS ::= BEGIN
   FlagInfo ::= SET { code INTEGER OPTIONAL}
   Flags ::= FlagInfo (WITH COMPONENTS {PRESENT})
END

Error Message

"a326w.asn", line 3 (Module-A0326W): A0326W: The identifier is missing from the NamedConstraint.

  Flags ::= FlagInfo (WITH COMPONENTS {PRESENT})


  "a326w.asn", line 3 (Module-A0326E): A0058E: 'Flags' is defined using WITH COMPONENTS but one of the elements does not have an identifier.

Possible Solution

Add the missing identifiers.

A0327W

Message Format

A0327W: The value for 'identifier' does not satisfy the constraints on its Type.

Message Cause

A value in a value assignment does not conform to an applied constraint in the base type.

Example

Module-A0327W DEFINITIONS ::= BEGIN
   FlagCode ::= INTEGER (1..20)
   FlagName ::= PrintableString
   FlagInfo ::= SET { code FlagCode, name FlagName OPTIONAL }
   flags FlagInfo ::= {code 200, name "CrossHatch" }
END

Error Message

"a0327w.asn", line 5 (Module-A0327W): A0327W: The value for 'code' does not satisfy the constraints on its Type.

Possible Solution

Change the value to conform to all subtype constraints.

A0328E

Message Format

A0328E: The PresenceConstraint 'OPTIONAL' is not permitted for CHOICE types.

Message Cause

A WITH COMPONENTS constraint for a CHOICE type contains one or more OPTIONAL keywords. OPTIONAL keywords are not allowed in WITH COMPONENTS notation for CHOICE types.

Example

Module-A0328E DEFINITIONS ::= BEGIN
   MYCHOICE  ::= CHOICE {first INTEGER, second REAL, third BOOLEAN }
   HerChoice ::= MYCHOICE (WITH COMPONENTS {first  PRESENT,
                                            second OPTIONAL,
                                            third  ABSENT})
END

Error Message

"a0328e.asn", line 4 (Module-A0328E): A0328E: The PresenceConstraint 'OPTIONAL' is not permitted for CHOICE types.

  second OPTIONAL,

Possible Solution

Remove the OPTIONAL keyword.

C0329E

Message Format

C0329E: The WITH COMPONENT constraint cannot be used between the SET/SEQUENCE and OF.  Please place the constraint on the component of the SET/SEQUENCE OF type.

Message Cause

A SET OF or SEQUENCE OF type has a WITH COMPONENTS constraint placed before the OF keyword.

Example

Module-C0329E DEFINITIONS ::= BEGIN
   Names ::= SET (WITH COMPONENT (SIZE(1..30))) OF VisibleString
END

Error Message

"a0329e.asn", line 2 (Module-C0329E): C0329E: The WITH COMPONENT constraint cannot be used between the SET and OF.  Please place the constraint on the component of the SET OF type.

  Names ::= SET (WITH COMPONENT (SIZE(1..30))) OF VisibleString

Example

--<OSS.NOCOPY Module-A0332W.Names>--

Module-A0332W DEFINITIONS ::= BEGIN
   Names ::= VisibleString --<PADDED>--
END

Error Message

"a0332w.asn", line 4 (Module-A0332W): A0332W: The NOCOPY directive forces 'Names' to have the UNBOUNDED directive.

Possible Solution

Remove the directive from the type that has the OSS.NOCOPY directive applied to it.

C0333E

Message Format

C0333E: COMPILER ERROR #47.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

C0334E

Message Format

C0334E: The type of the ASN.1 component must be a DefinedType.

Message Format

C0335W: No initialized variable will be generated for the value 'value reference' since its type is a complex BuiltinType.  Change the type to a DefinedType.

Message Cause

The name of an information object class definition does not conform to the ASN.1 standard's recommendations.

Example

Module-A0338E DEFINITIONS ::= BEGIN
   Error ::=  CLASS {
      &Parameter  OPTIONAL,
      &code  INTEGER UNIQUE
   }
END

Error Message

"a0338e.asn", line 2 (Module-A0338E): A0338E: 'Error' is not a legal objectclass reference.  It should begin with an uppercase letter and contain only uppercase letters, digits or hyphens.

  Error ::=  CLASS {

Possible Solution

Change the name of the information object class to start with an uppercase letter followed by only uppercase letters, digits, or hyphens.

C0339E

Message Format

C0339E: Field #x of CHOICE 'type reference' has ambiguous tags.  Check for a CHOICE without a tag included within itself, or an ANY without a tag within a CHOICE.

Message Cause

A CHOICE type contains a recursive element or an ANY alternative that does not have a tag.

Example

Module-C0339E DEFINITIONS ::= BEGIN
   Name1 ::= CHOICE {
      name [0] PrintableString,
      id   INTEGER,
           Name1
   }
END

Error Message

"c0339e.asn", line 5 (Module-C0339E): C0339E: Field #3 of CHOICE 'Name1' has ambiguous tags.  Check for a CHOICE without a tag included within itself, or an ANY without a tag within a CHOICE.

Possible Solution

To remove ambiguities, add an explicit tag.

A0340E

Message Format

A0340E: 'name' is not permitted as a Literal in a SyntaxList.

Message Cause

The input ASN.1 syntax contains an information object class definition with WITH SYNTAX notation, but one or more of the literals in the syntax list is an ASN.1 reserved word or contains other than all uppercase letters or hyphens.

Example

Module-A0340E DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType OPTIONAL,
      &errorCode INTEGER UNIQUE
   }
   WITH SYNTAX {
      [PARAM &ParameterType]
      INTEGER &errorCode
   }
END

Error Message

"a0340e.asn", line 8 (Module-A0340E): A0340E: 'INTEGER' is not permitted as a Literal in a SyntaxList.

  INTEGER &errorCode

Possible Solution

Replace the reserved word from the WITH SYNTAX block (INTEGER, in this case) with a valid literal.

C0341W

Message Format

C0341W: 'SET or CHOICE' contains an untagged ANY as the only item in a SET or CHOICE.  This is not recommended.  Consider adding a tag to the ANY.

Message Cause

A SET or a CHOICE type has an untagged ANY as its only element. This may cause tag ambiguities during decoding.

Example

Module-C0341W DEFINITIONS ::= BEGIN
   Choice ::= CHOICE { any ANY }
END

Error Message

"c0341w.asn", line 2 (Module-C0341W): C0341W: 'Choice' contains an untagged ANY as the only item in a SET or CHOICE.  This is not recommended.  Consider adding a tag to the ANY.

Possible Solution

Add an explicit tag to the ANY type.

A0342E

Message Format

A0342E: The first item following an OptionalGroup beginning with a Literal must be a Literal.

Message Cause

The input ASN.1 syntax contains an information object class definition with a WITH SYNTAX notation, but one of the literals in the syntax list is missing. Each element in the syntax list must be preceded by a literal that contains only uppercase letters or hyphens.

Example

Module-A0342E DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType OPTIONAL,
      &errorCode INTEGER UNIQUE
   }
   WITH SYNTAX {
      [PARAM &ParameterType]
      &errorCode
   }
END

Error Message

"a0342e.asn", line 8 (Module-A0342E): A0342E: The first item following an OptionalGroup beginning with a Literal must be a Literal.

  &errorCode

Possible Solution

Add the missing literal (identifying word) to the syntax list.

A0343E

Message Format

A0343E: Each OptionalGroup of a SyntaxList must contain either a PrimitiveFieldName or an OptionalGroup.

Message Cause

The input ASN.1 syntax contains an information object class definition with a WITH SYNTAX clause, but one of the literals in the syntax list does not have an information class field or an optional group associated with it.

Example

Module-A0343E DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType OPTIONAL,
      &errorCode INTEGER UNIQUE
   }
   WITH SYNTAX {
      [PARAMETER]
      CODE &errorCode
   }
END

Error Message

"a0343e.asn", line 7 (Module-A0343E): A0343E: Each OptionalGroup of a SyntaxList must contain either a PrimitiveFieldName or an OptionalGroup.

  [PARAMETER]

Possible Solution

Add a fieldname to the optional group after the literal in the syntax list.

A0344E

Message Format

A0344E: The FieldName of the VariableTypeValueSetFieldSpec for 'information object field' must refer to a type field.

Message Cause

One of the variable type field specifications from an information object class definition does not refer to an ASN.1 type.

Example

Module-A0344E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR ::= CLASS {
      &ParameterType OPTIONAL,
      &errorCode INTEGER UNIQUE
   }
   OPERATION ::= CLASS {
      &ArgumentType   OPTIONAL,
      &ResultType     OPTIONAL,
      &Errors         ERROR OPTIONAL,
      &Linked         OPERATION OPTIONAL,
      &resultReturned BOOLEAN DEFAULT TRUE,
      &code           INTEGER UNIQUE,
      &ValueSet       &code OPTIONAL
   }
END

Error Message

"a0344e.asn", line 14 (Module-A0344E): A0344E: The FieldName of the VariableTypeValueSetFieldSpec for '&ValueSet' must refer to a type field.

  &ValueSet   &code OPTIONAL

Possible Solution

Replace the fieldname with one that refers to an ASN.1 type.

A0345E

Message Format

A0345E: The field 'fieldname' is not optional and therefore must be present in the SyntaxList.

Message Cause

An information object class definition with a WITH SYNTAX clause is missing a non-optional field in its syntax list.

Example

Module-A0345E DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType,
      &errorCode INTEGER UNIQUE
   }
   WITH SYNTAX {
      CODE &errorCode
   }
END

Error Message

"a0345e.asn", line 8 (Module-A0345E): A0345E: The field '&ParameterType' is not optional and therefore must be present in the SyntaxList.

  }

Possible Solution

Add the missing field to the syntax list.

A0346E

Message Format

A0346E: 'identifier' is not a field of the CLASS being defined.

Message Cause

The input ASN.1 syntax contains an information object class definition with a WITH SYNTAX clause, but one of the fields listed in the syntax list doesn't appear in the information object class definition.

Example

Module-A0346E DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType OPTIONAL,
      &errorCode INTEGER UNIQUE
   }
   WITH SYNTAX {
      CODE &errorCode,
      NEW_FIELD &new
   }
END

Error Message

"a0346e.asn", line 8 (Module-A0346E): A0346E: '&new' is not a field of the CLASS being defined.

 NEW_FIELD &new

Possible Solution

Remove the undefined fieldname from the syntax list.

A0347E

Message Format

A0347E: The field 'fieldname' must occur only once in the SyntaxList.

Message Cause

The input ASN.1 syntax contains an information object class definition with a WITH SYNTAX clause, but one of the fields listed in the syntax list appears more than once.

Example

Module-A0347E DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType OPTIONAL,
      &errorCode INTEGER UNIQUE
   }
   WITH SYNTAX {
      CODE_ONE &errorCode,
      CODE_TWO &errorCode,
   }
END

Error Message

"a0347e.asn", line 8 (Module-A0347E): A0347E: The field '&errorCode' must occur only once in the SyntaxList.

 CODE_TWO &errorCode,

Possible Solution

Make sure that each fieldname appears only once in the syntax list.

A0348E

Message Format

A0348E: The field 'fieldname' must not be within an OptionalGroup since it did not have OPTIONAL specified.

Message Cause

The input ASN.1 syntax contains an information object class definition with a WITH SYNTAX clause, but one of the fields listed in square brackets in the syntax list is not marked as OPTIONAL in the class definition.

Example

Module-A0348E DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType,
      &errorCode INTEGER UNIQUE
   }
   WITH SYNTAX {
      [PARAMETER &ParameterType]
       ERRCODE   &errorCode
   }
END

Error Message

"a0348e.asn", line 7 (Module-A0348E): A0348E: The field '&ParameterType' must not be within an OptionalGroup since it did not have OPTIONAL specified.

 [PARAMETER &ParameterType]

Possible Solution

Mark the field referred to in the optional group as OPTIONAL in the information class definition.

A0349E

Message Format

A0349E: A Setting for 'item' could be misinterpreted as a Setting for 'item'.

Message Cause

The input ASN.1 syntax contains an information object class definition along with a syntax list, but the two named items could be misinterpreted for each other.

Possible Solution

Remove the ambiguity.

A0350E

Message Format

A0350E: Expecting the Literal 'syntax list literal'.

Message Cause

In a given information object class instance that uses a defined WITH SYNTAX notation, the name of the field being initialized does not match any of the names in the syntax list.

Example

Module-A0350E DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType OPTIONAL,
      &errorCode INTEGER UNIQUE
   }
   WITH SYNTAX {
      [PARAMETER &ParameterType]
      ERRCODE    &errorCode
   }

   anError ERROR ::=
   {
      ERRORCODE 1
   }
END

Error Message

"a0350e.asn", line 13 (Module-A0350E): A0350E: Expecting the Literal 'ERRCODE'.

  ERRORCODE 1

Example

Module-A0355E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   MYCLASS ::= CLASS {
      &OptTypFld  OPTIONAL,
      &DefTypFld    DEFAULT INTEGER,
      &varTypValFld     &DefTypFld
   }
END

Error Message

"a0355e.asn", line 6 (Module-A0355E): A0355E: The field '&varTypValFld' must have a DEFAULT value since it references the field '&DefTypFld' which has a DEFAULT value.

Possible Solution

Add the required value to the named field.

A0356E

Message Format

A0356E: The field ' information object field ' must be OPTIONAL since it references the field ' information object field ' which is OPTIONAL.

Message Cause

An information object field from an information object class definition must be optional.

Example

Module-A0356E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   MYCLASS ::= CLASS {
      &OptTypFld  OPTIONAL,
      &varTypValSetFld      &OptTypFld
   }
END

Error Message

"a0356e.asn", line 5 (Module-A0356E): A0356E: The field '&varTypValSetFld' must be OPTIONAL since it references the field '&OptTypFld' which is OPTIONAL.

Possible Solution

Add the OPTIONAL keyword to the information object field.

A0357E

Message Format

A0357E: 'information object field' is not a field of the CLASS 'information object class reference'.

Message Cause

An information object class definition contains a reference to an undefined field.

Example

Module-A0357E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   MYCLASS ::= CLASS {
      &OptTypFld  OPTIONAL,
      &varTypValSetFld      &OptTypeFld
   }
END

Error Message

"a0357e.asn", line 5 (Module-A0357E): A0357E: '&OptTypeFld' is not a field of the CLASS 'MYCLASS'.

Possible Solution

Make sure the spelling of the referenced field and its reference is correct.

A0358E

Message Format

A0358E: 'name' is not an object field or objectset field.  Only object fields or objectset fields may be used as link fields.

Message Cause

An information object class definition contains a non-object or non-object-set field that is used as a link field.

Example

Module-A0358E DEFINITIONS ::= BEGIN
   Dummy   ::= INTEGER
   MYCLASS ::= CLASS {
      &OptTypFld  OPTIONAL,
      &DefTypFld  DEFAULT INTEGER,
      &varTypValSetFld  &badObjFld.&OptTypeFld,
      &badObjFld        INTEGER
   }
END

Error Message

"a0358e.asn", line 6 (Module-A0358E): A0358E: '&badObjFld' is not an object field or objectset field.  Only object fields or objectset fields may be used as link fields.

Possible Solution

Remove the invalid link attempt.

A0359E

Message Format

A0359E: 'information object field' must be a type field.  The FieldName of a variableTypeValueFieldSpec or variableTypeValueSetFieldSpec must be a type field.

Message Cause

The input ASN.1 syntax contains an information object class definition in which a non-type field is used in a place where a type field is required.

Example

Module-A0359E DEFINITIONS ::= BEGIN
   Object ::= INTEGER
   MYCLASS ::= CLASS {
      &TypFld             INTEGER,
      &varTypValSetFld    &TypFld
   }
END

Error Message

"a0359e.asn", line 5 (Module-A0359E): A0359E: '&TypFld' must be a type field. The FieldName of a variableTypeValueFieldSpec or variableTypeValueSetFieldSpec must be a type field.

Possible Solution

Replace the non-type field with a type field.

A0360E

Message Format

A0360E: A Setting for some PrimitiveFieldName in an OptionalGroup must be present whenever a Literal for that OptionalGroup is present in the DefinedSyntax.

Message Cause

The input ASN.1 syntax contains an information object class instance in which a defined syntax is used for initialization, but one of the literals does not have an associated setting.

Possible Solution

Add an associated setting after the literal.

C0361S

Message Format

C0361S: Unable to open ossinfo file, default-ossinfo-path.

Message Cause

The ASN.1 compiler could not access the custom configuration file needed for successful operation.

Possible Solution

Consider the following solutions:

Place the ossinfo file in the default-ossinfo-path.
Set the OSSINFO environment variable in your operating system to point to the location of the ossinfo file.

A0362S

Message Format

A0362S: 'item' is being used in an invalid context.

Message Cause

A component of ASN.1 is used in an invalid context. For example, a regular type reference is used in an information object class definition as a linked field.

Example

Module-A0362S DEFINITIONS ::= BEGIN
   Object ::= INTEGER
   MYCLASS ::= CLASS {
      &TypFld            INTEGER,
      &OptTypFld         OPTIONAL,
      &DefTypFld         DEFAULT INTEGER,
      &varTypValFld      Object.&DefTypeFld,
      &varTypValSetFld   &TypFld,
      &valFld            PrintableString
   }
END

Error Message

"a0362s.asn", line 7 (Module-A0362S): A0362S: 'Object' is being used in an invalid context.

Possible Solution

Remove the item from the context.

A0363S

Message Format

A0363S: The ObjectClassFieldType 'information object field' is incorrectly defined.

Message Cause

The input ASN.1 syntax contains an information object class definition which contains a reference to a field in another class, but that field does not exist in the other class.

Example

Module-A0363S DEFINITIONS ::= BEGIN
   Object ::= INTEGER
   MYCLASS ::= CLASS {
      &OptTypFld    OPTIONAL,
      &DefTypFld      DEFAULT INTEGER,
      &varTypValFld     HERCLASS.&DefTypeFld,
      &valFld               PrintableString
   }
   HERCLASS ::= CLASS {
      &DefTypFld     INTEGER,
      &valFld        BOOLEAN
   }
END

Error Message

"a0363s.asn", line 6 (Module-A0363S): A0363S: The ObjectClassFieldType '&varTypValFld' is incorrectly defined.

Possible Solution

Make sure the spelling of the referenced field and its reference is correct.

A0364S

Message Format

A0364S: COMPILER ERROR #25 for field 'field'.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

A0365E

Message Format

A0365E: There must be at least one value of 'type reference' that satisfies the subtype constraint.

Message Cause

A subtype constraint defines an empty set of values.

Example

Module-A0365E DEFINITIONS ::= BEGIN
   IA5Str ::= IA5String (SIZE(0..6 ^ 10..20))
END

Error Message

"a0365e.asn", line 2 (Module-A0365E): A0365E: There must be at least one value of 'IA5Str' that satisfies the subtype constraint.

Possible Solution

Change the limits of the subtype constraint so that the intersection of two pairs of values does not yield an empty set.

C0366S

Message Format

C0366S: ossinfo file ossinfo-file-path is corrupt (number). Contact OSS technical support.

Message Cause

The ASN.1 compiler detected file corruption when processing the ossinfo file.

Possible Solution

Consider the following solutions:

Make sure you the ossinfo file is a binary file and not a text file.
Compare the corrupt file with the original file sent to you by OSS Nokalva.

If the problem persists, send the ossinfo file along with your platform and version number to Technical Support ‹support@oss.com› for review.

A0367W

Message Format

A0367W: The form '0' of NumericRealValue should be used for zero values, and not the alternate form.

Message Cause

The input ASN.1 syntax contains a value assignment of REAL type in which the assigned value is zero, but the mantissa, base, and exponent notation are also specified.

Example

Module-A0367W DEFINITIONS ::= BEGIN
   Speed ::= REAL
   upperLimit Speed ::= {55,10, 3}
   lowerLimit Speed ::= {0, 10, 3} -- wrong value for 0
   goodZero Speed   ::= 0          -- correct value for 0
END

Error Message

"a0367w.asn", line 4 (Module-A0367W): A0367W: The form '0' of NumericRealValue should be used for zero values, and not the alternate form.

  lowerLimit Speed ::= {0, 10, 3} -- wrong value for 0

Possible Solution

Replace the mantissa, base, and exponent notation with '0' .

C0368E

Message Format

C0368E: The control table external name 'name' should not begin with a digit.  Use the -externalname compiler parameter to change this name.

Message format when using the compiler GUI:

C0368E: The control table external name 'name' should not begin with a digit. To change this name, please type the new name in the "Control table external name" edit box in the "Code Generation" tab of the "Compiler Options" window.

Message Cause

The default or specified name for the pointer to the encoder/decoder control table begins with a digit.

Possible Solution

Specify the -externalName compiler option.

A0369W

Message Format

A0369W: '-' should not be present when the value of the SignedNumber is zero.

Message Cause

The input ASN.1 syntax contains a value assignment in which the assigned value is zero, but the minus sign (-) is specified in front of the "0" character.

Example

Module-A0369W DEFINITIONS ::= BEGIN
   Negative ::= INTEGER (MIN .. 0)
   negativeZero Negative ::= -0
END

Error Message

"a0369w.asn", line 3 (Module-A0369W): A0369W: '-' should not be present when the value of the SignedNumber is zero.

    negativeZero Negative ::= -0

Possible Solution

Remove the minus sign (-).

A0370E

Message Format

A0370E: The referenced field of the ObjectClassFieldType or ValueSetFromObjects could not be found in 'information object class reference'.

Error Message

"a0374e.asn", line 9 (Module-A0374E): A0374E: The open type 'eyes' is used in an ambiguous context within L.

Possible Solution

Add an explicit tag to the open type.

C0375E

Message Format

C0375E: Field 'identifier' of CHOICE 'type reference' has ambiguous tags.  Check for a CHOICE without a tag included within itself, or an open type without a tag within a CHOICE.

Message Cause

One or more elements of a CHOICE type may cause a tag conflict during runtime.

Possible Solution

Add explicit tags to the elements.

A0376E

Message Format

A0376E: The open type which is element x within a SET/SEQUENCE/CHOICE (within type reference) is used in an ambiguous context.

Message Cause

One or more elements of a CHOICE type may cause a tag conflict during runtime.

Example

Module-A0376E DEFINITIONS ::= BEGIN
   OPENTYPE ::= CLASS
   {
      &Type
   }
   L ::= [994] SET {
      seq SEQUENCE OF CHOICE {
         sharp INTEGER,
         OPENTYPE.&Type
      }
   }
END

Error Message

"a0376e.asn", line 9 (Module-A0376E): A0376E: The open type which is element 2 within a SET/SEQUENCE/CHOICE (within L) is used in an ambiguous context.

Possible Solution

Add explicit tags to the elements.

C0377E

Message Format

C0377E: Field #x of CHOICE 'type reference' has ambiguous tags.  Check for a CHOICE without a tag included within itself, or an open type without a tag within a CHOICE.

C0378W

Message Format

C0378W: 'type reference' contains an untagged open type as the only item in a SET or CHOICE.  This is not recommended.  Consider adding a tag to the open type.

Message Cause

In a CHOICE or SET type, an open type is listed without explicit tags. This may cause tag ambiguities during runtime.

Example

Module-C0378W DEFINITIONS ::= BEGIN
   OPENTYPE ::= CLASS {
      &Type
   }
   Choice ::= CHOICE { open OPENTYPE.&Type }
END

Error Message

"c0378w.asn", line 5 (Module-C0378W): C0378W: 'Choice' contains an untagged open type as the only item in a SET or CHOICE.  This is not recommended.  Consider adding a tag to the open type.

Possible Solution

Add an explicit tag to the open type.

C0379E

Message Format

C0379E: COMPILER ERROR #28.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

C0380I

Message Format

C0380I: The object 'information object reference' is not referenced by any Object or ObjectSet, or is referenced by an Object or ObjectSet which is not referenced in a table constraint.

Message Cause

An information object instance is not used in the specification.

Example

Module-C0380I DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType OPTIONAL,
      &errorCode INTEGER UNIQUE
   }
   WITH SYNTAX {
      [PARAMETER &ParameterType]
       ERRCODE   &errorCode
   }
   anError ERROR ::=
   {
     PARAMETER PrintableString
     ERRCODE 1
   }
END

Error Message

"c0380i.asn", line 10 (Module-C0380I): C0380I: The object 'anError' is not referenced by any Object or ObjectSet, or is referenced by an Object or ObjectSet which is not referenced in a table constraint.

Possible Solution

Add a reference to the information object instance in the input specification.

C0381I

Message Format

C0381I: The ObjectSet 'information object set reference' is not referenced in a table constraint, and is not referenced by any Object or ObjectSet, or is referenced by an Object or ObjectSet which is not referenced in a table constraint.

Message Cause

An information object set instance is not used in the specification.

Example

Module-C0381I DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR-CLASS ::= CLASS {
      &category       PrintableString (SIZE(1)),
      &code           INTEGER,
      &Type
   }
   WITH SYNTAX {&category &code &Type}

   ErrorSet ERROR-CLASS ::=
   {
      {"A" 1 INTEGER} |
      {"A" 2 REAL}    |
      {"B" 1 CHARACTER STRING}
   }
END

Error Message

"c0381i.asn", line 10 (C0381I): C0381I: The ObjectSet 'ErrorSet' is not referenced in a table constraint, and is not referenced by any Object or ObjectSet, or is referenced by an Object or ObjectSet which is not referenced in a table constraint.

Possible Solution

Add a reference to the information object set instance in the input specification.

A0382E

Message Format

A0382E: Can't export the imported name name. It is imported more than once or redefined.

Message Cause

The input ASN.1 syntax contains an attempt to export an item that was imported more than once or was redefined after being imported in the same module.

Example

Module1 DEFINITIONS ::= BEGIN
  EXPORTS A;
  IMPORTS A FROM Module2;
     A ::= OBJECT IDENTIFIER
     a A ::= {0 1 2 3}
     B ::= A
END

Module2 DEFINITIONS ::= BEGIN
  EXPORTS A;
     A ::= OBJECT IDENTIFIER
 END

Error Message

"a0382e.asn", line 2 (Module1): A0382E: Can't export the imported name A. It is imported more than once or redefined.

Possible Solution

Remove the item from the EXPORTS statement.

C0383E

Message Format

C0383E: Invalid enumerated value assignment.

A0385E

Message Format

A0385E: The value 'identifier' is used as a DefinedValue in CharacterStringList, but is not defined.

Message Cause

The value reference used on the right side of an assignment statement is not defined in the input.

Example

Module-A0385E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   string1 PrintableString ::= "This is a string"
   string2 PrintableString ::= {"o", "n", "e"}
   string3 PrintableString ::= {"o", "n", e}
END

Error Message

"a0385e.asn", line 5 (Module-A0385E): A0385E: The value 'e' is used as a DefinedValue in CharacterStringList, but is not defined.

Possible Solution

Add a definition for the value reference.

A0386W

Message Format

A0386W: 1990 ASN.1 does not permit white-space or new-line characters in a bstring or hstring.

Message Cause

A hexadecimal or binary value spans more than one line. According to ASN.1:1990 standard, this is not allowed.

Example

Module-A0386W DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   string1 OCTET STRING ::= '000F
                             AAA0'H
END

Error Message

"a0386w.asn", line 3 (Module-A0385E): A0386W: 1990 ASN.1 does not permit white-space or new-line characters in a bstring or hstring.

  string1 OCTET STRING ::= '000F

Possible Solution

Specify the -2021 option while compiling your syntax.

C0387E

Message Format

C0387E: The SHORTENNAMES directive must have a value that is equal to 16 or greater.

Message Cause

The argument of an OSS.SHORTENAMES directive has an incorrect value. The argument of this compiler directive must be greater than or equal to 16.

Example

--<OSS.SHORTENNAMES 10>--

Module-A0372E DEFINITIONS ::= BEGIN
   ThisVeryLongNameWillBeShortened  ::= INTEGER
END

Error Message

"c0387e.asn", line 1 (): C0387E: The SHORTENNAMES directive must have a value that is equal to 16 or greater.

 --<OSS.SHORTENNAMES 10>--

Possible Solution

Change the argument of the compiler directive to be greater than or equal to 16.

A0388W

Message Format

A0388W: DummyReference 'parameter reference' was not used.

Message Cause

In a parameterized type, one of the parameters is not used.

Example

Module-C0388W DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   PARAMETERIZED-OBJECT-CLASS {TypeParam,
                               INTEGER:valueParam,
                               INTEGER:ValueSetParam} ::= CLASS {
        &valueField1    TypeParam,
        -- commented out  &valueField2    INTEGER DEFAULT valueParam,
        &valueField3    INTEGER (ValueSetParam)
        }
   MY-OBJECT-CLASS ::=
                 PARAMETERIZED-OBJECT-CLASS {BIT STRING, 123, {4|5|6}}
END

Error Message

"a0388w.asn", line 4 (C0388W): A0388W: DummyReference 'valueParam' was not used.

INTEGER:valueParam,

A0392S: The TypeFromObject 'type reference' is incorrectly defined.

Message Cause

A definition of a type is based upon a component of an information object class, but the extracted component cannot be found in the class definition.

Example

Module-A0392S DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR-CLASS ::= CLASS {
      &category       PrintableString (SIZE(1)),
      &code           INTEGER,
      &Type
   }
   WITH SYNTAX {&category &code &Type}
   error1 ERROR-CLASS ::= { "A" 1 INTEGER }
   ErrorType ::= error1.&Typ
END

Error Message

"a0392s.asn", line 10 (Module-A0392S): A0396E: The field '&Typ' was not found in the object 'error1' used in the TypeFromObject or ValueSetFromObjects 'ErrorType'.


"a0392s.asn", line 10 (Module-A0392S): A0392S: The TypeFromObject 'ErrorType' is incorrectly defined.

Example

Module-A0396E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR-CLASS ::= CLASS {
      &category       PrintableString (SIZE(1)),
      &code           INTEGER,
      &Type
   }
   WITH SYNTAX {&category &code &Type}
   error1 ERROR-CLASS ::= { "A" 1 INTEGER }
   ErrorType ::= error1.&TypE
END

Error Message

"a0396e.asn", line 10 (Module-A0396E): A0396E: The field '&TypE' was not found in the object 'error1' used in the TypeFromObject or ValueSetFromObjects 'ErrorType'.


"a0396e.asn", line 10 (Module-A0396E): A0392S: The TypeFromObject 'ErrorType' is incorrectly defined.

Possible Solution

Ensure that the referenced component and its reference both use the same spelling.

A0397E

Message Format

A0397E: The value used in TypeFromObject 'type from object reference' is either undefined or is not an object.

A0398E

Message Format

A0398E: The field 'field' was not found in the object used in the TypeFromObject or ValueSetFromObjects 'type or value from object reference'.

A0399E

Message Format

A0399E: Field 'identifier' of the SET, SEQUENCE, or CHOICE is not permitted to be an ASN.1 component.

Message Cause

One of the components of a SET, SEQUENCE, or CHOICE is not an ASN.1 type.

Example

Module-A0399E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR-CLASS ::= CLASS {
                &category       PrintableString (SIZE(1)),
                &code           INTEGER,
                &OpenType,
                &FixedType      DEFAULT INTEGER,
                &Objset         ERROR-CLASS OPTIONAL
                }

    Choice ::= CHOICE {
                dummy       [0] Dummy,
                objectClass [1] ERROR-CLASS
                }
END

Error Message

"a0399e.asn", line 13 (Module-A0399E): A0399E: Field 'objectClass' of the SET, SEQUENCE, or CHOICE is not permitted to be an ObjectClass.

Possible Solution

Remove the invalid type from the SET, SEQUENCE, or CHOICE.

A0400E

Message Format

A0400E: The type in the SET OF or SEQUENCE OF is not permitted to be an ASN.1 component.

Message Cause

A type in a SET OF or SEQUENCE OF is not an ASN.1 type.

Example

Module-A0400E DEFINITIONS ::= BEGIN
   ERROR-CLASS ::= CLASS {
                &category       PrintableString (SIZE(1)),
                &code           INTEGER,
                &Type,
                &ObjSet         ERROR-CLASS OPTIONAL
                }

   SetOf ::= SET OF ERROR-CLASS
END

Error Message

"a0400e.asn", line 9 (Module-A0400E): A0400E: The type in the SET OF or SEQUENCE OF is not permitted to be an ObjectClass.

Possible Solution

Change the SET OF or SEQUENCE OF to reference a regular allowed ASN.1 type.

A0401E

Message Format

A0401E: The FieldName of the TypeFromObject must refer to a type field.

Message Cause

A TypeFromObject references a component of an information object class, but the referenced field is not a type field.

Example

Module-A0401E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR-CLASS ::= CLASS {
      &category       PrintableString (SIZE(1)),
      &code           INTEGER,
      &resultReturned BOOLEAN DEFAULT TRUE,
      &Type
   }
   WITH SYNTAX {&category &code &resultReturned &Type}
   error1 ERROR-CLASS ::= { "A" 1 TRUE INTEGER }
   ErrorType ::= error1.&resultReturned
END

Error Message

"a0401e.asn", line 11 (Module-A0401E): A0401E: The FieldName of the TypeFromObject must refer to a type field.
  ErrorType ::= error1.&resultReturned

Possible Solution

Use a reference that lists a type field in the desired information object class.

A0402E

Message Format

A0402E: The ObjectSet 'object set reference' is using an ObjectSet as a DefinedObjectClass.

Message Cause

In a value assignment, a value-filled information object set is used instead of a defined information object class reference.

Example

Module-A0402E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR-CLASS ::= CLASS {
                &category       PrintableString (SIZE(1)),
                &code           INTEGER,
                &Type
                }
                WITH SYNTAX {&category &code &Type}
   ErrorSet ERROR-CLASS ::=
   {
        {"A" 1 INTEGER} |
        {"A" 2 REAL}    |
        {"B" 1 CHARACTER STRING}
   }
   ErrorSet1 ErrorSet ::= {ErrorSet}
END

Message Cause

A ValueSetFromObject notation references an open type or another fluctuation type.

Example

Module-A0410E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR-CLASS ::= CLASS {
                &category       PrintableString (SIZE(1)),
                &code           INTEGER,
                &Type
                }
                WITH SYNTAX {&category &code &Type}

   ErrorSet ERROR-CLASS ::=
   {
        {"A" 1 INTEGER} |
        {"A" 2 REAL}    |
        {"B" 1 CHARACTER STRING}
   }
  error ERROR-CLASS ::= {"A" 1 INTEGER}
  ErrorType ::= ErrorSet.&Type
END

Error Message

"a0410e.asn", line 17 (Module-A0410E): A0410E: The ValueSetFromObjects 'ErrorType' must reference a field whose type is fixed.

Possible Solution

Replace the fluctuating type with a fixed type.

C0411S

Message Format

C0411S: COMPILER ERROR #33.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

C0412E/C0412W

Message Format

C0412E: parameterized type could not be processed.

Message Cause

This error occurs in the following situations:

A parameterized type employs a parameter which cannot be substituted (due to incompatibility).
The dummy reference specified was not used.

Possible Solution

Correct the parameterized type definition.

NOTE: Starting with version 8.1.2, if you specify the -ignoreIncompleteItems option, the ASN.1 syntax checker displays a warning instead of an error message.

A0413E/A0413W

Message Format

A0413E: 'parameterized reference' is an undefined ParameterizedReference.

Message Cause

The parameterized type that you are trying to use is undefined.

Example

Module-A0413E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ParamSeq {X} ::= SEQUENCE {
      a INTEGER,
      b X
   }
   aseq ParamSet {PrintableString} ::= { a 5, b "five"}
END

Error Message

"a0413e.asn", line 7 (Module-A0413E): A0413E: 'ParamSet' is an undefined ParameterizedReference.

  aseq ParamSet {PrintableString} ::= { a 5, b "five"}

Possible Solution

Example

Module-A0416E DEFINITIONS ::= BEGIN
  Type1 ::= [0] SEQUENCE {
                age   INTEGER,
                name  PrintableString,
                ...,
                date  UTCTime,
                COMPONENTS OF Type2
                }

   Type2 ::= [1] SEQUENCE {
                status  INTEGER (1..5),
                gender  ENUMERATED {male, female}
                }
END

Error Message

"a0416e.asn", line 7 (Module-A0416E): A0416E: 'COMPONENTS OF' is not permitted in a SET or SEQUENCE after an ellipsis ('...').

  COMPONENTS OF Type2

Possible Solution

Add the COMPONENTS OF clause before the ellipsis.

A0418E

Message Format

A0418E: Only one occurrence of '...' is permitted in each ENUMERATED.

Message Cause

An ENUMERATED type contains more than one ellipsis.

Example

Module-A0418E DEFINITIONS ::= BEGIN
  Type1 ::= ENUMERATED { a(0), b(1), ..., i(9), ... }
END

Error Message

"a0418e.asn", line 2 (Module-A0418E): A0418E: Only one occurrence of '...' is permitted in each ENUMERATED.

  Type1 ::= ENUMERATED { a(0), b(1), ..., i(9), ... }

Possible Solution

Make sure there is only one ellipsis in the ENUMERATED type's definition.

A0419E

Message Format

A0419E: 'type reference' must contain a base set of constraints before the extensibility mark.

Message Cause

The input ASN.1 syntax contains an extensibility marker that is not preceded by any elements.

Example

Module-A0419E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER (...)
END

Error Message

"a0419e.asn", line 2 (Module-A0419E): A0419E: 'Dummy' must contain a base set of constraints before the extensibility mark.

Possible Solution

Place one or more elements before the extensibility marker.

A0420W

Message Format

A0420W: 'type reference' is illegally defined, for it uses WITH COMPONENTS with an optional / absence constraint on a non-OPTIONAL element, 'identifier'.

Message Cause

An OPTIONAL or ABSENT keyword in a WITH COMPONENTS constraint is applied to a component defined with a DEFAULT value. According to the latest ASN.1 standard, this is not allowed. However, previous application standards accept this syntax. If you have previously specified the -designerWarnings option, you will receive a warning.

Example

Module-A0420W DEFINITIONS ::= BEGIN
   ParameterList ::= SEQUENCE {
                        requestID INTEGER DEFAULT 3,
                        command PrintableString
                        }
   Wrong ::= ParameterList (WITH COMPONENTS {requestID ABSENT, command})
END

Error Message

"a0420e.asn", line 6 (Module-A0420W): A0420W: 'Wrong' is illegally defined, for it uses WITH COMPONENTS with an absence constraint on a non-OPTIONAL element, 'requestID'.

Possible Solution

Remove the PRESENT or ABSENT keyword from the WITH COMPONENTS constraint.

A0421E

Message Format

A0421E: The size constraint on 'type reference' must contain a base set of constraints before the extensibility mark.

Message Cause

A size constraint includes an extensibility marker that is not preceded by any base values.

Example

Module-A0421E DEFINITIONS ::= BEGIN
   Dummy ::= BIT STRING (SIZE(...))
END

Error Message

"a0421e.asn", line 2 (Module-A0421E): A0421E: The size constraint on 'Dummy' must contain a base set of constraints before the extensibility mark.

Possible Solution

Place one or more base sets of values before the extensibility marker.

A0422E

Message Format

A0422E: The field 'field' referenced by the field 'field' was not found.

Message Cause

An information object class instance is missing a field that is required to establish the value of another field.

Example

Module-A0422E DEFINITIONS ::= BEGIN
   ERROR-CLASS ::= CLASS {
                &category       PrintableString (SIZE(1)),
                &code           INTEGER,
                &OpenType,
                &FixedType      DEFAULT INTEGER,
                &Objset         ERROR-CLASS OPTIONAL,
                &ValSetFixed    INTEGER,
                &vartypeval     &FixedTyp
                }

   error1 ERROR-CLASS ::= { &category    "A" ,
                            &code        1,
                            &OpenType    INTEGER ,
                            &ValSetFixed {1..5},
                            &vartypeval  5
                          }

   FixedValSet ::= error1.&ValSetFixed
END

Error Message

"a0422e.asn", line 17 (Module-A0422E): A0422E: The field '&FixedTyp' referenced by the field '&vartypeval' was not found.

  }

Possible Solution

Add the missing field to the information object class instance.

A0423E

Message Format

A0423E: The value for field 'field' referenced by field '&vartypeval' was not found.

Message Cause

An information object class instance is missing a field that is required to establish the value of another field.

Example

Module-A0423E DEFINITIONS ::= BEGIN
   ERROR-CLASS ::= CLASS {
                &category       PrintableString (SIZE(1)),
                &code           INTEGER,
                &OpenType,
                &FixedType      DEFAULT INTEGER,
                &Objset         ERROR-CLASS OPTIONAL,
                &ValSetFixed    INTEGER,
                &vartypeval     &FixedType
                } WITH SYNTAX  
                 {&category, &code, &OpenType, &ValSetFixed, &vartypeval}

   error1 ERROR-CLASS ::= { "A",
                             1,
                             INTEGER,
                             {1..5},
                             10
                          }
END

Error Message

"a0423e.asn", line 18 (Module-A0423E): A0423E: The value for field '&FixedType' referenced by field &vartypeval' was not found.

  }

Example

Module-C0427W DEFINITIONS ::= BEGIN
  Type1 ::= [0] SEQUENCE {
                age   INTEGER,
                name  PrintableString,
                date  UTCTime,
		...
                }
  ERROR MACRO ::= BEGIN
      TYPE NOTATION ::= "PARAMETER" NamedType | empty
      VALUE NOTATION ::= value(VALUE INTEGER)
      NamedType ::= identifier type | type
  END
END

Error Message

"a0427w.asn", line 8 (Module-C0427W): A0427W: Mixed 1990 and 2021 ASN.1 syntax: "..." on line 6 and "Macro definition" on line 8.

  ERROR MACRO ::= BEGIN

Example

Module-A0430E DEFINITIONS ::= BEGIN
   char1 UniversalString ::= {0, 1, 2, 300}
   char2 IA5String ::= {0, 16}
   char3 IA5String ::= {8, 15}
END

Error Message

"a0430e.asn", line 2 (Module-A0430E): A0430E: The number for the Cell in a Quadruple must be in the range from 0 to 255.

 char1 UniversalString ::= {0, 1, 2, 300}


 "a0430e.asn", line 3 (Module-A0430E): A0430E: The number for the TableRow in a Tuple must be in the range from 0 to 15.

 char2 IA5String ::= {0, 16} 


 "a0430e.asn", line 4 (Module-A0430E): A0430E: The number for the TableColumn in a Tuple must be in the range from 0 to 7.

 char3 IA5String ::= {8, 15}

Possible Solution

Ensure that the delimiters fall within the range indicated by the ASN.1 compiler.

A0431E

Message Format

A0431E: 'type reference' is defined using WITH COMPONENTS but has the CHOICE field 'identifier' constrained to be present.  Only one field of a CHOICE is permitted to have the PRESENT constraint.

Message Cause

A CHOICE type includes a WITH COMPONENTS constraint in which more than one element is marked as present. A CHOICE type can contain only one alternative.

Example

Module-A0431E DEFINITIONS ::= BEGIN
   MYCHOICE ::= CHOICE {first INTEGER, second REAL, third BOOLEAN }
   HerChoice ::= MYCHOICE (WITH COMPONENTS {first  PRESENT,
                                            second PRESENT,
                                            third  ABSENT})
END

Error Message

"a0431e.asn", line 3 (Module-A0431E): A0431E: 'HerChoice' is defined using WITH COMPONENTS but has the CHOICE field 'first' constrained to be present.  Only one field of a CHOICE is permitted to have the PRESENT constraint.

Possible Solution

Replace the PRESENT keyword with ABSENT.

A0432E

Message Format

A0432E: The only constraint permitted on 'INSTANCE OF' is a SimpleTableConstraint.

Message Cause

An INSTANCE OF type has an applied constraint that is not a simple table constraint.

Example

Module-A0432E DEFINITIONS ::= BEGIN
   ACCESS-CONTROL-CLASS ::= TYPE-IDENTIFIER   
   ERROR2 ::= INSTANCE OF ACCESS-CONTROL-CLASS (SIZE (10))
END

Error Message

"a0432e.asn", line 3 (Module-A0432E): A0432E: The only constraint permitted on 'INSTANCE OF' is a SimpleTableConstraint.

  ERROR2 ::= INSTANCE OF ACCESS-CONTROL-CLASS (SIZE (10))

Possible Solution

Replace the constraint with a simple table constraint.

A0433W

Message Format

A0433W: 'string' is invalid 2021 ASN.1 syntax.

Message Cause

The input ASN.1 syntax contains outdated notation that is not valid in ASN.1:2021.

Possible Solution

Replace the outdated syntax with its ASN.1:2021 equivalent or make sure you do not specify the ASN.1 version in use.

A0434E

Message Format

A0434E: The choice value 'value' is ambiguously defined.

Message Cause

The input ASN.1 syntax contains a value assignment to a CHOICE type in which the value assigned can be interpreted as belonging to one or more NamedBitLists or NamedNumberLists.

Example

Module-A0434E DEFINITIONS ::= BEGIN
   ChoiceType ::= CHOICE {
       degree  INTEGER {a(0), b(1)},
       level   BIT STRING {a(0), b(1)}
   }
   choiceValue ChoiceType ::=  a
END

Error Message

"a0434e.asn", line 6 (Module-A0434E): A0434E: The choice value 'a' is ambiguously defined.

Possible Solution

To remove the ambiguity, use the identifier-colon-value notation on the right side of the value assignment.

C0435E

Message Format

C0435E: Value's Type could not be processed.

Message Cause

The ASN.1 compiler could not process a parameterized type associated with a value assignment.

Possible Solution

Check the parameterized type.

C0436I

Message Format

C0436I: TypeReference 'type reference-DummyType' created because of recursive ParameterizedAssignment.

Message Cause

A recursive parameterized assignment requires an auxiliary type definition for proper representation in the header file.

Example

Module-C0436I DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ParamSeq {X} ::= SEQUENCE {
                        a INTEGER,
                        b X,
                        c ParamSeq {REAL} OPTIONAL
                        }
   aseq ParamSeq {PrintableString} ::= { a 5, b "five"}
END

Error Message

"c0436i.asn", line 6 (Module-C0436I): C0436I: TypeReference 'ParamSeq-DummyType' created because of recursive ParameterizedAssignment.

Possible Solution

Restructure the parameterized type so that it does not need a recursive definition.

A0437W

Message Format

A0437W: The right-hand side of ParameterizedAssignment 'ParamAssn' consists solely of a DummyReference.

Message Cause

A parameterized type definition includes only the dummy reference.

Example

Module-C0437W DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ParamAssn {X} ::= X
END

Error Message

"c0437w.asn", line 3 (Module-C0437W): A0437W: The right-hand side of ParameterizedAssignment 'ParamAssn' consists solely of a DummyReference.

  ParamAssn {X} ::= X

Possible Solution

Add one or more components on the right side of the parameterized type definition.

A0438E

Message Format

A0438E: ExceptionSpec is not permitted in this context.

Message Cause

An exclamation point is used in an incorrect context. It must be used in a user defined constraint or a constraint that includes dummy references.

Possible Solution

Remove the invalid exception specification.

A0439E

Message Format

A0439E: Expecting ASN.1 subtype or ASN.1 constraint.

Message Cause

The input ASN.1 syntax is missing a required subtype constraint.

Example

Module-A0439E DEFINITIONS ::= BEGIN
   ERROR ::= CLASS {
      &ParameterType ,
      &errorCode INTEGER UNIQUE
   }
   EmptyErrorSet ERROR ::= { }
END

Error Message

"a0439e.asn", line 6 (Module-A0439E): A0439E: Expecting a subtype or general constraint.

  EmptyErrorSet ERROR ::= { }

Possible Solution

Consider the following solutions:

Recopy the ossinfo file from its original location.
Make sure the OSSINFO environment variable points to the correct ossinfo file for your version of the ASN.1 compiler.

C0446S

Message Format

C0446S: ossinfo file "ossinfo file path" is a pre-5.0 version (number).
  Use current version of this file.

Message Cause

The ossinfo file that the ASN.1 compiler read is outdated.

Possible Solution

Modify the OSSINFO environment variable to point to the location of the ossinfo file shipped with the version of the ASN.1 compiler you are using.

C0447S

Message Format

C0447S: COMPILER ERROR #39.
  Use current version of this file.

Message Cause

The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.

A0448E

Message Format

A0448E: item is not the next item allowed according to the DefinedSyntax.
  Use current version of this file.

Message Cause

An exclamation point (signifying an exception specification) is placed in an inappropriate location.

Example

Module-A0452E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER (1..25 !)
END

Error Message

"a0452e.asn", line 2 (Module-A0452E): A0452E: ExceptionSpec is not permitted for this constraint.  ExceptionSpec may only be specified for UserDefinedConstraints and constraints that include DummyReferences.

     Dummy ::= INTEGER (1..25 !)

Possible Solution

Remove the exclamation point.

A0453E

Message Format

A0453E: 'type reference' is defined using FROM incorrectly.  Each endpoint of a permitted alphabet ValueRange must be a single quoted character.

Message Cause

One or more specified endpoints of a permitted alphabet value range constraint consist of more than one character.

Example

Module-A0453E DEFINITIONS ::= BEGIN
   CapVowels ::= PrintableString (FROM ("A".."EA"))
END

Error Message

"a0453e.asn", line 2 (Module-A0453E): A0453E: 'CapVowels' is defined using FROM incorrectly.  Each endpoint of a permitted alphabet ValueRange must be a single quoted character.

Possible Solution

Replace the multiple character endpoint with one that consists of a single character.

C0454E

Message Format

C0454E: 'type reference' is defined using FROM with MIN or MAX in a ValueRange.  Each endpoint of a permitted alphabet ValueRange must be a single quoted character.  MIN and MAX are not currently supported.

Message Cause

One or more specified endpoints of a permitted alphabet value range constraint are MIN or MAX reserved words.

Example

Module-C0454E DEFINITIONS ::= BEGIN
   CapVowels ::= PrintableString (FROM ("A"..MAX))
END

Error Message

"c0454e.asn", line 2 (Module-C0454E): C0454E: 'CapVowels' is defined using FROM with MIN or MAX in a ValueRange.  Each endpoint of a permitted alphabet ValueRange must be a single quoted character.  MIN and MAX are not currently supported.

Possible Solution

Replace the MIN or MAX keywords with single characters enclosed in quotation marks.

C0455E

Message Format

C0455E: PADDED directive for type reference requires a single size constraint.

C0456W

Message Format

C0456W: The structure for the open type value will be initialized to zeros since the open type value references a BuiltinType.  Consider using a DefinedType in the open type value in place of the BuiltinType.  Consider also making that DefinedType a PDU.

Message Cause

The input ASN.1 syntax contains a value assignment of an open type. However, the value on the right side references a built-in type.

Example

Module-C0456W DEFINITIONS ::= BEGIN
   A ::= TYPE-IDENTIFIER.&Type
   a A ::= [4] PrintableString : "ABC"
END

Error Message

"c0456w.asn", line 3 (Module-C0456W): C0456W: The structure for the open type value will be initialized to zeros since the open type value references a BuiltinType.  Consider using a DefinedType in the open type value in place of the BuiltinType.  Consider also making that DefinedType a PDU.

Example

. . . .

Msg ::= SEQUENCE {
                msgName         IA5String,
                tcipId          TCIP-CLASS.&id ({TCIP-ObjSet}),
                tcipType        TCIP-CLASS.&Type ({TCIP-ObjSet}{@tcipID})
        }

END

Error Message

"a0461e.asn", line 59 (Module-A0461E): A0461E: The field 'tcipID' was not found.

Possible Solution

Make sure the referenced field and the one in the component relation constraint have the same spelling.

A0462E

Message Format

A0462E: The type of field 'component relation constraint referenced field' must be SET, SEQUENCE, or CHOICE.

Message Cause

The input ASN.1 syntax contains a component relation constraint in which the referenced field is not of SET, SEQUENCE, or CHOICE type.

Possible Solution

To conform to Recommendation X.682 (2021) clause 10.8, replace the referenced field.

C0463E

Message Format

C0463E: 'type reference' has a directive name directive which requires directive name directive.

Message Cause

The input ASN.1 syntax is missing a required compiler directive.

Example

Module-C0463W DEFINITIONS ::= BEGIN
   R ::= REAL --<DECIMAL | NOPOINTER>--
END

Message Cause

In a constraint on a BMPString type, the group, the plane value, or both are invalid.

Example

Module-A0467W DEFINITIONS ::= BEGIN
   Name1 ::= BMPString ({1, 2, 3, 4} | {20, 30, 90, 100})
END

Error Message

"a0467w.asn", line 2 (Module-A0467W): A0467W: The group and plane for each quadruple in the BMPString value 'Name1' must be zero.

Possible Solution

Make sure the first two items in the quadruple are both zero.

C0468W

Message Format

C0468W: Generation of initialized C values for INTEGER types with the HUGE directive are not currently supported.  The structure for the HUGE integer value 'value reference' will be initialized to zeros.

Message Cause

A value assignment to an INTEGER type has the ASN1.HugeInteger or OSS.HUGE compiler directive applied to it. Currently, the ASN.1 compiler does not support value assignments to HUGE INTEGER types.

Example

Module-C0468W DEFINITIONS ::= BEGIN
    HugeInt ::= INTEGER --<HUGE>--
    ha HugeInt ::= 1267890
END

Error Message

"c0468w.asn", line 3 (Module-C0468W): C0468W: Generation of initialized C values for INTEGER types with the HUGE directive are not currently supported.  The structure for the HUGE integer value 'ha' will be initialized to zeros.

Possible Solution

Remove the value assignment.

NOTE: This error message is deprecated starting with release 8.5.

C0469E

Message Format

C0469E: The value 'value reference' must be one character long since the ONECHAR directive was specified for its Type.

Message Cause

A value assignment to a character string type has the OSS.ONECHAR directive applied to it. However, the value on the right side of the assignment consists of more than one character.

Example

Module-C0469E DEFINITIONS ::= BEGIN
    OneChar ::= PrintableString --<ONECHAR>--
    oc OneChar ::= "hello"
END

Error Message

"c0469e.asn", line 3 (Module-C0469E): C0469E: The value 'oc' must be one character long since the ONECHAR directive was specified for its Type.

Possible Solution

Replace the value on the right side with a single character or remove the OSS.ONECHAR directive.

C0470W

Message Format

C0470W: The size of the generated C structure for the ASN.1 type exceeds 64K bytes and may adversely affect CPU and memory performance.  Consider use of the LINKED or UNBOUNDED directive.

Message Cause

An ASN.1 type (for example, a SEQUENCE OF or a SET OF) is using the ARRAY representation, but the physical size of the array may cause inefficiencies during run time.

Example

Module-C0470W DEFINITIONS ::= BEGIN
    ArrayInt ::= SET (SIZE(500000)) --<ARRAY>-- OF INTEGER
END

Error Message

"c0470w.asn", line 2 (Module-C0470W): C0470W: The size of the generated C structure for the SET OF or SEQUENCE OF exceeds 64K bytes and may adversely affect CPU and memory performance.  Consider use of the LINKED or UNBOUNDED directive.

Example

Module-C0474W DEFINITIONS ::= BEGIN
  OS ::= IA5String (SIZE(500000)) --<VARYING>--
END

Error Message

"c0474w.asn", line 2 (Module-C0474W): C0474W: The size of the generated C structure for the character string exceeds 64K bytes and may adversely affect CPU and memory performance.  Consider use of the UNBOUNDED directive.

Possible Solution

Apply the OSS.UNBOUNDED directive to the type.

A0475W

Message Format

A0475W: ANY 'type reference' is used in an ambiguous context as a PDU.

Message Cause

An ANY type is used as a PDU, but the context is ambiguous because DEFINED BY is not used.

Example

Module-A0475W DEFINITIONS ::= BEGIN
   A ::= ANY
   Dummy ::= INTEGER
END

Error Message

"a0475w.asn" (Module-A0475W): A0475W: ANY 'A' is used in an ambiguous context as a PDU.

Possible Solution

Consider the following solutions:

Place the ANY type within a SET or SEQUENCE and use the DEFINED BY notation to remove ambiguity.
Replace the ANY type with an equivalent use of an information object class.

A0476W

Message Format

A0476W: The open type 'type reference' is used in an ambiguous context as a PDU.

Message Cause

An open type is used as a PDU, but the context is ambiguous because no type constraint is used.

Example

Module-A0476W DEFINITIONS ::= BEGIN
   A ::= TYPE-IDENTIFIER.&Type
   Dummy ::= INTEGER
END

Message format when using the compiler GUI:

C0479W: The EXTERNAL keyword was encountered on line x and treated as 2021 EXTERNAL, but the 1990 ASN.1 Syntax "excerpt" was encountered on line y. To force the 1990 EXTERNAL to be used, please check the "1990" radio button in the "Compiler" tab of the "Compiler Options" window.

Message Cause

An EXTERNAL type will be represented using the ASN.1:2021 specification for this type. However, your input also contains ASN.1:1990-specific notation.

Example

Module-C0479W DEFINITIONS ::= BEGIN
   E ::= EXTERNAL
   A ::= SEQUENCE {
      id   OBJECT IDENTIFIER,
      data ANY DEFINED by id
   }
END

Error Message

"c0479w.asn", line 5 (Module-C0479W): C0479W: The EXTERNAL keyword was encountered on line 2 and treated as 2021 EXTERNAL, but the 1990 ASN.1 Syntax "ANY" was encountered on line 5.  Consider using the '1990' compiler option to force the 1990 EXTERNAL to be used.

  data ANY DEFINED by id

Possible Solution

To instruct the ASN.1 compiler to use the ASN.1:1990 representation of the EXTERNAL type, specify the -1990 compiler option.

A0480E

Message Format

A0480E: The ObjectClassFieldType 'field reference' must not reference an objectfield or objectsetfield.

Message Cause

The input ASN.1 syntax contains an attempt to extract an object or object set field from an information object. This extraction is not valid.

Example

Module-A0480E DEFINITIONS ::= BEGIN
   Dummy ::= INTEGER
   ERROR-CLASS ::= CLASS {
                &category       PrintableString (SIZE(1)),
                &code           INTEGER,
                &OpenType,
                &FixedType      DEFAULT INTEGER,
                &Objset         ERROR-CLASS OPTIONAL
                }
                WITH SYNTAX {&category &code &FixedType &OpenType}

   error1 ERROR-CLASS ::= { "A" 1 INTEGER PrintableString }
   Choice ::= CHOICE {
                dummy           [0] Dummy,
                opentypefield   [2] ERROR-CLASS.&OpenType,
                fixedtypefield  [3] ERROR-CLASS.&FixedType,
                objset          [4] ERROR-CLASS.&Objset
                }
END

Error Message

"a0480e.asn", line 17 (Module-A0480E): A0480E: The ObjectClassFieldType 'objset' must not reference an objectfield or objectsetfield.

Possible Solution

Remove the invalid extraction attempt.

C0481E

Message Format

C0481E: Implementation limit exceeded by real value.

Message Cause

The value for a REAL type is too large to be represented in the conventional way on your specific platform.

Possible Solution

To correct this error, use the OSS.DECIMAL or the OSS.MIXED compiler directive. These compiler directives can hold large values on any platform.

A0482E/A0482W

Message Format

A0482E: 'item' is referenced as an External <X> reference, but it is not in the list of symbols imported from the module `module reference`.

Message Cause

The input ASN.1 syntax contains an attempt to use a component of an external module. However, the component was not imported from the external module.

Example

Module-A0482E DEFINITIONS ::= BEGIN
   IMPORTS Q FROM A;
   i A.B ::= TRUE
END

A DEFINITIONS ::= BEGIN
   EXPORTS Q;
   Q ::= INTEGER
   q Q ::= 3
   B ::= BOOLEAN
END

Error Message

"a0482e.asn", line 3 (Module-A0482E): A0482E: 'B' is referenced as an External <X> reference, but it is not in the list of symbols imported from the module `A`.

  i A.B ::= 3

Possible Solution

Add the missing item to the EXPORTS statement of the source module.

Module-A0488E DEFINITIONS ::= BEGIN
   ExtensibleChoice ::= CHOICE {
      ...,
      a INTEGER

   }
END

Error Message

"a0488e.asn", line 3 (Module-A0488E): A0488E: Extensible CHOICE type must have at least one alternative in the extension root.

  ...,

Possible Solution

Place one or more alternatives before the extension marker.

C0489E

Message Format

C0489E: Unrecognized standard directive 'directive name'.

Message Cause

The directive used is not one of the known directives supported by the compiler.

Example

--<ASN1.HUGE Module-C0489E.hugeINT>--

Module-C0489E DEFINITIONS ::= BEGIN
   HugeINT ::= INTEGER

END

Error Message

"c0489e.asn", line 1 (): C0489E: Unrecognized standard directive 'HUGE'.

  --<ASN1.HUGE Module-C0489E.hugeINT>--

Possible Solution

Check the spelling of the directive name. For more information, see Directives.

A0490E

Message Format

A0490E: Expecting '.' after name of scope.

Message Cause

A standard or OSS-new-style directive is missing a period (".") between the OSS or ASN1 part and the directive name.

Example

--<OSS HUGE Module-C0489E.HugeINT>--

Module-C0490E DEFINITIONS ::= BEGIN
   HugeINT ::= INTEGER

END

Error Message

""a0490e.asn", line 1 (): A0490E: Expecting '.' after name of scope.

--<OSS HUGE Module-C0489E.HugeINT>--

Possible Solution

Add the missing period after the OSS or ASN1 part of the directive specification.

C0491E

Message Format

C0491E: Constrained HUGE integers other than (0..MAX) are currently not supported with 'per' compiler option specified.

Message Cause

An ASN1.HugeInteger or OSS.HUGE compiler directive is used while the Packed Encoding Rules were specified. Currently, the ASN.1 compiler does not support such constraints with PER in use.

Example

--<ASN1.HugeInteger Module-C0491E.HugeINT>--

Module-C0491E DEFINITIONS ::= BEGIN
   HugeINT ::= INTEGER (0..1500000)
END

Error Message

"c0491e.asn", line 4 (Module-C0491E): C0491E: Constrained HUGE integers other than (0..MAX) are currently not supported with 'per' compiler option specified.

Possible Solution

Make sure you do not specify the -per/-uper option when compiling the input syntax.

C0492I

Message Format

C0492I: There are unused standard directives.  Specify the -gendirectives command-line option, then look at all lines containing "WARNING:" in the generated .gen file.

Message format when using the compiler GUI:

C0492I: There are unused standard directives.  Check the "Convert local directives to standard directives" box in the "Output Files" tab of the "Compiler Options" window, then look at all lines containing "WARNING:" in the generated .gen file.

Message Cause

A standard directive could not be applied to any part of the specification.

Example

--<ASN1.HugeInteger Module-C0492I.HugeInt>--

Module-C0492I DEFINITIONS ::= BEGIN
   HugeINT ::= INTEGER (0..1500000)

END

Error Message

C0492I: There are unused standard directives.  Specify the -gendirectives command-line option, then look at all lines containing "WARNING:" in the generated .gen file.

Possible Solution

Make sure the absolute reference that you specified is spelled correctly and exactly matches the component for the directive.

A0493E

Message Format

A0493E: The referenced field of the component relation constraint for 'identifier' must be an ObjectClassFieldType.

Message Cause

A SEQUENCE, SET, or CHOICE contains a component taken from an information object class, but the component relation constraint specified on this component references a non-information object field type.

Example

[Top portion not shown]

. . . .

Msg ::= SEQUENCE {
                msgName         IA5String,
                tcipId          TCIP-CLASS.&id ({TCIP-ObjSet}),
                tcipType        TCIP-CLASS.&Type ({TCIP-ObjSet}{@msgName})
        }

END

Error Message

"a0493e.asn", line 58 (Module): A0493E: The referenced field of the component relation constraint for 'tcipType' must be an ObjectClassFieldType.

Possible Solution

Replace the name after the '@' symbol with one that references a field from an information object (for example, tcipId).

C0494W

Message Format

C0494W: 'type reference' is defined using WITH COMPONENTS containing a ValueConstraint for the field 'identifier', but that constraint is being ignored since the ENCODABLE directive was specified for that field.

Message Cause

A WITH COMPONENTS constraint has a value constraint for one of the components listed. However, its value will not be checked during runtime by the built-in constraint checker because the OSS.ENCODABLE directive is applied to that component.

Example

Module-C0494W DEFINITIONS ::= BEGIN
   Set  ::= SET {
      d BOOLEAN,
      e INTEGER --<ENCODABLE>--,
      f VisibleString
   }
   Set1 ::= Set (WITH COMPONENTS {d, e (1 | 2), f})
END

Error Message

"c0494w.asn", line 7 (Module-C0494W): C0494W: 'Set1' is defined using WITH COMPONENTS containing a ValueConstraint for the field 'e', but that constraint is being ignored since the ENCODABLE directive was specified for that field.

Possible Solution

Remove the OSS.ENCODABLE directive.

C0495W

Message Format

C0495W: The constraint on 'type reference' is being ignored since the DeferDecoding directive or the ENCODABLE directive was specified for this type.

Message Cause

The subtype constraint on a type will be ignored because the ASN1.DeferDecoding or OSS.ENCODABLE directive is applied to the type.

Possible Solution

Remove the subtype constraint or the directive.

A0496E

Message Format

A0496E: 'type reference' is defined using WITH COMPONENTS, but the associated SET, SEQUENCE, or CHOICE has no components.

Message Cause

The input ASN.1 syntax contains a WITH COMPONENTS constraint, but the structure from which types will be extracted is empty.

Example

Module-A0496E DEFINITIONS ::= BEGIN
   Set  ::= SET {
   }
   Set1 ::= Set (WITH COMPONENTS {d, f})
END

Error Message

"a0496e.asn", line 4 (Module-A0496E): A0496E: 'Set1' is defined using WITH COMPONENTS, but the associated SET, SEQUENCE, or CHOICE has no components.

Possible Solution

Add the appropriate types to the empty structure.

A0497E

Message Format

A0497E: The identifier 'identifier' can occur only once in MultipleTypeConstraints.

Message Cause

A WITH COMPONENTS constraint lists the same component more than once.

Example

Module-A0497E DEFINITIONS ::= BEGIN
   FlagInfo ::= SET { code INTEGER, name PrintableString OPTIONAL }
   Flags ::= FlagInfo (WITH COMPONENTS {code PRESENT, code ABSENT})
END

Error Message

"a0497e.asn", line 3 (Module-A0497E): A0497E: The identifier 'code' can occur only once in MultipleTypeConstraints.

  Flags ::= FlagInfo (WITH COMPONENTS {code PRESENT, code ABSENT})

Possible Solution

Delete the duplicate components or change the names accordingly.

A0498E

Message Format

A0498E: No more than two occurrences of '...' are permitted in each SET/ SEQUENCE/CHOICE.

Message Cause

A SET, a SEQUENCE, or a CHOICE contains more than two extensibility markers. According to the ASN.1 syntax, this is not valid.

Example

Module-A0498E DEFINITIONS ::= BEGIN
  Type1 ::= SET {
     a  INTEGER,
     b  BOOLEAN,
     ... ,
     c  OCTET STRING,
     ... ,
     d  BIT STRING,
     ...
  }
END

Error Message

"a0498e.asn", line 9 (Module-A0498E): A0498E: No more than two occurrences of '...' are permitted in each SET or SEQUENCE.

  ...

Possible Solution

Make sure you do not have more than two extensibility markers in a SET, a SEQUENCE, or a CHOICE.

C0498W

Message Format

C0498W: A standard or OSS-specific directive cannot be applied to a macro definition.

Message Cause

A compiler directive is applied to a macro definition. The ASN.1 compiler does not support the application of directives to macros.

Example

--<ASN1.Nickname Module-C0498W.ERROR "NEW-ERR">--

Module-C0498W DEFINITIONS ::= BEGIN
    ERROR MACRO ::= BEGIN
       TYPE NOTATION  ::= "PARAMETER" NamedType | empty
       VALUE NOTATION ::= value(VALUE INTEGER)
       NamedType ::= identifier type | type
     END
     error ERROR ::= 5
END

Error Message

"c0498w.asn", line 6 (Module-C0498W): C0498W: A standard or OSS-specific directive cannot be applied to a macro definition.

  VALUE NOTATION ::= value(VALUE INTEGER)

Possible Solution

Remove the compiler directive.

A0499E

Message Format

A0499E: No root alternatives are permitted after a pair of '...' in each CHOICE.

Message Cause

A CHOICE type contains alternatives listed after two extensibility markers. This is not valid.

Example

Module-A0499E DEFINITIONS ::= BEGIN
   A ::= CHOICE {
         c BOOLEAN,
         ... ,
         ... ,
         d OCTET STRING
      }
END

Error Message

"a0499e.asn", line 5 (Module-A0499E): A0499E: No root alternatives are permitted after a pair of '...' in each CHOICE.

  ... ,

Possible Solution

Remove the alternatives or add them before the extensibility markers.

A0499W

Message Format

A0499W: The NOCOPY directive is not supported on BMPString or UniversalString types and is being ignored.

Message Cause

An OSS.NOCOPY or OSS.OBJHANDLE compiler directive is applied to a BMPString or UniversalString type. This is not supported.

Example

--<OSS.NOCOPY Module-A0499W.SwahiliString>--

Module-A0499W DEFINITIONS ::= BEGIN
   SwahiliString  ::= BMPString
END

Error Message

"a0499w.asn", line 4 (Module-A0499W): A0499W: The NOCOPY directive is not supported on BMPString or UniversalString types and is being ignored.

Possible Solution

Remove the compiler directive application.

This documentation applies to the latest versions of the OSS® ASN.1 Tools software.

Copyright © 2025 OSS Nokalva, Inc. All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means electronic, mechanical, photocopying, recording or otherwise, without the prior permission of OSS Nokalva, Inc.
Every distributed copy of the OSS® ASN.1 Tools is associated with a specific license and related unique license number. That license determines, among other things, what functions of the OSS ASN.1 Tools are available to you.