The OSS ASN.1 compiler and runtime routines can both generate error and informatory messages. Use these error messages to help pinpoint problems in your ASN.1 syntax or application code.
Go directly to the Runtime Error Reference to look up OSS ASN.1 Runtime error messages by message number.
There are four types of messages issued by the various OSS ASN.1 Tools components:
Only the runtime function messages are available through this page. See OSS ASN.1 Compiler Errors to look up the other three types of messages.
All four types of messages carry a unique code that identifies each issued message. This message code consists of six characters: the first identifies the OSS ASN.1 Tools component that issued the message, next is a four-digit message number, and the last indicates the severity level of the message. See the following table for more details:
in Message Code
A C L D E
ASN.1 syntax checker ASN.1 compiler input-file processor ASN.1 compiler command-line format checker Decoder routines Encoder routines
|Second through Fifth||Message Number||0001 to 9999||Unique, four-digit message ID number|
I W E S
Informatory message (Level 0)
Typical runtime function signal message
A typical XER encoding error message also contains the line number and position of the error occurrence, as shown in the following example:
D0174E: Canonical XER restrictions are violated: 'XML encoding for contained types should have been used'; check field 'content' (type: BIT STRING) of PDU #1 'DataPacket' at line 1 position 4.
A runtime function message can also have fewer details, depending on the encoder/decoder and the debug options used.
Go to the Runtime Error Reference to look up OSS ASN.1 runtime error messages by message number.
This documentation applies to release 10.0.1 and later of ASN-1Step®.
Copyright © 2021 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 ASN-1Step is associated with a specific license and related unique license number. That license determines, among other things, what functions of ASN-1Step are available to you.