Next: SIC /COLOR Up: SIC Previous: SIC MEMORY Contents Index
[SIC\]SIC MESSAGE
[SIC\]SIC MESSAGE Pack1 [[[S|L|A]-|=|+]F|E|W|R|I|D|T|C|U] [PackN...]
[SIC\]SIC MESSAGE Global [[[S|L|A]-|=|+]F|E|W|R|I|D|T|C|U] [ON|OFF]
[SIC\]SIC MESSAGE * [[[S|L|A]-|=|+]F|E|W|R|I|D|T|C|U] [PackN...]
[SIC\]SIC MESSAGE /COLOR [Args]
The command SIC MESSAGE allows to customize the general verbosity of all
the GILDAS commands, or to customize the color of the messages depending
on their kinds (see HELP SIC /COLOR for details).
Modify and display the messaging filters for one or more packages. Mes-
sages are usually printed on screen and into a message file in the
GAG_LOG: directory. Depending on its kind (from trace to fatal errors),
a message may be printed or not to one of these outputs. Messaging fil-
ters allow the user to fine tune the kinds of messages he wants to see.
Filters are either global (i.e. all the messages are filtered whathever
the package they belong to) or package-dependent (i.e. the messages are
filtered depending on the package they belong to).
The command SIC MESSAGE,
- without argument, outputs the messaging filters for all active pack-
ages;
- with one or more package name as arguments, displays the associated
filters, e.g. :
GREG> SIC MESSAGE SIC GLOBAL
sic on-screen active filter: FEWRI---U
sic to-mesfile active filter: FEWRIDTCU
global on-screen inactive filter: FE-------
global to-mesfile inactive filter: FEWRIDTCU
First column shows the package name, second column the output de-
vice, third column the filter status, last column the associated
filter;
- with a package name followed by a messaging rule (see below), up-
dates its the filter value and displays it. The filters of several
packages can be changed on the same command line, e.g. SIC MESSAGE
SIC S+D GREG L-W
The package name can additionally have two special values:
- * : all the package filters are modified according to a single input
rule;
- GLOBAL : set a global filter which can override all the package fil-
ters without loosing them. This global behavior is activated and de-
activated by the ON or OFF keyword.
A rule to change a filter is a single string composed of three parts,
from left to right:
- A, S and/or L as first argument to modify All, Screen, or Logfile
filters. This must be unique but is optional, default is Screen on-
ly.
- +, - or = as second argument to add to, remove from, or redefine
filter values. This operator must be unique, and it is optional: de-
fault is +.
- F, E, W, R, I, D, T, C and/or U as last argument(s) to modify the
filters on Fatal, Error, Warning, Result, Info, Debug, Trace, Com-
mand and Unknown messages. This argument is mandatory, and the let-
ters may be associated.
The message kinds are:
F)atal: Program will cleanly end now because a fatal error occured,
e.g. a required initialization of the program could not occur or an
error can not be safely recovered or the program is in an unstable
status and can not go on.
E)rror: Command or action could not be executed to its end. Such er-
rors can be recovered, and program can continue to run safely.
- It denotes an attempt to do something not allowed or not imple-
mented in the command.
- Command can not run to the end as it will not produce the expected
result.
W)arning: Command or action will go on executing without an error, but
- the user must be warned about a strange behavior;
- a result is produced, but user must be careful with its interpre-
tation.
R)esult: Information directly requested by the user. It concerns all
the results returned by active commands. This should be understand
as:
- "You asked for this, as a result, that happened"
- "This was created/changed accordingly to your request"
- "Here is what you asked for (some values,...) "
I)nfo: Additional information not directly expected by the user when
he runs the command. It gives secondary informations on current ac-
tions, or it concerns more or less the result and the processes to
obtain it, but it is not the result itself.
D)ebug: High level debugging, e.g. follow the steps of complex compu-
tation. By default, it will not be printed. User can activate it if
strange non-fatal behavior occurs.
T)race: Low-level debugging, e.g. track the program execution. By de-
fault, it will not be printed. User must use it wisely because it
may produce thousands of messages in a row (for example, in loops).
User can activate it in case of unforeseen fatal behavior.
C)ommand: Each command typed on the terminal is resolved and can
printed back to terminal and to logfile. This is equivalent to the
obsolescent SIC VERIFY ON behavior.
U)nknow: It is reserved for the migration from the old message facili-
ties to the new one, and to handle internal errors in messaging
process.
Simple examples:
SIC> SIC MESSAGE
sic on-screen active filter: FEWRI---U
sic to-mesfile active filter: FEWRIDTCU
SIC> SIC MESSAGE SIC GLOBAL
sic on-screen active filter: FEWRI---U
sic to-mesfile active filter: FEWRIDTCU
global on-screen inactive filter: FE-------
global to-mesfile inactive filter: FEWRIDTCU
SIC> SIC MESSAGE SIC S+D
sic on-screen active filter: FEWRID--U
sic to-mesfile active filter: FEWRIDTCU
SIC> SIC MESSAGE SIC L-DT
sic on-screen active filter: FEWRID--U
sic to-mesfile active filter: FEWRI--CU
SIC> SIC MESSAGE SIC A=FEWRI
sic on-screen active filter: FEWRI----
sic to-mesfile active filter: FEWRI----
SIC> SIC MESSAGE GLOBAL ON
Turning ON global filtering rules
SIC>
Q: I've lost all messages, SIC MESSAGE is silent, what happens?
A: Many message kinds are certainly disabled, in particular Results
printed to Screen. This is why SIC MESSAGE is also silent. Consider
typing SIC MESSAGE SIC S+R and you should see back messaging filters.