It is possible for two DPARs to show roughly the same transaction counts, but have very different CPU usage because there are different transactions being driven on each DPAR.

When enough workload is driven to stress the system to the configured CPU threshold and cause resource contention between transaction classes, then service policies will be breached.

For application where plain JCR code is required, the JCR module allows the transparent use of a transaction driven session with code that USES the JCR API directly.