Description:
MESSAGE adds text in the message buffer. The action of the MESSAGE built-in
depends on the first parameter. All forms of MESSAGE look for a buffer named
"message_buffer". If message buffer is mapped to a window, then the message is
displayed on the screen. If no buffer is available, the text is output to your
standard output device.
If the first parameter is a range, the entire range is output as an error
message. If the first parameter is a string, the string is output to the message
buffer. If the first parameter is an integer or keyword, the optional second
parameter is a severity indicator as follows: 0
(Warning), 1 (Success), 2 (Error), 3 (Informational).
If the first parameter is either a keyword or integer, a call is made to the
MESSAGE_TEXT built-in and the output is sent to the message buffer. The
optional Fao-paramters are only used when the first paramter is an integer or keyword.
Syntax:
MESSAGE ( message )
MESSAGE ( message, severity )
MESSAGE ( message, severity, FAO-parameters )
Valid types of message are: Integer, Keyword, Range, or String
Example:
MESSAGE ("my error message");
Errors:
TPU$_FLAGTRUNC Message flags cut to 4 bits.
TPU$_ILLSEVERITY Cannot use indicated severity.
TPU$_INVFAOPARAM Argument must be an integer or string.
TPU$_MSGNOTFND Unable to locate message.
TPU$_SYSERROR Error getting message from table.
Related Builtins:
MESSAGE