Re: SMF 119 records (TCPIP)
Someone at one time had put together a REXX program to process 119 records and produce reports. I used it at my last shop, however I do not remember who provided it. Regards, *Mark T. Regan, K8MTR* CTO1 USNR-Retired, 1969-1991 Nationwide Insurance, Retired, 1986-2017 On Tue, Mar 17, 2020 at 11:48 AM Pierre Fichaud wrote: > I do not have SAS. Pierre. > > -- > 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: SMF 119 records (TCPIP)
What documentation there is, is in SC27-3659 IP Programmer's Guide and Reference Appendix E. Anything more than that you will need to ask IBM/ HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pierre Fichaud Sent: Tuesday, March 17, 2020 8:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMF 119 records (TCPIP) [CAUTION: This Email is from outside the Organization. Do not click links or open attachments unless you trust the sender.] There are many sub-types for SMF 119 (X'77'). The common identification section has a flag byte called SMF119TI_Reason with the following values: X'C0' - Interval record, more records to follow X'80' - Interval record, last record in set X'60' - End of statistics record, more records to follow X'40' - End of statistics record, last record in set x'50' - Shutdown starts record, more record to follow x'10' - Shutdown starts record, last record in set X'48' - Events record, more records to follow x'08' - Events record, last record in set Is there a more detailed explanation of these values ? Can interval records be ignored if one takes the end of statistics records ? I guess shutdown starts records are cut when TCP/IP starts to shutdown ? When is an event record cut ? Can SMF119TI_RecordId be used to tie together different records of the same sub-type? Regards and TIA, Pierre. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF 119 records (TCPIP)
I do not have SAS. Pierre. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF 119 records (TCPIP)
I wrote a piece of software that processed *certain SMF 119 subtypes*. They were all "event" type records such as a TN3270 connection, a TN3270 disconnection, and so forth. For those purposes I was if I recall correctly able to utterly ignore this flag. Your mileage may vary. An event record is cut when the event occur. I am not familiar with shutdown subtypes. I don't mean they do not exist; just that I have not worked with them. "My" product was a realtime product; if you are interested in batch SMF reporting you might be much more interested in shutdown subtypes. I am familiar with SMF 30 interval records but not SMF 119 interval records. Again, not saying they do not exist, just that they were not of interest to me. I think a moral of the story is not to start from the contents of the flag byte but to start from "what subtypes -- what kinds of things -- am I interested in, does my code need to process?" Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pierre Fichaud Sent: Tuesday, March 17, 2020 6:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMF 119 records (TCPIP) There are many sub-types for SMF 119 (X'77'). The common identification section has a flag byte called SMF119TI_Reason with the following values: X'C0' - Interval record, more records to follow X'80' - Interval record, last record in set X'60' - End of statistics record, more records to follow X'40' - End of statistics record, last record in set x'50' - Shutdown starts record, more record to follow x'10' - Shutdown starts record, last record in set X'48' - Events record, more records to follow x'08' - Events record, last record in set Is there a more detailed explanation of these values ? Can interval records be ignored if one takes the end of statistics records ? I guess shutdown starts records are cut when TCP/IP starts to shutdown ? When is an event record cut ? Can SMF119TI_RecordId be used to tie together different records of the same sub-type? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF 119 records (TCPIP)
Do you have SAS? If so, look at MXG. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Pierre Fichaud Sent: Tuesday, March 17, 2020 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMF 119 records (TCPIP) There are many sub-types for SMF 119 (X'77'). The common identification section has a flag byte called SMF119TI_Reason with the following values: X'C0' - Interval record, more records to follow X'80' - Interval record, last record in set X'60' - End of statistics record, more records to follow X'40' - End of statistics record, last record in set x'50' - Shutdown starts record, more record to follow x'10' - Shutdown starts record, last record in set X'48' - Events record, more records to follow x'08' - Events record, last record in set Is there a more detailed explanation of these values ? Can interval records be ignored if one takes the end of statistics records ? I guess shutdown starts records are cut when TCP/IP starts to shutdown ? When is an event record cut ? Can SMF119TI_RecordId be used to tie together different records of the same sub-type? Regards and TIA, Pierre. -- 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
SMF 119 records (TCPIP)
There are many sub-types for SMF 119 (X'77'). The common identification section has a flag byte called SMF119TI_Reason with the following values: X'C0' - Interval record, more records to follow X'80' - Interval record, last record in set X'60' - End of statistics record, more records to follow X'40' - End of statistics record, last record in set x'50' - Shutdown starts record, more record to follow x'10' - Shutdown starts record, last record in set X'48' - Events record, more records to follow x'08' - Events record, last record in set Is there a more detailed explanation of these values ? Can interval records be ignored if one takes the end of statistics records ? I guess shutdown starts records are cut when TCP/IP starts to shutdown ? When is an event record cut ? Can SMF119TI_RecordId be used to tie together different records of the same sub-type? Regards and TIA, Pierre. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
