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 mmmm.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 <edja...@phoenixsoftware.com> 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
