Re: SMF Interval
Hi all, Yes, 30 minutes was my recommendation for safety. But if it were my shop, I would use 15 minutes, but not 5. Here’s my reasoning. My recommendations go out to people who are experienced and those who are newbies. When SMF writes its records, it’s one of the highest priority tasks. If there are too many records to write, it could tie up other tasks needing to free locks, etc. So using 30 minutes reduces those exposures. But as several people mentioned, most of the peaks are hidden during 30-minute periods. So I would use 15 and make sure that nothing gets locked out during syncing. The reason I wouldn’t use 5 minutes is the same reason. I’ve seen too many times with a sync of 5 minutes where there is work that is blocked. My technique is to use an external monitor or RMF Monitor III at 1 minute intervals. The overhead is really minimal. We have been busy the past few years on CMP, pricing, and new SW/HW, so the latest info I have on SMF parameters was in 2015 in a SHARE presentation. You can see that at https://watsonwalker.s3.us-west-1.amazonaws.com/ww/wp-content/uploads/2016/01/28151211/PR150812a.pdf. Alternatively, you can go to https://watsonwalker.com/publications/presentations/ and scan down to 2015. Cheers, Cheryl On Dec 29, 2023, at 6:20 PM, Mark Zelden wrote: On Fri, 29 Dec 2023 13:57:35 -0600, Mark Zelden mailto:m...@mzelden.com>> wrote: > On Thu, 28 Dec 2023 21:23:18 -0800, Ed Jaffe > wrote: > >> What SMF interval do most folks use? >> > > In my experience (from many shops / clients over the years), it matches the > RMF interval > and the most common if 15 minutes. Second most common is probably 30 (along > with > RMF) but I think most shops moved away from that to go to at least 15 years > ago. I have > seen some use 5 minutes and sometimes IBM will request that for a period of > time - perhaps > for a week to get a more accurate picture for a CP3000 study. > > This is typically what I use in SMFPRMxx: > > INTVAL(15) > SYNCVAL(59) > You didn't way why you wanted to know. But thinking about this more... I though i remembered Cheryl Watson doing a poll on this once. I searched her website and saw in 2008 there was a 3 part series on SMF / parms and she asked people to send in their parms, but I didn't see a follow up on the results. She did recommend setting INTVAL(30) and said using SYNCVAL(59) was no longer required and to use SYNCVAL(0). I won't go into the history for why people started coded SYNVCAL(59) to begin with (she does). Maybe someone on team Cheryl does have poll results from back then or more recently. However she also recommended changing RMF invterval from 15 to 30 to match SMF INTVAL (she previously suggested using RMF interval of 15, SMF INTVAL(30). Partially due to the number of SMF/RMF Type 74 records from DASD activity from the size of systems at the time. That to me makes no sense because even though there is more RMF data to store and process, the CPUs are much faster, the disk & I/O is much faster and storage is "cheaper", so it's all relative. I know I'm talking RMF interval now as opposed to your question on SMF INTVAL, but 30 minutes is just not granular enough in the large installations I have worked in. Be it for typical performance report & capacity planning or looking at WLM reports (although I use RMF III or Mainview CMF more for WLM tuning that post processing). Even in small environments I have always used 15 for both SMF and RMF/CMF. Back to your question: While I have mostly seen 15 minutes to match RMF / CMF 15 minutes, in my personal experiences, 30 minutes is the default and lot of people listen to Cheryl's advise (because it is good), so without any scientific polling, I'm sure that it is still very common to see INTVAL(30).I just don't agree and have never used anything higher than 15. This paper from Scott Chapman of EPS talks about the subject and he agrees with me that it should be no longer than 15 minutes and that RMF/SMF should be synced. https://www.pivotor.com/library/content/Chapman_SMFRecommendations_2022.pdf Best Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Cheryl Watson == Cheryl Watson Walker, CEO Watson & Walker, Inc. Sarasota, FL USA www.watsonwalker.com Cell/Text: 941-266-6609 == -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Interval
Hi Steve, JWT too low would cause 522s, not 322s. Regards, David On 2023-12-29 16:51, Steve Beaver wrote: Sorry my bad. I was the thinking about JWT Sent from my iPhone No one said I could type with one thumb On Dec 29, 2023, at 15:49, Steve Beaver wrote: Be careful setting in low. If TSO is On that system you will have a lot S322’s Sent from my iPhone No one said I could type with one thumb On Dec 29, 2023, at 15:05, Ed Jaffe wrote: On 12/29/2023 1:46 AM, Colin Paice wrote: With MQ some customers would set the interval to one minute for a period to get granular statistics and accounting to help with problem determination. The MQ accounting would report maximum response time for the interval. If you have a "spiky" problem, being able to identify the minute it occurred in, was very useful, and being able to correlate to other events. Note: This can produce a lot of data! This sounds like something that would be done temporarily. No? After that, they go back to "normal" and set it to: __ ? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Interval (and zCP3000)
I do some zCP3000 work too, and to avoid the transfer of large amounts of SMF data, I ask the client to run the CP3KEXTR extract program which (as you know) takes only what is needed for zCP3000 and creates reasonably sized text files that can generally be emailed. CP3KEXTR has an option to set its own interval, and for example, if SMF is set to 15 and the extract is set to 30, it looks like it averages SMF data and the resulting graphs are more "rounded" which of course I don't want. So I ask the user to set the extract number to 15, which so far with various clients, has matched their SMF interval. Check out the peaks in this sample of the same 15 minute SMF data extracted with 30 and then 15: https://www.mildredbrennan.com/mvs/extract30.png https://www.mildredbrennan.com/mvs/extract15.png If you happen to know, what happens if you start with 30 minute SMF data but specify 15 in the extract program? Does it complain or just spit out 30 minute results? On 12/30/2023 3:17 AM, Jim Elliott wrote: I do a lot of zCP3000 studies and most customers sending me data seem to be using a 15 minute interval. I have a couple using 30 minutes (and one 20 minutes), but I prefer 15 minutes for my studies. Regards, Jim -- 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 Interval
Yeah, the stuff I said there, plus... we see data from a lot of systems. Periodically I sample that data for interesting values, including what the SMF interval is. Historically that has been 15 minutes for right around 90% of the systems we see. Next most popular is 30 minutes in about 5% of the customers, although I actively discourage that when I see it. A few will show up with 5 or 10 minute intervals. And some customers will run with 1 minute intervals for all or part of the day. It should be noted that on the creation side, the interval only drives the data storage required and the tiny bit of CPU/IO required to write those records. But of course when you go to process the data, having more intervals will mean that processing the data will take longer and consume more resources. That's usually the bigger concern. Opinion: In general, if I was running a system today, I'd probably use 5 minutes. Yes, it's 3x the data (vs 15 minutes), but for most systems that shouldn't really be a problem. And it may better align with your non-mainframe platforms. The 1 minute intervals are I think overkill, especially given the data you can get out of the SMF records that have shorter (sub-minute) intervals like the 99s and 98s. When you have 1 minute SMF intervals, you can generate a whole lot of SMF 30 interval records. And if you carry that forward to RMF/CMF, the 74s can get quite voluminous. I'm not saying 1 minute intervals are never useful, but that's a rather exceptional condition. Day-in, day-out most customers manage their systems just fine with 15 minute intervals, diving down to event or shorter interval records (like the 99s) as needed. Because everything has exceptions... one exception to my above thinking might be for certain customers with extreme spikes for important events. I believe I once saw a financial services customer that set a 1 minute interval for a few minutes around market open/close. That makes sense to me. The "we needed 1 minute intervals for a particular problem we had several years ago and just left it set to that" makes much less sense to me. Scott Chapman On Fri, 29 Dec 2023 17:35:56 -0800, Ed Jaffe wrote: >On 12/29/2023 3:20 PM, Mark Zelden wrote: >> This paper from Scott Chapman of EPS talks about the subject and he agrees >> with >> me that it should be no longer than 15 minutes and that RMF/SMF should be >> synced. >> >> https://www.pivotor.com/library/content/Chapman_SMFRecommendations_2022.pdf > >Super helpful. Thanks, Mark! > >-- >Phoenix Software International >Edward E. Jaffe >831 Parkview Drive North >El Segundo, CA 90245 >https://www.phoenixsoftware.com/ > > > >This e-mail message, including any attachments, appended messages and the >information contained therein, is for the sole use of the intended >recipient(s). If you are not an intended recipient or have otherwise >received this email message in error, any use, dissemination, distribution, >review, storage or copying of this e-mail message and the information >contained therein is strictly prohibited. If you are not an intended >recipient, please contact the sender by reply e-mail and destroy all copies >of this email message and do not otherwise utilize or retain this email >message or any or all of the information contained therein. Although this >email message and any attachments or appended messages are believed to be >free of any virus or other defect that might affect any computer system into >which it is received and opened, it is the responsibility of the recipient >to ensure that it is virus free and no responsibility is accepted by the >sender for any loss or damage arising in any way from its opening or use. > >-- >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 Interval
I do a lot of zCP3000 studies and most customers sending me data seem to be using a 15 minute interval. I have a couple using 30 minutes (and one 20 minutes), but I prefer 15 minutes for my studies. Regards, Jim -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Interval
With the MQ people - it ranged from 10 minutes up to 1 hour. The default is 30 mins MQ 9.3.0 has enhanced its stats and accounting to provide granularity at .ss - down to the seconds level. See https://www.ibm.com/docs/en/ibm-mq/9.3?topic=module-using-csq6sysp#q019300___acctime For example a short lived CICS transaction will run and produce an accounting record -this takes perhaps 50 ms. A long running transaction might produce an accounting record every 30 minutes (or at end of task, whichever came first), by specifying an accounting interval of 1 second, they get the same order of magnitude duration. This granularity was in response to customer demand! Also some customers would arrange the interval to be on the hour for z/OS, 2 mins past the hour for DB2, 4 mins past the hour for MQ etc. because if they were all on the hour, SMF to data sets could not keep up! Using SMF to a CF stream, and splitting by smf record type solved that problem Colin On Fri, 29 Dec 2023 at 21:06, Ed Jaffe wrote: > On 12/29/2023 1:46 AM, Colin Paice wrote: > > With MQ some customers would set the interval to one minute for a period > to > > get granular statistics and accounting to help with problem > determination. > > The MQ accounting would report maximum response time for the interval. > If > > you have a "spiky" problem, being able to identify the minute it > occurred > > in, was very useful, and being able to correlate to other events. > > Note: This can produce a lot of data! > > This sounds like something that would be done temporarily. No? > > After that, they go back to "normal" and set it to: __ ? > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system > into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > 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 Interval
Our site used 6 minutes. On Fri, Dec 29, 2023 at 7:36 PM Ed Jaffe wrote: > On 12/29/2023 3:20 PM, Mark Zelden wrote: > > This paper from Scott Chapman of EPS talks about the subject and he > agrees with > > me that it should be no longer than 15 minutes and that RMF/SMF should > be synced. > > > > > https://www.pivotor.com/library/content/Chapman_SMFRecommendations_2022.pdf > > Super helpful. Thanks, Mark! > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system > into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Interval
Perhaps using RMF III VSAM data stores with a 60 second sampling interval would be a better a better approach. Michael At 03:46 AM 12/29/2023, Colin Paice wrote: With MQ some customers would set the interval to one minute for a period to get granular statistics and accounting to help with problem determination. The MQ accounting would report maximum response time for the interval. If you have a "spiky" problem, being able to identify the minute it occurred in, was very useful, and being able to correlate to other events. Note: This can produce a lot of data! On Fri, 29 Dec 2023 at 05:23, Ed Jaffe wrote: > What SMF interval do most folks use? > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system > into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Interval
On 12/29/2023 3:20 PM, Mark Zelden wrote: This paper from Scott Chapman of EPS talks about the subject and he agrees with me that it should be no longer than 15 minutes and that RMF/SMF should be synced. https://www.pivotor.com/library/content/Chapman_SMFRecommendations_2022.pdf Super helpful. Thanks, Mark! -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Interval
On Fri, 29 Dec 2023 13:57:35 -0600, Mark Zelden wrote: >On Thu, 28 Dec 2023 21:23:18 -0800, Ed Jaffe >wrote: > >>What SMF interval do most folks use? >> > >In my experience (from many shops / clients over the years), it matches the >RMF interval >and the most common if 15 minutes. Second most common is probably 30 (along >with >RMF) but I think most shops moved away from that to go to at least 15 years >ago. I have >seen some use 5 minutes and sometimes IBM will request that for a period of >time - perhaps >for a week to get a more accurate picture for a CP3000 study. > >This is typically what I use in SMFPRMxx: > >INTVAL(15) >SYNCVAL(59) > You didn't way why you wanted to know. But thinking about this more... I though i remembered Cheryl Watson doing a poll on this once. I searched her website and saw in 2008 there was a 3 part series on SMF / parms and she asked people to send in their parms, but I didn't see a follow up on the results. She did recommend setting INTVAL(30) and said using SYNCVAL(59) was no longer required and to use SYNCVAL(0). I won't go into the history for why people started coded SYNVCAL(59) to begin with (she does). Maybe someone on team Cheryl does have poll results from back then or more recently. However she also recommended changing RMF invterval from 15 to 30 to match SMF INTVAL (she previously suggested using RMF interval of 15, SMF INTVAL(30). Partially due to the number of SMF/RMF Type 74 records from DASD activity from the size of systems at the time. That to me makes no sense because even though there is more RMF data to store and process, the CPUs are much faster, the disk & I/O is much faster and storage is "cheaper", so it's all relative. I know I'm talking RMF interval now as opposed to your question on SMF INTVAL, but 30 minutes is just not granular enough in the large installations I have worked in. Be it for typical performance report & capacity planning or looking at WLM reports (although I use RMF III or Mainview CMF more for WLM tuning that post processing). Even in small environments I have always used 15 for both SMF and RMF/CMF. Back to your question: While I have mostly seen 15 minutes to match RMF / CMF 15 minutes, in my personal experiences, 30 minutes is the default and lot of people listen to Cheryl's advise (because it is good), so without any scientific polling, I'm sure that it is still very common to see INTVAL(30).I just don't agree and have never used anything higher than 15. This paper from Scott Chapman of EPS talks about the subject and he agrees with me that it should be no longer than 15 minutes and that RMF/SMF should be synced. https://www.pivotor.com/library/content/Chapman_SMFRecommendations_2022.pdf Best Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Interval
Sorry my bad. I was the thinking about JWT Sent from my iPhone No one said I could type with one thumb > On Dec 29, 2023, at 15:49, Steve Beaver wrote: > > Be careful setting in low. If TSO is > On that system you will have a lot > S322’s > > Sent from my iPhone > > No one said I could type with one thumb > >>> On Dec 29, 2023, at 15:05, Ed Jaffe wrote: >>> >>> On 12/29/2023 1:46 AM, Colin Paice wrote: >>> With MQ some customers would set the interval to one minute for a period to >>> get granular statistics and accounting to help with problem determination. >>> The MQ accounting would report maximum response time for the interval. If >>> you have a "spiky" problem, being able to identify the minute it occurred >>> in, was very useful, and being able to correlate to other events. >>> Note: This can produce a lot of data! >> >> This sounds like something that would be done temporarily. No? >> >> After that, they go back to "normal" and set it to: __ ? >> >> -- >> Phoenix Software International >> Edward E. Jaffe >> 831 Parkview Drive North >> El Segundo, CA 90245 >> https://www.phoenixsoftware.com/ >> >> >> >> This e-mail message, including any attachments, appended messages and the >> information contained therein, is for the sole use of the intended >> recipient(s). If you are not an intended recipient or have otherwise >> received this email message in error, any use, dissemination, distribution, >> review, storage or copying of this e-mail message and the information >> contained therein is strictly prohibited. If you are not an intended >> recipient, please contact the sender by reply e-mail and destroy all copies >> of this email message and do not otherwise utilize or retain this email >> message or any or all of the information contained therein. Although this >> email message and any attachments or appended messages are believed to be >> free of any virus or other defect that might affect any computer system into >> which it is received and opened, it is the responsibility of the recipient >> to ensure that it is virus free and no responsibility is accepted by the >> sender for any loss or damage arising in any way from its opening or use. >> >> -- >> 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 Interval
Be careful setting in low. If TSO is On that system you will have a lot S322’s Sent from my iPhone No one said I could type with one thumb > On Dec 29, 2023, at 15:05, Ed Jaffe wrote: > > On 12/29/2023 1:46 AM, Colin Paice wrote: >> With MQ some customers would set the interval to one minute for a period to >> get granular statistics and accounting to help with problem determination. >> The MQ accounting would report maximum response time for the interval. If >> you have a "spiky" problem, being able to identify the minute it occurred >> in, was very useful, and being able to correlate to other events. >> Note: This can produce a lot of data! > > This sounds like something that would be done temporarily. No? > > After that, they go back to "normal" and set it to: __ ? > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > 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 Interval
On 12/29/2023 1:46 AM, Colin Paice wrote: With MQ some customers would set the interval to one minute for a period to get granular statistics and accounting to help with problem determination. The MQ accounting would report maximum response time for the interval. If you have a "spiky" problem, being able to identify the minute it occurred in, was very useful, and being able to correlate to other events. Note: This can produce a lot of data! This sounds like something that would be done temporarily. No? After that, they go back to "normal" and set it to: __ ? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Interval
On Thu, 28 Dec 2023 21:23:18 -0800, Ed Jaffe wrote: >What SMF interval do most folks use? > In my experience (from many shops / clients over the years), it matches the RMF interval and the most common if 15 minutes. Second most common is probably 30 (along with RMF) but I think most shops moved away from that to go to at least 15 years ago. I have seen some use 5 minutes and sometimes IBM will request that for a period of time - perhaps for a week to get a more accurate picture for a CP3000 study. This is typically what I use in SMFPRMxx: INTVAL(15) SYNCVAL(59) Best Regards and Happy New Year! Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Interval
Ed, in my experience 15 minutes for the most. I've seen 10 minutes too. IMHO big SMF DATA producers are DB2, CICS, IMS, MQ etc. with their accounting records that are not SMF Interval related. Choosing a maximum of 15 minutes may be better to correlate issues. Best regards. Max Il giorno ven 29 dic 2023 alle ore 06:23 Ed Jaffe < edja...@phoenixsoftware.com> ha scritto: > What SMF interval do most folks use? > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system > into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > 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 Interval
With MQ some customers would set the interval to one minute for a period to get granular statistics and accounting to help with problem determination. The MQ accounting would report maximum response time for the interval. If you have a "spiky" problem, being able to identify the minute it occurred in, was very useful, and being able to correlate to other events. Note: This can produce a lot of data! On Fri, 29 Dec 2023 at 05:23, Ed Jaffe wrote: > What SMF interval do most folks use? > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system > into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > 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 Interval
Ed, The most common I have seen is 30 minutes. 15 minutes is also not rare. Mike On Fri, 29 Dec 2023 at 07:23, Ed Jaffe wrote: > What SMF interval do most folks use? > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system > into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Mike Shorkend m...@shorkend.com Tel: +972524208743 <https://www.linkedin.com/in/MikeShorkend/> <https://twitter.com/mikeShorkend> -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SMF Interval
What SMF interval do most folks use? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
