> a couple of customers who had tested in a POC, didn´t liked the installation schema
Please contact me offline. We have nearly a 100% success rate with POC's. I know of no customers who "didn't like the installation schema." Every single POC we have installed in Mexico has either been successful or is still in progress. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Carlos Cordero Sent: Monday, November 09, 2015 3:46 PM To: [email protected] Subject: Re: SMF type 119 to catch TN3270 Yes, I mean the DS names referenced by the user during the TSO telnet transmisión. Currently the FTP messages are handled by recording SMF 119 subtype 70, included the DS name and member. The case of IND$FILE (protected in RACF by program class) the current scope for recording events in transmissions reaches only the RACF messages audit/alert in "insufficiente access auth" message and that is the only event where the resource name appears; but, local and remote IP are missing, also the DS name in the cases of "allowed" permissions on specifics resources. I'm trying to search for the local/remote IP in other way for IND$FILE transmissions. I've heard about correlog tool, a couple of customers who had tested in a POC, didn´t liked the installation schema. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
