> That answer hasn't changed since SMF was originally shipped ... Except for the addition of IEFU84 and IEFU85, right?
Not to disagree at all with your fundamental points, of course. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of William Richardson Sent: Monday, December 02, 2013 8:42 AM To: [email protected] Subject: Re: IXGBRWSE - SMF Logstream Jose, The LOGGER provided SUBSYS DD interface (using IFASEXIT for "SMF" records) gives you direct access to the data in the logstream and is essentially a 'well-behaved logger' aplication that is doing the IXGCONN and IXGBRWSE (and dealing with the multiplicity of error codes) for you and giving you 'record' level access to the data via basic (old fashioned) QSAM or BSAM OPEN/GET/CLOSE level interfaces. IF you want to get close-to-real time access to the data in the logstream then you are correct that you have to build an application from the ground up using LOGGER IXG* services - the only "SMF" specific thing in the application is the data itself (and the format of the blocks). Which is back to your original point about the mapping of these BLOCKS. More to your actual point (I think) ....... IF you want REAL time access to the data being written to SMF (DASD or LOGSTREAM) you have to use the SMF provided SMF interface exits (IEFU83/4/5) to capture and process the data AS IT is passed to SMF to be written. That answer hasn't changed since SMF was originally shipped (but it was made a whole lot simpler with the implementation of 'Dynamic Exits' back in 1992). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
