The MICS CICS component (also IDMS and IMS) have a keen feature which can help sites categorize transactions as short, medium, long, etc., but also to help segregate outliers as "excessive" transactions. When the cccRLRT exit assigns TRANTYPE="X" then MICS sets aside that transactions "response" and "distribution count" measurement variables into a separate group, starting with "Excessive" Transaction execution (and others related, as well).
So, any MICS administrator who was not around when MICS was implemented/configured, it may be worthwhile to have a look at those install parameters, and in particular any component-level (unit database PARMS) relative longevity routine exit in component-level cccRLRT member.
As well, any sites with end-users who go after their own MICS reporting, it's also important not to keep them in the dark, by providing simple code examples, such as this one where excessive transactions are combined in with "normal" for the purposes of getting an overall response average, not one that avoids "skewing" due to frequent-type utility or long-running outlier transactions -- those that can skew down true internal response time as reported within MICS and those transactional components you have licensed. Have a look at Chapter 7 of your MICS component guide and the "RLRT" exit reference for more details.
Scott Barry
SBBWorks, Inc.
* use code below prior to any MICS summarization macro ;
* invocation to include excessive trans executions. ;
CSUTRANS = SUM(CSUTRANS,CSUETRN);
CSUETRN = 0;
CSUTRSTM = SUM(CSUTRSTM,CSUERSTM);
CSUERSTM = 0;