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 [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 Barkow, Eileen Sent: Wednesday, November 05, 2014 9:35 AM To: [email protected] Subject: Re: Exposing USS Messages to z/OS SYSLOG 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:[email protected]] On Behalf Of Paul Gilmartin Sent: Wednesday, November 05, 2014 9:28 AM To: [email protected] Subject: Re: Exposing USS Messages to z/OS SYSLOG 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- 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
