2. Type of messages#

The logical printing units are established at the beginning of the execution of the work, by the supervisor. The prints issued by the routines described in the following paragraphs will be carried out on these logical units without the possibility of redirection.

The messages sent will be directed only according to their type:

Code

Message Type

Output Files

F

Fatal error message, execution stops after the message is printed.

MESSAGEERREURRESULTAT

E

Error message, execution continues (a bit) cf. [§ 2.2] .

MESSAGEERREURRESULTAT

A

Alarm message.

MESSAGERESULTAT

I

Information message.

MESSAGE

Z

Recoverable exception throwing in python

2.1. Type F messages#

This type of message is followed by an immediate shutdown of the application; it is used to detect a serious error that cannot allow the normal continuation of an Aster command. Sending a F error message causes execution to stop.

By default for « real » users (if the DEBUT/CODE keyword is not used), execution stops after validating the concepts that can be validated:

  • concepts produced by orders already executed

  • The concept being created if the order provided for it (for example, for order STAT_NON_LINE, the time steps already archived are validated).

On the other hand, if the command file uses DEBUT/CODE, the code stops immediately and calls the abort () routine in order to create a « core file » that can be used by the post-mortem debugger.

2.2. Type E messages#

This type of message makes it possible to analyze a series of errors before stopping the program. For example, the syntactic analysis of the command file by the Supervisor or the analysis of the mesh file by the command LIRE_MAILLAGE.

The sender of a E message must send a F message at the end of its analysis.

2.3. Type A messages#

A alarm messages that may unnecessarily worry users should not be abused. The message must be clear and include ways to avoid this alarm.

The number of alarm messages is automatically limited to 5 successive identical messages.

It is recommended that users who have type A messages « repair » their command file to make them disappear.

2.4. Type I messages#

I messages are informational messages*.*

2.5. Type Z messages#

Z messages are messages that allow the « exceptions » mechanism*.* This type of message is only used in the 2 routines utexcm and utexcp. and should not be used elsewhere! See [§ 8] for exceptions in general.