HP-UX SNAplus2 CSV Programmer's Guide

Common Service Verbs Reference
LOG_MESSAGE (HP-UX Systems Only)
Chapter 2 71
• Each field name (such as Message) must be at the start of a line,
followed by a colon. Spaces or tabs following the colon are ignored.
All the text associated with the field name must be in a single line
(except when lines are concatenated using the $ character, as
described below); there is no limit on the length of the line.
• In the Cause, Action, and String fields, the following characters can
be used to control the format of the text written to the log file:
\t
Insert a tab character in the output text.
$
(followed by a new-line character in the source text)
Insert a new-line character in the output text, and
continue with the following line of the source file.
This enables you to specify a text field that extends
over more than one line. The last line of the text
field must not end with a $ character.
\n
Insert a new-line character in the output text, and
continue with the following character of the source
file. This enables you to specify a text field as a
single line in the source file, and to specify where
line breaks will appear in the output. However, it is
recommended that you split long text fields into
multiple lines using the $ character, as described
above, for readability.
\$
Insert a $ character in the output text.
%n (in the “String” parameter only)
Insert the nth parameter supplied to the log call in
the output text.
The logging code does not insert new-line characters into text strings
except where \n or $ characters are included in the source text. To
ensure that the output text is easily readable on an 80-column
screen, use these characters to force line breaks.