Step 2: Configure and start syslogd

The Advisor and Agent write most log messages and trace data to the syslog daemon (syslogd). A limited number of messages are written to the MVS™ console, but these are unaffected by syslogd configuration. For the Advisor and Agent to be able to write their log messages and trace data to syslogd, syslogd must be properly configured and started before the Advisor and Agent are started.

Because it is likely that you will be running an Agent on the same system as the Advisor, for better readability, you might want to configure syslogd to place Advisor and Agent log output in separate files. For further information, see Configuring the syslog daemon. In a sysplex subplexing environment, this step requires additional actions. For information about the changes to this step, see Syslogd considerations in a subplexing environment.

Tip: As more data is logged by the Advisor and Agent, performance of the Advisor and Agent can be adversely affected. The amount of data that is logged by the Advisor and Agent is determined by the debug_level statement. Backing the syslogd output file with a z/OS® File System instead of an HFS file system can minimize performance impacts caused by logging.