Event Management Configuration › How to Configure Optional Event Management Tasks › Set Up the Berkeley syslog daemon › Reroute Messages to a Remote Host

Reroute Messages to a Remote Host

Event Management on z/OS can accept syslog messages from any remote system running a compatible BSD syslog service.

To instruct the syslog daemon to route all messages to a remote machine, edit the syslogd configuration file and insert the remote hostname in the action part of the line, prefixing the hostname with a single at sign (@).

Note: The syslog daemon makes use of DNS (Domain Name Services) and relies on proper definition of the hostname and IP address of the receiving host.

Example: The following syslogd configuration illustrates an entry on the local node that routes all messages with a priority of info and above to the remote host known as titan:

# @(#) $Revision:  66.1  $
#
# syslogd configuration file

# See syslogd(1M) for information about the format of this file

mail.debug       /usr/spool/mqueue/syslog
*.info,mail.none /usr/adm/syslog
*.alert          /dev/Event
*.alert          root
*.emerg          *
*.info           /cai/nsmem/oprconfig/abcfred/pipe/oprpipexxxx
*.info           @titan

Note: The syslogd configuration file contains tabs as field delimiters in addition to spaces. Typically, the first and second columns are separated by tabs as well as spaces. Do not use blanks alone to delimit fields, as this will cause the syslog daemon to ignore the line in question or give improper results.

To send messages to additional hosts, simply add more lines as needed. If you want to limit the messages to certain priorities or facilities, do so with the first part of the command line. For more information on selecting and routing messages, see the man pages for syslogd.