2. What should you read in this listing?

Overall, the listing contains a lot of useless impressions (those that say « everything is fine »). This information does not facilitate the task of reading, but it makes it possible to verify that the sources taken into account are indeed the right ones.

So, you don’t have to read the whole listing! The information that should not be missed are fatal errors and alarms.

Fatal errors (the ones that will make it impossible to restore) all start with the string « (F/U-« ). For example:

(F/u-015-bis): The /cluster/members/members/member2/tmp/519552/vabhhts/histor file does not conform to the canvas

(f/U-H01B): X0.00.00 documentary keys are forbidden.

(F/U-046): acou_face3: SUPPRESSION SOUS - CATALOGUE IMPOSSIBLE

(F/U-091): ERROR (S) and WARNING (S) FORTRAN (detected by g77):

The alarms all start with the string « (A/U- ». For example:

(A/U-040): MODIF OK from: calculel/calcul.f

(A/U-558): size_simple__: modification of a unit whose manager is: JMBHH01

(A/U-043): decal: FORSUPPR ROUTINE OK

(A/U-044): sslx101a: SUPPRESSION CAS - TEST OK

These examples show that unfortunately, these « alarms » are not always alarms!

To help the user find their way around, the asverif tool summarizes the alarms that resulted in a non-zero return code. Warning: this summary is only produced if no fatal error is detected.

Example:

###############################################################################

### Summary of Alarms resulting in a return code = 2:

(a/u-H10): Modification of document: U4.02.01


(A/U-222): calculation: Modification of map TOLE

The errors preceded by an A have been added to the map

Errors preceded by an S have been removed from the map

A CRP_20 CALCUL

###############################################################################

2.1. Summary

When using one of the agla tools (asverif/asrest/pre_eda), you must first search for the string « (F/U ») in the listing. This channel « points » to fatal errors. When all the fatal errors are corrected, you should then look at the Alarms summary.

Note:

Recently, a new check has been made concerning the consistency between the message identifiers used in the sources (for example: ALGELINE_12) and the presence of these messages in the message catalogs (bibpyt/Messages/.py). Unfortunately, this check (at the end of the listing) does not emit a message* « (F/U ») in the listing.

The problems detected: « missing » message or « unused » message appear in the following form in the listing:

Unused messages:

CALCULEL4_4 PREPOST6_37

Messages that do not exist:

PREPOST6_36