Kees,
Its working on my 1.13 system. Not sure if you just had a typo with
/dev/syslog. Its /dev/console or /dev/operlog for operlog you have to add 1
byte to the front of the message though:
The following are system console files:
/dev/console (major 9, minor 0). Data written to the /dev/console file is sent
to the console and is displayed in message BPXF024I by means of a
write-to-operator function. This message also contains the user ID of the
process that wrote to the console. It is automatically created the first time
the system is IPLed and is created with minor number 0.
/dev/operlog (major 9, minor 1). This device file is intended for the syslog
daemon. Data written to the /dev/operlog file is sent directly to the sysplex
message log, OPERLOG, which must be active, and is displayed in message
BPXF060I. For each write operation to /dev/operlog, the first character is
removed from the message and used as a message indicator code with the
following values:
'00'x
The message originated on a remote system.
'80'x
The message originated on the local system.
Improperly-formatted messages written to /dev/operlog will result in an error
return code with EINVAL as the errno.
Using /dev/operlog is a quick way of logging messages.
Command ===>
****** ************************
000001 Øthis is a test
8A88A48A484A8AA444444444
038920920103523000000000
-------------------------------
Cp test /dev/operlog
Results in
STC28666 00000280 BPXF060I LOGGED BY SYSLOGD FROM A LOCAL SOURCE 000
000 00000280 this is a test
Cp test /dev/console
Results in
14310 07:17:28.72 STC28666 00000000 BPXF024I (userid) this is a test
I actually think you get more information from /dev/console as you get the
userid writing the message too, with /dev/operlog you do not.
_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Engineering
[email protected]
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H
p 616.653.8429
f 616.653.2717
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Vernooij, CP (SPLXM) - KLM
Sent: Thursday, November 06, 2014 2:11 AM
To: [email protected]
Subject: Re: Exposing USS Messages to z/OS SYSLOG
Dave,
We can get /dev/operlog working, is the new in 2.1?
/dev/syslog seems to be accepted, but does not go to syslog. Is this a valid
device?
Kees.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Jousma, David
Sent: 05 November, 2014 14:59
To: [email protected]
Subject: Re: Exposing USS Messages to z/OS SYSLOG
Not exactly sure, but check out the manual for syslog.conf there are specific
special files called /dev/operlog and /dev/console
_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Engineering [email protected]
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Jacky Bright
Sent: Wednesday, November 05, 2014 8:52 AM
To: [email protected]
Subject: Exposing USS Messages to z/OS SYSLOG
I have requirement of exposing Mainframe USS messages appearing in WAS Started
tasks on z/OS (For eg. BBOO0221W ) to Mainframe SYSLOG.
Is there any way to achieve this ?
JAcky
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
********************************************************
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
