On Thu, Jun 11, 2015 at 1:01 PM, Carlos Cordero <jccorde...@hotmail.com> wrote:
> Both.. > I have some code with I can share which _might_ be of some help. But it may (most likely _will_) violate your shop's standards. Or cause your boss to say "no". The IBM IND$FILE function basically runs a TSO command from the READY prompt. The 3270 emulator "talks" with this command via the 3270 data stream, much like a "screen scraping" application. What my code does is "front end" the normal IBM code, and simply creates a WTO message to send to the z/OS SYSLOG. The WTO contains the TSO id and the TSO command, along with a S or E for "Start of transfer" and "End of transfer". This is sufficient to tell you who did the transfer and the name of the z/OS data set involved. It also, if it is APF authorized, makes the TSO session non-swappable. Another possibility is to set up RACF auditing on the IND$FILE command, but that (in and of itself) will not tell you the name of the DSN involved. > > > Thanks > > -- Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. My sister opened a computer store in Hawaii. She sells C shells down by the seashore. If someone tell you that nothing is impossible: Ask him to dribble a football. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
