Routing USS program messages to the MVS console
Any USS program can write to /dev/console and the output will go to the MVS console.
For example, from OMVS in TSO, enter:
The SDSF log shows:
How SYSLOGD output is routed to the MVS console
SYSLOGD messages can be directed to /dev/console by coding the following statement in /etc/syslog.conf:
Then an attempt to use sendmail when sendmail is not configured yields:
1284 : ipv6 socket
426
426 00000281 is unavailable,set inetmode to AF_INET
STC06976 00000281 BPXF024I (BMVJOJ2) May 29 08:27:17 BBSYSC sendmail
1284 : NOQUEUE: 427
427 00000281 SYSERR(MVSSTC): /etc/mail/sendmail.cf: line 0: EZZ7585I cannot open
427 00000281 /etc/mail/sendmail.cf: EDC5129I No such file or directory.
How remote logging works
SYSLOGD messages can also be directed from one syslogd to the syslogd of another system by coding the hostname as the log file in /etc/syslog.conf:
For example, coding *.* @BBSYSC in the syslog.conf for the zLinux system lnx02jj, will cause the log traffic to be directed to the log file of BBSYSC.
Log on to lnx02jj and enter:
Yields the multiline message on SJSC:
897 00000281 message on
Starting and stopping SYSLOGD
SYSLOGD can be started or stopped by a user with superuser authority (UID 0). To stop SYSLOGD, enter:
To start SYSLOGD, enter:
# -m 15 will put a mark in the log every 15 minutes.
For more information see the following IBM documentation:
- z/OS Communications Server: IP Configuration Guide
- z/OS Communications Server: IP Configuration Reference
Related topic