What Grega Bremec said is right on!
SYSLOG uses "facility" and "priority" to route its messages.
(Use of the word "route" here means which FILE a message goes into,
not necessarily which host it goes to.) There are conventions for
how the messages look, but SYSLOGD will probably record
ANYTHING that you throw at it.
> Thank you for responding. To give more information it is running under
> Unix System Services (z/os v1.4) using syslogd and then I am going to
> ship to a z/linux LPAR running SUSE SLES 8.
Excellent!
Be aware that the Linux receiver must be enabled.
Linux SYSLOGD normally has remote traffic disabled.
I forget which YaST screens I had to walk through [sigh]
but the file /etc/sysconfig/syslog should have a line like:
SYSLOGD_PARAMS="-r"
> You were correct I entered the cmd you suggested and PSSQLID did not
> come back. The name from the list I am wanting is PS831P. I have entered
> the 3 part notation such "*.PS831P.* /var/log/pserv" and when I restart
> syslog, it doesn't like it. It seems to only want the 2 part like "*.*".
It appears to me that USS SYSLOGD does things a bit differently
from how they are done on Unix and Linux (unless NG approaches this).
The usual syntax for /etc/syslogd.conf is something like
facility.priority /var/log/somefile
facility.priority @remotehost
where either "facility" or "priority" can be wildcarded
and the white space between that and the filename MUST BE TABBED.
And, prefixing the filename with "@" tells SYSLOGD to send to
a host instead of to a file. In Unix (or Linux) the facility names
are hard coded when SYSLOGD is built (again, not knowing if NG
gets past this). Same for priorities.
Finally,
everyone should know that CMS/TSO Pipelines
makes a great SYSLOG source. Assuming your TSO Pipelines
is up to date (has working TCP* stages), the simplification is
PIPE something | UDP 514
where your "something" generates UDP packets.
This is trivial in REXX, even accounting for A/E charset issues.
-- R;
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
