I was just issuing the command: D tcpip,tn3270,t,conn,max=* In order to list all tn3270 connections and capture it in the rexx. It was captured in the rexx but it was also written to the system log. Output was around 8,000 lines. That’s why I wanted to avoid writing to system log.
Politics: Poli (many) - tics (blood sucking parasites) On Tue, May 21, 2024 at 1:48 PM Paul Gilmartin < 0000042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 21 May 2024 12:24:14 -0500, Tom Marchant wrote: > > >I certainly hope not. The system log is supposed to be a log of things > done to the system. > > > I'd hardly regard DISPLAY, for example, as "things done to". If there's a > security concern, the command should be rejected, not executed and logged. > > But what was the OP trying to do, and what alternatives exist? > > > >On Tue, 21 May 2024 13:19:03 -0400, Roberto Halais wrote: > > > >>I have a rexx that issues console commands thru ISFEXEC. Is there a way > to > >>prevent the command output to not appear in the system syslog. > >>I capture the output in my rexx but it also appears in the system log. > > > -- > gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
