RSC/MP 7.3 Installation and Configuration Guide

Configuring the RSC/MP Transport (Piccolo)
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011
5-17
Specifying Piccolo Logging
Specifying Piccolo Logging
All Piccolo log messages are written to a text file by the Pipeman process. The
location, size, and detail level of the logs can be specified using the LogFileName,
LogFileEntries, and LogLevel options in the [PIPEMAN] section of the configuration
file.
The LogFileName option specifies the name of the primary log file. The Pipeman
process also maintains up to ten secondary log files which are created when the
PIPECP LOGSWITCH command is used or when the LogFileEntries value has been
exceeded. The secondary log file names consist of the concatenation of the primary
log file name and a single digit from 0 through 9, with 0 being the newest and 9 being
the oldest copy of the primary log file. When the number of log files exceeds the
number of entries specified by the LogFileEntries option, the log files are rolled over as
follows:
•
The secondary log file 9, if present, is deleted.
•
The secondary log files are rolled over (for example, file 8 is renamed as file 9, file
7 is renamed as file 8, and so on).
•
The primary log file is renamed as secondary log file 0.
•
A new primary log file is opened.
Available disk space and performance are the main considerations when selecting the
location and attributes of the log file. Enough disk space must exist to accommodate
the specified log entries. If disk space is insufficient for log messages to be written, the
Pipeman process suspends logging. When sufficient disk space is made available,
logging can be re-enabled using the PIPECP LOGSWITCH command. Details about
log level and size specification can be found in Configuration Options Reference on
page 5-19.
Because the Pipeman process opens the primary log file for exclusive access, you
cannot view the primary log file while the Pipeman process is running. To view the
primary log file you must stop the Pipeman process or roll the log files over using the
PIPECP LOGSWITCH command. Alternatively, you can also use the PIPECP
LOGVIEW command to display log events. See PIPECP Commands on page 11-2 for
more information about the PIPECP commands that manage log activity.