Here's another example of a management by exception display. Monitoring IMS with the management by exception approach works well. Often when I'm monitoring an IMS system I'm looking for such things as workload that is queuing, and resources that have failed or stopped/abended altogether. The example I show here is a typical example of an IMS display I might create using OMEGAMON IMS and the TEP. In this example I show message regions over a certain percentage busy, transactions that have queued, and PSBs and databases that have stopped or are in a problem status. Just like with the other example, I'm focusing on potential problem scenarios, and tuning out the background 'noise'.