Re: IXGBRWSE - SMF Logstream
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of William Richardson Sent: Monday, December 02, 2013 8:42 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
Hi, Bill. Thank you for your answer. I think the better option (for my case) is the using IXGBRWSE, even with the format of the block not well resolved (I could be more confortable with this block mapped with a IBM macro). With the IXGBRWSE it is possible to require a specific date and time (TOD format) to beginning the browser (with the intrinsic risk and control). José ADAUTO Ribeiro De: William Richardson bi...@us.ibm.com Enviada: Segunda-feira, 2 de Dezembro de 2013 14:41 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: 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). Bill (former SMF Component owner) -- 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
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). Bill (former SMF Component owner) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
Hi, Thank you for your complement. Yes, it's getting better, however I would like to obtain the records as soon as possible and be active to reading the next one. I think it's possible only using IXGBRWSE. Am I correct ? José ADAUTO Ribeiro De: William Richardson bi...@us.ibm.com Enviada: Quarta-feira, 27 de Novembro de 2013 12:38 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: Re: IXGBRWSE - SMF Logstream Jose (and others dealing with this specific question); Quick update ... please use the 'Obtaining SMF data from Logstream' section in the SMF at the z/OS 2.1 level (it was drastically re-written and much improved at that level) Bill -- 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
Re: IXGBRWSE - SMF Logstream
Jose (and others dealing with this specific question); Quick update ... please use the 'Obtaining SMF data from Logstream' section in the SMF at the z/OS 2.1 level (it was drastically re-written and much improved at that level) Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
Jose, Please check out the section Obtaining records from SMF log streams in the 'SMF' manual to see how to do exactly what you are trying to do; specifically the part related to the 'IFASEXIT' interface provided by the LOGGER SUBSYS (which will de-block the records and present them to the application using standard QSAM/BSAM methods). NOTE: The section of the documentation referenced above is written and based on EREP's use of LOGGER but has the SMF details included. The logger 'block' that you are trying to deal with is just like a 'block' on a regular DASD dataset (can be thought of as). Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
Hi, I'll read carefully this section and do some tests. Thank you very much. José ADAUTO Ribeiro De: William Richardson bi...@us.ibm.com Enviada: Segunda-feira, 25 de Novembro de 2013 15:17 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: Re: IXGBRWSE - SMF Logstream Jose, Please check out the section Obtaining records from SMF log streams in the 'SMF' manual to see how to do exactly what you are trying to do; specifically the part related to the 'IFASEXIT' interface provided by the LOGGER SUBSYS (which will de-block the records and present them to the application using standard QSAM/BSAM methods). NOTE: The section of the documentation referenced above is written and based on EREP's use of LOGGER but has the SMF details included. The logger 'block' that you are trying to deal with is just like a 'block' on a regular DASD dataset (can be thought of as). Bill -- 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
Re: IXGBRWSE - SMF Logstream
Thank Peter and Nick Jones for your explanation. Only now I could answer. Thinking about compatibility: when the SMF is written on SMF files (MANx) it is possible to read, with a user program (in assembler, obviously), any records by user's criteria. Now, using SMF Logstream this will not be possible if IBM doesn't give us support with IXGBRWSE. I know installations which have this kind of access on SMF MANx files to get some informations as soon as possible. I think that has good services using this kind of facility. I think IXGBRWSE could be more flexible on z/OS 2.1 and give an option to the caller specifies a parameter about the compression or this uncompression could be another available standard service. José ADAUTO Ribeiro De: Peter Relson rel...@us.ibm.com Enviada: Segunda-feira, 18 de Novembro de 2013 16:14 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: Re: IXGBRWSE - SMF Logstream IXGBRWSE returns via the buffer keyword the exact area that the exploiter requested to be written to the logstream. Thus, it is that exploiter that knows the mapping. I conclude, by the fact that SMF apparently documents only the SMF record itself (and that an SMF record is only part of the logstream record), that ether - SMF does not want you to be reading these records and dealing with them on your own; or - it's an oversight; or - it was thought about but was not thought worthwhile. Is there a business need for reading the logstream that such a program as IFASMFDL does not accommodate? Peter Relson z/OS Core Technology Design -- 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
Re: IXGBRWSE - SMF Logstream
Hi Jose, We do not ship an official mapping macro for the SMF buffers returned by a log stream browse. The intended interface to get SMF records in log streams is IFASMFDL. You can however IXGBRWSE the log stream and see the buffers are returned in a consistent format, but this is of course not supported by IBM. In some cases the data returned by the log stream browse has to be manipulated by SMF before the user sees it, such as if zEDC compression is turned on in z/OS V2R1. -Nick Jones z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
Hi Nick I'm using the IXGBRWSE to browse the SMF logstream, I don't understand why it is unsupported , or that is the supported way to get the SMF log streams ? On 18.11.2013 13:20, Nick Jones wrote: Hi Jose, We do not ship an official mapping macro for the SMF buffers returned by a log stream browse. The intended interface to get SMF records in log streams is IFASMFDL. You can however IXGBRWSE the log stream and see the buffers are returned in a consistent format, but this is of course not supported by IBM. In some cases the data returned by the log stream browse has to be manipulated by SMF before the user sees it, such as if zEDC compression is turned on in z/OS V2R1. -Nick Jones z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Kind regards, / Mit freundlichen Grüßen Miklos Szigetvari Research Development ISIS Papyrus Europe AG Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria T: +43(2236) 27551 333, F: +43(2236)21081 E-mail: miklos.szigetv...@isis-papyrus.com Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111 Visit our brand new extended Website at www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS Papyrus accepts no responsibility for malicious or inappropriate content. --- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
IXGBRWSE returns via the buffer keyword the exact area that the exploiter requested to be written to the logstream. Thus, it is that exploiter that knows the mapping. I conclude, by the fact that SMF apparently documents only the SMF record itself (and that an SMF record is only part of the logstream record), that ether - SMF does not want you to be reading these records and dealing with them on your own; or - it's an oversight; or - it was thought about but was not thought worthwhile. Is there a business need for reading the logstream that such a program as IFASMFDL does not accommodate? Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
Hi, Charles. Thank you for your answer. I would like to complement my question: the IXGBRWSE macro with REQUEST=READCURSOR (or READBLOCK) returns in buffer area not only a record of SMF, but several of them, each one preceded by a block of information. The first two bytes at the beginning of the buffer contains the total size returned, followed by two bytes set to zero (at least in dumps which I analyzed). I wonder if there is a IBM macro that maps the area preceding the SMF record itself. Thank you, José ADAUTO Ribeiro De: Charles Mills charl...@mcn.org Enviada: Sábado, 16 de Novembro de 2013 22:19 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: Re: IXGBRWSE - SMF Logstream Just a guess -- is it supposed to be a vanilla SMF record, or is there some sort of prefix or wrapper on it? SMF records are mapped by -- well, most of them anyway -- IFASMFR. The macros, and many of the record types, are documented in z/OS MVS System Management Facilities (SMF). Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jose ADAUTO Ribeiro Sent: Saturday, November 16, 2013 9:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IXGBRWSE - SMF Logstream Hi, Please, could someone tell me wich macro maps the buffer returned at IXGBRWSE when reading a SMF Logstream with REQUEST=READCURSOR (or REQUEST=READBLOCK) and MULTIBLOCK=NO ? I could understand what was returned analyzing a dump, but I would like to have a mapping through the macro indicated by IBM. -- 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
Re: IXGBRWSE - SMF Logstream
Are you talking about IXGBRMLT? The doc for IXGBRWSE has it listed in the programming notes. Jon Perryman. From: Jose ADAUTO Ribeiro jada...@uol.com.br Thank you for your answer. I would like to complement my question: the IXGBRWSE macro with REQUEST=READCURSOR (or READBLOCK) returns in buffer area not only a record of SMF, but several of them, each one preceded by a block of information. The first two bytes at the beginning of the buffer contains the total size returned, followed by two bytes set to zero (at least in dumps which I analyzed). I wonder if there is a IBM macro that maps the area preceding the SMF record itself. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
On 11/17/2013 4:15 PM, Jose ADAUTO Ribeiro wrote: Hi, Charles. Thank you for your answer. I would like to complement my question: the IXGBRWSE macro with REQUEST=READCURSOR (or READBLOCK) returns in buffer area not only a record of SMF, but several of them, each one preceded by a block of information. The first two bytes at the beginning of the buffer contains the total size returned, followed by two bytes set to zero (at least in dumps which I analyzed). Normally an SMF record contains an SDW, followed by a record type and time stamp, followed by data. The standard mapping macros include these data. If you have an extra length field and zeroes, it may be a (pseudo) BDW. Several IBM services use a similar format (e.g., old IGGCSI00). If you have other data, it might help if you displayed them for us. Gerhard Postpischil Bradford, Vermont -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
Hi, IXGBRMLT maps only MULTIBLOCK=YES requests. I need MULTIBLOCK=NO. Thank you, José ADAUTO Ribeiro De: Jon Perryman jperr...@pacbell.net Enviada: Domingo, 17 de Novembro de 2013 20:02 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: Re: IXGBRWSE - SMF Logstream Are you talking about IXGBRMLT? The doc for IXGBRWSE has it listed in the programming notes. Jon Perryman. From: Jose ADAUTO Ribeiro jada...@uol.com.br Thank you for your answer. I would like to complement my question: the IXGBRWSE macro with REQUEST=READCURSOR (or READBLOCK) returns in buffer area not only a record of SMF, but several of them, each one preceded by a block of information. The first two bytes at the beginning of the buffer contains the total size returned, followed by two bytes set to zero (at least in dumps which I analyzed). I wonder if there is a IBM macro that maps the area preceding the SMF record itself. -- 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
Re: IXGBRWSE - SMF Logstream
Hi, Sorry, but I need to map the information that precede the SMF record on the block. I already use the IFASMFxx macro to map the SMF records. Thank you, José ADAUTO Ribeiro De: Gerhard Postpischil gerh...@valley.net Enviada: Domingo, 17 de Novembro de 2013 20:09 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: Re: IXGBRWSE - SMF Logstream On 11/17/2013 4:15 PM, Jose ADAUTO Ribeiro wrote: Hi, Charles. Thank you for your answer. I would like to complement my question: the IXGBRWSE macro with REQUEST=READCURSOR (or READBLOCK) returns in buffer area not only a record of SMF, but several of them, each one preceded by a block of information. The first two bytes at the beginning of the buffer contains the total size returned, followed by two bytes set to zero (at least in dumps which I analyzed). Normally an SMF record contains an SDW, followed by a record type and time stamp, followed by data. The standard mapping macros include these data. If you have an extra length field and zeroes, it may be a (pseudo) BDW. Several IBM services use a similar format (e.g., old IGGCSI00). If you have other data, it might help if you displayed them for us. Gerhard Postpischil Bradford, Vermont -- 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
IXGBRWSE - SMF Logstream
Hi, Please, could someone tell me wich macro maps the buffer returned at IXGBRWSE when reading a SMF Logstream with REQUEST=READCURSOR (or REQUEST=READBLOCK) and MULTIBLOCK=NO ? I could understand what was returned analyzing a dump, but I would like to have a mapping through the macro indicated by IBM. Thanks in advance. José ADAUTO Ribeiro -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IXGBRWSE - SMF Logstream
Just a guess -- is it supposed to be a vanilla SMF record, or is there some sort of prefix or wrapper on it? SMF records are mapped by -- well, most of them anyway -- IFASMFR. The macros, and many of the record types, are documented in z/OS MVS System Management Facilities (SMF). Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jose ADAUTO Ribeiro Sent: Saturday, November 16, 2013 9:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IXGBRWSE - SMF Logstream Hi, Please, could someone tell me wich macro maps the buffer returned at IXGBRWSE when reading a SMF Logstream with REQUEST=READCURSOR (or REQUEST=READBLOCK) and MULTIBLOCK=NO ? I could understand what was returned analyzing a dump, but I would like to have a mapping through the macro indicated by IBM. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
