Exposing USS Messages to z/OS SYSLOG

[Jacky Bright]

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 list...@listserv.ua.edu with the message: INFO IBM-MAIN

[John McKown]

On Wed, Nov 5, 2014 at 7:51 AM, Jacky Bright <jacky....@gmail.com> wrote:

> 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
>
>

​I'm not familiar with WAS​. But there is a pseudo device called
/dev/console that is "write-only". Everything written to that device is
sent to the z/OS SYSLOG. As an example. on a z/OS UNIX shell, I entered the
command:

echo 'hello from john!' >/dev/console

And on the z/OS SYSLOG, there was the line:

N 4000000 LIH1 14309 07:56:14.38 STC44699 00000094 BPXF024I (RACFID)
hello from john!

​If WAS logs to a UNIX file, then specify /dev/console as the name of the
file. If WAS logs to the UNIX syslog daemon, then set the appropriate entry
in the /etc/syslog.conf to write to /dev/console.
​


--
The temperature of the aqueous content of an unremittingly ogled
culinary vessel will not achieve 100 degrees on the Celsius scale.

Maranatha! <><
John McKown

[Jousma, David]

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
david....@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717

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.

[Lizette Koehler]

Do you have OPS/MVS? Do you have OPS/MVS USS function? That may help.

If the STC JOB LOG sees the USS messages, then you should see them in SYSLOG. Check your SYSLOG Routing codes.

If the USS messages are in STDERR or STDOUT, then you may not be able to do this.


Lizette

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On
> Behalf Of Jacky Bright
> Sent: Wednesday, November 05, 2014 6:52 AM
> To: IBM-...@LISTSERV.UA.EDU
> Subject: Exposing USS Messages to z/OS SYSLOG
>

[Lizette Koehler]

Will that work for the WebSphere/MQ task that is writing to STDOUT? Can you tell the STC to redirect to SYSLOG this way?

Lizette

[Jousma, David]

Don’t know about that, but as John pointed out, you can make those special devices the destination like any other file.

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.

[Paul Gilmartin]

On Wed, 5 Nov 2014 07:02:25 -0700, Lizette Koehler wrote:

>Will that work for the WebSphere/MQ task that is writing to STDOUT? Can you tell the STC to redirect to SYSLOG this way?
>

exec 2>/dev/console
(or dup2( open( "/dev/console" ), 2 ); )
You could probably do it, but would you want to?

Some sites configure console automation to deflect BPXF024I.

-- gil

[Barkow, Eileen]

I can get /dev/console to work but not /dev/operlog.
Either get permission denied to /dev/operlog when not in su mode:
/dev/operlog CL(FSOBJ ) FID(00000000000000000000000300000009)
INSUFFICIENT AUTHORITY TO OPEN
ACCESS INTENT(-W-) ACCESS ALLOWED(OTHER ---)
EFFECTIVE UID(0420050912) EFFECTIVE GID(0420000000)

Or invalid argument when in su mode:

echo: FSUM7362 writing: EDC5121I Invalid argument.
# echo 'write to dev operlog'>/dev/operlog
echo: FSUM7362 writing: EDC5121I Invalid argument.
# exit
$ echo 'write to dev operlog'>/dev/operlog
FSUM7343 cannot open "/dev/operlog" for output: EDC5111I Permission denied.
$

What is the syntax to write to /dev/operlog ?

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin
Sent: Wednesday, November 05, 2014 9:28 AM
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Exposing USS Messages to z/OS SYSLOG

[Jousma, David]

The same, but looks like you don’t have access, you asked for write access, but were given none. /dev/operlog only works if you have operlog active too. I'd say /dev/console is probably what you want anyway.

_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Engineering
david....@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717

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.

[Pabitra Mukhopadhyay]

Hello Jacky,

Have you tried setting ras_message_routing_copy_console variable? It copies the WAS messages IDs to the operator console.

Thanks,
Pabitra

[Vernooij, CP - KLM , SPLXM]

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.

********************************************************
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
********************************************************

[Jousma, David]

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.

[Hank Oerlemans]

http://www-01.ibm.com/support/docview.wss?uid=swg1PM93967

refers to ras_message_routing_console and BBOO0221W

Perhaps this is of use to you ?

Hank