By comparing MVIMS traces with related MVDB2 traces we find out that MVIMS (sometimes?) do NOT assign a db2 wait (like lock wait) to ESS category (instead MVIMS put this part of elapse time into APPL). This is true for many ims transactions - but not for all. In other cases we have a clear match: db2 wait is assigned in ESS-DB2. We see no pattern when this wrong assignment happens.
Does anyone of MVIMS user see this wrong mapping, too?