AionDS Messages and Codes Guide

Overview
Overview
.........................................................................................................................................................................................................˝..........................................
Fatal system errors
7-2 AionDS Messages and Codes
A fatal system error occurs when AionDS detects an internal inconsistency or
operating condition that requires the development or execution system to be
shut down. The error is displayed on the user’s terminal, and is also written
to the AionDS system log. Some common causes of fatal system errors are:
■ A bug in the AionDS product which, upon detection, jeopardizes the
integrity of the application being developed or executed.
■ A bug in the application, such as a knowledge base logic error or an API
data transfer error, which, upon detection, jeopardizes the integrity of the
application execution.
■ An operating system error, which, upon detection, jeopardizes the
integrity of the application being developed or executed. For example, a
memory allocation request is made to the operating system, but there is
not enough memory available to satisfy the request.
.........................................................................................................................................................................................................˝..........................................
Fatal system error
processing
Fatal system errors can occur at edit time and runtime. AionDS performs the
following actions when a fatal system error is detected:
1 The fatal system error is displayed on the user’s terminal.
2 The AionDS consultation trace is flushed and closed.
3 The AionDS system log is flushed and closed.
4 If a local SQL database connection exists, a ROLLBACK request is
issued to cancel any uncommitted database changes.
5 A call is made to the operating system to terminate the development or
execution system.