Perhaps I remembered the logic incorrectly, or perhaps it has changed. If the command does its own access the the broadcast of user log data set, that makes an audit even more difficult.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Tony Harminc [[email protected]] Sent: Sunday, February 6, 2022 2:11 PM To: [email protected] Subject: Re: Is there a TSO SEND history anywhere? On Sun, 6 Feb 2022 at 10:17, Seymour J Metz <[email protected]> wrote: > > No. There are several scenarios, as I noted on Friday, February 4, 2022 12:15 > PM, and that CLIST doesn't help for any of them. You could use a GTF trace > and look at the parameters for MGCR, TPUT and WTO. The only logging that the > system does for any of the scenario is logging the SEND operator command (not > the SEND TSO command) to syslog, and that does not involve a temporary > dataset. I don't see the SEND operator command (and hence MGCR) anywhere in the scenario. The TSO SEND command itself does all the dealing with Broadcast, as I remember. Tony H. ---------------------------------------------------------------------- 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
